sodcalculator

10 Tech How-To

Windows Terminal Preview 1.6: Settings UI Explained

Guide 10-45821 · Updated · Step by step

Yes, Windows Terminal Preview 1.6 introduced a built-in settings interface, moving away from requiring users to manually edit the JSON configuration file. This graphical settings menu allows you to change profiles, appearance, and behavior directly within the app, making the terminal far more approachable for new users.

Background: Before the Settings Menu

Prior to version 1.6, Windows Terminal relied entirely on a single JSON file (typically named settings.json) for all configuration. Users had to locate this file in the app data folder, open it in a text editor, and carefully edit JSON syntax—a single misplaced comma could break the entire configuration. While this approach offered powerful flexibility, it presented a steep learning curve for those unfamiliar with JSON or command-line tools.

The developer team acknowledged this friction and began work on a graphical settings interface. The goal was to provide a visual way to modify common options while still retaining the JSON file for advanced users who wanted full control. The preview release of version 1.6 marked the first time this UI appeared in a public build, signaling a major step toward making the terminal more user-friendly.

How the Settings Interface Works

When you open Windows Terminal Preview 1.6 and press Ctrl + , (comma), the settings page appears as a new tab within the terminal window. The interface is split into two main sections: a sidebar on the left and a content area on the right.

The sidebar lists all your profiles (e.g., PowerShell, Command Prompt, WSL distributions) along with global settings options like “Startup” and “Interaction.” Clicking a profile shows its specific settings—such as the command line executable, starting directory, icon, color scheme, and font. The global sections let you adjust the default terminal application, the number of columns and rows for new windows, and keyboard shortcuts.

Every change you make in the UI is immediately written back to the settings.json file. This means you can switch between using the graphical interface and editing the JSON directly—both stay in sync. The UI essentially acts as a friendly wrapper around the same underlying configuration.

How to Access and Navigate

Getting to the settings is straightforward:

  • Launch Windows Terminal Preview 1.6.
  • Press Ctrl + , (comma) on your keyboard.
  • Alternatively, click the dropdown arrow next to the “+” (new tab) button and select “Settings.”

Once inside, you’ll notice the sidebar with your profiles. Click any profile to edit its properties. For example, to change the background image of a profile, select it, then scroll to the “Appearance” section and browse for an image file. The change applies immediately after you click “Save” (or in some builds, it applies as soon as you make the selection).

If you prefer to keep using the JSON file, you can still click the “Open JSON file” button at the bottom of the settings sidebar. This opens the file in your default text editor, letting you make advanced edits that the UI doesn’t yet expose.

Common Problems and Misconceptions

One frequent misconception is that the settings UI replaces the JSON file entirely. It does not—the UI is simply a front-end for the same file. If you manually edit the JSON while the settings tab is open, you may need to close and reopen the settings tab to see the changes reflected.

Another issue some users encounter is that the settings UI doesn’t appear in the stable version of Windows Terminal. That’s expected: the settings interface was introduced in the Preview channel first. If you’re on the stable release, you won’t see it until the feature is merged into a stable update. To get it early, you need to install Windows Terminal Preview from the Microsoft Store or GitHub releases.

Some users also report that certain settings they expect to find (like “default terminal application” on older Windows 10 builds) are missing. This is because some features depend on the OS version. For instance, the “default terminal” option only appears if your Windows version supports the underlying API.

Comparison: Preview vs. Stable

The Preview version of Windows Terminal includes features that are still being tested and may change before they reach the stable channel. The settings UI is a prime example. In Preview 1.6, the interface was functional but had some rough edges—for instance, the search box to filter settings was added later, and some options were not yet implemented.

Stable versions of Windows Terminal (starting from version 1.6, which was released later) include the settings UI in a more polished form. By the time it hit stable, the interface had been refined based on feedback from Preview users, with better keyboard navigation and more complete options.

If you’re a developer or enthusiast who wants the latest features and doesn’t mind occasional bugs, Preview is the way to go. For daily use, stable is safer and more reliable.

Cost and Availability

Windows Terminal is free and open source. Both the stable and Preview versions are available at no cost. You can download them from the Microsoft Store (search for “Windows Terminal” and “Windows Terminal Preview”) or from the official GitHub repository. The app runs on Windows 10 version 18362.0 or higher and Windows 11.

Because it’s open source, you can also build it yourself from source code, though most users will simply install the pre-built binaries. There are no paid tiers or premium features—everything is included in the free download.

Alternatives to the Built-in Settings

Even with the new UI, some users prefer third-party tools to manage their terminal configuration. For example, the wt command-line tool allows you to launch terminal windows with specific profiles and settings from the command line. You can also use PowerShell scripts to modify the JSON file programmatically, which is handy for automating setup across multiple machines.

Another alternative is to use a different terminal emulator altogether, such as Hyper, Alacritty, or ConEmu. Each has its own configuration approach—some use a GUI, others use text files. However, none integrate as seamlessly with Windows’ native shell environments as Windows Terminal does.

For most users, the built-in settings UI is sufficient and the most convenient option. It’s especially helpful for those who are new to terminal customization and don’t want to learn JSON syntax.

Frequently Asked Questions

Can I still edit settings.json if I use the UI?

Yes, absolutely. The UI and the JSON file are two views of the same configuration. You can switch between them at any time. Changes made in one will be reflected in the other after a refresh. The “Open JSON file” button in the settings sidebar makes this easy.

Why don’t I see the settings UI in my Windows Terminal?

If you’re using the stable version of Windows Terminal, the settings UI may not be available if your version is older than 1.6. The UI was first introduced in Preview 1.6, so you need to update to at least that version. Check your version by clicking the dropdown arrow and selecting “About.” If you’re on an older build, update via the Microsoft Store or GitHub.

Does the settings UI cover every option in the JSON file?

No, not yet. Some advanced options (such as custom key bindings with multiple modifiers, or certain experimental features) are still only accessible by editing the JSON directly. The UI covers the most common settings, but the team is gradually adding more options with each release.

Will my settings carry over from Preview to stable?

Yes, because both versions use the same settings.json file located in the same folder (%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState for Preview, and the similar path without “Preview” for stable). If you install stable, it will read the same settings file, so your profiles and preferences remain intact.

Is the settings UI available in Windows Terminal 1.7 and later?

Yes, the settings UI has been continuously improved and is present in all subsequent versions, both Preview and stable. Later versions added features like a search bar in settings and more profile options, making it even more comprehensive.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →