How to Compare and Choose a Windows Terminal Theme

Updated

Windows Terminal Themes (windowsterminalthemes.dev) is a browser-based gallery of hundreds of color schemes for Windows Terminal. To choose one, narrow the list with the Dark or Light filter, click through candidate themes, and judge each on the same three previews: the codeblock, the terminal mock-up, and the color swatches. Pick the theme whose preview stays readable for the text you actually look at all day — usually code and shell output — rather than the one with the most striking palette.

What the site gives you to compare with

The gallery is a single-page app, so you need JavaScript enabled for it to render. Once loaded, the comparison surface is consistent across every theme:

  • Dark / Light filters — two selectors at the top of the list. Use them first to cut the catalog roughly in half.
  • Codeblock preview — shows syntax-highlighted sample code (the page's own sample includes CRA compile output, Cypress run, and Jest pass/fail lines).
  • Terminal preview — a mock terminal showing shell-style output, including a local dev server message with http://localhost:3000/themes and a network URL.
  • Colours preview — the full swatch set for the theme, so you can see the 16 ANSI colors plus background and foreground at a glance.
  • Theme name and list navigation — a scrollable name list (3024 Night, Aardvark Blue, Abernathy, Adventure, Afterglow, and on through Dracula, Gruvbox, Kanagawa, Material, and many more), with Prev / Next controls and a credit line for the current theme.

Because every theme is shown through the same previews, you are comparing like with like. That is the main reason to use this site instead of pasting schemes one at a time into your terminal.

A practical comparison workflow

  1. Filter by background first. If you work in a bright room or prefer high contrast, start with Light; otherwise start with Dark. This is the single biggest cut.
  2. Scan names you recognize. Familiar families — Dracula, Gruvbox, Catppuccin (Frappe / Macchiato / Mocha), Solarized, Material, One-style variants, Tokyo-Night-adjacent options like Kanagawa — give you a known baseline. If you already like one of these elsewhere, compare its variants here rather than starting from scratch.
  3. Read the codeblock, not the palette. Ask: can I tell a string from a keyword from a comment without squinting? Syntax highlighting is where most themes fail.
  4. Check the terminal preview for prompt and output legibility. Look at the dim/comment colors and the "failed" style lines — those are the ones that disappear in low-contrast themes.
  5. Open the Colours view. Confirm the ANSI colors are distinguishable from each other. Red vs. magenta and blue vs. cyan are the usual collisions.
  6. Shortlist two or three, then switch between them using Prev / Next to compare back-to-back. Side-by-side beats memory.
  7. Copy the one you want and apply it in Windows Terminal's settings.

What to weigh when two themes look equally good

Dimension What to look for Why it matters
Contrast Foreground clearly separated from background Long reading sessions; low contrast causes fatigue
Syntax distinctness Keywords, strings, comments, types all differ You read code more than you read the palette
ANSI separation 16 colors mutually distinguishable ls, git diff, test output rely on them
Dim/comment color Still visible, not near-background Log lines and comments are often dimmed
Accent brightness Bright colors not blown out Errors and warnings should stand out, not glare
Family consistency Matches themes you use in editors Reduces context switching

A theme that wins on palette aesthetics but loses on the dim-color row is usually the wrong pick for a terminal you stare at daily.

Common sticking points

  • Blank page or no theme list. The app requires JavaScript; if the list never appears, that is the cause, not a missing theme.
  • Preview looks different from your real terminal. The preview uses the site's own font and rendering. Your terminal's font, ligatures, and opacity will change the result — treat the preview as a color guide, not a pixel-accurate mock-up.
  • Two names look identical. Some entries are near-duplicates or variants (for example the Catppuccin set, or Dracula vs. Dracula+). Compare them directly with Prev / Next rather than assuming they are the same.
  • You like the colors but not the contrast. Many families ship both a standard and a "hard"/darker variant (GruvboxDark vs. GruvboxDarkHard is the classic case). Try the sibling before abandoning the family.

Choosing, in one line

Filter dark or light, shortlist by familiar family names, then pick the theme whose codeblock and terminal previews you can read fastest — and confirm the ANSI swatches are all distinct before you copy it.