5 ways to reduce VS Code RAM usage
1 Audit extensions per workspace
Use VS Code's workspace-specific extension recommendations. Disable extensions you don't need for the current project.
2 Use Process Explorer
Help → Open Process Explorer shows exactly which extension or language server is consuming memory.
3 Close unused windows
Each VS Code window runs its own set of extension hosts and language servers. Close windows for projects you're not actively editing.
4 Disable TypeScript auto-import for large repos
In large monorepos, TypeScript's auto-import suggestion feature indexes the entire project. Disable it in settings if your repo has 1000+ files.
5 Restart Extension Host
Instead of restarting VS Code entirely, use the command palette: 'Developer: Restart Extension Host'. This reclaims extension memory without losing your window state.
Lighter alternatives to VS Code
If VS Codeis consistently eating too much RAM, consider switching to a lighter alternative. Here's how they compare:
1 Helix
Different paradigmTradeoff: Modal editing, no plugin system yet
Get Helix →2 Neovim
Different paradigmTradeoff: Steep learning curve, requires terminal comfort
Get Neovim →3 Sublime Text
Some adjustmentTradeoff: No built-in terminal, fewer IDE features
Get Sublime Text →4 Zed
Easy switchTradeoff: Maturing extension ecosystem, no remote SSH yet
Get Zed →5 Nova
Easy switchTradeoff: macOS-only, smaller plugin ecosystem
Get Nova →How DevPulse helps with VS Code
DevPulse groups VS Code's main window, extension hosts, and language servers into one view. It detects runaway TypeScript servers and zombie language server processes.
Instead of guessing how much RAM VS Code consumes or manually checking Activity Monitor, DevPulse gives you a clear, always-visible answer in your menu bar.