zed/docs/src/macos.md
Xin Zhao 6aa90e750d
Some checks are pending
Congratsbot / check-author (push) Waiting to run
Congratsbot / congrats (push) Blocked by required conditions
deploy_nightly_docs / deploy_docs (push) Waiting to run
run_tests / check_postgres_and_protobuf_migrations (push) Blocked by required conditions
run_tests / orchestrate (push) Waiting to run
run_tests / check_style (push) Waiting to run
run_tests / extension_tests (push) Blocked by required conditions
run_tests / clippy_windows (push) Blocked by required conditions
run_tests / clippy_linux (push) Blocked by required conditions
run_tests / clippy_mac (push) Blocked by required conditions
run_tests / clippy_mac_x86_64 (push) Blocked by required conditions
run_tests / run_tests_windows (push) Blocked by required conditions
run_tests / run_tests_linux (push) Blocked by required conditions
run_tests / run_tests_mac (push) Blocked by required conditions
run_tests / doctests (push) Blocked by required conditions
run_tests / check_workspace_binaries (push) Blocked by required conditions
run_tests / build_visual_tests_binary (push) Blocked by required conditions
run_tests / check_wasm (push) Blocked by required conditions
run_tests / check_dependencies (push) Blocked by required conditions
run_tests / check_docs (push) Blocked by required conditions
run_tests / check_licenses (push) Blocked by required conditions
run_tests / check_scripts (push) Blocked by required conditions
run_tests / tests_pass (push) Blocked by required conditions
docs: Update actions format (#54869)
Self-Review Checklist:

- [ ] I've reviewed my own diff for quality, security, and reliability
- [ ] Unsafe blocks (if any) have justifying comments
- [ ] The content is consistent with the [UI/UX
checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
- [ ] Tests cover the new/changed behavior
- [ ] Performance impact has been considered and is acceptable

Change the actions in docs to adopt the right format.

Release Notes:

- N/A
2026-05-07 06:55:11 +00:00

3.5 KiB

title description
Zed on macOS Zed is developed primarily on macOS, making it a first-class platform with full feature support.

Zed on macOS

Zed is developed primarily on macOS, making it a first-class platform with full feature support.

Installing Zed

Download Zed from the download page. The download is a .dmg file—open it and drag Zed to your Applications folder.

For the preview build, which receives updates about a week ahead of stable, visit the preview releases page.

After installation, Zed checks for updates automatically and prompts you when a new version is available.

Homebrew

You can also install Zed using Homebrew:

brew install --cask zed

For the preview version:

brew install --cask zed@preview

Building from Source

To build Zed from source, see the macOS development documentation.

System Requirements

  • macOS 10.15.7 (Catalina) or later
  • Apple Silicon (M1/M2/M3/M4) or Intel processor

Zed uses Metal for GPU-accelerated rendering, which is available on all supported macOS versions.

Installing the CLI

Zed includes a command-line tool for opening files and projects from Terminal. To install it:

  1. Open Zed
  2. Open the command palette with Cmd+Shift+P
  3. Run {#action cli::InstallCliBinary}

This creates a zed command in /usr/local/bin. You can then open files and folders:

zed .                    # Open current folder
zed file.txt             # Open a file
zed project/ file.txt    # Open a folder and a file

See the CLI Reference for all available options.

Uninstall

  1. Quit Zed if it's running
  2. Drag Zed from Applications to the Trash
  3. Optionally, remove your settings and extensions:
rm -rf ~/.config/zed
rm -rf ~/Library/Application\ Support/Zed
rm -rf ~/Library/Caches/Zed
rm -rf ~/Library/Logs/Zed
rm -rf ~/Library/Saved\ Application\ State/dev.zed.Zed.savedState

If you installed the CLI, remove it with:

rm /usr/local/bin/zed

Troubleshooting

Zed won't open or shows "damaged" warning

If macOS reports that Zed is damaged or can't be opened, it's likely a Gatekeeper issue. Try:

  1. Right-click (or Control-click) on Zed in Applications
  2. Select "Open" from the context menu
  3. Click "Open" in the dialog that appears

This tells macOS to trust the application.

If that doesn't work, remove the quarantine attribute:

xattr -cr /Applications/Zed.app

CLI command not found

If the zed command isn't available after installation:

  1. Check that /usr/local/bin is in your PATH
  2. Try reinstalling the CLI via {#action cli::InstallCliBinary} in the command palette
  3. Open a new terminal window to reload your PATH

GPU or rendering issues

Zed uses Metal for rendering. If you experience graphical glitches:

  1. Ensure macOS is up to date
  2. Restart your Mac to reset the GPU state
  3. Check Activity Monitor for GPU pressure from other apps

High memory or CPU usage

If Zed uses more resources than expected:

  1. Check for runaway language servers in the terminal output ({#action zed::OpenLog})
  2. Try disabling extensions one by one to identify conflicts
  3. For large projects, consider using project settings to exclude unnecessary folders from indexing

For additional help, see the Troubleshooting guide or visit the Zed Discord.