# How to install an extension in VS Code on Mac: step by step for 2026

> How to install an extension in VS Code on Mac: open the Extensions view with Shift-Command-X, click Install, and fix common errors.

URL: https://www.lazur.app/how-to/install-an-extension-in-vs-code
Updated: 2026-11-09

To install an extension in VS Code on Mac, press Shift-Command-X, search for the extension, open its page, and click Install. For a .vsix file you already downloaded, use Install from VSIX in the Extensions view or the Command Palette.

## Quick answer

- Press Shift-Command-X, search for the extension, open its details page, and click Install.
- Check the publisher name first. Since VS Code 1.97, a third-party publisher needs your confirmation on the first install.
- For a .vsix file, use Install from VSIX. For Terminal installs, set up the code command first.
- If an install fails with connect ETIMEDOUT, check your proxy settings before you try again.

Applies to: VS Code on macOS, Apple silicon and Intel, current stable build 1.145. Time: 5 min. Difficulty: Easy.

## What you need

- VS Code installed in the Applications folder
- Internet access to the Extension Marketplace
- A macOS version that your VS Code release supports
- The publisher name or ID of the extension you want, if you know it

## How to Install a VS Code extension on a Mac in VS Code on a Mac

1. **Open Visual Studio Code.** Open VS Code from the Applications folder, or from Launchpad if you pinned it there. Wait for the main window to appear before you continue. If the disk image is still open, eject it first.
2. **Open the Extensions view.** (View > Extensions) Shortcut: ⇧⌘X. Press Shift-Command-X. You can also choose View > Extensions from the menu bar, or click the Extensions icon in the Activity Bar. The Extensions view opens in the sidebar with a search box at the top.
3. **Search for the extension.** Type the extension name in the search box, for example Python. For an exact match, type @id:publisher.name, such as @id:ms-python.python. Each result shows its publisher name under the title.
4. **Open the details page.** Click the extension in the results. Its details page opens in the editor area. Read the description and check the publisher before you install anything.
5. **Click Install.** Click the Install button on the details page. Wait for the install to finish. The button changes to a Manage gear button when it is done.
6. **Confirm the trust prompt if it appears.** Since VS Code 1.97, the first install from a third-party publisher shows a dialog. Confirm that you trust the publisher only if the name matches the one you checked on the details page.
7. **Enable the extension if needed.** Click the Manage gear button and choose Enable, or Enable (Workspace), if the extension is disabled. To list disabled extensions, search for @disabled in the Extensions view.
8. **Install a .vsix file (optional).** (View > Command Palette) Shortcut: ⇧⌘P. Press Shift-Command-P, type Install from VSIX, and choose Extensions: Install from VSIX. Pick the .vsix file in the window that opens. You can also use Install from VSIX in the dropdown at the top of the Extensions view.
9. **Set up the code command (optional).** Shortcut: ⇧⌘P. Press Shift-Command-P, type shell command, and run Shell Command: Install 'code' and optionally 'copilot' commands in PATH. Answer the Copilot prompt with Yes, No, or Escape. Restart Terminal, then run code . in a project folder to confirm it works.
10. **Confirm the install.** Open the Extensions view, search for the extension name, and check that it shows the Manage gear. Open a file type the extension supports and test one feature. If nothing changes, use the troubleshooting list below.

## What you need before you install

You need Visual Studio Code on your Mac and an internet connection. VS Code supports both Apple silicon and Intel Macs. Microsoft publishes three macOS downloads: Apple silicon, Intel, and Universal. The Universal build is meant for both chip types, so pick it when you are unsure.

Newer VS Code versions need newer macOS releases. Microsoft's FAQ says so, but it does not list a minimum version. The latest stable release is VS Code 1.145, dated November 4, 2026. The menu labels in this guide come from Microsoft's docs, so your screen may differ slightly on an older build.

- Move VS Code into Applications. Open the .dmg and drag Visual Studio Code.app into the Applications folder.
- Open VS Code from Applications, not from the disk image.
- Write down the publisher name of the extension you want, if you know it.
- If you sit behind a firewall, allow marketplace.visualstudio.com, *.gallery.vsassets.io, and *.gallerycdn.vsassets.io.

## Find the Extensions view on a Mac

You have three ways in. Press Shift-Command-X, choose View > Extensions from the menu bar, or click the Extensions icon in the Activity Bar. The Activity Bar is the strip of icons along the edge of the window. All three open the same view. The keyboard shortcut is the fastest once it becomes habit.

![Developer at a Mac laptop learning how to install an extension in VS Code](https://images.lazur.app/content-images/howto/install-an-extension-in-vs-code/how-to-install-an-extension-in-vs-1-3e7227.jpg)

## Search for an extension by name or by ID

Type a name in the search box at the top of the Extensions view. Many extensions have similar names, so read the publisher line under each result. For an exact match, search with @id:publisher.name. The ID joins the publisher and the extension name with a period. For example, @id:ms-python.python finds the Python extension from Microsoft.

If you copied an ID from a README, a team chat, or a project file, the ID search saves time. It skips the lookalikes entirely. Names change more often than IDs, so the ID is the safer thing to keep in your notes.

## Read the details page before you click Install

Select an extension and its details page opens in the editor area. Read the description. Check who published it. Ask yourself whether it does the job you need. A short check takes less than a minute and prevents most wrong installs.

- The publisher name matches the company or person you expect.
- The description matches the task you have in mind.
- The ID matches the one in your notes or in a project file, such as .vscode/extensions.json.
- You expect a trust prompt if the publisher is a third party.

## Confirm the trust prompt and finish the install

Starting in VS Code 1.97, the first install from a third-party publisher shows a dialog. The dialog asks you to confirm that you trust the publisher. Read the name in the dialog. Confirm only if it matches the name you checked on the details page.

After you confirm, wait for the install to finish. The Install button changes to a Manage gear button when it is done. Until then, do not click it again. A second click adds no value and can confuse the status you are reading.

## Enable, disable, and find extensions again

The Manage gear opens a menu. If an installed extension does nothing, it may be disabled. Search for @disabled in the Extensions view to list disabled extensions. Then open the gear menu and choose Enable. Choose Enable (Workspace) if you want the extension active only in the current project.

- **75.9%** of all respondents in the 2025 Stack Overflow Developer Survey said they use Visual Studio Code ([source](https://survey.stackoverflow.co/2025/technology))

About three in four respondents to the 2025 Stack Overflow survey said they use VS Code. That is a large audience, so the steps in this guide stick to what Microsoft documents.

## Install an older version or a pre-release build

Right-click an extension and choose Install Another Version to pick an older build. This helps when the newest release breaks your setup. Use the dropdown arrow on the Install button to choose Install Pre-Release Version. Microsoft does not give a version number for pre-releases on that page.

Pre-release builds can behave differently from the stable release. Use them on a test project first. Keep your normal projects on the stable build until you know the pre-release works for you.

## Install an extension from a .vsix file

A .vsix file is an extension package you already have on disk. Use Install from VSIX from the dropdown in the Extensions view. You can also run Extensions: Install from VSIX from the Command Palette. Press Shift-Command-P to open the Command Palette, type the command name, and pick your file.

VSIX installs have auto-update turned off by default. A package you installed from a file will not update itself. Check the publisher's download page yourself when you want a newer build.

| Method | Where to start | Best for |
| --- | --- | --- |
| Marketplace search | Extensions view, Shift-Command-X | Most extensions |
| Specific version | Right-click the extension, then Install Another Version | Rolling back a broken update |
| Pre-release | Dropdown arrow on the Install button | Testing early builds |
| VSIX file | Extensions view dropdown or Shift-Command-P | Packages you already have on disk |
| Command line | Terminal: code --install-extension | Scripts and repeat setups |

_Five ways to add an extension in VS Code on Mac, from Microsoft's docs._

## Use the code command from Terminal

The Terminal route needs the code command. Press Shift-Command-P, type shell command, and run Shell Command: Install 'code' and optionally 'copilot' commands in PATH. The Copilot prompt accepts Yes, No, or Escape. Answer as you like, then restart Terminal.

After the restart, run code --install-extension followed by an extension ID, or by the path to a .vsix file. Insiders builds use code-insiders instead of code. If you use both builds, check which command you typed before you install.

## Fix a not compatible error

Some extensions refuse to install because they need a newer VS Code. Microsoft's docs do not explain this error. Treat the steps here as a starting point, not as an official fix. Update VS Code to the latest stable build, then try the install again.

If the error stays, read the extension's Marketplace page for its requirements. Then try an older build with Install Another Version. Older builds sometimes match an older VS Code, so test one at a time.

![Person typing on a MacBook while searching for a VS Code extension](https://images.lazur.app/content-images/howto/install-an-extension-in-vs-code/how-to-install-an-extension-in-vs-2-56f632.jpg)

## Fix network errors such as connect ETIMEDOUT

A message that says connect ETIMEDOUT during install usually means your Mac reaches the internet through a proxy. Microsoft's network page covers proxy support in detail. Your IT team can tell you the proxy address. Ask before you change any setting.

Older proxy settings still exist in VS Code. They include http.proxy, http.proxyStrictSSL, and http.proxyAuthorization. Change them only with a known address. A wrong value keeps the install failing and can hide the real cause.

## Work with Gatekeeper warnings and missing files

If VS Code itself will not open, check the file first. Microsoft's FAQ says missing files can come from antivirus quarantine settings, so check those and reinstall. The docs do not cover Gatekeeper warnings, so this guide gives no fix for them.

## Extensions in VS Code for the Web and remote windows

VS Code for the Web runs at vscode.dev. It runs only some extensions in the browser. Extensions that cannot run there show a warning icon with a Learn Why link. Installed extensions stay in browser local storage, and Settings Sync keeps them close to your desktop setup.

Remote windows are a separate case. Extensions do not sync to SSH, dev container, or WSL windows. If you work over SSH or in a dev container, install the extension again inside that remote window.

## Mistakes people make on the first install

- Installing a lookalike. Two extensions can share a name, so check the publisher line.
- Mixing Insiders and stable. Insiders uses code-insiders in Terminal, so the command differs.
- Assuming a disabled extension is missing. It still shows as installed until you enable it.
- Expecting a .vsix file to update itself. Auto-update is off by default for VSIX installs.
- Skipping the trust dialog. Read the publisher name before you confirm.

![Programmer at a desk checking the publisher before installing an extension](https://images.lazur.app/content-images/howto/install-an-extension-in-vs-code/how-to-install-an-extension-in-vs-3-c34c38.jpg)

## What to do after the extension is installed

Open a project and test the extension on a small file first. Confirm that it does the job before you rely on it for real work. If you use VS Code all day, pin it to the Dock. Control-click the Dock icon and choose Options > Keep in Dock. The step-by-step guide is at [keep VS Code in the Dock](https://www.lazur.app/how-to/keep-vs-code-in-the-dock-in-vs-code).

If you want Terminal access, read [how to install the code command in VS Code](https://www.lazur.app/how-to/install-the-code-command-in-vs-code). For a wider setup, the [VS Code for developers on Mac](https://www.lazur.app/for/developers/vs-code) page covers shortcuts and debugging.

## Shortcuts

- Open the Extensions view: ⇧⌘X
- Open the Command Palette: ⇧⌘P
- Find disabled extensions in the search box: @disabled

## If it does not work

- **Install fails with connect ETIMEDOUT** Your Mac probably reaches the internet through a proxy. Read Microsoft's network connections page for proxy support. Behind a firewall, allow marketplace.visualstudio.com, *.gallery.vsassets.io, and *.gallerycdn.vsassets.io. Ask your IT team before you change proxy settings.
- **Installed extension does nothing** It is probably disabled. Search for @disabled in the Extensions view, click the Manage gear, and choose Enable, or Enable (Workspace) for the current project only.
- **Terminal says command not found: code** Run Shell Command: Install 'code' and optionally 'copilot' commands in PATH from the Command Palette, then restart Terminal. Insiders users run code-insiders instead.
- **Extension says it is not compatible with this VS Code version** Microsoft's docs do not explain this error. Update VS Code to the latest stable release and try again. If it still fails, read the extension's Marketplace page and try an older build with Install Another Version.
- **VS Code will not open or a file looks missing** Check your antivirus quarantine settings, then reinstall VS Code. Newer VS Code releases need newer macOS versions, so check your macOS version as well.
- **Extension is missing in an SSH or dev container window** Extensions do not sync to remote windows. Install the extension again inside that remote window.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Where is the Install button?”: Lazur draws a circle and a label around the Install button on the details page, so you can find it without hunting through the window. (Points at it)

## FAQ

### Where is the Extensions view in VS Code on Mac?

Press Shift-Command-X, choose View > Extensions from the menu bar, or click the Extensions icon in the Activity Bar. All three open the same view.

### Why does VS Code ask me to trust a publisher?

Starting in VS Code 1.97, the first install from a third-party publisher shows a trust dialog. Confirm only after you check that the publisher name matches the one you expected.

### What is the difference between Install Another Version and Install Pre-Release Version?

Install Another Version lets you pick an older build from the list. Install Pre-Release Version installs a build the publisher marks as pre-release. Pre-release builds can change more often, so test them first.

### Can I install an extension in VS Code for the Web on a Mac?

Only some extensions run at vscode.dev. Extensions that cannot run there show a warning icon. Installed extensions are stored in browser local storage.

### Do extensions I install on my Mac show up in SSH or dev container windows?

No. Extensions do not sync to remote windows such as SSH, dev containers, or WSL. Install them again inside each remote window you use.

### Can I install an extension without using the Extensions view?

Yes. Set up the code command with Shell Command: Install 'code' and optionally 'copilot' commands in PATH. Then run code --install-extension with an extension ID or a .vsix path.

### Does VS Code have a version for Apple silicon Macs?

Yes. Microsoft lists separate Apple silicon, Intel, and Universal macOS downloads. The Universal download is meant for both chip types, so it is the safe pick if you are unsure.

## Sources

1. [Extension Marketplace: Visual Studio Code docs](https://code.visualstudio.com/docs/configure/extensions/extension-marketplace), Microsoft, checked 2026-11-09
2. [Visual Studio Code on macOS: docs](https://code.visualstudio.com/docs/setup/mac), Microsoft, checked 2026-11-09
3. [Visual Studio Code 1.145 release notes](https://code.visualstudio.com/updates/v1_145), Microsoft, checked 2026-11-09
4. [VS Code for the Web: docs](https://code.visualstudio.com/docs/setup/vscode-web), Microsoft, checked 2026-11-09
5. [VS Code FAQ: docs](https://code.visualstudio.com/docs/supporting/faq), Microsoft, checked 2026-11-09
6. [Network connections in VS Code: docs](https://code.visualstudio.com/docs/setup/network), Microsoft, checked 2026-11-09
7. [Stack Overflow Developer Survey 2025: Technology](https://survey.stackoverflow.co/2025/technology), Stack Overflow, checked 2026-11-09