VS Code Profiles Guide: Set Up Per-Project Extensions, Settings and Workspace Switching

What Profiles actually do​

VS Code Profiles let you create sets of customizations and quickly switch between them or share them. Singh's article focuses on extensions, settings and visual tweaks. Microsoft's documentation shows the scope is wider. Microsoft's training material says each profile can include settings, extensions, key bindings, snippets, and tasks.

The feature has been around for a while. According to the VS Code 1.75 release notes (January 2023), Profiles became generally available then. The notes also said you can open multiple workspaces (folders) with different profiles applied at the same time.

Setting one up​

Singh's steps match the official flow:

1. Open the Profiles editor. Microsoft's documentation gives two routes: the File > Preferences > Profiles menu, or the Manage gear at the bottom of the Activity Bar.
2. Select New Profile. Give it a name, and optionally an icon.
3. Pick a starting point. You can copy an existing profile, use a built-in template, or create an empty profile. An empty profile has no settings, extensions or snippets.
4. Review the contents before you commit. Each template or profile you copy from can be browsed section by section. There is also a Preview button that opens a window with the new profile applied.
5. Select Create, then configure it as usual. You install or disable extensions, change settings and rearrange views. Those changes are stored in whichever profile is active.

You don't have to make every profile a full copy of your setup. You can include only some categories, such as settings and extensions, and let the rest fall back to the Default Profile. Microsoft's example is a profile that leaves out keyboard shortcuts and so uses the default ones.

Templates​

Singh mentions the Python, Node.js and Java templates. The documentation lists more, including Data Science, Doc Writer, Angular and Java Spring. The Python template, for instance, bundles extensions such as Ruff and the Remote Development pack, plus a few Python-specific settings. The Node.js template includes ESLint, Jest and Prettier, among others.

Templates are hosted externally. If they don't appear when you create a profile, check your internet connection.

The key boundary: folders, not file types​

Singh warns that opening a single Python or Java file won't switch profiles. The documentation explains why. Profiles attach to a folder or workspace, not to a language. When you create or select a profile, it is associated with the current folder or workspace. Whenever you open that folder, the workspace's profile becomes active. If you open another folder, the profile changes to that folder's profile, if one was already set. You can review these links in the Folders & Workspaces section of the Profiles editor.

Microsoft's workspace documentation adds a related point. Opening a file from the File menu puts you outside a workspace. In that mode, some VS Code capabilities are reduced. Don't expect per-project automation from a loose file.

So the practical routine is:

• Open the project folder.
• Choose the profile once, from the gear menu or the Profiles: Switch Profile command.
• Reopen the folder later and VS Code applies that profile again.

Two Python projects can have two different profiles. Two Java projects can too. The grouping is by project, not by language.

Sharing things across profiles​

Separation has a cost, which is duplicated setup. Two actions reduce it:

• Apply Extension to all Profiles, in the Extensions view, makes an extension available everywhere. Unchecking it reverses this.
• Apply Setting to all Profiles, in the Settings editor, shares a setting. Changes made in any profile carry to the others until you uncheck it.

Use these for the things you want everywhere, such as a Git helper or your preferred font.

One limitation to know: you can't inherit from another profile and override a few values. Copying a profile makes a one-time copy. It stays unlinked from its source, so later changes to the original don't flow through.

Telling windows apart​

Singh's favorite benefit is visual. Different themes and layouts make it obvious which project a window belongs to. That's a matter of taste, and nothing in the evidence suggests it measurably improves productivity. Still, it's a cheap technique if you often have several windows open.

VS Code also offers built-in cues. The Manage button shows the active profile's icon. If none is set, it displays a badge with the first two letters of the active profile's name. The profile name can also appear in the title bar. One community write-up (Rob O'Leary) shows that you can add the ${profileName} variable to the window.title setting.

Launching, syncing and storage​

• New window with a profile: use File > New Window with Profile.
• Command line: use the --profile option followed by the profile name, together with a folder or workspace. If the named profile doesn't exist, a new empty profile with that name is created. That behavior can quietly create a stray profile if you mistype a name.
• Settings Sync: profiles can move between machines when Profiles is checked in the Settings Sync configuration.
• Remote caveat: VS Code doesn't synchronize extensions to or from a remote window. That covers SSH, dev containers and WSL. Windows developers using WSL should test their setup rather than assume local and remote extension sets match.
• Storage: on Windows, profiles live under %APPDATA%\Code\User\profiles. For Insiders, the folder is Code - Insiders.

Other uses​

Profiles aren't only for languages. Microsoft's documentation suggests them for demos and teaching. A demo profile can carry a larger font, a higher zoom level and a high-visibility theme. That keeps your everyday setup untouched.

Two other uses are worth knowing:

• Troubleshooting: an Empty Profile switches off extensions and modified settings. That helps you tell whether a problem comes from an extension, a setting, or VS Code itself.
• Temporary profiles: the Profiles: Create a Temporary Profile command makes an empty profile that is deleted when VS Code closes. It's handy for trying an extension without committing.

To undo project associations, you can set a project back to the Default Profile. The Developer: Reset Workspace Profiles Associations command resets all associations without deleting any profiles.

Is it worth it?​

Singh himself says he hasn't used Profiles for long, and he admits that people with only a handful of extensions may not need them. That seems fair. Profiles pay off when your projects pull in conflicting extensions, formatters or settings. A leaner approach is to use workspace settings in .vscode/settings.json, which Microsoft says override global user settings for that workspace. Profiles go further by isolating extensions and UI layout as well.

If you want to try it, start small:

• Create one profile from a template that matches your main project type.
• Share the two or three extensions you use everywhere.
• Open a project folder and assign the profile.
• Keep an Empty Profile around for troubleshooting.

Afterward, the extension list is tidier and easier to read. It tells you why each extension is installed.