Apps
Audacious
Playback in Audacious can leave behind temporary files under ~/.cache/audacious, including cached album art, decoded stream buffers, and plugin-generated metadata thumbnails used to speed up library browsing and internet radio playback. When those cache files become stale or oversized, Kudu removes them so Audacious can rebuild fresh artwork and stream cache data without touching playlists, equalizer settings, plugins, or saved stations.
Why clean Audacious?
- Stale cached album art keeps showing the wrong cover after tags or embedded artwork change, so tracks display outdated images even though the files were updated
- Corrupted stream buffer files from interrupted internet radio sessions can cause playback to stall, skip, or reconnect repeatedly when reopening the same station
- Oversized cached artwork and metadata from large music libraries waste disk space and make cache directory scans slower during startup
- Old plugin cache entries can keep showing incorrect track details or thumbnails until Audacious is forced to rebuild them from the source files
- After library retagging or replacing music files in place, cached metadata may not match the current files, leading to mismatched covers and confusing now-playing information
- Removing accumulated temporary cache files helps resolve odd one-off issues like missing artwork refreshes or delayed stream starts without affecting playlists or user preferences
What gets cleaned
Cache paths Kudu targets
Linux
~/.cache/audacious |
Frequently asked
Common questions about Audacious
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.