There is no single “slow laptop” switch in Visual Studio Code. The settings most likely to help are targeted exclusions that stop VS Code from discovering or analyzing folders you do not need: use files.exclude for the documented project-file search performed while opening large folders, jsconfig.json’s exclude list for JavaScript and TypeScript IntelliSense, and (for broad workspace searches) search.exclude. These settings reduce specific work rather than making every part of VS Code faster. Turn off the minimap only if you want a simpler display; the documentation does not establish it as a performance fix.
Start with the symptom, not a list of “speed” switches
Choose the setting according to the operation that is slow. A folder that takes a long time to open has a different cause from lagging JavaScript suggestions, and neither is necessarily fixed by hiding editor decorations.
As an Amazon Associate I earn from qualifying purchases.
| What feels slow | Setting or file to investigate | What it changes |
|---|---|---|
| Opening a large folder or workspace | files.exclude (preferably at workspace scope) |
Keeps selected folders out of the search for typical project files that VS Code performs while opening a folder. |
| JavaScript or TypeScript IntelliSense | exclude in jsconfig.json |
Removes non-source directories from that project’s language-service analysis. |
| Searches over huge dependency or build trees | search.exclude |
Excludes matching paths from text search; it does not configure JavaScript/TypeScript project analysis. |
| General large-workspace discovery | files.exclude and, where appropriate, search.exclude |
Limits the relevant file-discovery or search feature. The two settings are not interchangeable. |
| Visual clutter | editor.minimap.enabled |
Removes the minimap from the editor display. This is an interface choice, not a documented speed guarantee. |
| Startup or UI actions after installing extensions | Extension-specific settings and extension investigation | Extensions activate lazily, but an extension can still be responsible for a particular delay; there is no universal built-in setting that fixes every extension. |
VS Code has two important setting scopes. User settings apply across instances you open, while workspace settings belong to one project and can override user values when that setting supports both scopes. Use a workspace rule when only one large project needs exclusions; a global rule can hide or omit files in projects where you still need them.
Open the right Settings editor
You can make these changes through the graphical editor or directly in JSON. Open the Command Palette and choose one of the following commands:
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
- Preferences: Open Settings (UI) for searchable controls and scope selectors.
- Preferences: Open User Settings (JSON) for global configuration.
- Preferences: Open Workspace Settings (JSON) for the current project.
When a setting is available in both scopes, the workspace value takes precedence for that project. JSON edits must use valid JSON: quote property names and values, separate entries with commas, and keep the outer braces.
Fix slow folder opening with a narrow files.exclude rule
Why this can help
The Visual Studio Code FAQ attributes delays and CPU use when opening folders containing many files to VS Code’s search for typical project files. The documented remedy is to use files.exclude to keep selected directories out of that project-file search.
This is not a promise that every filesystem operation becomes faster. It targets the opening-folder/project-file discovery described by the FAQ. Exclude only directories that are irrelevant to the project configuration you need VS Code to find.
Configure it for one workspace
- Open the large project in VS Code.
- Open the Command Palette with Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS.
- Run Preferences: Open Workspace Settings (JSON).
- Add a targeted pattern under
files.exclude. For example:
{
"files.exclude": {
"**/largeGeneratedOrIrrelevantFolder": true
}
}Replace the example path with the actual directory in your tree. A pattern such as **/largeGeneratedOrIrrelevantFolder matches that folder name at any depth; use a more specific path when similarly named folders contain files you need. If you already have a files.exclude object, add a comma between properties rather than creating a second object with the same name.
Check the result and recover if needed
- Close and reopen the workspace, then observe whether opening the folder is more responsive.
- If a needed project file or directory disappears from the Explorer or from the feature you were troubleshooting, narrow the glob or remove the rule.
- Do not use a broad pattern such as
**/*; it can hide practically the entire tree and make diagnosis harder.
The setting is a scope control, not a deletion operation. The files remain on disk, but VS Code will treat matching paths as excluded for the relevant file-discovery behavior.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Reduce JavaScript and TypeScript IntelliSense work with jsconfig.json
When this is the right fix
If completion, parameter hints, diagnostics, or navigation become sluggish in a JavaScript or TypeScript project, configure the project’s source boundary. The official JavaScript project configuration guidance recommends excluding folders that are not source code, with node_modules and generated output such as dist as useful examples.
This exclusion belongs to the project configuration. It tells the JavaScript/TypeScript language service which files should not be part of that project’s analysis; it is different from hiding files in the Explorer or excluding them from text search.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Step-by-step example
- At the project root, create or open
jsconfig.json. A TypeScript project may already have atsconfig.json; follow that project’s existing configuration instead of creating conflicting project definitions. - Keep your existing compiler options and add an
excludearray for dependency and generated folders. - For example:
{
"compilerOptions": {
"module": "CommonJS",
"target": "ES6"
},
"exclude": [
"node_modules",
"dist"
]
}The module and target values above are illustrative options from the official example; retain the options your application actually requires. Adapt folder names to your build system: a generated directory might be called build, out, or something project-specific. Do not exclude a directory that contains source files you expect IntelliSense to index.
Validate the project boundary
- Open a source file after saving
jsconfig.jsonand test completion and diagnostics. - Check that imports from required source directories still resolve.
- If a generated declaration or source file is genuinely needed for editing, remove that path from
excludeor use a narrower pattern.
Excluding dependencies and generated output can reduce language-service scope, but the documentation does not attach a universal percentage improvement. The result depends on the project’s file count, dependency tree, and the operation that was slow.
Control broad text search with search.exclude
Large dependency and build directories can also make repository-wide text searches expensive or noisy. For that case, investigate search.exclude in the workspace settings. The IntelliSense documentation notes that, in very large workspaces, excluding large folders such as node_modules or build output with files.exclude or search.exclude can help keep workspace work manageable: IntelliSense documentation.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Use the setting for the feature you intend to change:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →search.excludelimits matching paths in VS Code’s text-search results.files.excludeis the file-exclusion mechanism to investigate for file discovery and the FAQ’s typical-project-file search.jsconfig.json(or the project’s TypeScript configuration) controls JavaScript/TypeScript analysis.
A workspace example for search-only exclusions is:
{
"search.exclude": {
"**/node_modules": true,
"**/dist": true
}
}Use patterns that match your repository and remember that search results will intentionally omit those directories. If you periodically need to search generated output, remove or temporarily disable the relevant rule instead of assuming the search is complete.
Decide between user and workspace scope
| Scope | Best use | Risk |
|---|---|---|
| User settings | A preference that should follow you into most VS Code instances, such as a personal interface choice. | A broad exclusion can affect unrelated projects and hide files you need elsewhere. |
| Workspace settings | Project-specific dependency, generated-output, or large-folder exclusions. | The rule affects collaborators if the workspace configuration is committed, so document intentional exclusions in the project. |
Start at workspace scope when diagnosing a single slow repository. Move a rule to user scope only when the same behavior is wanted across your projects. Scope precedence does not change what a setting means; it only determines which value applies.
Use the minimap only as an optional display simplification
The minimap is the narrow code overview at the side of the editor. The user-interface documentation shows that it can be disabled with editor.minimap.enabled: User interface: Minimap.
{
"editor.minimap.enabled": false
}Turning it off removes that visual element; it does not guarantee faster typing, indexing, startup, or search. If you prefer a less busy interface or want to eliminate one continuously rendered element, set it at user scope. If you are measuring a performance problem, treat this as a reversible preference rather than evidence-based remediation.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Investigate extensions instead of assuming a built-in setting will fix them
Extensions can affect startup and UI operations. VS Code describes extension activation as lazy in its Extension Host documentation, meaning an extension generally activates when its contribution is needed rather than all at once. Lazy activation does not prove that an extension is harmless: a particular extension can still be responsible for a delay after activation.
A practical extension branch
- Note the exact slow action: startup, opening a folder, saving a file, completion, search, or a command supplied by an extension.
- Temporarily reproduce the action in a clean environment, such as an extension-disabled test session, if your VS Code installation provides that option.
- If the delay disappears, re-enable extensions methodically to identify the contributor.
- Inspect that extension’s own settings and documentation. Change only options that correspond to its behavior, and restore them if they break required features.
This process avoids claiming that files.exclude, search.exclude, or the minimap controls extension code. Those settings address different scopes of work.
A decision procedure for a slow laptop
- Classify the delay. Is the pause while opening a folder, during text search, while JavaScript/TypeScript IntelliSense analyzes files, during startup, or during a general UI action?
- Measure one change at a time. Record the original behavior, apply one narrow rule, then repeat the same action. Multiple simultaneous changes make it impossible to know which scope helped or caused a missing result.
- For folder-opening delays, identify irrelevant, oversized directories and add a workspace
files.excludepattern aimed at the FAQ’s project-file search. - For JavaScript/TypeScript lag, add non-source dependencies and generated output to the project’s
jsconfig.jsonor existing TypeScript configuration. - For repository-wide search lag or noise, add appropriate
search.excludepatterns, understanding that search results will omit those paths. - For a very large workspace, review both file-discovery and search exclusions. The IntelliSense documentation says performance can lead to partial IntelliSense disabling, so reducing oversized folders may restore a more manageable project scope, but the exact effect is workspace-dependent.
- For startup or UI-specific delays, investigate extensions and their settings rather than applying unrelated file exclusions.
- Only then consider visual cleanup. Disable the minimap if you want it gone, without treating that change as a measured performance remedy.
Common mistakes and how to undo them
Excluding source code to chase a speed gain
If completion, navigation, or diagnostics vanish after an exclusion, the pattern is probably matching code you still need. Narrow the glob to generated or dependency directories and remove the broader entry.
Confusing hidden files with unanalysed files
A files.exclude or search.exclude rule does not replace a language-service project configuration. Conversely, a jsconfig.json exclusion does not necessarily remove a directory from text search. Choose the control based on the feature that is slow.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsApplying a project workaround globally
A dependency folder that is irrelevant in one repository may contain source or generated artifacts you inspect in another. Keep the first experiment in workspace settings, then promote it to user settings only if that behavior is consistently desirable.
Expecting a quantified result
The official material describes the work each setting limits but does not publish a universal benchmark, percentage, or guaranteed response-time reduction. Judge success by repeating the same action and checking that required project features still work.
Assuming the laptop itself has been diagnosed
These settings address VS Code’s file discovery, search, project analysis, or display. If the entire operating system remains slow after a targeted test, the evidence here does not identify a hardware, operating-system, or specific extension cause.
A compact configuration checklist
- Open the correct User or Workspace Settings editor from the Command Palette.
- Keep folder-opening exclusions narrow and tied to irrelevant large directories.
- Put JavaScript/TypeScript non-source directories in the project configuration’s
excludearray. - Use
search.excludewhen the problem is text-search scope, not IntelliSense. - Check whether an extension is involved in startup or a particular UI action.
- Disable
editor.minimap.enabledonly as an optional display preference. - After each change, verify completion, navigation, diagnostics, Explorer visibility, and search results that your work requires.
What to expect after the changes
The best outcome is narrower work: VS Code spends less effort searching irrelevant directories when opening a large folder, the JavaScript/TypeScript language service analyzes fewer non-source files, or text search skips dependency and generated trees. The trade-off is intentional omission from one feature, so every exclusion should be reviewed against the files you actually need. If the symptom does not match the setting’s scope, revert it and continue with the next branch of the decision procedure rather than stacking unrelated “performance” tweaks.
Recommended Free Tools
Frequently Asked Questions
Should I put every exclusion in User Settings?
No. Start with Workspace Settings for a project-specific slow folder or dependency tree. Use User Settings only when the same exclusion is appropriate across the projects you open.
Will disabling the minimap make VS Code faster?
It removes the minimap from the display, but the cited documentation presents it as a visual option and does not establish a performance improvement.
Why did IntelliSense stop finding a file after I added an exclusion?
The file may be outside the project scope you configured. Remove that path from the `exclude` list or narrow the pattern so only dependencies or generated output are excluded.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
