https://github.com/deevus/zed-windows-builds
Unofficial nightly builds of the Zed editor for Windows
https://github.com/deevus/zed-windows-builds
Last synced: 13 days ago
JSON representation
Unofficial nightly builds of the Zed editor for Windows
- Host: GitHub
- URL: https://github.com/deevus/zed-windows-builds
- Owner: deevus
- Created: 2024-07-20T02:39:30.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2026-05-21T05:47:46.000Z (29 days ago)
- Last Synced: 2026-05-21T10:21:51.442Z (29 days ago)
- Language: Shell
- Size: 130 KB
- Stars: 1,368
- Watchers: 20
- Forks: 90
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
Awesome Lists containing this project
README
# Unofficial builds of Zed for Windows
[](https://github.com/deevus/zed-windows-builds/actions/workflows/test.yml)
[](https://github.com/deevus/zed-windows-builds/actions/workflows/test-integration.yml)
[](https://github.com/deevus/zed-windows-builds/actions/workflows/nightly.yml)
[](https://github.com/deevus/zed-windows-builds/actions/workflows/stable.yml)
> [!NOTE]
> **Official Windows builds are now available!** Download Zed for Windows from the official website: https://zed.dev/download
>
> This repository continues to provide unofficial community builds for:
>
> - **OpenGL stable builds** — for systems where Vulkan/DX11 isn't available (Zed upstream does not ship an OpenGL variant)
> - **Nightly builds** (Vulkan and OpenGL) — for users who want bleeding-edge commits
>
> The Scoop `extras/zed` manifest now pulls stable Vulkan/DX11 builds directly from `zed-industries/zed` upstream — this repo no longer produces stable Vulkan/DX11 builds.
**NOTE: This is not a support channel for Zed on Windows.**
These builds are for those who want to live on the bleeding edge or just want to test Zed out on Windows.
Any issues with the Windows build should go through official channels, as this repository does not concern itself with the source code of Zed or issues found therein.
If you have suggestions for improvements to the build process, please start a discussion or make a PR.
All installation instructions below require that [Scoop](https://scoop.sh/) is installed on your system.
## Stable version
Zed's Scoop manifest now uses official upstream binaries from `zed-industries/zed`:
```pwsh
scoop bucket add extras
scoop install extras/zed
```
## Nightly builds
```pwsh
scoop bucket add versions
scoop install versions/zed-nightly
```
## DX11 doesn't work for you?
Install the OpenGL version
### Stable OpenGL version
```pwsh
scoop bucket add extras
scoop install extras/zed-opengl
```
### Nightly OpenGL version
```pwsh
scoop bucket add versions
scoop install versions/zed-opengl-nightly
```
### For Windows 10 users
Zed may not start unless you install the [Microsoft Visual C++ Redistributable 2022](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022) package. If you are using Scoop, you can install it using the following command:
```pwsh
scoop bucket add extras
scoop install vcredist2022
```
## Updates
```pwsh
# Stable version
scoop update zed
# Stable OpenGL version
scoop update zed-opengl
# Nightly version
scoop update zed-nightly
# Nightly OpenGL version
scoop update zed-opengl-nightly
```
## Is it safe?
This repository is just a [simple GitHub workflow](./.github/workflows/build.yml) that builds Zed from `main` and publishes a release every night at UTC+0000. (Additionally on push for testing).
See the [Zed homepage](https://zed.dev/) or [official repository](https://github.com/zed-industries/zed) for more details.
## Build Process
The build process is designed to be robust and handle partial failures gracefully:
- **Resilient Builds**: If one build variant (DX11 or OpenGL) fails, the other will still complete and create a release
- **Comprehensive Testing**: All build scripts are thoroughly tested with automated test suites
- **Quality Assurance**: Each release includes SHA256 checksums for integrity verification
### Testing
The build and release scripts are automatically tested with every change:
- **Script Tests**: Unit tests for the release preparation logic
- **Integration Tests**: End-to-end testing of the build and release workflows
- **Failure Scenarios**: Testing of partial build failures to ensure robust handling
See the [scripts directory](./scripts/) for more details about the testing infrastructure.