Drawing in the Terminal, 2026

What replaced libcaca — and the quiet graphics renaissance that came with it.

COMPILED BY CLAUDE (OPUS 4.8)  ·  2026-06-18  ·  SOURCES: GITHUB + NPM (LIVE)

---

aalib (1997, monochrome ASCII) → libcaca (2002, "Colour ASCII Art" + a cacaview/img2txt CLI) defined the genre: take an image, map cells to characters by luminance, dither in 16 colors. Brilliant for its era — and effectively frozen since. libcaca's last release is v0.99.beta20 from 2021; the repo's own description is a literal 💩 emoji. It still ships in distros, but nobody starts new work on it.

What changed underneath it: 24-bit truecolor went mainstream, Unicode kept minting denser block glyphs, GPUs got into terminals, and three image protocols matured. The successors split along those lines.

If you mean "a tool/library that turns a PNG/GIF/video into terminal output" — the img2txt lineage — this is the table. Click any column header to sort.

★ counts & "updated" are pulled live from GitHub.

A · Graphics protocols — the real "modern rendering"

Terminals can now stream actual raster images into the grid. Three protocols, in rough order of momentum (hover a card & click to read the spec):

You rarely implement these by hand — you let chafa, timg, terminal-image or a TUI lib probe the terminal and pick. To actually see pixels you need a capable emulator (see §6).

B · The character-cell resolution ladder kept climbing

When there's no protocol (SSH to a basic box, CI logs, a retro vibe), you fake pixels with block glyphs. Unicode keeps adding denser ones — each step doubles the "sub-pixels" per character cell:

Node didn't inherit the C lineage — it grew its own, and the scale is wild. Monthly npm downloads beside GitHub stars; both update live. (For calibration, chalk alone pulls ~1.8 billion/mo.) Sortable.

downloads & ★ are pulled live.

Here's the twist — if by "modern libcaca" you mean "how do people draw rich things in a terminal now," the center of gravity isn't an image library at all. It's the new wave of app frameworks, each massively starred. Sortable.

★ & "updated" are pulled live.

These are why the terminal feels alive again in 2026 — installers, AI coding agents, dashboards, git UIs. Several now speak "Mode 2026" (DEC synchronized output) to kill flicker; Ink v6.7+ and Bubble Tea v2 adopted it. Most embed an image lib (ratatui-image, textual-image, ink-image) when they need a real picture.

None of the pixel stuff matters if the emulator can't render it. Your renderer is only as good as the terminal under it (hover & click each):

If you just want to throw an image in the terminal

# chafa auto-detects kitty/sixel/iterm2 and falls back to unicode. that's it.
chafa image.png
chafa -f sixel movie.gif            # force a protocol
chafa --symbols octant photo.jpg    # force fanciest char art (Unicode 16)

One tool, every output mode, actively developed. Don't overthink it — chafa it is.

If you're embedding in an app

Link libchafa (C/FFI) for image→cells. For a whole UI, use your language's framework — and let it own rendering rather than hand-rolling escape codes:

go get github.com/charmbracelet/bubbletea   # Go
cargo add ratatui                            # Rust
pip install textual                          # Python
npm i ink react                              # Node
npm i terminal-image                         # Node, images only

The verdict in one breath

chafa is the modern libcaca — full stop. But "terminal rendering in 2026" is a much bigger story: GPU terminals + Kitty/Sixel protocols for real pixels, the octant/braille Unicode ceiling for fallback, and a per-language TUI-framework boom (Bubble Tea / Ratatui / Textual / Ink) where most actual "drawing" now happens. libcaca and aalib walked so this could run. 🫡

Three things that aren't renderers — but they decide whether your rendering is fast, or works at all. (You asked for the asterisks; here they are.)

A · Shells & prompts — they gate your latency, not your pixels

A "slow terminal" is usually a slow prompt. These are shell config, not renderers, but they're where the lag lives. Sortable.

★ & "updated" pulled live.

B · Multiplexers — the protocol-killers

Run inside tmux or zellij and your image protocols can vanish — the multiplexer sits between the app and the terminal, so Kitty/Sixel output gets mangled unless you turn on passthrough.

C · The silicon — GPU is baseline, TPU isn't a thing

GPU acceleration is now standard, not a differentiator; the interesting axis is the rendering API. Ghostty's custom Zig engine even hits ~2 ms key-to-screen. Sortable.

★ pulled live.

---

Star counts & "updated" dates are fetched live from the GitHub REST API; npm download counts from the npm registry API. A scheduled GitHub Action re-bakes data.json daily, so the tables stay current with no per-visitor rate limits.

Background reading: chafa — hpjansson.org · Terminal Graphics Protocols — Akmatori · Kitty graphics protocol spec · rothgar/awesome-tuis · Bubble Tea vs Ratatui (2026) · lnqs/textual-image · Best terminal for Mac 2026