Zed Editor
Zed stores temporary package and runtime data on disk so its bundled Node-based features can avoid downloading the same npm package tarballs and metadata repeatedly, and it also writes diagnostic log files for the editor, language tooling, and background services. Over time that cache can accumulate stale package archives, outdated package index data, and oversized logs that no longer match the current build or extension state. Kudu removes Zed's downloaded Node package cache and log files only, leaving projects, editor settings, accounts, keymaps, and installed source code untouched.
Why clean Zed Editor?
- Corrupted npm package tarballs or metadata in Zed's Node cache can make extension or language helper downloads fail, showing repeated install errors or features that never finish setting up
- Outdated cached package data after a Zed update can cause the editor to re-try dependency resolution on every launch, which users notice as slow startup and repeated background download activity
- A partially written cache entry from an interrupted download can leave Node-powered features stuck in a broken state, with formatters, linters, or language servers failing to start until the cache is rebuilt
- Large accumulated logs from crashes, extension failures, or verbose diagnostics can consume hundreds of megabytes, leading users to notice Zed taking more disk space than expected
- Stale logs make troubleshooting harder because current errors are buried under old sessions, and clearing them gives a clean record the next time a launch failure or extension problem is reproduced
- Cache directories under Zed's app data can keep obsolete package versions that are no longer used, so cleaning removes dead download artifacts while preserving workspaces, settings, and login state
Cache paths Kudu targets
Windows
%LocalAppData%/Zed/node/cache |
%LocalAppData%/Zed/logs |
macOS
~/Library/Caches/dev.zed.Zed |
~/Library/Logs/Zed |
Linux
~/.cache/zed |
Common questions about Zed Editor
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.