How to Remove Pacman Cache on Linux

Before You Clean

Pacman’s downloaded packages can be useful for reinstalls or downgrades. Removing every cached version trades away that fallback.

Review and Clean Manually

1. Check /var/cache/pacman/pkg usage and finish any running package operation.

2. If pacman-contrib is installed, inspect paccache --help and preview pruning with paccache -d.

3. Use sudo paccache -r only after reviewing the preview. Its default retention keeps recent versions rather than deleting every package.

4. Avoid pacman -Scc as routine maintenance when cached packages are needed for recovery. Never delete pacman’s database or lock files to save space.

5. Verify available space and keep a known-good recovery plan.

Where Kudu Helps

Kudu can scan Pacman Package Cache, but a broad file selection does not implement paccache’s version-retention policy. If retaining rollback packages matters, use paccache and leave that cache out of Kudu’s cleanup.

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