Zed and the 8ms Frame
Why the creators of Atom abandoned the web to build a GPU-accelerated engine for code.
- Zed replaces standard web-based rendering with a custom GPU-accelerated engine to achieve a 120fps refresh rate.
- The editor uses Conflict-free Replicated Data Types to enable native real-time collaboration without server-side latency.
- Built by the creators of Atom, the project utilizes Rust and a custom UI framework to bypass the performance limitations of the DOM.
- AI integration in Zed treats large language models as core primitives rather than simple sidebar extensions.
The 8-Millisecond Mandate
For a decade, the developer ecosystem accepted a compromise. Editors like VS Code and Atom offered incredible extensibility by running on web technologies, but they taxed the CPU and introduced subtle input latency. Zed reverses this tradeoff. Built entirely in Rust, it targets a 120fps refresh rate. This means every single frame (including syntax highlighting, cursor blinks, and scrolling) must compute in under 8.3 milliseconds.
Achieving this required discarding the Document Object Model completely. Instead of rendering HTML and CSS, Zed treats the text editor like a high-performance AAA game engine.
Beyond the DOM
The irony of Zed is its lineage. The project was founded by the very engineers who created Atom and helped ignite the Electron revolution. After years of optimizing web-based editors, they hit a hard performance ceiling. They realized that achieving true zero-latency typing required talking directly to the metal.
To do this, they built their own UI framework from scratch called GPUI. It bypasses standard operating system windowing toolkits and communicates directly with Metal on macOS or Vulkan on Linux and Windows.
We're excited to announce that Zed is now an open source project. The code for Zed itself is available under a copyleft license to ensure any improvements will benefit the entire community (GPL for the editor, AGPL for server-side components). GPUI, the UI framework that powers Zed, is distributed under the Apache 2 license, so that you can use it to build high-performance desktop applications and distribute them under any license you choose.
Coding in Parallel
Performance is only half the architecture. Zed was designed from day one to be multiplayer. Instead of relying on a central server to mediate edits, it uses Conflict-free Replicated Data Types (CRDTs). When two developers edit the same file, their local buffers update instantly, and the operations are mathematically merged in the background.
The Agentic Shift
Zed approaches AI integration differently than its predecessors. Rather than treating large language models as a simple autocomplete sidebar, the editor incorporates AI agents as core primitives. The internal codebase relies heavily on a skills directory, treating prompts as version-controlled logic.
In short, LLMs automate typing, not thinking.
The New Editor Hierarchy
Zed occupies a unique space in the developer tooling landscape. It offers the GUI comforts and integrated features of VS Code, but operates with the mechanical sympathy and low memory footprint of terminal-based editors like Neovim.
| Feature | Zed | VS Code | Neovim |
|---|---|---|---|
| Core Language | Rust | TypeScript | C / Lua |
| UI Rendering | GPU (Direct Metal/Vulkan) | Electron (DOM / WebGL) | Terminal Emulator |
| Collaboration | Native CRDTs | Live Share Extension | Third-party Plugins |
| Extensibility | WASM (Growing) | JavaScript (Massive) | Lua (Extensive) |