Apps
Kudu
Kudu stores several Chromium and Electron runtime caches under its Windows profile, including HTTP disk cache entries in Cache_Data, V8 compiled script data in Code Cache, GPU process cache files in GPUCache, and rotating diagnostic logs in logs. These files speed up loading the app shell, reusing fetched web assets, and caching rendered or compiled resources, but they can become stale after an app or graphics driver update; Kudu removes only those disposable caches and old logs while leaving user data, settings, accounts, and passwords untouched.
Why clean Kudu?
- Outdated HTTP cache entries in Cache_Data can make Kudu load an older app shell or asset bundle, which shows up as missing UI fixes, broken styling, or a screen that does not match the current release
- Invalidated V8 bytecode in Code Cache after a Kudu update can cause a noticeably slow first launch, repeated renderer restarts, or a blank window until the scripts are recompiled
- Stale GPUCache data from a previous graphics driver version can trigger black panels, flickering, or sluggish redraws because Chromium's cached GPU resources no longer match the current driver
- Corrupted Chromium disk cache records can lead to buttons that do nothing, partial page loads, or sign-in views that never finish rendering even though the network is working
- Large accumulated logs in the logs folder waste profile disk space and make troubleshooting harder by burying current errors under old startup traces and renderer crash reports
- After many updates, cache folders can keep obsolete web assets and compiled code that Kudu no longer uses, leading to unnecessary profile growth and longer cleanup or backup times
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/kudu/Cache/Cache_Data |
%AppData%/kudu/Code Cache |
%AppData%/kudu/GPUCache |
%AppData%/kudu/logs |
Frequently asked
Common questions about Kudu
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.