How to Audit VS Code Extensions and Remove Unused Ones

This guide walks you through reviewing every extension installed in Visual Studio Code, identifying the ones you no longer use, and uninstalling them cleanly. You’ll end up with a faster, more stable editor, fewer context-menu items, and less clutter in your command palette. No special tools are needed—everything is done through VS Code’s built-in interface and a couple of terminal commands.

What You’ll Need

• Visual Studio Code installed (any recent version, 1.80 or later is fine).
• Access to the terminal or command prompt on your computer.
• About 10–15 minutes of uninterrupted time.

Step-by-Step

1. Open the Extensions view. Click the square icon on the left sidebar (or press Ctrl+Shift+X on Windows/Linux, Cmd+Shift+X on macOS). This shows all installed extensions in a list.
2. Sort by installed date. In the Extensions view, click the “…� (More Actions) button at the top, then select “Sort by: Install Date�. This puts the oldest extensions first—those are often the forgotten ones.
3. Review each extension. Go through the list one by one. For each, ask: “Do I remember using this in the last month?� If you don’t recognize the name or purpose, click on it to see the description and last updated date. If it’s still unclear, skip it for now—you’ll test it later.
4. Mark candidates for removal. As you identify extensions you’re unsure about, right-click them and select “Disable�. This turns them off without uninstalling. Do this for all questionable ones.
5. Work normally for a day or two. Use VS Code as you usually would—edit files, run tasks, use keyboard shortcuts. Pay attention to any missing features or error messages. If nothing breaks, those disabled extensions are safe to remove.
6. Uninstall the disabled extensions. Go back to the Extensions view, click the filter icon, and select “Disabled�. For each one, right-click and choose “Uninstall�. VS Code removes them immediately—no restart needed, though some extensions may ask for a reload.
7. Check for orphaned extensions. Some extensions install companion tools or language servers that live outside VS Code. To see them, open a terminal and run code --list-extensions. This shows every extension ID. Compare it with what’s in the Extensions view—if you see extras, they’re likely dependencies of other extensions. Leave those alone unless you’ve uninstalled the parent extension.
8. Clean up extension settings. Uninstalling an extension does not remove its settings from your settings.json file. Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P), type “Preferences: Open Settings (JSON)â€�, and look for keys that reference the removed extensions. Delete those lines carefully—only the ones you’re sure belong to uninstalled extensions.
9. Clear the extension cache (optional). If you want to reclaim disk space, delete the entire extensions folder. On Windows it’s %USERPROFILE%\.vscode\extensions, on macOS/Linux it’s ~/.vscode/extensions. VS Code will recreate it on next launch, and you can reinstall only what you need. This is a nuclear option—do it only if you’re comfortable reinstalling everything.
10. Set a regular review schedule. Add a recurring calendar reminder every 3–6 months to repeat this audit. Extensions accumulate quickly, especially after trying new tools or following tutorials.

Common Mistakes

• Uninstalling extensions that are dependencies. Some extensions, like language packs or debuggers, are required by other extensions. If you remove a dependency, the parent extension may break. Always check the extension’s page for “Extension Dependenciesâ€� before removing.
• Deleting settings for extensions that are still installed. If you remove a setting line for an active extension, it reverts to default, which may change behavior unexpectedly. Only delete settings for extensions you’ve fully uninstalled.
• Disabling instead of uninstalling, then forgetting. Disabled extensions still take up disk space and may still load in some contexts. If you’re done testing, uninstall them—don’t leave them disabled forever.
• Removing extensions that are part of a workspace recommendation. If you open a project with a .vscode/extensions.json file, VS Code may suggest re-installing removed extensions. That’s fine—it means the project needs them. Just reinstall when prompted.

Tips

• Use the “Outdatedâ€� filter. Extensions that haven’t been updated in over a year are more likely to be abandoned or incompatible with newer VS Code versions. Review those first.
• Check the extension’s marketplace page. Look at the number of installs and recent reviews. A low install count or negative recent reviews are red flags.
• Keep a “coreâ€� list. Write down the 5–10 extensions you truly rely on. When you’re tempted to install a new one, ask if it replaces something you already have.
• Use profiles for different workflows. VS Code Profiles let you have separate extension sets for, say, web development and Python. That way you don’t need to disable extensions when switching contexts—just switch profiles.
• Sync your extensions list. If you use Settings Sync, your extension list is stored in the cloud. After cleaning up, sign in to sync to ensure your other devices get the trimmed list.

Troubleshooting

• VS Code won’t start after uninstalling an extension. Launch VS Code from the terminal with code --disable-extensions. This starts without any extensions. Then re-enable or reinstall the one you removed—it was likely critical. If it still fails, move your settings.json to a backup location and try again.
• An extension reappears after uninstalling. This usually means it’s a dependency of another extension. Check the parent extension’s page and uninstall that instead, or leave the dependency in place.
• Extension list in terminal shows more than in the UI. Some extensions are installed globally or per-user. Use code --list-extensions --show-versions to see details. If you see an extension you don’t recognize, look it up online before removing—it might be a required component.
• Settings.json has errors after deleting lines. VS Code will show a red squiggle and a notification. Open the file, check for missing commas or brackets, and undo if needed. If you’re unsure, use the Settings UI (not JSON) to search for the extension’s name and remove entries there—it’s safer.
• Keyboard shortcuts stop working. Some extensions add keybindings. After uninstalling, check your keybindings.json for references to the removed extension and delete those lines.

Frequently Asked Questions

How do I see how many extensions I have?

Open the Extensions view—the count is shown in the sidebar next to “Installedâ€�. You can also run code --list-extensions | wc -l (macOS/Linux) or code --list-extensions | find /c /v "" (Windows).

Can I undo an uninstall?

No, uninstalling is permanent. But you can reinstall any extension from the marketplace by searching its name and clicking “Install�. If you’re unsure, disable first, test, then uninstall.

Does uninstalling an extension delete my configuration for it?

No. Your settings, keybindings, and workspace files remain. You may need to manually remove those settings if you don’t want them.

Are there extensions that are safe to remove without checking?

Most extensions are independent. The main exceptions are language packs (like Spanish Language Pack) and debugger extensions that other tools depend on. If an extension has “Dependencies� listed on its page, check those first.

Will removing extensions make VS Code noticeably faster?

Yes, especially if you have many extensions that run on startup. Each extension consumes memory and CPU. Removing unused ones reduces startup time and improves responsiveness, though the effect varies.

What’s the difference between disabling and uninstalling?

Disabling turns off the extension but keeps it installed. Uninstalling removes it entirely. Disabling is useful for testing; uninstalling is for permanent removal.

Related

• Convert Milliseconds to Date and Time
• Work Done Formula: How to Calculate Work in Physics
• Grams to Grams Formula: Convert and Scale Mass