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

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.

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.

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.

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.

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.

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.

If you want Terminal access, read how to install the code command in VS Code. For a wider setup, the VS Code for developers on Mac page covers shortcuts and debugging.