User and workspace settings
AI agents: See llms.txt for documentation discovery and navigation. Documentation articles are also available as Markdown by appending .md to the article URL. Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. User and workspace settings View as Markdown Ask in VS Code Ask in VS Code Insiders You can configure Visual Studio Code to your liking through its various settings.
Nearly every part of VS Code's editor, user interface, and functional behavior has options you can modify. VS Code provides different scopes for settings: User settings - Settings that apply globally to any instance of VS Code you open. Workspace settings - Settings stored inside your workspace and only apply when the workspace is opened. VS Code stores setting values in a settings JSON file. You can change settings values either by editing the settings JSON file or by using the Settings editor , which provides a graphical interface to manage settings.
User settings User settings are your personal settings for customizing VS Code. These settings apply globally to any instance of VS Code you open. For example, if you set the editor font size to 14 in your user settings, it will be 14 in all instances of VS Code on your computer. You can access your user settings in a few ways: Select the Preferences: Open User Settings command in the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) Select the User tab in the Settings editor ( ⌘, (Windows, Linux Ctrl+, ) ) Select the Preferences: Open User Settings (JSON) command in the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) Workspace settings Workspace settings are specific to a project and override user settings.
If you have specific settings that you want to apply to a specific project, you can use workspace settings. For example, for a backend server project, you might want to set the files.exclude setting to exclude the node_modules folder from the File Explorer. Note A VS Code "workspace" is usually just your project root folder. You can also have more than one root folder in a VS Code workspace through a feature called Multi-root workspaces .
Get more info about VS Code workspaces . VS Code stores workspace settings at the root of the project in a .vscode folder. This makes it easy to share settings with others in a version-controlled (for example, Git) project. You can access the workspace settings in a few ways: Select the Preferences: Open Workspace Settings command in the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) Select the Workspace tab in the Settings editor ( ⌘, (Windows, Linux Ctrl+, ) ) Select the Preferences: Open Workspace Settings (JSON) command in the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) Not all user settings are available as workspace settings.
For example, application-wide settings related to updates and security can not be overridden by Workspace settings. Settings editor The Settings editor provides a graphical interface to manage both user and workspace settings. To open the Settings editor, navigate to File > Preferences > Settings . Alternately, open the Settings editor from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) with Preferences: Open Settings or use the keyboard shortcut ( ⌘, (Windows, Linux Ctrl+, ) ).
By default, the Settings editor opens in a modal overlay on top of the editor area. You can change this behavior with the workbench.editor.useModal Open in VS Code Open in VS Code Insiders setting. When you open the Settings JSON file, it opens as a regular editor tab in the main window. When you open the Settings editor, you can search and discover the settings you are looking for. When you search using the search bar, the Settings editor filters the settings to only show those that match your criteria.
This makes finding settings quick and easy. VS Code applies changes to settings directly as you change them. You can identify settings that you modified by the colored bar on the left of the setting, similar to modified lines in the editor. In the example below, the Side Bar location and File Icon Theme were changed. The gear icon alongside the setting ( ⇧F9 (Windows, Linux Shift+F9 ) ) opens a context menu with options to reset a setting to its default value, and to copy the setting ID, copy a JSON name-value pair, or copy the settings URL.
Tip A settings URL enables you to navigate directly to a specific setting in the Settings editor from the browser. The URL is in the format vscode://settings/<settingName> , where <settingName> is the ID of the setting you want to navigate to. For example, to navigate to the workbench.colorTheme setting, use the URL vscode://settings/workbench.colorTheme . Settings groups Settings are represented in groups, so that you can navigate to related settings quickly.
There is a Commonly Used group at the top, which shows popular customization settings. In the following example, the source control settings are focused by selecting Source Control in the tree view. Note VS Code extensions can also add their own custom settings, and those settings are visible under an Extensions section. Settings editor filters The Settings editor search bar has several filters to make it easier to manage your settings.
To the right of the search bar is a filter button with a funnel icon that provides options to easily add a filter to the search bar. Modified settings To check which settings you have configured, there is a @modified filter in the search bar. A setting shows up under this filter if its value differs from the default value, or if its value is explicitly set in the respective settings JSON file. This filter can be useful if you have forgotten whether you configured a setting, or if the editor is not behaving as you expect because you accidentally configured a setting.
Other filters There are several other handy filters to help with searching through settings. Type the @ symbol in the search bar to discover the different filters. Here are some of the filters available: @ext : settings specific to an extension. You provide the extension ID such as @ext:ms-python.python . @feature : settings specific to a Features subgroup. For example, @feature:explorer shows settings of the File Explorer. @haspolicy : settings that are controlled by your organization . @id : find a setting based on the setting ID.
For example, @id:workbench.activityBar.visible . @lang : apply a language filter based on a language ID. For example, @lang:typescript . See Language-specific editor settings for more details. @tag : settings specific to a system of VS Code. For example, @tag:workspaceTrust for settings related to Workspace Trust , @tag:accessibility for settings related to accessibility, or @tag:advanced for advanced VS Code settings.
Advanced settings are intended for specialized scenarios. By default, advanced settings are hidden from search results unless you use the @tag:advanced filter. To always show advanced settings in the Settings editor, enable workbench.settings.alwaysShowAdvancedSettings Open in VS Code Open in VS Code Insiders . The search bar remembers your settings search queries and supports undo or redo ( ⌘Z (Windows, Linux Ctrl+Z ) / ⇧⌘Z (Windows, Linux Ctrl+Y ) ).
You can quickly clear a search term or filter with the Clear Settings Search Input button at the right of the search bar. Extension settings Installed VS Code extensions can also contribute their own settings, which you can review under the Extensions section of the Settings editor. You can also review an extension's settings from the Extensions view ( ⇧⌘X (Windows, Linux Ctrl+Shift+X ) ) by selecting the extension and reviewing the Feature Contributions tab.
Extension authors can learn more about adding custom settings in the configuration contribution point documentation . Settings JSON file VS Code stores setting values in a settings.json file. The Settings editor is
The rest of this page is on the live site.