How to Remove Snap Cache on Linux

Before You Clean

Snap downloads, retained revisions, and per-app data have different lifecycles. Do not treat /var/lib/snapd or ~/snap as one disposable cache.

Review and Clean Manually

1. Inspect installed revisions with snap list --all and check disk usage.

2. Finish any running snap change before maintenance.

3. If removing an old disabled revision is justified, use sudo snap remove NAME --revision=REVISION for the exact reviewed revision. Keep a usable rollback version.

4. Do not delete installed .snap files, snapshots, or app data by hand. Do not pipe every disabled revision into removal without review.

5. Check the app starts and its documents and settings remain.

Where Kudu Helps

Kudu targets Snap’s download cache and per-app common/.cache subdirectories. It does not remove installed snap revisions or snapshots; use snap’s own commands for those.

Open Clean up > System Cleaner and run Scan. Review the relevant category and expand its results to inspect the paths. Set exclusions for anything you need to keep, then check the full selected total before Clean. Results search filters the view; it does not erase selections elsewhere.

After cleaning, check the summary and Activity > Cleanup receipts for removed, skipped, or failed items. A receipt is an outcome record, not a backup. Recovery Centre restores supported settings, not deleted files. Compare actual disk free space and test the original symptom; cache removal alone is not a promise of better performance.

Download Kudu Free → · Cleaning reference

References

• Official maintenance documentation
• Kudu cleaner rules