This guide shows you how to add a new profile in Windows Terminal on Windows 10, letting you launch different command-line tools (like PowerShell, Command Prompt, or WSL) from one app. You’ll learn the quick way using the settings UI and the more precise way by editing the settings.json file. No prior experience is needed, just a working Windows Terminal installation.
What You’ll Need
- Windows 10 (version 1903 or later recommended)
- Windows Terminal installed from the Microsoft Store (or via GitHub)
- The command-line application you want to add (e.g., PowerShell 7, Git Bash, or a Linux distro via WSL) already installed on your system
Step-by-Step
- Open Windows Terminal. Press the Start button, type “Terminal”, and click the app. If you have multiple profiles, you can open the default one.
- Open Settings. Click the dropdown arrow (chevron) next to the new tab button (the “+” icon) in the title bar, then select “Settings”. This opens the settings.json file in your default text editor (usually Notepad).
- Locate the “profiles” array. In the JSON file, find the section that starts with
"profiles". Inside it, there is a"list"array. Each item in that array is a profile object. You’ll add your new profile inside this list. - Find the GUID of your application (if needed). For most apps, you can use a command-line tool to generate a unique GUID. Open PowerShell or Command Prompt and run:
[guid]::NewGuid().ToString(). Copy the output (e.g.,{12345678-1234-1234-1234-123456789012}). You’ll use this as the"guid"for your new profile. If you’re adding a WSL distro, you can skip this step—Windows Terminal can auto-generate a GUID for WSL profiles. - Add a new profile object. At the end of the
"list"array, add a comma after the last profile (if there is one), then paste the following JSON block:{ "guid": "{your-generated-guid}", "name": "My New Profile", "commandline": "cmd.exe", "icon": "ms-appx:///Assets/TerminalIcon.ico" }Replace
{your-generated-guid}with the GUID you copied. Change"name"to something descriptive. For"commandline", put the path to the executable you want to run. For example:- Command Prompt:
cmd.exe - PowerShell 7:
pwsh.exe - Git Bash:
C:\Program Files\Git\bin\bash.exe - WSL (Ubuntu):
wsl.exe -d Ubuntu
- Command Prompt:
- Save the file. In Notepad, press Ctrl+S to save your changes.
- Reload Windows Terminal. Close the Settings tab and then close the terminal window entirely. Reopen Windows Terminal. Your new profile should now appear in the dropdown menu next to the “+” icon.
Common Mistakes
- Missing comma after the previous profile. If you add a new profile after an existing one, you must place a comma after the closing brace of the previous profile. Otherwise, the JSON is invalid and Windows Terminal will show an error.
- Using the same GUID twice. Each profile must have a unique GUID. If you copy an existing one, the new profile will overwrite the old one or cause a conflict.
- Incorrect command line path. If the path to your executable is wrong, the profile will open and immediately close. Double-check the path, especially for 32-bit vs 64-bit program files.
- Editing the wrong JSON. Windows Terminal uses a settings.json file. Make sure you are editing the one from the Settings menu, not a random file from the internet.
Tips
- Use the “Add new profile” button in the Settings UI (if you have a recent version). Click the dropdown arrow → “Settings” → then click the “Add new profile” button (a plus icon) at the bottom of the left sidebar. This auto-generates a GUID and gives you a form to fill in.
- Set a custom
"tabTitle"and"suppressApplicationTitle"to true if you want the tab to always show your name, not the program’s title. - Use environment variables in the command line, like
%USERPROFILE%, to make paths portable. - If you add a WSL distro, you can omit the GUID entirely—Windows Terminal will auto-generate one for you. Just add
"source": "Windows.Terminal.Wsl"and the distro name. - Backup your settings.json file before making big changes. Copy it to another folder.
Troubleshooting
Profile doesn’t appear in the dropdown. First, check that you saved the file and restarted Windows Terminal completely (not just closed the tab). If it still doesn’t show, open the settings.json again and verify that the JSON is valid. You can use an online JSON validator or look for red squiggles in Notepad. A common issue is a missing comma or an extra brace.
Profile appears but crashes immediately. This usually means the command line path is wrong or the executable can’t run. Test the command in a regular Command Prompt window to see if it works. For example, type pwsh.exe and see if it starts. Also, check that you have the correct path for 32-bit vs 64-bit applications.
“The file cannot be opened” error. This happens when the JSON is malformed. Windows Terminal will show a dialog with the specific error. Open the file and look for missing commas, unmatched braces, or extra quotes. If you can’t fix it, you can reset the settings by deleting the settings.json file (Windows Terminal will recreate it with defaults).
Profile runs but with wrong icon. The icon path might be incorrect. Use a full path to an .ico or .png file, or use the built-in icon path as shown in the example. For custom icons, you can use a path like C:\MyIcons\myicon.png.
Frequently Asked Questions
Q: Can I add a profile without editing the JSON?
A: Yes, in recent versions of Windows Terminal, you can use the “Add new profile” button in the Settings UI. It provides a form for name, command line, and other options. This is the easiest method for beginners.
Q: How do I add a WSL distribution as a profile?
A: If you have WSL enabled and a distro installed, Windows Terminal usually auto-detects it and adds a profile automatically. If not, you can add a profile with "source": "Windows.Terminal.Wsl" and set the "name" to your distro’s name.
Q: Why does my profile open a blank window and close?
A: This is almost always a wrong command line path. Double-check the executable path. For example, for Git Bash, the path is often C:\Program Files\Git\bin\bash.exe, not C:\Program Files\Git\git-bash.exe.
Q: Can I set a different starting directory for my profile?
A: Yes, add a "startingDirectory" property to the profile object. For example, "startingDirectory": "C:\Users\YourName".
Q: How do I make my new profile the default?
A: In the settings.json, find the "defaultProfile" property (it’s outside the profiles list) and set it to the GUID of your new profile. For example, "defaultProfile": "{your-guid}".
Q: Where is the settings.json file located?
A: It’s in a hidden folder. The typical path is %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json. You can also open it from the Settings menu.
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
- MacBook Charger Not Working? Fix It Now
- Fix Windows Cannot Be Installed to This Disk
- Zoom on iPhone & iPad: Host or Join a Meeting
- Fix iPhone SE 4 Unable to Activate: Step-by-Step
- Keep Important Emails From Getting Buried in iPhone Mail Categories
- How to Clear RAM on iPhone: Speed It Up