Skip to content

Zed: High-Performance GPU-Accelerated Code Editor

Ultra-fast code editor written in Rust, featuring 120 FPS GPU-accelerated rendering, Tree-sitter AST parsing, real-time multiplayer collaboration, and native AI completions.

62.5kGPL-3.0 / AGPLRustUpdated Today
GitHub

Hardware Pre-Flight Check

Verify your system meets runtime requirements before setup

Verified Specs
System RAM4 GB MinRec: 8 GB
GPU VRAMCPU OnlyNo GPU Required
Free Storage~1 GBFast SSD Recommended
Accelerators
VulkanDirectX 12Apple MetalOpenGL

Will Zed run on your PC?

We can automatically scan your local GPU and System RAM right from the browser to see if your hardware meets the requirements for this repository. No downloads required.

3-Tier Audience Playbook

Actionable guidance tailored to your technical workflow

3 Experience Levels
Beginner Quickstart

Download the one-click installer from zed.dev. Open any project folder to enjoy instant typing latency and automatic syntax highlighting.

Intermediate Production

Configure custom keybindings (Vim mode included), connect GitHub Copilot or Anthropic Claude API keys for inline completions, and collaborate via channels.

Advanced Scaling

Write custom extensions in Rust using WebAssembly (WASM), configure granular Language Server Protocol (LSP) settings, and customize theme shaders.

What is Zed?

Zed is a next-generation code editor built by the original creators of Atom and Tree-sitter. Engineered from scratch in Rust, it rejects Electron in favor of direct GPU rendering, ensuring that every frame renders at the monitor’s native refresh rate (up to 120 FPS).

Zed couples raw rendering performance with native Tree-sitter parsing for accurate syntax trees, integrated Language Server Protocol (LSP) support, and built-in real-time collaborative editing.

Key Architectural Strengths

  • GPU-Accelerated Rendering: The entire interface is drawn directly using hardware graphics shaders (Metal on macOS, Vulkan/DirectX on Linux and Windows), eliminating DOM layout reflows.
  • Tree-sitter AST Core: Syntax highlighting, code navigation, and structural edits operate on dynamic Abstract Syntax Trees for superior precision.
  • Multiplayer Collaboration: Built-in shared workspace channels allow real-time multi-cursor pairing, shared terminals, and screen streaming.
  • WASM Extension Architecture: Extensions run in sandboxed WebAssembly runtimes, ensuring that third-party plugins cannot freeze the editor thread.

Installation & Setup

macOS & Windows

Download pre-packaged binaries directly from zed.dev or install via package managers:

# macOS with Homebrew
brew install --cask zed

# Windows with Winget
winget install ZedIndustries.Zed

Linux (Flatpak or Direct Script)

curl -f https://zed.dev/install.sh | sh

Configuration & Tuning

Configuration is stored in a clean JSON format at ~/.config/zed/settings.json:

{
  "theme": "One Dark",
  "vim_mode": true,
  "ui_font_size": 15,
  "buffer_font_size": 14,
  "telemetry": {
    "diagnostics": false,
    "metrics": false
  },
  "languages": {
    "TypeScript": {
      "format_on_save": "on",
      "formatter": {
        "external": {
          "command": "prettier",
          "arguments": ["--stdin-filepath", "{buffer_path}"]
        }
      }
    }
  }
}

Objective Alternatives & Tradeoffs Matrix

Head-to-head comparison without vendor bias or dismissal

VS Code Core• Execution speed & input latency vs ecosystem & plugin breadth
Compare Guide→
✓ Choose Zed if:

You value instantaneous file opening, zero typing lag, low memory footprint, and built-in real-time pairing.

⚖ Choose VS Code Core if:

You rely on rare specialized extensions, complex proprietary enterprise debuggers, or extensive GUI plugins.

Sublime Text• Open-source Rust architecture with native collaboration vs proprietary C++ codebase
Project Link↗
✓ Choose Zed if:

You want an open-source, actively evolving editor with native Git blame, AI integration, and collaborative pairing.

⚖ Choose Sublime Text if:

You prefer a mature closed-source editor with classic Python 3 plugin infrastructure.

Common Production Pitfalls & Gotchas

Battle-tested solutions for frequent setup errors and bottlenecks

!

Window rendering artifacts or black screen on older Linux distributions

Tested Fix:Ensure Vulkan graphics drivers are updated, or force software rendering fallback via command line flags.
!

Language Server Protocol (LSP) binary not detected in PATH

Tested Fix:Configure the explicit binary path in ~/.config/zed/settings.json under the 'lsp' configuration block.
!

Extension marketplace missing a specific VS Code plugin

Tested Fix:Zed uses WebAssembly extensions rather than Node.js packages; check Zed's official extensions registry or write a lightweight WASM wrapper.

Comments are powered by GitHub Discussions and will appear here once connected.