Skip to content

Recommendation

Situational

Disable it if you do not want to send data about the editor’s usage and errors — that is how BoosterX itself formulates the recommendation.

The setting appears in BoosterX only when Visual Studio Code is installed; without the editor running, it does not remove any Windows background load.

Main effect
Disabling VS Code telemetry
FPS and memory
See the research

According to the public documentation, Visual Studio Code collects three kinds of data: information about feature usage, information about errors without the editor crashing, and diagnostic data on crashes. BoosterX switches the editor to the off level using the standard telemetry.telemetryLevel setting, which disables all three kinds at once. The setting is shown in BoosterX only when Visual Studio Code is detected on the PC; the telemetry of installed extensions is not controlled by this setting — extensions have their own toggles.

Disabling applies only to the current user, and data already sent before the change is not returned. The editor itself offers intermediate levels (crash only, crash and error only) — BoosterX switches the setting entirely: off or a return to the default value. Problem reports sent manually work separately.

In VS Code, open File → Preferences → Settings and search for “telemetry”: the telemetry.telemetryLevel parameter should show “off”. The command “Developer: Show Telemetry” will show which events are still being generated.

Open “Optimization” → “Privacy” → “Dev tools and CLI” → “Visual Studio Code telemetry” and move the toggle to the “Enabled” position: BoosterX will apply the “off” level of the editor’s standard telemetry setting. Click “Apply”. If “Instant apply” is enabled, a separate button is not required. To revert, move the toggle to the “Disabled” position and apply the change again: BoosterX will return the value to the default — the editor’s telemetry will be collected again.

Last verified: 2026-09-19.