Understanding Vscodium's Telemetry Removal: Privacy Gains and Trade-offs

Why telemetry matters in a code editor

When you open VS Code, the editor periodically sends usage statistics to Microsoft's telemetry endpoints. For many developers this data helps improve the product, but it also raises privacy concerns and adds a small amount of network overhead. Vscodium, the community-built binary of VS Code, addresses this by stripping the telemetry modules from the core distribution.

How the telemetry removal works

The Vscodium build process excludes the telemetry package that ships with the official Microsoft release. This package contains the code responsible for gathering events such as command usage, startup performance, and extension activity, and for transmitting them to api.telemetry.microsoft.com. By removing it at compile time, the resulting binary:

• No longer initializes the telemetry client.
• Has a smaller on-disk footprint because the telemetry components and associated resources are omitted.
• Does not generate outbound requests to Microsoft telemetry endpoints during normal operation.

Verifying the absence of telemetry traffic

You can confirm that telemetry is disabled by watching network activity while using Vscodium:

1. Launch Vscodium.
2. Open the Developer Tools via Help → Toggle Developer Tools.
3. Select the Network tab.
4. Perform typical editing actions (open a file, run a command, install an extension).
5. Look for any requests to domains containing telemetry.microsoft.com or vortex.data.microsoft.com. If telemetry is removed, you should see no such requests.

Note: this check only shows that the core editor does not emit telemetry; it does not guard against telemetry that an extension might bundle itself.

Measuring the binary size reduction

Because the telemetry package is omitted, the Vscodium installer is typically smaller than the VS Code installer. To verify:

1. Download the latest Vscodium installer for your platform from https://github.com/VSCodium/vscodium/releases.
2. Download the corresponding VS Code installer from https://code.visualstudio.com/.
3. Compare the file sizes (for example, using ls -lh on Linux or macOS, or the file properties dialog on Windows).
4. You should observe a difference in the range of 10-15 MB, with Vscodium being the smaller file.

Trade-offs and limitations

Removing telemetry brings clear privacy and size benefits, but it also introduces some practical considerations:

• Update checks remain. Vscodium still contacts an update server to check for new versions unless you disable update checks in your settings. This can reveal that a Vscodium instance is running.
• Extension compatibility. A few extensions rely on the telemetry API to report their own usage or to adapt behavior based on editor telemetry. When the API is missing, those extensions may log warnings or fall back to a reduced feature set. Reviewing an extension's source or release notes can help you anticipate such issues.
• Feedback to Microsoft. Because usage data is no longer sent, Microsoft's product team loses a signal that could help prioritize bug fixes or performance improvements for the broader VS Code ecosystem. This is an intentional trade-off made by the Vscodium maintainers.

Actionable steps for privacy-conscious developers

If you decide that Vscodium's telemetry removal aligns with your workflow, consider the following checklist:

1. Install Vscodium from the official GitHub releases to ensure you receive the unmodified build.
2. After launch, open Developer Tools → Network and verify that no telemetry endpoints appear during normal use.
3. Check the installer size against the VS Code download to confirm the expected reduction.
4. Review the extensions you rely on; look for any mentions of telemetry in their documentation and test them in an isolated workspace.
5. If you wish to suppress update checks, add "update.mode": "none" to your settings.json.

By following these steps you can enjoy a smaller, privacy-focused editor while staying aware of the remaining data flows and extension-level considerations.