7 minute read

Quick Answer

Zed is a next-generation code editor built from scratch in Rust to achieve unprecedented performance. Unlike traditional editors that run on JavaScript/Electron, Zed uses a custom GPU-accelerated UI framework (GPUI) to render at 120fps with sub-millisecond latency. It features native CRDT-based collaboration (no plugins needed), AI integration via the Agent Client Protocol (ACP), and Wasm extensions for security. While its extension ecosystem is smaller than VS Code’s, Zed offers the best typing experience and collaboration features available, making it ideal for performance-focused developers.


What is Zed?

Zed is a reimagining of the code editor from first principles. Developed by the creators of Atom and Tree-sitter, Zed addresses the fundamental limitations of Electron-based editors like VS Code:

Problem Electron Solution Zed’s Solution
Performance JavaScript overhead GPU rendering (GPUI)
Memory High RAM usage Rust efficiency
Collaboration Plugin required Native CRDTs
Extensions Node.js (flexible but risky) Wasm (sandboxed)

The result is an editor that feels instantaneous and scales from small scripts to multi-million line codebases without degradation.


Key Features

1. GPUI: GPU-Accelerated Rendering

Zed’s custom UI framework renders directly to the GPU:

  • 120fps target frame rate for smooth scrolling
  • Sub-millisecond latency for key presses
  • Parallel rendering (CPU for logic, GPU for pixels)
  • Efficient for massive files (millions of lines)

Practical Impact:

  • No “typing lag” on large files
  • Smooth multi-cursor operations
  • Instant syntax highlighting via Tree-sitter
  • Responsive even on legacy hardware

2. CRDTs: Native Collaboration

Conflict-free Replicated Data Types power real-time collaboration:

  • Every keystroke synced to peers
  • Cursors tracked as state vectors
  • Follow Mode: Sync viewport with host developer
  • Offline-first: Works without network, merges on reconnect

Advantages over VS Code Live Share:

  • No “locking” conflicts
  • Lower bandwidth (only send operations, not state)
  • Better scaling for large teams

3. Agent Client Protocol (ACP)

Zed’s open standard for AI integration:

Feature Description
Unified Interface Connect any AI provider via ACP
Tool Support Agent can read files, run terminals, edit code
Multi-Model GPT-5, Gemini 2.5, Claude, local models
Extensible Third parties can build ACP agents

4. Model Agnostic AI Support

Zed supports multiple LLM providers:

Provider Models Context Best For
OpenAI GPT-5, GPT-5-mini, GPT-5-nano, GPT-4o 400k Deep reasoning
Google Gemini 3.0 Pro, Gemini 2.5 Pro/Flash 2M Massive context
Anthropic Claude 3.5 Sonnet, Opus, Haiku 200k High-quality coding
xAI Grok 4 128k-2M Vision support
BYOK Local models via API keys Varies Privacy/cost

5. Wasm Extensions: Secure & Fast

Extensions run in WebAssembly sandbox:

  • Can’t crash the main editor (process isolation)
  • Fast execution (near-native speed)
  • Permission model (explicit access requests)
  • Supports: Languages, themes, slash commands, MCP servers

6. Helix Integration

For Vim users, Zed includes:

  • Vim mode with modal editing
  • Helix keybindings (Kakoune-style)
  • Tree-sitter for syntax-aware operations
  • Multi-cursor support

Technology Stack Support

Systems Programming

Language Support Level Features
Rust ⭐⭐⭐⭐⭐ Native (Zed is Rust), rust-analyzer, macro expansion, runnable tests
C/C++ ⭐⭐⭐⭐⭐ clangd, CMake projects, lldb debugging, header navigation
Go ⭐⭐⭐⭐⭐ gopls, go.mod awareness, gofmt, delve debugging

Web Development

Framework Status Notes
React Native vtsls (fast TS), JSX support, eslint/prettier
Next.js Native RSC awareness, Server Components, App Router
Vue Strong Volar (LSP for Vue), single-file components
Svelte Strong Svelte Language Server, inlay hints
Astro Good Component-aware, content collections
Angular Good Angular Language Service, standalone components

Backend & Scripting

Language Features
Python pyright/basedpyright, ruff (linting/formatting), venv/conda detection
PHP (Laravel) zed-for-laravel kit (phpactor, pint, Blade templates, artisan tasks)
Ruby (Rails) solargraph/ruby-lsp, .ruby-version respect, ERB templates, rubocop

Database & Infrastructure

  • SQL: Tree-sitter parsing, PostgreSQL/MongoDB via MCP
  • Terraform: tree-sitter-hcl, prefillRequiredFields
  • Docker: Dockerfile and docker-compose validation

Zed vs Competitors

Zed vs VS Code

Aspect Zed VS Code
Architecture Rust + GPUI Electron (JavaScript)
Performance Sub-ms latency, 120fps Moderate, occasional lag
Collaboration Native CRDTs Plugin required (Live Share)
Extensions Wasm (secure, limited) Node.js (flexible, risky)
Resource Usage Low RAM, efficient High RAM, bloated
Startup Time Instant Slow (cold start)

Winner: Zed for performance and collaboration, VS Code for extension ecosystem.

Zed vs Cursor

Aspect Zed Cursor
Type Speed Instant (sub-ms) Fast (but slower than Zed)
AI Integration ACP (multi-model) Built-in (Claude/GPT)
Context Engine File-based ranking Deep Context RAG
Privacy Local-first, optional cloud Cloud-synced by default
Cost Free core + usage-based $20/mo flat

Winner: Zed for performance and model choice, Cursor for deep context understanding.

Zed vs JetBrains

Aspect Zed JetBrains
Startup Instant Slow (indexing overhead)
Performance Consistent 120fps Variable (GC pauses)
AI Multi-model via ACP JetBrains AI (proprietary)
Resources Lightweight Heavy (Java-based)
Cost Free + usage $20-50/month per IDE

Winner: Zed for speed and efficiency, JetBrains for enterprise features (refactoring, database tools).


Business Model

Open Core with Token Billing

Component Pricing
Editor Free (open source: GPL/Apache/AGPL)
Pro Plan $10/month
Token Credit $5 monthly stipend
Frontier Models List price + ~10% markup
Fast Models Often free or cheap

Transparency

Unlike flat-rate subscriptions, Zed’s model is transparent:

  • Fast Models (GPT-5-nano, Claude Haiku): Often included
  • Frontier Models (GPT-5, Opus): Pay what you use
  • No throttling of frontier models (unlike competitors)

Platform Support

macOS: Lead Platform

  • Best Experience: Apple Silicon optimized
  • Metal API: GPU rendering via Metal
  • Energy Efficient: Great battery life on M1/M2/M3
  • Requirement: macOS 12+ (Monterey) or later

Linux: Vulkan Required

  • Requirement: Vulkan 1.3 capable hardware
  • Display: Wayland and X11 support
  • Drivers: RADV recommended (amdvlk problematic)
  • Packaging: .tar.gz, Flatpaks, AUR packages

Windows: New Frontier

  • Rendering: DirectX 11
  • WSL 2: Remote development into Linux
  • Status: Stable (late 2025)
  • Native Support: Improving rapidly

Best For

1. Performance Enthusiasts

Developers tired of Electron bloat:

  • Sub-millisecond latency typing
  • 120fps scrolling through files
  • Low memory footprint vs VS Code
  • Instant startup times

2. Remote Developers

WSL2 + SSH support enables:

  • Local GUI on Windows, Linux containers for code
  • SSH directly to remote servers
  • Hybrid workflow: Windows UX + Linux toolchain

3. Real-Time Collaborators

Native CRDTs enable:

  • Multiplayer coding without plugins
  • Follow Mode: Watch pair programming
  • Offline-first: Works without internet
  • Better scaling than VS Code Live Share

4. Privacy-Conscious Developers

Local-first AI options:

  • BYOK (Bring Your Own Key) for any provider
  • Local models via API (Ollama, LM Studio)
  • Zero telemetry option available
  • No cloud sync required

5. Vim Users

Helix integration provides:

  • Modal editing familiarity
  • Kakoune-style keybindings
  • Tree-sitter for text objects
  • Multi-cursor support

Avoid For

1. Extension-Heavy Workflows

Zed’s extension ecosystem is smaller:

  • Missing: Many niche VS Code extensions
  • API Limitations: No custom UI/webviews yet
  • Workaround: Build your own (Wasm is easy)

Better: VS Code for plugin availability.

2. Windows Legacy Hardware

Requirements:

  • DirectX 11 capable GPU
  • Windows 10/11 64-bit
  • WSL 2 for Linux toolchains

Avoid: Old machines without GPU acceleration.

3. JetBrains Users

If you rely on:

  • IntelliJ IDEA’s refactoring
  • PyCharm’s scientific tools
  • DataGrip’s database management

Better: JetBrains IDEs for enterprise Java/Python.

4. UI-Focused Developers

If you need:

  • Drag-and-drop page builders
  • Visual designers
  • No-code interfaces

Better: Cursor, v0, or web-based tools.


FAQ

Is Zed faster than VS Code?

Yes, significantly. Zed’s GPUI rendering achieves sub-millisecond latency compared to VS Code’s Electron overhead. Users report instant key response and smooth 120fps scrolling even in massive files.

Does Zed support VS Code extensions?

No. Zed has its own Wasm extension ecosystem. However:

  • Many language protocols (LSP) are supported natively
  • Themes can be converted (JSON-based)
  • Keybindings can be imported from VS Code

Can I use Zed for Python development?

Yes, excellent support:

  • pyright or basedpyright for type checking
  • ruff for ultra-fast linting/formatting
  • venv/conda auto-detection
  • Runnable tests via code lenses

What’s the Agent Client Protocol (ACP)?

ACP is Zed’s open standard for AI integration:

  • Universal Interface: Connect any AI provider
  • Tool Support: Agents can read files, run terminals
  • Multi-Model: GPT-5, Gemini 2.5, Claude, local models
  • Extensible: Third parties can build ACP agents

Does Zed have AI autocomplete?

Yes, multiple options:

  1. Zeta Model: Open-source, trained for Edit Prediction
  2. Frontier Models: GPT-5, Gemini, Claude via ACP
  3. Local Models: Ollama, LM Studio via BYOK

Summary

Strengths

  • Unmatched performance (GPUI, Rust, sub-ms latency)
  • Native CRDT collaboration (no plugins required)
  • Model-agnostic AI (ACP, BYOK, local models)
  • Wasm extensions (secure, fast, sandboxed)
  • Open source (transparent development)
  • Multi-platform (macOS, Linux, Windows)
  • Vim/Helix support (modal editing)

Weaknesses

  • Smaller extension ecosystem than VS Code
  • No webview/UI customization for extensions yet
  • Learning curve for non-VS Code users
  • Less mature than established IDEs for some workflows
  • Windows support still improving

Bottom Line

Zed is the future of code editors. By proving that a Rust-based, GPU-accelerated architecture can match and exceed Electron-based editors, Zed has set a new standard for performance and collaboration.

Who Should Switch to Zed:

  • Performance enthusiasts tired of Electron lag
  • Remote developers using WSL2 or SSH
  • Teams wanting native CRDT collaboration
  • Privacy advocates wanting local AI control
  • Vim users wanting modern features

Who Should Stay with VS Code:

  • Heavy extension users (niche plugins)
  • Enterprises with existing VS Code infrastructure
  • Developers needing webview-based extensions
  • Teams invested in Microsoft ecosystem

The Trajectory: Zed is rapidly maturing. As its extension ecosystem grows and Windows support improves, it becomes increasingly viable as a complete VS Code replacement. For early adopters and performance purists, the switch is already compelling.

For developers prioritizing typing speed, collaboration, and local AI control, Zed offers an experience that no Electron-based editor can match. The 120fps, sub-millisecond latency future is here – and it’s called Zed.

Updated: