# foot and other terminal emulators

Address: https://nowa.im/cotty/research/studies/2026-11-terminal-emulators/  
Created: 2026-11-22

What is a current terminal emulator made of, and how do the common ones differ? foot shows how little one needs: a Wayland client, a CPU renderer and a font library, in a package under 1 MB. The common emulators differ in language, renderer and platform. Rendering is not an open problem in any of them.

This note was first part of a longer note on what a terminal is. The argument of that note is now the post [What a terminal is](https://nowa.im/cotty/posts/what-a-terminal-is/). The facts with a date stay here.

## Findings

### foot

These facts are first-hand. They come from inspecting foot 1.28.0 as installed on one machine on 2026-11-22: its linked libraries (with `ldd`), its package metadata and its memory use.

foot is the default terminal of Omarchy as of November 2026. Omarchy selects `foot.desktop` through `xdg-terminal-exec`.

Its technology:

- C, built with Meson, by Daniel Eklöf, MIT license, hosted on Codeberg.
- Display: `libwayland-client`. There is no X11 code.
- Rendering: `pixman`, drawing on the CPU into a shared memory buffer. It does not use the GPU.
- Fonts: `fcft`, the author's own library, on top of FreeType, HarfBuzz and fontconfig.
- Keyboard and text: `xkbcommon` and `utf8proc`.
- The installed package is 812 KiB. On that machine each window uses about 50 to 70 MB of resident memory.

Its character:

- It redraws only the cells that changed, renders on several threads, and is compiled with PGO.
- Server mode: `foot --server` with `footclient`.
- Built-in URL mode and scrollback search.
- It supports Sixel, OSC 8, OSC 52, the Kitty keyboard protocol and input methods.
- It deliberately leaves out tabs and splits (left to the window manager), ligatures, the Kitty graphics protocol, and every platform other than Wayland.

### Comparison

This table was written from general knowledge of each project. It was not checked against their documentation.

| | foot | Alacritty | Kitty | Ghostty | WezTerm |
|---|---|---|---|---|---|
| Language | C | Rust | C and Python | Zig | Rust |
| Rendering | CPU (pixman) | GPU (OpenGL) | GPU (OpenGL) | GPU | GPU |
| Platforms | Wayland only | All | Linux, macOS | Linux, macOS | All |
| Tabs and splits | None | None | Yes | Yes | Yes, with its own multiplexer |
| Image protocol | Sixel | None | Kitty | Kitty | Both |
| Configuration | ini | toml | conf | Plain text | Lua |

## What this means for cotty

- Several mature emulators render well, with CPU and with GPU renderers. That is the standard cotty's own rendering has to reach.
- An existing engine is a real option for cotty's renderer. That question is open in [Positioning](https://nowa.im/cotty/product/positioning/).

## Sources

- foot: inspection of the installed package, as described above. The project is at [codeberg.org/dnkl/foot](https://codeberg.org/dnkl/foot).
- The comparison table: general knowledge, not verified.

## Not covered

- Measurements of the other emulators: latency, memory and startup time.
- Emulators that are specific to macOS or Windows.
