This is not a fork. This is a repository of scripts to automatically build Microsoft's
vscode repository into freely-licensed binaries with a community-driven default configuration.
- Why Does This Exist
- More Info
- Supported Platforms
If you are on a Mac and have Homebrew installed:
brew install --cask vscodium
brew tap homebrew/cask-versions
brew install --cask vscodium-insiders
Note for macOS users: if you can't open the App, please read the following troubleshooting.
If you use Windows and have Windows Package Manager installed:
winget install -e --id VSCodium.VSCodium
winget install -e --id VSCodium.VSCodium.Insiders
choco install vscodium
choco install vscodium-insiders
If you use Windows and have Scoop installed:
scoop bucket add extras
scoop install vscodium
snap install codium --classic
Any issues installing VSCodium using your package manager should be directed to that repository's issue tracker.
flatpak install flathub com.vscodium.codium
flatpak run com.vscodium.codium
Build instructions can be found here
This repository contains build files to generate free release binaries of Microsoft's VS Code. When we speak of "free software", we're talking about freedom, not price.
When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.
When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a "clean" build, without the Microsoft customizations, which is by default licensed under the MIT license
This repo exists so that you don't have to download+build from source. The build scripts in this repo clone Microsoft's vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.
Microsoft's build process (which we are running to build the binaries) does download additional files. Those packages downloaded during build are:
- Pre-built extensions from the GitHub:
- From Electron releases (using gulp-atom-electron)
For more information on getting all the telemetry disabled, tips for migrating from Visual Studio Code to VSCodium and more, have a look at the Docs page page.
If you have any issue, please check the Troubleshooting page or the existing issues.
Please note that some Visual Studio Code extensions have licenses that restrict their use to the official Visual Studio Code builds and therefore do not work with VSCodium. See this note on the Docs page for what's been found so far and possible workarounds.
If you would like to see the commands we run to build
vscode into VSCodium binaries, have a look at the workflow files in
.github/workflows for Windows, GNU/Linux and macOS. These build files call all the other scripts in the repo. If you find something that doesn't make sense, feel free to ask about it on Gitter.
The builds are run every day, but exit early if there isn't a new release from Microsoft.
The minimal version is limited by the core component Electron, you may want to check its platform prerequisites.
- macOS (
dmg) macOS 10.15 or newer x64
- macOS (
dmg) macOS 11.0 or newer arm64
- GNU/Linux x64 (
- GNU/Linux arm64 (
- GNU/Linux armhf (
- Windows 10 / Server 2012 R2 or newer x64
- Windows 10 / Server 2012 R2 or newer arm64
If you would like to support the development of VSCodium, feel free to send BTC to
|for the logo
|for CDN and domain name
|for providing a Mac mini M1