macos-terminal-themes: Color Schemes for the Default macOS Terminal.app
Color schemes for default macOS Terminal.app
At a glance
- What is it?
- A port of the iTerm2 color scheme collection into .terminal profile files that Terminal.app can import directly. It solves a narrow problem well, and it is not a terminal emulator, a shell framework or a theme manager.
- Who is it for?
- Adopt this if you use the stock macOS Terminal.app and want the iTerm2 scheme collection without installing iTerm2 or a shell framework. Do not adopt it if you need a theme manager, Windows or Linux support, or a licence you can verify before shipping it inside a product.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 80 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- lysyi3m/macos-terminal-themes6,577 ★ · +50
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| lysyi3m/macos-terminal-themes | 6.5k | 6.6k |
50 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The gap macos-terminal-themes fills: iTerm2 schemes on stock Terminal.app
Terminal.app ships with a small set of profiles. The README names several of them directly, listing "Pro", "Basic" and "Grass" as default themes that are deliberately excluded because you already have them. Everything else in the collection comes from outside. The README states the themes were initially ported from the iTerm2 color schemes collected by @mbadolato, which is the reference collection most people encounter when they go looking for a dark scheme.
The audience is narrow and specific. If you already run iTerm2, you do not need this repository: you would import the original scheme files instead. If you run a terminal emulator on Linux, the .terminal profile format is not what you want. This project exists for the person who keeps the built-in Terminal.app, either by preference or because a managed Mac restricts what can be installed, and wants a scheme that did not ship with the OS.
That constraint is the whole value proposition. Terminal.app profile files are plist documents that carry background color, foreground color, cursor color and the full ANSI palette. Producing a correct one by hand means entering sixteen color values in a GUI. The repository does that conversion in bulk, and the screenshots/ directory provides a preview image per scheme so you can judge a palette before importing it.
What a .terminal file actually is, and what the repository contains
The top level of the repository holds .gitignore, CONTRIBUTING.md, README.md, screenshots/, themes/ and tools/. The themes/ directory is the deliverable. It contains .terminal files, one per scheme, named after the scheme: the README links "3024 Day.terminal", "3024 Night.terminal", "AdventureTime.terminal", "Afterglow.terminal", "Alabaster.terminal", "AlienBlood.terminal" and many more, with spaces preserved in names like "Atom One Light.terminal", "Ayu Light.terminal", "Ayu Mirage.terminal", "Belafonte Day.terminal", "Bright Lights.terminal" and "Chalice Dark.terminal".
A .terminal file is not a script and not a plugin. It is a settings profile that Terminal.app reads and stores. Importing one adds a profile to your Terminal settings; it does not modify your shell configuration, your dotfiles, your prompt or your font. That separation explains the prerequisite the README calls out: since terminal themes are just color schemes, color formatting for your shell has to be enabled first, and the README points to a specific comment on issue 1 for the details. A profile can define the exact palette your shell uses, but if nothing in your shell emits escape sequences for color, the window stays monochrome.
The tools/ directory exists alongside themes/ and, according to the README, supports the contribution path: CONTRIBUTING.md documents the steps and the tools that generate the previews. So the screenshots are not hand-captured artifacts; they are produced by repository tooling. The primary language listed for the repository is Swift, which is consistent with macOS-native tooling rather than a cross-platform build.
Installing a macOS terminal theme: import through Settings or double-click
There is nothing to compile and no package to install. The README says to clone or download the repository first, then work from the themes/ folder.
git clone https://github.com/lysyi3m/macos-terminal-themes.git
cd macos-terminal-themes
ls themes/ | headThe listing should show .terminal files such as "3024 Day.terminal" and "AdventureTime.terminal". From there the README gives two routes. The first is the Settings route: open Terminal > Settings > Profiles, or press cmd+,, click the ... menu below the profile list, choose Import..., and select a .terminal file from themes/. Keep the imported profile selected and click Default, then open a new window with cmd+N. The second route is to double-click a .terminal file, which opens a new window with that theme; the README says to make it stick with Shell > Use Settings as Default.
There is one macOS behavior to expect. The README notes that macOS quarantines files downloaded from the internet, so opening one can fail with a security warning. The documented workarounds are to right-click the file and choose Open, or to import it through the settings path instead. Cloning with git rather than downloading a zip avoids the quarantine flag in the first place, which is why the clone route above is the cleaner starting point.
After importing, verify the result rather than assuming it. Open a new window and run a command that produces colored output, such as a directory listing with color enabled or a git status in a repository with modified files. If everything renders in a single color, the profile imported correctly and the shell side is what needs attention.
Two limitations that decide whether this is the right tool
The first limitation is that this is a file collection, not a manager. There is no CLI, no configuration file, no list command, no way to switch schemes from the shell, and no upgrade mechanism beyond pulling the repository again. If you maintain several machines or want to script theme selection into a dotfiles bootstrap, this repository gives you the .terminal files and nothing else; the switching logic is yours to write. The README also does not document a rollback path, so if you import a profile and set it as Default, restoring your previous appearance means selecting the old profile in Settings > Profiles and clicking Default again. That is a Terminal.app operation, not a project feature.
The second limitation is scope. The README is explicit that some default macOS themes are excluded, so this is not a complete inventory of every scheme available for Terminal.app. It is the iTerm2-derived set plus whatever contributors have added. If the palette you want lives only in another collection, this repository will not have it.
A third constraint is worth stating plainly: the repository metadata does not include a licence. The README's Contributing section points to CONTRIBUTING.md. For personal use on your own Mac that is unlikely to matter. For bundling these profiles into a product, an internal image or a course handout, it matters, and the answer is not in the README.
How it differs from iTerm2 and from shell theme frameworks
The obvious alternative is iTerm2 with the original mbadolato color scheme collection. The difference is not cosmetic: iTerm2 is a separate terminal emulator you install and run, and its scheme files are in its own format. This repository exists precisely because those files do not load into Terminal.app. Choosing between them is choosing between staying on the built-in terminal and adopting a different emulator. If Terminal.app's feature set is sufficient for you, iTerm2 brings a large amount of surface area you did not ask for.
The other common alternative is a shell-side theme framework, typically paired with a prompt customizer and a font with glyph support. That approach operates at a different layer. It changes what your prompt prints and which colors your shell asks for, and it travels with your dotfiles across machines and operating systems. It does not change the window background, the cursor color or the sixteen-color ANSI palette that Terminal.app applies. The two approaches compose: a shell framework decides how output is colored, and a .terminal profile decides what those color slots actually look like. The README's prerequisite note is effectively pointing at this boundary, since a profile with no color output to render is invisible.
A third option is to build the profile yourself in Settings > Profiles, adjusting each color by hand. That is viable for one scheme and tedious for several, and it is the manual process this repository replaces.
Maintenance, contribution and what to check before adopting
The repository is not archived. Its last push was on 2026-08-27, which is recent enough that describing it as unmaintained would be inaccurate. The repository has no published GitHub releases, which fits the shape of the project: themes are consumed from the repository contents, so versioned releases would add little. Upgrading means pulling the branch again and re-importing whichever .terminal files changed. If you have customized an imported profile inside Terminal.app, re-importing will not merge your edits; you would be creating or replacing a profile.
Contribution has a documented path. CONTRIBUTING.md describes the steps for adding a theme and names the tools that generate the previews, which live in tools/. That matters if you plan to fork the collection for an internal palette set, because the screenshot generation is part of the workflow rather than something you would invent.
On licensing, the honest position is that no licence is stated in the repository metadata. The README links to the upstream iTerm2 collection as the origin of the themes, and upstream terms may bear on redistribution, but nothing in the repository metadata settles the question. Treat that as an open item to verify in the repository itself, not as a settled fact, and do not assume permissive terms because the files are plain text.
Editorial conclusion
Adopt this if you use the stock macOS Terminal.app and want the iTerm2 scheme collection without installing iTerm2 or a shell framework. Do not adopt it if you need a theme manager, Windows or Linux support, or a licence you can verify before shipping it inside a product. Before relying on it, open the themes/ directory and confirm the scheme you want is actually present, check whether the repository carries a LICENSE file, and read the prerequisite comment linked from the README about enabling color formatting for your shell, because a correct .terminal profile still renders flat if your shell is not emitting color.
Frequently asked questions
How do I change the terminal theme in Mac using macos-terminal-themes?
Clone or download the repository, then either open Terminal > Settings > Profiles, use the ... menu to Import... a .terminal file from themes/ and click Default, or double-click a .terminal file and use Shell > Use Settings as Default. Open a new window with cmd+N to see the result.
What is the best terminal theme for macOS in the macos-terminal-themes collection?
The repository does not rank its schemes. It provides screenshots in the screenshots/ directory and a preview image per theme, so the choice is a visual one you make by comparing those previews against your own display and font.
Are the most popular terminal themes included in macos-terminal-themes?
The collection was initially ported from the iTerm2 color schemes collected by @mbadolato, and the README states that some default macOS themes such as "Pro", "Basic" and "Grass" are excluded because Terminal.app already ships them. The README does not publish popularity rankings.
What is a macOS terminal used for, and does macos-terminal-themes change that?
The repository only supplies color profiles for the default macOS Terminal.app. Importing a .terminal file changes the window background, cursor and ANSI palette; it does not change what the terminal is for or how it executes commands.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/lysyi3m-macos-terminal-themes)Star history chart for your README
[](https://hysenlabs.com/projects/lysyi3m-macos-terminal-themes)Was this useful?