SystemRequires admin/root
Snap Cache
Snapd keeps downloaded .snap package files in /var/lib/snapd/cache so installs, refreshes, and rollbacks can reuse local copies instead of fetching them again. Over time this directory accumulates superseded snap revision archives and partial download artifacts that are no longer needed after newer revisions are installed. Kudu clears those cached snap package files from snapd’s system cache without touching installed snaps, user data, accounts, or application settings.
Why clean Snap Cache?
- Old snap revision archives stay behind after repeated refreshes, so /var fills up and users start seeing low disk space warnings or failed package operations
- Large cached .snap files in /var/lib/snapd/cache can consume several gigabytes on systems with many snaps installed, leaving less room for logs, updates, and temporary files
- Interrupted or partial snap downloads can linger in the cache and contribute to repeated refresh retries, with users noticing stuck or repeatedly restarting snap update jobs
- When the cache contains obsolete package archives from superseded revisions, rollbacks and refresh logic may still keep extra disk reserved even though the active snap is working normally
- Systems with small root partitions are especially affected because snapd stores its cache under /var, and the visible symptom is refreshes or installs failing with no space left on device errors
- Cleaning removes only reusable download artifacts, so it is a practical way to recover space when snap operations are blocked by cache growth while leaving installed applications and their data intact
What gets cleaned
Cache paths Kudu targets
Linux
/var/lib/snapd/cache |
Frequently asked
Common questions about Snap 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.