Zed Editor
Zed stores downloaded Node package archives and related package-manager cache data for JavaScript and TypeScript workflows, along with application log files written during editor startup, extension activity, language-server communication, and background tasks. These caches help avoid re-downloading npm package tarballs and speed repeated environment setup, while the logs capture diagnostics when project indexing, package resolution, or integrations misbehave. Kudu removes Zed's Node package cache and accumulated logs only, leaving projects, settings, extensions, accounts, and editor history untouched.
Why clean Zed Editor?
- Corrupted downloaded npm tarballs in Zed's Node cache can make dependency setup fail with repeated package extraction or integrity errors inside the editor
- A stale package cache can keep Zed reusing bad archives after a network interruption, so JavaScript or TypeScript environments never finish preparing until the cache is rebuilt
- Old cached package data can conflict with newer lockfiles or registry metadata, showing up as missing modules, failed installs, or language features not activating in one project
- Runaway log growth from repeated language-server crashes or extension errors can consume hundreds of megabytes and shows up as unexpected disk usage in the Zed cache folders
- Large log directories slow down troubleshooting because the newest startup or package-resolution errors are buried under old sessions, making current problems harder to isolate
- After clearing damaged cache entries, Zed fetches fresh Node package archives on demand, which often resolves stuck dependency bootstrap loops without affecting source files or editor settings
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.