Ghostty vs iTerm2 (2026): Which Mac Terminal Should You Use?

You open iTerm2, and somewhere under Settings there are eleven years of decisions: a profile per client, a trigger that turns failed test names red, a hotkey window that drops down when you hit Option-Space. Then a coworker shows you Ghostty and it feels faster before you have typed anything. For most Mac developers in 2026, Ghostty is the better daily terminal: it is quicker, lighter, configured in a plain text file you can keep in git, and native in every way that matters on macOS. iTerm2 is still the right call if your day runs through tmux control mode, or through the pile of triggers and Python scripts you have built up over the years, because Ghostty has no real equivalent for those.

This page is the two-way version of the question. We already ran the latency and throughput numbers in our iTerm2 vs Ghostty vs Kitty benchmarks, and the full Ghostty review covers the app on its own. Here the focus is narrower. Which of your iTerm2 habits survive the move, which ones die, and when should you not bother?

The short version

If you...	Pick
Mostly run a shell, an editor, and a dev server locally	Ghostty
Keep your dotfiles in git and want the terminal in there too	Ghostty
Live in remote tmux sessions and like native tabs for them	iTerm2
Rely on triggers, automatic profile switching, or scripted window layouts	iTerm2
Also work on Linux and want one terminal everywhere	Ghostty
Prefer clicking through a settings window over editing a file	iTerm2

Two very different projects

iTerm2 is George Nachman's project, and it has been the default "real" Mac terminal for well over a decade. It is free and GPL-licensed. It runs only on macOS, and the feature list reads like a record of every request a power user has ever made. That history is the point. Somebody wanted to trigger a macOS notification when a regex matched in output, so now you can.

Ghostty started as Mitchell Hashimoto's side project, hit 1.0 at the end of 2024, and now runs as a nonprofit-backed open source project under the MIT license. It is written in Zig with a shared core, and the macOS app is a genuine Swift and AppKit application drawing through Metal. On Linux it uses GTK. The design goal is narrow. Be fast and correct about terminal standards, and feel like it belongs on whatever platform it runs on. Features get added slowly and on purpose.

You can feel that difference within a day.

Speed and resource use

Ghostty is faster. In our earlier benchmarks it led iTerm2 on input latency and left it far behind on raw throughput, which you notice when something dumps a few hundred thousand lines of build log and Ghostty simply keeps up while iTerm2 visibly scrolls. Idle memory per window is lower too, and launch is close to instant.

Whether that matters to you depends on how you work. If your terminal mostly shows a Neovim buffer and a test runner, iTerm2's Metal renderer is perfectly smooth and you will not lose a minute of your day to it. Throughput gaps only become real during the moments when a terminal is flooded: cat on a huge file, or a Kubernetes log tail at full blast. Those moments are short. They are also exactly when you are trying to read something.

Configuration

This is the biggest day-to-day difference, and people tend to have strong feelings about it either way.

iTerm2 is configured through a GUI. Profiles, colors, keys, and window behavior all live in a deep settings window, saved to a plist. You can point iTerm2 at a custom folder and sync that plist through dotfiles, and dynamic profiles let you define profiles in JSON, but the plist itself is not something anyone wants to diff in a pull request.

Ghostty has a text file at ~/.config/ghostty/config with key = value lines, and that's all. Pressing Cmd-comma opens the file in your editor. A complete working setup is often under twenty lines:

font-family = JetBrains Mono
font-size = 14
theme = catppuccin-mocha
window-padding-x = 8
macos-option-as-alt = true
keybind = global:cmd+grave_accent=toggle_quick_terminal

The defaults are good, which is why the file stays short. Run ghostty +show-config --default --docs to see every option with its documentation, and ghostty +list-themes to preview the hundreds of bundled color schemes. Reloading the config takes a keystroke. If you hate editing config files, you will find this tiresome; if you already keep a .zshrc and a Neovim config in git, it will feel like the terminal finally joined the rest of your setup.

What you lose leaving iTerm2

Be honest with yourself about this list before switching, because none of these have a drop-in Ghostty replacement today.

• tmux control mode. Running tmux -CC in iTerm2 turns tmux windows into native tabs and panes, with normal scrolling and copy. For anyone who spends the day attached to remote sessions, this is iTerm2's killer feature and the main reason people go back. In Ghostty you run tmux the ordinary way, prefix key and all (our multiplexer comparison covers how to make that pleasant).
• Triggers. Regex matches on output that recolor text, post notifications, run commands, or answer password prompts. Ghostty does nothing like this.
• Automatic profile switching. iTerm2 can change colors when you SSH into production, based on hostname or user. A lot of people use this as a safety rail and only notice it when it's gone.
• The Python API and saved arrangements. Scripted window layouts, status bar components, and custom automation.
• Smaller conveniences: instant replay of the screen history, broadcast input to several panes, Cmd-click on a file path to open it in your editor at the right line, and the built-in password manager.

Scrollback search deserves its own mention. It was the most requested missing feature in Ghostty for a long time after 1.0, so check the release notes for the version you install rather than assuming it behaves like iTerm2's Cmd-F.

What you gain

Native tabs and splits that look and behave like every other Mac app, including proper macOS window tabbing. A quick terminal that slides down from the top of the screen on a global hotkey (the closest thing to iTerm2's hotkey window, and for most people a full replacement). Shell integration that installs itself for zsh, bash, fish, and elvish with no script to source, which gives you jump-to-prompt and new tabs that open in the current directory. Support for the Kitty graphics and keyboard protocols, so image previews in yazi and modern key handling in Neovim just work. And the same terminal, with the same config file, on your Linux machine.

Font rendering also tends to look closer to native macOS text in Ghostty, though this is the kind of thing you should judge with your own eyes and your own font.

Head-to-head

Dimension	Ghostty	iTerm2
Price and license	Free, MIT	Free, GPL v3
Platforms	macOS, Linux	macOS only
Built with	Zig core, Swift/AppKit UI, Metal	Objective-C and Swift, Metal
Configuration	Plain text file	Settings GUI, plist, dynamic profiles in JSON
Throughput on large output	Excellent	Adequate
Drop-down terminal	Quick terminal	Hotkey window
tmux integration	Plain tmux	Native tabs via tmux -CC
Triggers and automation	None	Triggers, Python API, arrangements
Inline images	Kitty graphics protocol	iTerm2 inline image protocol, imgcat
Shell integration	Automatic	Install script, richer features

A note on AI features

iTerm2 3.5 shipped an AI assistant that needed your own OpenAI key, and the backlash was loud enough that it was moved into a separate, optional plugin in the next point release. Nothing in iTerm2 sends your terminal contents anywhere unless you install that plugin and configure it. Ghostty has no AI features at all. If you want an AI-first terminal, that is a different category, and our Ghostty vs Warp comparison is the place to look.

Migrating without losing a week

Install Ghostty with brew install --cask ghostty and keep iTerm2 installed. Run both for a week. Start your config with only a font, a theme, and macos-option-as-alt = true (iTerm2 users with Option-based word jumping will miss it immediately otherwise). Recreate your hotkey window with the quick terminal keybind shown above; macOS will ask for Accessibility permission the first time you use a global keybind. If you SSH into older servers and see garbled output or broken backspace, the remote machine does not know Ghostty's xterm-ghostty terminfo entry. Copy it over with infocmp -x xterm-ghostty | ssh yourserver -- tic -x -, or set TERM=xterm-256color for those hosts in your SSH config. Then pay attention to which iTerm2 window you keep opening. If it is the one with your tmux sessions in it, that is your answer.

The verdict

Ghostty wins for the majority of Mac developers: faster, calmer, versionable, and pleasant out of the box. iTerm2 wins for a smaller group whose workflow is built on its automation, and for them there is no reason to move. Neither choice is a mistake. Both are free, so the cost of trying Ghostty is one evening and a short config file, and the worst case is you drag iTerm2 back into the Dock. For the wider field, including Kitty and WezTerm, see our best terminal emulators roundup.