qBittorrent
qBittorrent writes session and diagnostic log files that record libtorrent activity, tracker announces, peer connections, RSS updates, WebUI events, and transfer errors while torrents are running. These text logs can accumulate over time after long seeding sessions, repeated tracker failures, or verbose troubleshooting, taking up space and preserving stale error history that no longer reflects the current state of your client. Kudu removes qBittorrent's disposable log files only, without touching your torrents, resume data, categories, settings, accounts, or downloaded content.
Why clean qBittorrent?
- Large accumulated session and error logs from months of seeding make the qBittorrent cache folder grow unexpectedly, so you notice disk usage increasing even when no new downloads were added
- Old tracker timeout and connection failure entries bury current events in the logs, making it harder to troubleshoot why a torrent is stalled or why peers are not connecting right now
- Repeated logging of unreachable trackers, RSS refresh failures, or WebUI login attempts can generate many small writes, which is most noticeable on low-space systems where qBittorrent's support files keep expanding
- After network, VPN, or proxy changes, stale historical log noise can make normal operation look broken because the log still shows pages of previous socket and announce errors
- Verbose logs created during debugging sessions continue consuming space long after the original issue is fixed, and users typically only notice when the application support folder becomes unusually large
- Clearing old qBittorrent logs gives you a clean diagnostic baseline, so any new tracker, DHT, or peer connection errors are easier to spot instead of being mixed with obsolete warnings
Cache paths Kudu targets
Windows
%LocalAppData%/qBittorrent/logs |
macOS
~/Library/Application Support/qBittorrent/logs |
Linux
~/.cache/qBittorrent |
Common questions about qBittorrent
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.