Apps
npm Cache
npm keeps a local content-addressable cache of downloaded package tarballs, package metadata, and integrity index entries so installs can reuse artifacts instead of fetching everything again. Over time, the _cacache store and legacy Windows npm-cache folders can accumulate stale metadata, partial downloads, and old tarballs from many install sessions. Kudu removes these cached npm artifacts only, freeing disk space and clearing corrupted cache entries without touching your projects, node_modules folders, lockfiles, accounts, or npm configuration.
Why clean npm Cache?
- A corrupted tarball or incomplete download in npm's content-addressable cache can trigger EINTEGRITY, Z_DATA_ERROR, or unexpected end of JSON input errors during install
- Stale package metadata causes npm to resolve against outdated dist-tags or manifest details, which shows up as installs pulling an older version than you expected
- Years of cached package tarballs from temporary installs, CI scripts, and global tool updates can grow the cache into multiple gigabytes and leave low disk space warnings
- Interrupted installs may leave cache index entries pointing at unusable content, causing repeated fetch retries and noticeably slower npm install runs
- Systems upgraded from older npm versions on Windows can keep both current and legacy cache locations, so duplicate cached artifacts waste space with no benefit
- If npm repeatedly reuses a bad cached response, package installs may fail offline or on flaky networks until the damaged cache entries are removed
- Cache verification can fix integrity records, but it does not compact the store layout; clearing it fully removes obsolete tarballs and metadata while leaving your actual projects untouched
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/npm-cache |
%AppData%/npm-cache |
macOS
~/.npm/_cacache |
Linux
~/.npm/_cacache |
Frequently asked
Common questions about npm 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.