Skip to content
binary releases of VS Code without MS branding/telemetry/licensing
Branch: master
Clone or download
Latest commit e4db49f May 23, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update issue templates Apr 11, 2019
src/resources Resize win32 70x70 icon May 18, 2019
.gitignore Windows builds with Azure Pipelines (#58) Nov 27, 2018
.travis.yml Feature/DMG (#162) May 17, 2019 Add code of conduct Oct 12, 2018 Update Apr 30, 2019
LICENSE Testing build Aug 13, 2018 Add more info to more info May 22, 2019
VSCodium-AppImage-Recipe.yml AppImage support (#108) Apr 19, 2019
azure-pipelines.yml Build cleanup and Windows ia32 (#103) Apr 5, 2019 Add updateUrl and releaseNotesUrl to product.json May 20, 2019
check_tags.ps1 Build cleanup and Windows ia32 (#103) Apr 5, 2019 Update check for Mac artifact Apr 12, 2019 AppImage support (#108) Apr 19, 2019 Add execute permissions to May 19, 2019 Sign mac app (#136) Apr 24, 2019 Commit version JSON after deploy (#158) May 16, 2019 Merge branch 'master' into fix-arm64-build Mar 1, 2019 Sign mac app (#136) Apr 24, 2019 CRLF endings on Windows and shasum bugfixes May 19, 2019 Add script to trigger Azure pipelines build Jan 23, 2019 Undo telemetry before build (#27) Oct 5, 2018 Update logic to disable telemetry and crash reporting settings Apr 14, 2019 Pull before commit May 20, 2019
win32-build.yml Refactor update_version to support Windows builds May 18, 2019

current release windows_build_status build status license Gitter

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.

Table of Contents


🎉 🎉 Download latest release here 🎉 🎉

More info / helpful tips are here.

Install with Brew (Mac)

If you are on a Mac and have Homebrew installed:

brew cask install vscodium

Note: if you see "App can’t be opened because it is from an unidentified developer" when opening VSCodium the first time, you can right-click the application and choose Open. This should only be required the first time opening on a Mac.

Install with Chocolatey (Windows)

If you use Windows and have Chocolatey installed (thanks to @Thilas):

choco install vscodium

Install with Scoop (Windows)

If you use Windows and have Scoop installed:

scoop bucket add extras
scoop install vscodium

Install with Package Manager (Linux)

You can always install using the downloads (deb, rpm, tar) on the releases page, but you can also install using your favorite package manager and get automatic updates. @paulcarroty has set up a repository with instructions here. Any issues installing VSCodium using your package manager should be directed to that repository's issue tracker.

Install on Arch Linux

VSCodium is available in AUR as package vscodium-bin, maintained by @plague-doctor.

Flatpak Option (Linux)

VSCodium is not available as a Flatpak app, but @amtlib-dot-dll has done significant work to package up the open source build of Visual Studio Code without telemetry, very similarly to VSCodium. That package is available here and the build repo is here.

Why Does This Exist

This repository contains build files to generate free release binaries of Microsoft's VSCode. When we speak of "free software", we're talking about freedom, not price.

Microsoft's downloads of Visual Studio Code are licensed under this not-FLOSS license and contain telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

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.

If you want to build from source yourself, head over to Microsoft's vscode repo and follow their instructions. This repo exists to make it easier to get the latest version of MIT-licensed VSCode.

Microsoft's build process does download additional files. This was brought up in Microsoft/vscode#49159 and Microsoft/vscode#45978. These are the packages downloaded during build:

More Info


For more information on getting all the telemetry disabled and tips for migrating from Visual Studio Code to VSCodium, have a look at this Docs page.

Extension Licensing

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.

How do are the VSCodium binaries built?

If you would like to see the commands we run to build vscode into VSCodium binaries, have a look at the .travis.yml file (for Linux and OS X builds) and the win32-build.yml file (for Windows builds). 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. To examine the build logs, go here for Linux / OS X and here for Windows

Supported OS

  • OS X (zip, dmg)
  • Linux x64 (deb, rpm, AppImage, tar.gz)
  • Linux x86 (deb, rpm, tar.gz)
  • Windows x64
  • Windows x86

The ARM architecture is not currently supported but is being worked on.


If you would like to support the development of VSCodium, feel free to send BTC to 3PgjE95yzBDTrSPxPiqoxSgZFuKPPAix1N.



You can’t perform that action at this time.