Terminal Emulators Worth Learning
Ghostty, Kitty, Alacritty, WezTerm, foot, and Windows Terminal compared — features, benchmarks, and how to choose without chasing benchmarks.
By Velloreth
The terminal emulator is one of the few programs you stare at for hours every day, and it is the one most people never choose — they keep whatever the operating system shipped.
Before comparing options, it helps to separate three layers that get conflated constantly:
- Terminal emulator — the window itself. It renders glyphs, handles fonts and colors, owns tabs and paste buffers, and talks to the OS.
- Shell — bash, zsh, fish. It interprets commands inside the terminal and has nothing to do with how text is drawn.
- Multiplexer — tmux, Zellij. Panes and persistent sessions, independent of any window.
Swapping your terminal does not change your shell, and none of them replace tmux — though some try to fold its job in.
What actually matters in a terminal
Feature lists are misleading here. These are the things you notice within a week:
| Concern | Why it matters |
|---|---|
| Throughput | Build logs, cat of large files, and AI agent output scroll faster than you can read — slow terminals show it |
| Input latency | Small individually, constant in aggregate — you type thousands of commands a day |
| Font rendering | Ligatures, correct bold/italic fallback, and per-monitor DPI handling |
| Clipboard | OSC 52 lets you copy from inside tmux or SSH without a local paste buffer |
| Shell integration | Marks command boundaries, so you can jump between prompts or re-run the last command |
| Hyperlinks | OSC 8 makes https://... in output clickable without wrapping text in angle brackets |
| Graphics | Kitty protocol or Sixel for images — file previews, charts, timg, TUI file managers |
| Config lifecycle | One file you can put in dotfiles versus a preferences GUI with no export |
Nobody needs all of it. Throughput, fonts, and clipboard are the table stakes; graphics and shell integration are the upgrade path.
The candidates
Alacritty — Rust, GPU-rendered, and deliberately featureless. No tabs, no splits, no image protocol, one TOML file. Its README says window management belongs to a multiplexer, and it means it: you pair it with tmux or Zellij and stop thinking about it. If your instinct is “a terminal should render text and get out of the way,” this is that instinct written in code.
Kitty — the feature-rich end, also GPU-accelerated, written in C with a Python extension system. Tabs, splits, sessions, background images, custom shaders, and the graphics protocol it originated — now adopted by Ghostty and WezTerm. Its “kittens” are small Python programs that extend the terminal; kitten ssh is the one people cite when asked why they switched. The cost is surface area: kitty.conf has a lot in it, and kittens only run in Kitty.
Ghostty — by Mitchell Hashimoto, written in Zig, first stable release in December 2024. The pitch is “fast, feature-rich, and native”: platform-native UI (AppKit on macOS, GTK 4 with libadwaita on Linux), native tabs and splits, system theme switching, support for Kitty’s graphics protocol, and a plain key = value config file. It reads like Alacritty’s simplicity with Kitty’s feature list, which is roughly how users describe it. macOS and Linux only.
WezTerm — Rust, cross-platform including Windows, configured entirely in Lua, with a built-in multiplexer — the only candidate here that genuinely wants to replace tmux. It also supports both the Kitty graphics protocol and Sixel, which is rare. The Lua config is either the draw or the dealbreaker.
foot — Wayland-only, CPU-rendered, and tiny. No tabs, no images, INI config. In independent benchmarks it posts the lowest input latency and the fastest large-file throughput of the field, which is a strong argument if you run a Wayland compositor and pair it with a multiplexer anyway.
Windows Terminal — ships with Windows and is the correct default there: tabs, splits, profiles for PowerShell, cmd, and WSL, GPU-rendered, and configured through a JSON file you can version. Nothing else on Windows comes close to being the sane choice for most people.
iTerm2 — the long-standing macOS default, mature and deeply configurable, with shell integration and good accessibility. It also shows its age in throughput comparisons against the GPU-native generation.
Benchmarks, with the usual caveats
Numbers from different sources disagree wildly, because results depend on hardware, compositor, and what is being rendered. One independent comparison worth reading (vizenc’s terminal-benchmark, run on a ThinkPad T430 under Hyprland with default configs) reported:
| Metric | foot | Alacritty | Kitty | Ghostty | WezTerm |
|---|---|---|---|---|---|
| Input latency (ms, lower better) | 15.0 | 16.7 | 18.3 | 38.3* | 30.8 |
cat of an 11 MB file (ms) | 251 | 404 | 401 | 407 | 1246 |
| DOOM-fire render (FPS) | 199 | 164 | 273 | 135 | 64 |
| Memory after reboot (MB) | 43 | 75 | 91 | 174 | 130 |
* The Ghostty latency figure looks like a measurement artifact (GTK under XWayland); other tests place it much closer to Kitty.
Read this as directional, not definitive. What survives across sources is the shape: foot and Alacritty are lean, Kitty renders sustained scrolling fastest, WezTerm trails on raw I/O while offering the most built-in capability, and Ghostty sits in the middle with the largest memory footprint of the group.
If you want your own numbers, hyperfine will give them to you in a minute:
hyperfine --warmup 3 \
'kitty -e true' \
'alacritty -e true'
Startup time and a large scrollback dump are the two tests you can run honestly on your own hardware.
Multiplexer or native tabs?
This is the real architectural decision, more than which binary you pick.
Native tabs and splits (Kitty, Ghostty, WezTerm, Windows Terminal) keep everything in one process, match your platform’s window behavior, and cost nothing to learn. Their weakness is sessions: close the laptop, and your panes go with it.
tmux or Zellij give you detachable sessions — a build that keeps running over SSH, panes that survive a dropped connection — at the price of another layer: prefix keys, copy-mode, configuration, and the occasional terminal-feature mismatch inside nested panes.
Reasonable defaults: on a laptop where you close the lid, native tabs are enough. If you live over SSH or want work to survive reboots, learn tmux regardless of your terminal. Alacritty users do not get a choice, which is either the point or the problem.
Fonts, colors, and the settings worth changing first
Performance debates aside, most people’s first impression of a new terminal comes down to two settings: the font and the theme.
Font. Pick something with a clear distinction between 0/O, 1/l, and I — you will read code in it for hours. Ligatures (=>, !=, === drawn as single glyphs) are a taste decision: teams that love them exist, and so do teams that find them misleading when reading a diff. What is not optional is fallback handling: your terminal should substitute a missing glyph from another font instead of rendering a box, and the GPU-native terminals do this through platform font APIs while Alacritty wants an explicit font.fallback list in its TOML.
Theme. Get your editor and terminal on the same theme and the seam between them disappears. Most of these terminals also switch themes on the system light/dark change, which is worth enabling once and forgetting.
Scrollback. Defaults vary from a few thousand lines to effectively unlimited. If you scroll back through build output, raise it — and check what memory that costs in the terminal you chose, since unlimited scrollback in a slow terminal is how you end up swapping.
Mouse and clipboard. Enable the middle-click paste only if you use it, and if you run tmux, turn on its clipboard integration (set -g set-clipboard on or external) so OSC 52 reaches the system paste buffer — that is what lets you copy from a pane inside an SSH session and paste locally.
These five changes take ten minutes and matter more to daily comfort than any benchmark in this article.
Three features to try in the first week
New terminals have a learning curve measured in days, not hours. Three things are worth trying before you decide the switch was a mistake:
- Shell integration. Kitty, Ghostty, WezTerm, and iTerm2 mark where each command started and ended. In supported terminals you can jump between prompts, re-run the previous command, or select a command’s entire output — features that quietly save more time than raw rendering speed.
- Graphics. With the Kitty protocol supported (Kitty, Ghostty, WezTerm), TUI file managers and preview tools can render images inline. Try
timgor open a file manager likeyaziand see whether previews change how you browse. - Remote work.
kitten sshin Kitty handles terminfo and forwarding elegantly; elsewhere, the terminfo fix below is the equivalent setup step. A terminal that only works on your laptop is a terminal you will stop using the first week you work from a server.
The SSH terminfo trap
Terminals advertise themselves through TERM, and remote hosts need a matching terminfo entry to run full-screen programs (vim, less, htop).
Ghostty sets TERM=xterm-ghostty, and most servers do not ship that entry — the symptom is Error opening terminal: xterm-ghostty the moment you open an editor over SSH. Two fixes:
# copy the terminfo entry to the remote host once
infocmp xterm-ghostty | ssh my-server 'tic -'
# or just use a universal TERM for that session
ssh my-server
export TERM=xterm-256color
Kitty has the same class of problem with xterm-kitty. It is not a reason to avoid these terminals; it is a reason to know where the terminfo database lives on your servers.
Switching without breaking your day
The safe way to move is incremental:
- Keep the default installed. When something renders wrong at 4pm, you switch back in one click instead of debugging.
- Migrate config before muscle memory. Font, font size, scrollback, theme, and keybindings first — those are what make it feel like yours.
- Re-check your workflow, not the features. Can you still copy out of tmux? Do colors match in
lazygit? Doesbatoutput look right? Does your editor’s underline rendering behave? - Test the annoying cases on day one: a large
git log -p, a build log scrolling at full speed, a full-screen editor over SSH, and pasting a multi-line command. - Only then move your config into dotfiles and remove the default from your dock — not from your system.
Most people who bounce back to their old terminal do so in the first two days, over clipboard or font issues, not performance.
What to pick
There is no universal answer, only constraints:
- Windows → Windows Terminal, then stop deliberating.
- Wayland, minimal, pair with tmux → foot.
- macOS or Linux, want native feel with the features built in → Ghostty.
- Want everything, including SSH kittens and custom shaders → Kitty.
- Want one config for all three OSes and a built-in multiplexer → WezTerm.
- Want the terminal to do nothing but render → Alacritty plus tmux.
Any of these will feel like an upgrade over the default. The one you configure and keep is the right one — which is why the honest advice is to pick from the table above by your OS and your pane habits, install it alongside what you have, and give it one working week.