How to Configure Windows Terminal for Use With WSL
A complete walkthrough setting up Windows Terminal specifically for a smooth WSL experience — default profile, font, and the settings that most commonly need adjusting.
Windows Terminal auto-detects installed WSL distros and creates profiles for them automatically, but a handful of deliberate configuration steps make the actual day-to-day experience meaningfully better.
Step 1: confirm Windows Terminal detected your WSL distro
Windows Terminal → dropdown arrow next to the + tab button →
your installed WSL distro should appear automatically as a profileIf a distro doesn’t appear, confirm it’s actually installed and registered (wsl --list --verbose from PowerShell) — Windows Terminal detects distros dynamically from WSL’s own registered distro list.
Step 2: set your WSL distro as the default profile
Windows Terminal → Settings → Startup →
Default profile → select your WSL distroThis makes opening a new Windows Terminal window or tab launch directly into your WSL distro’s shell, rather than PowerShell or Command Prompt.
Step 3: install and configure a Nerd Font for icon glyph support
Windows Terminal → Settings → your WSL profile →
Appearance → Font face → select an installed
Nerd Font variantIf your shell prompt or TUI tools use icon glyphs, a properly installed Nerd Font is a prerequisite — without one, these glyphs render as broken boxes or question marks regardless of any other configuration.
Step 4: set a sensible default starting directory
Windows Terminal → Settings → your WSL profile →
General → Starting directory →
leave blank/default to use the distro's own
default (typically your Linux home directory)Leaving this at its default generally gives the most intuitive behavior — opening directly into your Linux-side home directory rather than a Windows-side path.
Step 5: configure the color scheme
Windows Terminal → Settings → your WSL profile →
Appearance → Color schemeWindows Terminal ships several built-in schemes and supports importing custom ones — check here first if colors look wrong specifically inside Windows Terminal but correctly elsewhere.
Step 6: enable a comfortable scrollback buffer size
Windows Terminal → Settings → your WSL profile →
Advanced → History sizeA larger scrollback buffer is genuinely useful for reviewing long build or log output without needing to redirect it to a file first.
Step 7: set up keyboard shortcuts that don’t conflict with your shell or tmux
Windows Terminal → Settings → Actions →
review default keybindings for conflicts with
anything your shell or tmux configuration relies onWindows Terminal has its own global keybindings (new tab, split pane) that can occasionally overlap with shell or tmux prefix keys — worth checking specifically if you experience unexpected keybinding conflicts.
Step 8: use Windows Terminal’s own pane splitting alongside or instead of tmux
Alt+Shift+D split pane (default keybinding)Windows Terminal supports native pane splitting — some users prefer this for simple cases and reserve tmux specifically for session persistence across disconnects, since Windows Terminal’s own panes don’t survive closing the terminal application itself.
Step 9: verify everything works together
echo $TERM
neofetch # or any TUI tool, to visually confirm
# rendering and colors look correctWhy configuring this once is worth the up-front time
A properly configured Windows Terminal profile — correct default distro, working font, sensible color scheme — removes a whole category of small daily friction points (broken icons, wrong colors, opening into the wrong shell) that otherwise resurface repeatedly across every new terminal window until deliberately fixed.