18 - Nov - 2026

I almost ditched VS Code for being slow, but these settings saved it

I’ve used VS Code for at least six years, and it has only gotten slower. Sure, my machine isn’t getting any younger, but it’s capable enough to handle most of what I need VS Code for. And in this RAMageddon, my PC needs to stop working completely before I can even consider buying a new one.

While switching to a new code editor is an option, I decided to give VS Code another chance and do some performance optimization. With a bit of help from the internet and some trial and error, a few tweaks to the settings saved me the hassle of switching to a new platform.

Turn off Minimap

A small visual feature with a not-so-small rendering cost

vs code settings search for minimap options
Tashreef Shareef / MakeUseOf

Minimap is useful when you want to navigate a long file quickly, but it comes with a rendering cost. It’s essentially a scaled-down version of your entire file that VS Code has to draw and update continuously as you type or scroll. On modern hardware, this overhead is negligible. On an older machine like mine, every bit of rendering work adds up.

I also found the Minimap to be more of a distraction than a navigation aid. It sits there taking up a nice chunk of horizontal space, and I rarely clicked on it. Once I turned it off, the editor felt a bit snappier during scrolling, and I got back some screen real estate that I’d rather use for code.

To disable it, press Ctrl +, to open Settings, search for Minimap, and uncheck the Editor: Minimap Enabled option.

Disable CodeLens

Stop computing data you never click on

vs code settings search for codelens options
Tashreef Shareef / MakeUseOf

CodeLens shows reference counts, implementations, and test runners directly above your functions and classes. It sounds helpful in theory, and it is, if you use it. The problem is that CodeLens computes this data for every symbol visible on screen, and it does so continuously. Every time you scroll or type, it recalculates.

If you rarely click on those inline references, you’re handing over CPU and memory to a feature that’s competing with essentials like IntelliSense and syntax highlighting. On a machine that’s already struggling, that trade-off isn’t worth it.

You don’t lose the functionality entirely, either. Find All References (Shift + F12) and Go to Implementations give you the same information on demand, without the constant background cost.

To turn off CodeLens, press Ctrl +, to open Settings, search for CodeLens, and uncheck Editor: CodeLens.

Turn off search on type

Stop triggering full-project searches with every keystroke

vs code settings search on type with ample notes plugin
Tashreef Shareef / MakeUseOf

Search on type triggers a full workspace search with every character you type. If you type slowly or pause mid-word, VS Code runs partial searches one after another. On big projects, even a short query forces VS Code to scan every file, then build and render a massive results list, causing disk and CPU usage spikes.

If your projects live on an HDD or an older SSD, you’ll feel the impact more than most. The search panel becomes sluggish, and the rest of the editor can stutter while VS Code chews through thousands of files looking for a two-letter fragment.

Turning off search on type means a search only fires after you type the full query and hit Enter. You still get the same results, just without the wasted work in between. To turn it off, open Settings (Ctrl +,), search for search on type, and uncheck Search: Search on Type.

Remove extensions you don’t need

The oldest trick in the book, and the easiest to forget

This one gets repeated in every VS Code performance guide for a reason: it works. Extensions can pile up quickly, and most of us install them for one project, then never think about them again. Each extension loads at startup, hooks into editor events, and consumes memory whether you’re actively using it or not.

I’d been guilty of this for years. Press Ctrl + Shift + X to open the Extensions pane, then type @installed in the search bar to see everything currently loaded. Look for extensions with a particularly high Activation Time, shown in milliseconds next to the extension name. That number tells you how long each extension took to start up. Remove anything with a long load time that you don’t actually use.

I was surprised to find at least a dozen plugins that I hadn’t touched in months, yet they loaded every single time I launched VS Code. Removing them shaved a few seconds off my startup time and freed up memory for the extensions I do use.

Hide node_modules from the Explorer

Thousands of files your editor doesn’t need to think about

vs code settings json editing java home deprecation warning
Tashreef Shareef / MakeUseOf

If every drop of performance counts, hiding node_modules from the Explorer can help with a few droplets. A typical JavaScript project’s node_modules folder contains thousands of files and subfolders. VS Code uses lazy loading, so those files are only read when you expand the folder, but even accidentally clicking on it can freeze the sidebar briefly on an older machine.

Hiding node_modules prevents that from happening. Better yet, files hidden through files.exclude also don’t appear in Quick Open (Ctrl + P) and search results by default. When there’s less to scan, sort, and display, there’s less work for the editor.

This doesn’t break anything, either. The TypeScript language server still reads node_modules for autocomplete and type information, so your IntelliSense keeps working exactly as before. To hide it, open your settings.json file and add:

"files.exclude": {
"**/node_modules": true
}

If you need to browse node_modules again, use Ctrl + P and type the path directly or remove the line.

Open a narrow working folder

A habit change that does more than any setting

vs code explorer showing ample notes plugin pdf annotator project files
Tashreef Shareef / MakeUseOf

The last one isn’t a setting you toggle, but a habit. Instead of opening a top-level repository or a parent folder like “Software Projects,” open the specific subfolder you’re working on, like “Software-Projects/my-app.”

Go to File > Open Folder, then choose the project folder itself, not the directory above it. What this does is reduce the number of files in your workspace. Fewer files means less CPU and memory usage across the board. You also get less noisy search results, shorter startup times for language servers like TypeScript and Python, and a shorter file tree that’s easier to navigate.

If your code needs access to files from an adjacent folder, you can add it to the workspace as a second root using multi-root workspaces instead of opening the parent. That way, you get access to shared libraries without forcing VS Code to index everything else sitting next to your project.

The hardware problem that the software can’t fix

Beyond these tweaks, there’s one more thing that could be dragging your VS Code performance down, and it’s your storage drive. VS Code reads and writes project files constantly to index, search, and cache extension data. If the drive those files live on is slow or starting to fail, no amount of settings optimization will help.

Check the disk activity when VS Code is running. If you see sustained high usage or unexplained spikes, your drive might be the bottleneck. An old HDD will always struggle with the kind of random read/write patterns a code editor demands. Even an aging SSD can slow down as it fills up or develops bad sectors. You can use CrystalDiskInfo to check your storage drive health before it quietly takes your files with it. If the drive checks out fine and these settings still aren’t enough, then it might actually be time for a hardware upgrade, but at least you’ll know the software side isn’t holding you back.

Leave a Reply

Your email address will not be published. Required fields are marked *