Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

VSCodium is a community-built distribution of Microsoft’s open-source Code – OSS editor source. Its binaries remove Microsoft branding and licensing customizations and have editor telemetry disabled. It is not simply Microsoft Visual Studio Code with one setting changed: VSCodium uses the Open VSX extension registry instead of Microsoft’s Marketplace, so some extensions—especially certain Microsoft or proprietary ones—may be unavailable or incompatible.

What VSCodium is—and how it relates to VS Code

VSCodium is built from the Code – OSS source repository, the codebase behind Visual Studio Code. The VSCodium project says its scripts clone Microsoft’s repository, apply a customized product.json, build the editor, and publish binaries. It describes this as a binary distribution, not an independent fork. The resulting VSCodium binaries are distributed under the MIT license.

Microsoft distinguishes the open-source source code from its branded product: “The source code is available to everyone under a standard MIT license,” while Visual Studio Code is a distribution of Code – OSS with Microsoft-specific customizations and is released under Microsoft’s product license. See Microsoft’s Visual Studio Code FAQ for that distinction.

In practical terms, VSCodium offers a familiar Code – OSS editor without Microsoft’s branding and product-specific customizations. It is a separate distribution, so its services, extension sources, and compatibility are not identical to Microsoft’s Visual Studio Code.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Is VSCodium VS Code without telemetry?

The VSCodium project says telemetry is disabled in its binaries and provides documentation on removing and checking for telemetry. That applies to telemetry built into the editor; it is not a guarantee that every component you add is silent.

Separately installed extensions may collect usage data under their own policies. Microsoft notes that the editor’s telemetry setting does not control data collection by extensions. Review an extension’s privacy terms and settings independently; see Microsoft’s telemetry guidance.

Why VSCodium does not use Microsoft’s Extension Marketplace

VSCodium uses the Open VSX Registry. The VSCodium project explains that Microsoft’s Marketplace terms limit Marketplace Offerings to Visual Studio Products and Services, so alternative Code – OSS distributions use another registry. Microsoft likewise says Marketplace offerings are provided for the Visual Studio family and that Marketplace-acquired Microsoft extensions are not licensed for use outside it. Its policy explanation is in the Visual Studio Code FAQ.

Consequently, searching Open VSX will not necessarily find every extension listed for VS Code, and an extension’s presence in a registry does not by itself establish that it is licensed or compatible with VSCodium.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Will your VS Code extensions work in VSCodium?

Many extensions are available through Open VSX, but compatibility is not automatic. Two separate issues matter: whether the extension is available from a registry VSCodium can use, and whether its license and technical requirements permit or support use in this distribution.

  • Registry availability: An extension on Microsoft’s Marketplace may not be listed on Open VSX.
  • License: Some extensions restrict use to official Visual Studio Code builds. Microsoft extensions acquired from its Marketplace are not licensed for use outside the Visual Studio family.
  • Technical compatibility: Extensions can depend on APIs or services that differ between distributions. Microsoft identifies proprietary examples such as Wallaby.js, Google Cloud Code, and Remote Development extensions; check each publisher’s terms and support information.
  • Extension privacy: An extension may have its own telemetry or data practices, regardless of the editor’s telemetry setting.

Before switching, identify any essential extensions and check their availability, license, and documented support. The VSCodium project explains its registry choice and extension limitations in its extension documentation; Microsoft discusses extension licensing and authors’ control over licenses in its FAQ.

How to install VSCodium

The project documents package-manager installation for macOS, Windows, and Linux. Choose the channel that matches your operating system and follow the current VSCodium installation instructions, since supported packages and platform requirements can change by release.

Windows

With WinGet installed, run:

winget install -e --id VSCodium.VSCodium

The project also lists Chocolatey and Scoop as Windows installation options.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

macOS

VSCodium supports installation through Homebrew. The project lists macOS 12 or newer for x64 and arm64 systems; confirm current release requirements and the recommended Homebrew command in its installation guide.

Linux

For Snap, the documented command is:

sudo snap install codium --classic

For Flatpak, the documented command is:

flatpak install flathub com.vscodium.codium

Other project-supported options include deb and rpm repositories, AppImage and tar.gz packages where available, plus AUR and Nix. Package and architecture availability varies; check the project’s current installation instructions for the right package for your distribution.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What to check before switching from VS Code

The editor experience may feel familiar because both distributions are based on Code – OSS, but moving is not a perfect one-for-one replacement. Before changing your daily setup, check these practical points:

  • List the extensions you rely on and verify availability in Open VSX.
  • Read the license and publisher support notes for extensions that are missing or Microsoft-branded.
  • Review extension-specific privacy policies if telemetry or data handling is important to you.
  • Confirm that VSCodium has a current package for your operating system and CPU architecture.

These checks identify the most common reasons a VS Code workflow may not transfer intact: registry differences, extension licensing, technical support boundaries, and package availability.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

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.