Gaming
Lutris
Game installs and runners in Lutris create a local cache under ~/.cache/lutris for downloaded installer scripts, game assets, wine runner archives, and temporary files used while setting up or updating games. Those files speed up reinstalls and avoid re-downloading the same packages, but they can become outdated, partially downloaded, or simply accumulate after many installs. Kudu removes Lutris download and installer cache contents while leaving your installed games, prefixes, accounts, and configuration untouched.
Why clean Lutris?
- A broken or interrupted runner download in the Lutris cache can make installs fail repeatedly with checksum or extraction errors until the bad archive is removed
- Old cached installer files can cause Lutris to reuse outdated setup data, leading to launchers installing the wrong version or failing after a script update
- Repeated game installs and test setups leave large runner archives and installer downloads behind, so users notice ~/.cache/lutris consuming several gigabytes of disk space
- Stale temporary installer data can make a reinstall behave inconsistently, such as skipping expected download steps or stopping early because Lutris thinks required files are already present
- Corrupted cached game assets often show up as install loops, immediate unpacking failures, or wine setup errors during the preparation stage
- Cleaning the cache forces Lutris to fetch fresh installer resources, which helps when a game suddenly stops installing even though your library entries, prefixes, and settings are still intact
What gets cleaned
Cache paths Kudu targets
Linux
~/.cache/lutris |
Frequently asked
Common questions about Lutris
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.