Treat every item below as a reversible experiment, not a guaranteed speed-up.
The short version
- Turn off Minimap and CodeLens if you never use them.
- Consider turning off live search-as-you-type.
- Audit your extensions with VS Code's built-in tools before uninstalling.
- Hide
node_moduleswhere it isn't already hidden. - Open the project folder, not the folder above it.
- Rule out storage and system causes before blaming the editor.
Minimap: a free-up of space, maybe of cycles
Shareef says the Minimap is a scaled-down render of the whole file that VS Code has to keep redrawing. Turning it off made scrolling feel "a bit snappier" on his machine and gave him horizontal space back.
Microsoft's documentation confirms what the feature is. The Minimap is a code outline for quick navigation, and you can select or drag its shaded area to jump around. Microsoft's own docs for the user interface say it can be moved left or disabled with "editor.minimap.enabled": false in user or workspace settings. The docs make no performance claim. Any speed gain is machine-specific.
To change it: press Ctrl+, to open Settings, search for Minimap, and clear Editor: Minimap Enabled. Or add the JSON line above to settings.json.
CodeLens: convenience traded for background work
CodeLens is the inline annotation above functions and classes that shows reference counts and similar data. Shareef argues it recalculates constantly. That is stated more strongly than the sources support, and the actual cost will vary by language extension.
What the documentation does support is that reference information shown in CodeLens can be turned on or off through the editor.codeLens setting. You also don't lose the underlying capability. Go to References is Shift+F12, and Go to Implementation is Ctrl+F12 on Windows.
To change it: open Settings, search for CodeLens, and clear Editor: CodeLens. Some language extensions add their own CodeLens settings, so check those too.
Search on type: fewer intermediate searches, slower feedback
VS Code can update full-text search results while you type. Shareef recommends turning that off so a search runs only when you press Enter. The setting is search.searchOnType.
Microsoft's release notes for version 1.41 describe the history. Search results update as you type, which helps when building complicated regular expressions. The feature can be disabled with search.searchOnType, and search.searchOnTypeDebouncePeriod adjusts the delay, which defaulted to 300 ms. That default dates from the 2019 notes. Check your installed version before assuming it still applies.
The 300 ms debounce also undercuts the claim that every keystroke triggers a full scan. Short pauses are batched. The cost you actually pay depends on project size and disk speed. If you rely on live feedback for regex work, you may prefer to lengthen the debounce rather than switch the feature off.
Extensions: audit first, then uninstall
Shareef says extensions "load at startup" and consume memory whether you use them or not. That is too broad. VS Code lets extensions declare activation events and loads them lazily. The example given is that the Markdown extension should load only when a Markdown file is opened. Cost therefore depends on how each extension is written.
Housekeeping still pays off, and VS Code has better diagnostics than eyeballing a list:
- Press Ctrl+Shift+X and type
@installedto see what you have. - Open the Command Palette with Ctrl+Shift+P and run Developer: Show Running Extensions. It gives basic stats and sorts extensions from longest to shortest activation time.
- An extension loaded on startup is labelled "Startup Activation".
- Run Developer: Startup Performance for a deeper audit of launch.
- Developer: Open Process Explorer shows RAM, CPU, renderer and extension host processes.
Before you delete anything, test. One troubleshooting guide suggests temporarily disabling extensions, including starting VS Code with all extensions disabled, to find the culprit. The --disable-extensions command-line switch does this. If the editor suddenly feels quick, re-enable extensions in batches until the slowness returns.
Hiding node_modules: check before you add the line
Shareef recommends this snippet:
"files.exclude": {
"**/node_modules": true
}
Microsoft's settings documentation actually uses this case as its example. For a backend server project, it suggests setting files.exclude to exclude the node_modules folder from the File Explorer. The glob patterns also follow your operating system's case-sensitivity rules, which means case-insensitive on Windows.
Three points are worth knowing:
files.excludeandsearch.excludeare different. Your brief notes thatfiles.excludehides items from the Explorer and from text search, whilesearch.excludeaffects only search and leaves the folder visible.- Your project may already exclude it. VS Code's JavaScript project documentation says it excludes
node_modulesby default when there is nojsconfig.json. The line may be redundant. - IntelliSense isn't guaranteed untouched. Shareef says the TypeScript language server still reads the folder. Microsoft's sources here don't confirm that for every setup. After changing it, test autocomplete, types and your build.
Open the narrow folder
Opening Software-Projects/my-app rather than Software-Projects keeps unrelated files out of the Explorer and out of search. That is sound practice. If you need a shared library next door, a multi-root workspace lets you add it as a second root without opening the whole parent.
Shareef also promises shorter startup for language servers such as TypeScript and Python. The documentation gathered here doesn't back that up, so read it as plausible rather than proven. Less noisy search results are the safer expectation.
To do it: choose File > Open Folder and pick the project folder itself.
When it's the PC, not the editor
Shareef closes by suggesting you check your storage drive. His claims about constant reads and writes, and about CrystalDiskInfo, aren't verified by Microsoft's documentation. The sensible reading is that slowness can come from the editor, an extension, the project or the system. High disk activity alone doesn't prove a failing drive. If you suspect one, back up first, and treat any third-party drive-health reading as a hint rather than a verdict.
A sensible order of operations
- Disable extensions as a test and see whether the problem is extension-related.
- Open only the folder you need.
- Switch off Minimap and CodeLens if you don't use them.
- Lengthen or disable search on type if searches feel janky.
- Add the
node_modulesexclusion if it isn't already in effect. - Only then look at hardware.
The bottom line
Nothing here is risky, and everything can be undone. The honest framing is that these changes remove optional work. They won't rescue a machine that's genuinely underpowered. Shareef's own "a few seconds off startup" is a personal anecdote, not a benchmark. Change one thing at a time so you can tell which one helped, and put back anything you miss.
References
- I almost ditched VS Code for being slow, but these settings saved it MakeUseOf · 2026-11-16T19:30:17+00:00
- Code Navigation code.visualstudio.com
- This hidden tool showed me exactly which VS Code extensions were slowing my laptop down daily.dev