Battle.net
Battle.net relies on an embedded Chromium-based interface for its launcher screens, store pages, login flows, and social panels, which creates HTTP disk cache entries, image assets, JavaScript bundles, and Chromium GPU shader cache data under its local Cache folder. It also writes rotating launcher and update logs in both LocalAppData and Roaming profile locations to record agent activity, patching events, authentication handoffs, and UI errors; Kudu removes these disposable web cache files and log files without touching installed games, account data, saved credentials, or settings.
Why clean Battle.net?
- Stale Chromium web cache can leave the launcher stuck showing outdated news panels, missing store artwork, or blank social panes until the cached HTML, scripts, and images are rebuilt
- Invalid GPU cache entries after a graphics driver update can cause black launcher windows, flickering tabs, or sluggish scrolling because old shader data no longer matches the current driver
- Corrupted cached JavaScript bundles or API responses can break login and shop views, leading to endless loading spinners, buttons that do nothing, or pages that never fully render
- Oversized Battle.net log folders accumulate patcher, updater, and agent diagnostics over time, consuming noticeable disk space even though the files are only useful for troubleshooting
- Repeated launcher errors get recorded across both LocalAppData and Roaming log locations, making support logs noisy and harder to review when you are trying to diagnose a current install or update problem
- Cached CDN files from interrupted launcher updates can cause the app to repeatedly re-download interface assets or open slowly while it retries failed web content requests
Cache paths Kudu targets
Windows
%LocalAppData%/Battle.net/Cache |
%LocalAppData%/Blizzard Entertainment/Battle.net/Logs |
%AppData%/Battle.net/Logs |
Common questions about Battle.net
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.