What the editor does
The editor turns one 20-color palette into six native terminal configurations. Adjust the 16 ANSI slots plus background, foreground, cursor, and selection; the preview and contrast checks update immediately.
Exports and install paths
Every export uses the same palette, so colors stay consistent when you switch terminals. The table lists the usual install location for each terminal; the full steps live on the terminal page.
| Family | Install location |
|---|---|
| Herdr App | ~/.config/herdr-app/themes/<name>.json |
| Ghostty | ~/.config/ghostty/themes/<name> |
| Alacritty | ~/.config/alacritty/alacritty.toml |
| Kitty | ~/.config/kitty/<name>.conf |
| iTerm2 | *.itermcolors → Profiles → Colors |
| Windows Terminal | settings.json → schemes[] |
Privacy and sharing
The editor needs no account and does not upload your palette. Color math, previews, and exports run in the browser; a share link only stores the palette state in the URL hash.
Submit to the catalog
Fill in family, slug, and name, then press Submit. GitHub's new-file page opens with the full JSON prefilled; review it, open a pull request, and CI validates the schema, duplicate colors, contrast, and the full build. See the contribution guide for the workflow.
Frequently asked questions
Is the terminal theme editor free?
Yes. The editor runs locally in your browser, requires no account, and does not upload your palette to a server.
Which formats can I export?
Herdr App JSON, Ghostty, Alacritty, Kitty, iTerm2, and Windows Terminal. Every format uses the same 16-color ANSI palette.
Is my palette uploaded anywhere?
No. Color math, previews, and exports happen in the browser. A share link only puts the palette state in the URL hash.
How do I submit a theme to the catalog?
Fill in family, slug, and name, then press Submit. The editor puts the full theme JSON into the new-file value parameter on GitHub; review it, open a pull request, and CI validates the schema, duplicate colors, and build.