Zed: A Rust-Based Multiplayer Editor That Puts Performance First

The Problem Zed Solves: Latency and Collaboration

Zed addresses a specific pain point: code editors that feel sluggish on large projects and that treat collaboration as an afterthought. The project's tagline, 'Code at the speed of thought,' signals a focus on reducing perceived latency. It is built in Rust, a language chosen for performance and memory safety. The creators previously built Atom and Tree-sitter, so they have experience with editor infrastructure. Zed is for developers who spend hours in their editor and notice every millisecond of lag. It is also for teams that want multiplayer editing without leaving their editor, a feature that is often bolted on in other tools. The README does not list specific performance benchmarks, but the architecture suggests a low-level approach. If you are happy with Electron-based editors and rarely collaborate, Zed may not solve a problem you have.

How Zed Works: A Multiplayer, Rust-Based Architecture

The repository does not include a detailed architecture document, but the README and project structure reveal key mechanisms. Zed is written in Rust, which compiles to native code, avoiding the overhead of a JavaScript runtime. The multiplayer feature is central, not an add-on. The README mentions 'multiplayer code editor' in the first line, and the project's home page emphasizes collaboration. The editor likely uses a client-server model where edits are synchronized in real time, though the exact protocol is not described in the README. The use of Tree-sitter, a parsing system, suggests that syntax highlighting and code analysis are incremental and fast. The codebase is large, with scripts for license management and CI, indicating a mature project. Without more documentation, the internal data flow remains partially opaque, but the Rust foundation and Tree-sitter integration point to a performance-first design.

Getting Zed Running: Downloads and Package Managers

Zed can be installed on macOS, Linux, and Windows via direct download from zed.dev or through local package managers. The README links to installation docs for each platform. For example, macOS users can use Homebrew or a direct download, and Linux users can use a package manager like apt or snap, depending on their distribution. Windows users have similar options. Building from source is also possible, with separate guides for each OS under docs/src/development. The README does not provide exact commands, but the existence of these guides implies that a build requires cloning the repository and following platform-specific steps. For most users, the easiest path is the official download, which avoids compiling a large Rust project. The default branch is main, and recent releases include v1.18.0-pre and v1.17.2, so updates are frequent. If you need a specific version, you can likely find it on the releases page.

The Licensing Constraint: GPL-3.0-or-later and Its Implications

Zed's source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked. This is a significant consideration for adoption. GPL-3.0 is a copyleft license, meaning that if you modify Zed and distribute it, your modifications must be licensed under the same terms. This is fine for personal use or internal tools, but it can be problematic for companies that want to embed Zed in a proprietary product. The README also notes that license information for third-party dependencies must be correct for CI to pass. They use cargo-about to automate compliance. If you contribute to Zed, you must ensure your crate's license is specified. This licensing structure is a clear boundary: Zed is open source, but not permissive like MIT or Apache-2.0. Before adopting Zed as a base for a commercial product, you should consult a lawyer, as the README itself advises.

A Genuine Limitation: No Web Version and Platform Gaps

Zed is not available on the web. The README explicitly lists 'Web' as a platform not yet available, with a tracking discussion link. This is a real limitation for developers who need to edit code in a browser, whether for remote work or for environments like Chromebooks. Also, while macOS, Linux, and Windows are supported, the README does not mention other platforms like BSD or mobile. If your team uses a mix of operating systems, you need to verify that Zed runs on all of them. The lack of a web version also means that collaboration is tied to the desktop app, which may be a hurdle for teams that rely on browser-based tools. This is not a minor gap: many modern editors, like VS Code, have a web version. Zed's performance focus may come at the cost of portability.

The Alternative: VS Code and the Trade-Off in Approach

The most direct alternative to Zed is Visual Studio Code (VS Code), which is built on Electron and JavaScript. VS Code is not as fast as a native Rust editor, but it offers a web version, a massive extension ecosystem, and a permissive license (MIT for the core, but the product is proprietary). The approach differs fundamentally: VS Code uses a web technology stack, which makes it cross-platform and easy to extend, but it consumes more memory and has higher latency on large files. Zed's Rust-based approach is a bet on native performance. If your priority is raw speed and you do not need a web editor, Zed is a compelling choice. If you rely on extensions, remote development, or browser-based workflows, VS Code may be safer. The trade-off is clear: performance versus ecosystem and portability. The README does not compare itself to VS Code, but the difference in architecture is decisive.

Maintenance and Upgrade Cost: What to Expect

Zed is actively developed, with releases as recent as v1.18.0-pre and v1.17.2 in August 2026. The default branch is main, and the project is not archived, so maintenance is ongoing. The upgrade cost depends on how you install Zed. If you use a package manager, updates are straightforward. If you build from source, you must keep up with the Rust toolchain and dependencies. The README mentions that CI requires correct license information, which suggests that contributing or maintaining a fork involves a license-compliance workflow. The use of cargo-about means that any new dependency must have a recognized license. This is a maintenance burden if you fork Zed. The project is developed by a for-profit company, Zed Industries, Inc., which means that direction may be influenced by commercial interests. Sponsorships are accepted, but they come with no perks. This is a stable project, but you should monitor the release notes for breaking changes, especially if you use custom builds.

Editorial conclusion

Zed is for developers who prioritize low-latency editing and collaborative workflows, especially those on macOS, Linux, or Windows who can use the official downloads or package managers. It is not for teams that require a web editor or who cannot accept GPL-3.0-or-later licensing. Before adopting, verify that your platform is supported and that your organization's licensing policies align with GPL-3.0-or-later, and check the docs for building from source if you need custom builds.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes