VS Code

Why clean VS Code?

• Invalidated V8 compiled script data after a VS Code or Electron update can make the first launch unusually slow, with the window appearing late while bytecode is rebuilt
• Stale CachedExtensions entries can leave an updated extension loading old bundled assets, showing missing icons, broken webviews, or commands that do nothing until the cache is regenerated
• Corrupted Chromium HTTP cache files in Cache_Data can cause blank Marketplace panels, sign-in pages that never finish loading, or extension webviews that render as empty white screens
• Large accumulated log folders from repeated crashes, verbose extension debugging, or long-running sessions can consume hundreds of megabytes and are usually only noticed when disk space starts shrinking unexpectedly
• Renderer and extension host crashes often leave behind logs that keep growing between launches, so recurring startup problems are accompanied by oversized log directories and slower troubleshooting
• After network changes or expired cached responses, VS Code may keep serving stale web content from its disk cache, leading to outdated release notes, broken extension details pages, or repeated reload prompts
• Cached extension bundles and script caches can become inconsistent after interrupted updates, causing a slow startup sequence with repeated extension activation delays and warnings in the developer console

Common questions about VS Code

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.