You can move from Visual Studio Code to VSCodium without rebuilding your setup by installing VSCodium first, then either copying the documented user and extension folders or using the third-party Sync Settings workflow. Manual copying gives you the most control; Sync Settings is convenient when you already use a repository-backed configuration. Neither method can make an unavailable, license-restricted, or incompatible extension work.
The commands and paths below follow VSCodium’s current project documentation. Installation pages are rolling documents, so check the VSCodium repository and installation instructions for changes affecting your operating system before running a package-manager command.
As an Amazon Associate I earn from qualifying purchases.
What moves from VS Code to VSCodium
VSCodium keeps its own user-data and extension locations instead of silently reusing Visual Studio Code’s profile. A migration therefore has two parts:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Your editor configuration, including
settings.jsonandkeybindings.json, copied from the VS Code user directory to the matching VSCodium user directory. - Your installed extension packages, copied from VS Code’s extension directory to VSCodium’s
~/.vscode-oss/extensionsdirectory.
VSCodium uses Open VSX as its preset extension gallery. A copied extension may still fail to activate if it expects Visual Studio Code-specific services, APIs, or licensing terms. Treat the file copy as a transfer of packages, not a compatibility guarantee.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
There are also settings that belong to a project rather than to your global profile. A project’s .vscode folder travels with the project, while the user folders in this guide hold editor-wide preferences and shortcuts. If a project behaves differently after the migration, inspect both the global profile and that project’s workspace files.
Install VSCodium on your operating system
macOS with Homebrew
For the stable macOS build, open Terminal and run:
brew install --cask vscodiumThe VSCodium project also lists an Insiders cask. Use the repository’s current instructions if you specifically need that channel, because package names and release practices can change. Stable and Insiders are separate choices: install Insiders only when you deliberately want pre-release changes and are prepared to verify your extensions again.
After Homebrew finishes, launch VSCodium once from Applications or Spotlight and then quit it. That first launch lets the application create its normal user and extension directories before you copy anything.
Windows with WinGet
Open Windows Terminal or PowerShell and run the stable package command documented by VSCodium:
winget install -e --id VSCodium.VSCodiumAccept any WinGet prompts, then start VSCodium from the Start menu. An Insiders package is also listed by the project; select that only when you intentionally want pre-release builds. Launch the installed editor once, close it completely, and only then begin the migration.
WinGet may ask you to accept source or package agreements. Read the prompt and confirm that the package identifier is VSCodium.VSCodium before proceeding. If your organization manages software installation, follow its approval process instead of forcing a user-level install.
Linux and other platforms
Use the installation and release instructions in the VSCodium repository for Linux and any platform not covered by the two commands above. Do not assume that the macOS Homebrew or Windows WinGet command applies to a Linux distribution, container, or manually downloaded build. Choose the package format and repository appropriate to your distribution, then launch VSCodium once before migrating so it creates its destination directories.
On Linux, the documented profile locations use your home directory and are independent of whether you installed a package, archive, or another supported build. If you switch between operating-system accounts, containers, or remote environments, perform the copy in the same account and environment that will run VSCodium. A successful copy in one home directory will not automatically appear in another.
Decide which migration method fits
Manual copying is the straightforward choice for a one-time move. It uses the documented paths, lets you select exactly which files and extension folders to transfer, and does not require a repository or another extension. It is also easier to audit: you can compare the destination with the source and restore the backup if anything looks wrong.
Sync Settings is better suited to a setup that you already keep in a repository or intend to reuse across installations. It still requires preparation in both editors, a configured repository, and a final download into VSCodium. It is not a magic import button and does not bypass Open VSX availability, licensing, or build-compatibility limits.
Whichever method you choose, keep VS Code installed and leave its original profile untouched until you have opened a representative project in VSCodium and confirmed that your essential tools work.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteRank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Prepare for a safe migration
Close both editors
Quit VS Code and VSCodium before copying files. Running editors can overwrite a file after you replace it, leaving you with a partial migration or a configuration that appears to disappear on the next launch.
Check for background windows as well as the main window. On some desktops an editor can remain available from a dock, taskbar, or menu-bar icon after its visible window is closed. End that session before replacing profile files.
Back up VSCodium’s existing profile
If you have already opened VSCodium, preserve its current user directory before replacing files. Copy the entire VSCodium User folder to a dated backup location, or at minimum duplicate the files you plan to replace. This gives you a rollback if a setting, keybinding, or extension behaves unexpectedly.
Do not overwrite your only copy of the VS Code profile. The source remains useful for comparison, and it is the easiest way to recover if you later decide to return to VS Code.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check disk access
Use the same operating-system account that runs the editor. If the destination is owned by another account or protected by file permissions, the copy can appear successful while VSCodium cannot read or update the files.
Make sure there is enough free space for the extension directory. Copying does not remove the original packages, so the migration temporarily requires room for both profiles. If you use a removable or network-backed home directory, wait for the file operation to finish before launching VSCodium.
Manual migration: copy settings and keybindings
VSCodium’s migration documentation identifies these source and destination user directories:
| Platform | VS Code user directory | VSCodium user directory |
|---|---|---|
| Windows | %APPDATA%CodeUser |
%APPDATA%VSCodiumUser |
| macOS | $HOME/Library/Application Support/Code/User |
$HOME/Library/Application Support/VSCodium/User |
| Linux | $HOME/.config/Code/User |
$HOME/.config/VSCodium/User |
Step 1: open the two profile folders
- Open the VS Code user directory for your platform from the table.
- Open the equivalent VSCodium user directory in a second file-manager window.
- If VSCodium has never created the destination folder, start it once and close it, then check again. Create only missing folders that the documented path requires.
On Windows, %APPDATA% expands to the roaming application-data folder for the signed-in account. Paste the path into File Explorer’s address bar rather than searching for a similarly named folder. On macOS, spaces in Application Support are part of the directory name. On Linux, show hidden folders if your file manager hides names beginning with a period.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStep 2: copy the configuration files
Copy settings.json and keybindings.json from the VS Code User folder into the VSCodium User folder. Copy rather than move, so the original VS Code profile remains usable. If a destination file already exists, keep the backup you made and then replace the destination with the VS Code copy.
The migration guide calls out those two files specifically. If you have additional user-level files that you deliberately maintain, inspect them individually instead of blindly overwriting the whole destination folder; editor-specific state can contain paths or services that do not apply to VSCodium.
Copying the files preserves their names and extensions exactly. Do not let a file manager rename a duplicate to something such as settings (1).json, and do not save a JSON file as plain text with an extra .txt suffix. If you use a text editor to inspect a file, avoid changing its contents unless you know why.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Step 3: account for workspace settings
Settings stored inside a project’s .vscode directory are separate from the user profile. They remain with the project and do not need to be copied through the user-folder procedure. Reopen a representative project in VSCodium and check its workspace settings if behavior differs from your global profile.
Free tools Windows power users keep installed
One-click scans. No signup required.
A project can intentionally override a global setting, so test both a familiar project and a new empty folder. This distinguishes a profile migration problem from a workspace-specific configuration.
Manual migration: copy extensions
VSCodium documents its extension storage as ~/.vscode-oss. The corresponding VS Code directory is ~/.vscode/extensions. With both editors closed, copy the contents of the VS Code directory into VSCodium’s extension directory:
- Open your home directory and locate
.vscode/extensions. Hidden files may need to be shown in your file manager. - Open or create
.vscode-oss/extensionsin the same home directory. - Copy the extension folders from
~/.vscode/extensionsinto~/.vscode-oss/extensions. Copy the contents, not an extra nestedextensionsfolder. - Start VSCodium and wait while it scans the transferred packages. Open the Extensions view and inspect warnings before opening a project.
On Windows, the tilde notation represents your user profile. Use the equivalent hidden folders under your home directory rather than typing the Unix-style path literally into File Explorer. If you use a command-line copy tool, verify the source and destination before confirming an overwrite.
Copy all extension folders as a group if you want the same inventory, or select individual folders for a cautious trial. A folder name often includes the publisher, extension, and version, so avoid renaming it. If an extension has several version folders, let VSCodium determine which package it can load rather than manually editing metadata.
What a successful copy looks like
- Your familiar settings and keyboard shortcuts are active after VSCodium restarts.
- Transferred extensions appear in the installed list rather than showing only as downloadable items.
- Project features such as language support or formatting work without activation errors in the Output panel.
Seeing a folder in .vscode-oss/extensions does not prove that the extension is usable. Continue with the compatibility checks below. Test language servers, debuggers, formatters, and other extensions that your daily work depends on; an extension can appear installed while a particular feature remains unavailable.
Use Sync Settings instead of copying folders
VSCodium’s migration page documents a semi-automatic workflow based on a third-party extension called Sync Settings. It is not a built-in VSCodium import command. You must install and configure the extension in both editors and give it access to the same repository.
Step 1: install and configure Sync Settings in both editors
- Install the Sync Settings extension in VS Code.
- Install the same extension in VSCodium.
- Configure the repository, authentication, and any synchronization options identically in both editors. The extension’s own instructions determine the repository format and credentials.
Confirm that the repository is the one you intend to use before uploading. If it contains older settings, decide which copy is authoritative. Repository-backed synchronization can expose configuration to anyone with access to that repository, so use the access controls and credentials appropriate for your environment.
Step 2: upload from VS Code
In VS Code, open the Command Palette and run Sync Settings: Upload (user -> repository). Wait for the upload to finish and confirm that the repository contains the profile data you intend to move.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Step 3: download into VSCodium
In VSCodium, open the Command Palette and run Sync Settings: Download (repository -> user). Allow the extension time to install or restore the supported configuration and extensions.
Run the commands in that order when VS Code is your source of truth. Downloading first can replace the VSCodium profile with whatever is already in the repository, which may not be the setup you meant to migrate.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Step 4: monitor installation and restart
Watch the Output panel while extensions are being installed. When activity has stopped, restart VSCodium. The migration documentation specifically recommends waiting for extension installation to complete and checking the Output panel before restarting; interrupting that process can leave an incomplete profile.
After the restart, compare the installed extension list with the one you expected and open a test project. Sync Settings transfers what it supports; it is not a promise that every extension package, machine-specific path, or build-specific service will transfer successfully.
Recommended Free Tools
Manual copy or Sync Settings?
| Consideration | Manual folder copy | Sync Settings workflow |
|---|---|---|
| User effort | One-time file operations after installing VSCodium | Install and configure the extension in both editors, then upload and download |
| Control | You choose exactly which files and extension folders move | The extension transfers the configuration and extension data it supports |
| Repository requirement | None | A configured repository is required by the extension |
| Best fit | A local migration or a cautious, selective transfer | A repeatable setup shared through a repository-backed workflow |
| Compatibility limits | Copied packages can still be unavailable or incompatible | Transferred packages can still be unavailable or incompatible |
Choose manual copying when you want a clear audit trail and selective replacement. Choose Sync Settings when you already maintain editor configuration in a repository and accept the extra extension setup. Keep a backup either way.
Neither method is inherently more compatible. Manual copying can make it easier to omit a problematic extension, while Sync Settings can make repeated migrations more consistent. In both cases, verify the result in VSCodium instead of assuming that a completed file operation means a completed migration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Handle extensions that are missing from Open VSX
VSCodium defaults to Open VSX rather than Microsoft’s Visual Studio Marketplace. The project warns that some extensions familiar from VS Code may not be present. A missing listing is therefore not necessarily an installation error.
Ask for an Open VSX publication
Check whether the extension maintainer publishes an Open VSX package or accepts requests to do so. Publishing is controlled by the maintainer, so availability can change independently of your VSCodium installation.
Use VSCodium’s documented publication-request route
If the maintainer has not published the extension, follow the request route described in VSCodium’s Extensions and Marketplace documentation. This is a request for distribution, not a promise that the package will be accepted.
Install a VSIX from a legitimate release source
Some projects distribute a VSIX from their own release page or source repository. Verify that the file really comes from the extension’s maintainer, inspect its version and license, and keep a record of where it came from. Do not assume that a VSIX copied from an arbitrary download site is safe or authorized.
Before choosing this route, look for an Open VSX version from the same maintainer and compare its release notes with the VSIX. A package built for the official editor may depend on services that VSCodium does not provide even when the installation itself succeeds.
VSIX installation and compatibility cautions
Microsoft’s Extension Marketplace documentation describes installing a local VSIX through the Extensions view’s Install from VSIX command or with:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →code --install-extension path/to/file.vsixThat command is documented for VS Code. VSCodium’s command name and packaging can differ by build, so use the VSCodium interface and current project instructions for your installation rather than substituting a command without checking it.
A package can install and still be unusable. VSCodium’s documentation notes that some extensions are licensed only for official Visual Studio Code builds or depend on build-specific services. Review the extension license and stated compatibility before importing it. Also remember that Microsoft’s documentation says auto-update is disabled by default for a VSIX-installed extension in VS Code; a manually installed package may require you to obtain and install later updates yourself.
Keep track of manually installed versions so you know when to check the maintainer’s release page again. If the extension later appears in Open VSX, compare the available package and decide whether switching is appropriate. Remove a failed package from VSCodium before testing another build if the two versions could conflict.
Troubleshoot a migration that did not work
Settings did not appear
- Confirm that you copied into the VSCodium
Userdirectory for the same operating system, not into the VS Code source folder again. - Check the filename and extension:
settings.jsonandkeybindings.jsonmust not have an added.txtsuffix. - Close VSCodium, restore your backup if necessary, and copy the files again while the editor is not running.
- Open the files in a text editor and check for malformed JSON if VSCodium reports a configuration error.
If only some preferences are missing, compare the files rather than repeating the entire copy. A workspace setting may be overriding the global value, or the setting may belong to an extension that did not activate.
Extensions are not listed after copying
- Verify that the folders are directly inside
~/.vscode-oss/extensions, without an extra directory level. - Check that you copied the contents of
~/.vscode/extensions, not only a shortcut or a partial selection. - Confirm that the account running VSCodium can read the destination folders.
- Restart VSCodium after the copy and inspect the Extensions view and Output panel.
On Windows, recheck that you used the home profile’s hidden .vscode and .vscode-oss folders, not the application-install directory. On macOS and Linux, verify that the copy went to the same home directory used when launching VSCodium.
An extension appears but fails to activate
Read the activation error in the Output panel and check the extension’s license and supported products. A failed activation is often a compatibility or build-specific limitation rather than a bad folder copy. Look for an Open VSX release or a maintainer-provided version before trying another package.
Test the extension in a small or representative project after each change. This makes it clear whether the failure is caused by the package, its configuration, or a project-specific dependency.
Sync Settings stops partway through
- Confirm that the extension is installed and configured in both editors.
- Verify repository access and credentials in the extension’s settings.
- Run the upload command in VS Code again, then the download command in VSCodium; do not reverse the order if the repository is meant to be the source of truth.
- Keep the Output panel open, wait for extension installation to finish, and restart only after activity has stopped.
If the repository contains an unexpected profile, stop and inspect it before downloading again. Restore the VSCodium backup rather than repeatedly applying an uncertain configuration.
Final verification checklist
- VSCodium launches normally and is on the intended stable or Insiders channel.
settings.jsonandkeybindings.jsonare present in the VSCodium user directory for your platform.- Your most important editor preferences and shortcuts behave as expected in a test project.
- Transferred extensions appear in the installed list and activate without errors.
- Extensions that were unavailable in Open VSX have been checked for maintainer publication, licensing, and compatibility before any VSIX installation.
- Your original VS Code profile and pre-migration VSCodium backup remain intact until you are satisfied with the result.
- The project’s own
.vscodesettings have been checked where workspace behavior differs from your global preferences. - You know which extensions came from a VSIX and therefore may need manual update checks.
Frequently Asked Questions
How do I move my VS Code settings to VSCodium?
Close both editors, copy settings.json and keybindings.json from VS Code’s platform-specific User directory to the equivalent VSCodium User directory, then restart VSCodium. Keep a backup before replacing existing files.
Can I copy my VS Code extensions to VSCodium?
Yes. With both editors closed, copy the contents of ~/.vscode/extensions into ~/.vscode-oss/extensions. The folders may appear in VSCodium, but activation and licensing are not guaranteed.
Why is an extension missing in VSCodium?
VSCodium uses Open VSX, so an extension listed in Microsoft’s marketplace may not have an Open VSX package. Ask the maintainer to publish it, use VSCodium’s documented request route, or obtain a VSIX from a legitimate maintainer release source after checking its license and compatibility.
Should I use manual copying or Sync Settings?
Use manual copying for a selective, one-time local migration. Use Sync Settings when you already maintain a repository-backed editor configuration and are comfortable installing and configuring the extension in both editors.
Does installing a VSIX make an extension compatible with VSCodium?
No. A VSIX can install while still depending on official Visual Studio Code services, APIs, or licensing. Check the extension’s stated supported products and monitor VSCodium’s Output panel for activation errors.
Will a VSIX-installed extension update automatically?
Microsoft’s VS Code documentation says auto-update is disabled by default for a VSIX-installed extension in VS Code. Plan to check the maintainer’s release source and install later updates yourself; use VSCodium’s current instructions for its own update behavior.
The Bottom Line
Install VSCodium using the project’s current platform instructions, launch it once, and back up its profile. For the most control, copy VS Code’s settings.json, keybindings.json, and extension folders into VSCodium’s documented destinations. If you already use a repository-backed setup, Sync Settings can upload from VS Code and download into VSCodium after you configure it in both editors. In either case, verify each extension through Open VSX, a legitimate VSIX source, and its licensing and compatibility requirements before relying on it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
