settings.json, is located in the user-specific application data directory at %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json. You can access this location by opening File Explorer, pasting that path into the address bar, and pressing Enter. This direct path allows you to view and edit configuration options for profiles, colors, and actions without navigating through the graphical interface.
Locating the Configuration Directory
Windows Terminal stores its user-level configurations in a specific folder within your local app data. Unlike older applications that might store settings in the registry or the main Program Files directory, this modern terminal uses a package-based storage system. To find the exact file, you need to resolve the environment variable%LOCALAPPDATA% which typically points to C:\Users\\AppData\Local .
Within that local data folder, there is a subdirectory named Packages. Inside Packages, look for a folder starting with Microsoft.WindowsTerminal_ followed by a unique identifier string such as 8wekyb3d8bbwe. The version suffix may vary slightly depending on updates, but the prefix remains constant. Navigate into that folder, then enter LocalState. Here you will find the settings.json file. If the file does not exist, creating it manually is possible, but it is safer to launch the terminal once to generate the default structure.
Editing Settings via the User Interface
For most users, modifying thesettings.json file directly is unnecessary. Windows Terminal provides a robust graphical user interface for managing these configurations. To access it, open Windows Terminal and click the dropdown arrow next to the new tab button, then select Settings. Alternatively, you can press Ctrl + , (comma) to open the settings page immediately.
This interface is divided into several sections including General, Profiles, Actions, and Startup. When you change a setting here, the application automatically writes the changes to the settings.json file in the background. This method prevents syntax errors that commonly occur when editing JSON files manually. For example, if you want to change the default profile or adjust color schemes, use the UI controls. However, for advanced customizations like defining new keyboard shortcuts or complex command-line arguments, manual editing of the JSON file may still be required.
Manual Editing Best Practices
If you choose to edit thesettings.json file directly, you must ensure that no instance of Windows Terminal is running. The application locks the file while active, preventing modifications. Close all terminal windows before opening the file in a text editor like Notepad or VS Code. Always create a backup of the original file before making changes. This allows you to restore the previous state if the new configuration causes the terminal to fail launching.
JSON is sensitive to syntax. A missing comma, an unclosed bracket, or a typo in a key name will cause the terminal to reject the file and revert to defaults. Pay close attention to the structure. The root object contains keys like profiles, actions, and schemes. Each profile has its own set of properties such as commandline, startingDirectory, and icon. When adding a new profile, ensure it is added to the list array within the profiles section. Incorrect placement will result in the setting being ignored.
Troubleshooting Missing Files
Sometimes thesettings.json file may appear missing even after installing Windows Terminal. This usually happens if the application has not been launched at least once after installation. The first run initializes the user profile and creates the necessary directories and files. Simply open the Start menu, search for "Windows Terminal," and launch it. Once it closes, check the LocalState folder again; the file should now be present.
If the file exists but appears empty or corrupted, you can reset the configuration. Delete the settings.json file and restart Windows Terminal. It will regenerate a fresh default configuration file. This is useful if you have made extensive changes and cannot determine what caused a malfunction. Note that resetting clears all custom profiles and preferences, so consider exporting your current settings if you wish to keep them.
Related Resources
While configuring the terminal, you might also need to manage other system components. For instance, if you are dealing with performance issues related to visual effects, you might explore how to reset video codecs as detailed in our guide on How to Reset the Windows 10 Video Codecs. Additionally, keeping your operating system up to date ensures you have the latest security patches and feature improvements for Windows Terminal, which can be found in our article on Windows Outdated: How to Update Your Operating System.Frequently Asked Questions
Can I store the settings file in a different location?
No, Windows Terminal does not support specifying a custom path for the settings.json file via command-line arguments or registry edits. The file must reside in the standard LocalState directory associated with the installed package. Workarounds involving symbolic links are unsupported and may break during updates.
Why did my settings disappear after updating?
Major updates sometimes introduce breaking changes to the schema, causing the terminal to ignore unrecognized keys. If you see a warning about invalid settings, review the release notes for that version. Typically, the terminal retains core settings but may discard experimental features or deprecated options introduced in previous versions.
How do I share settings between multiple computers?
You can copy the settings.json file from one machine to another, provided both machines have the same versions of Windows Terminal installed. Ensure that any paths specified in profiles, such as executable locations or starting directories, are valid on the target machine. Differences in drive letters or user names may require manual adjustment of those specific fields.
Is it safe to delete the LocalState folder?
Deleting the entire LocalState folder removes all user settings, history, and cached data for Windows Terminal. While this resets the application to its default state, it does not affect your system stability or other applications. After deletion, launching the terminal again will recreate the folder and default settings file automatically.
What happens if I edit the file while the terminal is open?
If you save changes to settings.json while Windows Terminal is running, the changes will not take effect until you restart the application. The terminal reads the configuration file only at startup. Some minor changes might trigger a reload, but relying on this behavior is unstable. Always close the terminal before editing to ensure consistency.