Apps
electron-builder Cache
Electron-builder keeps a download cache of build-time artifacts such as Electron ZIP packages, NSIS installers, winCodeSign bundles, AppImage tools, and other helper binaries so packaging jobs do not fetch them again on every run. These files are stored under its Cache directory and can accumulate across Electron versions, target platforms, and failed downloads, especially in CI or active release workflows. Kudu removes only these re-downloadable cached archives and extracted helper files, not your app source, build configuration, signing credentials, or packaged releases.
Why clean electron-builder Cache?
- A partially downloaded Electron or helper archive can trigger checksum mismatches or extraction errors, which you would see as packaging failures that disappear after the file is fetched again
- Old cached artifacts from previous Electron or target builds pile up across versions and architectures, leading to unexpectedly large disk usage under the electron-builder cache folder
- Stale winCodeSign, NSIS, or AppImage helper bundles can cause signing or installer creation steps to fail with missing file or corrupted archive messages during build
- Interrupted CI jobs often leave incomplete cached downloads behind, and the next run may repeatedly fail at the same download or unpack stage until the bad cache is removed
- Switching between branches, Electron versions, or platform targets can leave multiple unused binary archives in place, making local builds consume storage long after those versions are no longer used
- Corrupted extracted tool directories can produce hard-to-diagnose build errors such as helper executable launch failures, permission errors, or unexpected exit codes during packaging
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/electron-builder/Cache |
macOS
~/Library/Caches/electron-builder |
Linux
~/.cache/electron-builder |
Frequently asked
Common questions about electron-builder Cache
Related cleaners
Free & open source
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.