wterm: When Your Browser Becomes a Real Terminal

Web terminals have been around for a while, but most of them feel... off. The text selection is janky, keyboard shortcuts don't work right, and performance is rough. That's because most approaches either canvas-render everything or wrap a JavaScript terminal library that wasn't built for this purpose.

wterm takes a different approach. The core is written in Zig and compiled down to a WebAssembly binary that comes in at around 12KB. That's smaller than most images people embed in their websites. But it's not just about size—this architecture gives you real VT100/VT220/xterm escape sequence parsing without the overhead of running JavaScript through a compatibility layer.

The clever part? It renders to the DOM rather than drawing pixels on a canvas. This means you get native text selection, proper copy/paste behavior, browser find functionality, and even screen reader accessibility without extra work. Your browser already handles all of that for regular text nodes—wterm just leverages that infrastructure.

Performance comes from what they call "dirty-row tracking." Instead of redrawing the entire terminal each frame, the system only re-renders rows that have actually changed. This ties into requestAnimationFrame so it syncs with the browser's refresh cycle. The result is smooth animations even when you're running applications that produce lots of output.

Built-in themes include the classics—Solarized Dark, Monokai, Default, and a Light theme—all customizable through CSS custom properties. Since it supports 24-bit color with full RGB SGR sequences, your colors won't look washed out or quantized.

For the connectivity, there's a WebSocket transport layer that handles reconnection automatically. You can pair this with a PTY backend (SSH server, local shell, whatever) and get a real terminal session running in a browser tab.

Why does this matter?

We're seeing a shift toward browser-based development environments. Projects like VS Code in the browser, GitHub Codespaces, and AI-powered coding tools like Cursor are pushing the browser as an IDE. But a real development workflow needs a real terminal. You can't vibe code without a shell.

wterm provides the foundation for that. It's not trying to be a full product—it's a component that does one thing extremely well. The 12KB WASM core could be embedded in an online IDE, a cloud development platform, or even a browser-based SSH client that doesn't feel like a toy.

The fact that it's built with Zig is worth noting too. Zig gives you low-level control and efficient WASM output without the complexity of something like Rust. The ecosystem for WASM development is maturing fast, and we're going to see more native-speed applications running entirely in the browser.

If you're building any kind of browser-based development tool, wterm is worth bookmarking. The source is available at wterm.dev, and it's the kind of project where you can see how thoughtful architecture choices lead to a small, fast, capable result.

Sometimes the best technical solutions are the ones that work with the browser instead of against it. wterm does exactly that—and at 12KB, it proves that size isn't everything, but it helps.