zed-industries

    zed-industries/zed

    #94 this week

    Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.

    backend
    gpui
    rust-lang
    text-editor
    zed
    Rust
    NOASSERTION
    86.5K stars
    9.4K forks
    86.5K GitHub watchers
    Updated 7/6/2026
    View on GitHub

    Backblaze Generative Media Hackathon

    Build the next generation of AI media apps with Genblaze, stored on Backblaze B2. $10,000 in prizes.

    Enter the hackathon

    Loading star history...

    Use Cases & Benefits

    • Zed is a high-performance, multiplayer code editor designed for fast, collaborative coding experiences.
    • Built in Rust, it leverages technologies from Atom and Tree-sitter for advanced text editing and syntax parsing.
    • Currently supports macOS and Linux with Windows and web versions in development, indicating some platform limitations.
    • With over 64,000 stars and 5,000 forks, Zed shows strong community interest and adoption.
    • Ideal for developers seeking a modern, collaborative editor with robust performance and real-time multiplayer features.

    About zed

    Zed

    Zed CI

    Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


    Installation

    On macOS and Linux you can download Zed directly or install Zed via your local package manager.

    Other platforms are not yet available:

    Developing Zed

    Contributing

    See CONTRIBUTING.md for ways you can contribute to Zed.

    Also... we're hiring! Check out our jobs page for open roles.

    Licensing

    License information for third party dependencies must be correctly provided for CI to pass.

    We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

    • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
    • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
    • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

    Discover Repositories

    Search across tracked repositories by name or description