How to Clean Up Flatpak Files on Linux

Before You Clean

Flatpak runtimes, cached downloads, and per-app data are distinct. The whole ~/.var/app directory includes settings and user data, not only cache.

Review and Clean Manually

1. Inspect installed apps and runtimes with flatpak list. Check whether they are installed for the user or system-wide.

2. Review unused user runtimes with flatpak uninstall --user --unused. Read the proposed removals before confirming.

3. For system installations, use flatpak uninstall --system --unused only with the appropriate permission and after reviewing the list.

4. Keep app data unless explicitly removing it is part of the job. Do not use --delete-data or delete ~/.var/app wholesale as cache cleanup.

5. Reopen apps and confirm required runtimes and local data remain.

Where Kudu Helps

Kudu’s Linux system rules target per-app cache subdirectories and Flatpak repository temporary data. They do not prune installed runtimes or erase the entire app sandbox. Use Flatpak itself for runtime removal.

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