VSCodium: the same editor, built without telemetry
What it does
VSCodium is a community project that compiles the open-source code behind Visual Studio Code into ready-to-install binaries. The upstream repository is MIT licensed, but the binaries Microsoft distributes carry their own product licence, branding, telemetry endpoints and a marketplace restricted to Microsoft-approved extensions. VSCodium removes that layer: the build scripts strip the Microsoft branding and the default telemetry settings, keep the MIT licence on the resulting package, and publish installers for Windows, macOS and Linux. What remains is the editor developers already know - the same command palette, the same settings format, the same debugging and source-control panes - with an Open VSX extension registry in place of the Microsoft marketplace.
The workflow
Installation mirrors its upstream twin: download the user or system setup executable, run it, and optionally let the installer add the editor to PATH and the Explorer context menu. Extensions install from Open VSX through the same Extensions sidebar. Settings, keybindings and workspace files use the classic JSON layout, so profiles can be copied between VSCodium and Visual Studio Code almost unchanged. Because the extension marketplace differs, provisioning scripts that reference Microsoft extension identifiers need a fallback to Open VSX identifiers or to a vendored VSIX file.
Practical settings and limits
The honest limitation is the extension catalogue: Open VSX carries a large and growing collection, but a handful of popular Microsoft-owned extensions simply are not published there, including the C# Dev Kit, Live Share and the remote development packs. Extensions can be installed from a VSIX file downloaded elsewhere, subject to their own licence terms. Updates arrive on the project's own cadence rather than Microsoft's, so feature parity usually trails by days or weeks. Telemetry is disabled by default but the relevant settings still exist if an organisation wants to re-enable product analytics. The binaries are not signed the way Microsoft's are, so SmartScreen may show a warning on first run.
Who should choose something else
Choose the official Microsoft build if you depend on the restricted extensions, remote development, or enterprise support channels. Choose a JetBrains IDE if you want a fully integrated toolchain rather than an assembled one. Choose a small native editor such as Notepad++ or Lite XL if the goal is quick text editing without the Electron runtime and its memory footprint.
- Best for
- Developers who want the VS Code experience with permissive licensing, no telemetry and no Microsoft account tie-in.
- Good to know
- Extensions come from Open VSX; a few Microsoft-published extensions are not available there.
VSCodium packages the open-source editor code that also powers Visual Studio Code, rebuilt without Microsoft branding, telemetry or the proprietary marketplace client. It installs like any desktop application and keeps the familiar layout and shortcuts.
How to get started
- Download the 64-bit Windows installer from the official VSCodium site.
- Run the setup wizard and pick a per-user or machine-wide installation.
- Leave the PATH and context-menu options enabled so folders can be opened from Explorer.
- Launch the editor and browse the Extensions panel, which resolves against the Open VSX registry.
- Import an existing VS Code profile or paste your settings JSON to keep keybindings and themes.
Questions & answers
Is VSCodium a fork of Visual Studio Code?
It is a rebuild rather than a fork. The project compiles the same MIT-licensed source with branding and telemetry removed, and ships the binaries under the MIT licence.
Will my favourite extensions install?
Most will, through Open VSX. A few Microsoft-owned extensions are not published there; side-load them as VSIX files where their licence allows, or stay on the official build.
Does it update itself?
The editor keeps its own update channel, so new versions arrive after the upstream source ships. The MSI variant can be deployed through standard software-management tooling.
