Gaming
Battle.net
Battle.net writes rotating launcher log files under LocalAppData and Roaming AppData while it handles sign-in, update checks, game discovery, agent communication, and embedded web-based interface events. These text logs can grow over time as the client records patching failures, network retries, CDN requests, and startup diagnostics for Blizzard Agent and the launcher shell. Kudu removes only these Battle.net log files to recover disk space and clear accumulated diagnostic noise without touching installed games, account data, saved settings, or login credentials.
Why clean Battle.net?
- Launcher and Agent retry loops can generate large volumes of repeated network and patcher log lines, showing up as Battle.net using far more AppData space than expected
- Persistent update or login failures leave behind old diagnostics that make current launcher problems harder to isolate when you need fresh logs for support
- Repeated game-scan and install-detection errors can produce constantly growing logs, and the visible symptom is disk usage increasing even when no games are being downloaded
- Long histories of CDN timeout, authentication, and agent handshake entries clutter troubleshooting, so clearing them helps confirm whether a fix actually stopped the current error
- Crash and startup diagnostics from older launcher builds remain after updates, which can leave confusing references to issues you no longer see in the current Battle.net client
- Background patch service problems often cause log spam every time Windows starts, and users typically notice fan noise, brief disk activity, or AppData cleanup tools reporting oversized Battle.net folders
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/Blizzard Entertainment/Battle.net/Logs |
%AppData%/Battle.net/Logs |
Frequently asked
Common questions about Battle.net
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.