Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 40 ยท Extensions

Installing and Managing Extensions

Learn how the VS Code Extensions view works: search, install, update, disable per workspace, check publishers and keep your extension list safe and small.

Out of the box, VS Code is a fast editor with a lot of built-in features. Almost everything else, such as support for a new language, a linter, a theme or a database browser, arrives as an extension. Extensions are small packages written by Microsoft, by companies and by individual developers, and they plug into the editor through a documented API.

This lesson shows how to find, install, update, disable and remove extensions, and how to decide whether an extension is worth trusting. We cannot run VS Code on this site, so the examples describe real menus and commands, and the runnable code blocks are small, clearly labelled stand-ins that model the ideas.

The Extensions view

Open the Extensions view with the Activity Bar icon (four squares, one offset), or press Ctrl+Shift+X (Cmd+Shift+X on macOS). The view has three parts:

  • A search box that queries the Marketplace.
  • Collapsible lists: Installed, Recommended and sometimes Disabled.
  • A filter button (funnel icon) and a more actions (...) menu for sorting, updating all and showing built-in extensions.

Typing in the search box filters the Marketplace live. You can narrow it with special words:

Search text What it shows
@installed Extensions you already have
@enabled / @disabled By state
@outdated Installed extensions with a newer version
@builtin Extensions that ship with VS Code
@recommended Suggestions from the workspace and for your files
@category:"linters" A Marketplace category
@sort:installs Order by popularity

Clicking an extension opens its details page: the README, a Features tab, the changelog, and the Runtime Status once it is installed. Read the README before you install anything.

Installing and uninstalling

Click Install on the details page. Most extensions are active immediately; a few ask you to reload the window. You can also install from the command line, which is handy for setup scripts:

Terminal
code --list-extensions --show-versions
code --install-extension esbenp.prettier-vscode
code --uninstall-extension esbenp.prettier-vscode

Every extension has an ID of the form publisher.name. The ID is stable, so share IDs rather than screenshots when you tell a teammate what you use.

You can also install from a downloaded .vsix file: in the ... menu choose Install from VSIX.... Do this only for files you obtained from a source you trust.

Removing an extension is the Uninstall button on its page. If you only want a break, use Disable instead; it keeps your settings but stops the extension from running.

Enable and disable: global and per workspace

The gear icon on each extension offers Disable and Disable (Workspace). The second option is very useful: a heavy Python extension has no business running in a plain HTML project. Per-workspace choices are stored in the editor's own state, not in your project folder, so they do not pollute the repository.

Updates

By default VS Code checks for updates and installs them automatically. You can change that in settings:

JSON
{
  "extensions.autoUpdate": true,
  "extensions.autoCheckUpdates": true
}

If you prefer control, set extensions.autoUpdate to "onlyEnabledExtensions" or false, and use @outdated to update by hand. Reading a changelog before a major version bump is a good habit.

Judging an extension

An extension runs with the same permissions as VS Code itself: it can read your files, start processes and use the network. That makes the choice a security decision. Check these signals on the details page:

  1. Publisher. A blue verified-publisher check means the publisher proved ownership of a domain. It is not a guarantee of quality, but impersonators lack it.
  2. Install count and rating. Not proof, but a tiny count on a copy-cat name is a warning.
  3. Repository and issues. A linked source repository with recent activity is a good sign.
  4. Permissions of the idea. Does a "color theme" really need to run a language server? If the feature list looks wrong, skip it.
  5. Workspace Trust. Many extensions limit what they do in untrusted folders. Restricted Mode, which VS Code offers when you open a folder you did not create, keeps such extensions limited until you trust the folder.

Typosquatting happens: names like prettier-vscode and prettler-vscode can sit side by side. Always compare the publisher and the install count, not just the name.

A runnable stand-in: an extension inventory

The code below models the data you see in the Installed list. It is plain JavaScript, not the VS Code API; it only shows how you might audit your own list.

JS Stand-in: audit an extension list

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Stand-in: search filters like @installed

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Keeping the list small

Every enabled extension costs startup time and memory. Use the command Developer: Show Running Extensions to see activation times, and Developer: Startup Performance to see what slowed startup. Remove what you do not use, and prefer one good extension over three overlapping ones. Extension packs and recommendations cover what to keep.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which shortcut opens the Extensions view on Windows and Linux?

    Ctrl+Shift+X opens Extensions. Ctrl+Shift+E is the Explorer and Ctrl+Shift+P is the Command Palette.
  2. 2. You want a heavy extension to be off only in one project. What do you choose?

    Disable (Workspace) turns the extension off for the current workspace only and keeps it available elsewhere.
  3. 3. What does an extension ID such as esbenp.prettier-vscode consist of?

    An extension ID is publisher.name, which is stable across versions.
  4. 4. Why should you check the publisher before installing?

    Extensions run with broad permissions, so trust in the publisher matters. Unverified extensions can be installed; they are just riskier.

Summary

  • Extensions add languages, tools and themes; open the Extensions view with Ctrl+Shift+X.
  • Use @installed, @outdated and similar filters to manage your list.
  • code --install-extension publisher.name automates setup.
  • Disable per workspace to keep projects light.
  • Treat extensions as code you are choosing to run: check publisher, repository and need.

Next: Essential Extensions by Task