Apps
Kudu
Kudu on Windows stores several Chromium and Electron runtime caches under its profile, including HTTP disk cache entries in Cache_Data, V8 compiled script data in Code Cache, GPU shader and rendering artifacts in GPUCache, and rotating diagnostic logs in logs. These files speed up the app after the first run, but they can become stale after Kudu, Chromium, or graphics driver updates; Kudu removes only rebuildable cache and old log data while leaving your settings, accounts, saved preferences, and active files protected by recency and lock checks.
Why it matters
Why clean Kudu?
- Outdated HTTP disk cache entries in Cache_Data can leave parts of Kudu's interface stuck on old assets, showing blank panels, missing styling, or views that do not refresh correctly until the cache is rebuilt
- Invalidated V8 bytecode in Code Cache after an Electron or app update can make Kudu start slowly or pause on first open while scripts are recompiled
- Stale GPUCache data after a graphics driver update can cause Chromium's GPU pipeline to reject old shader artifacts, leading to black windows, flicker, or jerky scrolling until fresh cache files are generated
- Corrupted GPU cache files can trigger rendering glitches such as invisible icons, broken transparency, or white flashes when switching between screens
- Accumulated logs in Kudu's logs folder can grow unexpectedly during repeated startup failures or debug-heavy sessions, consuming disk space and making it harder to spot current errors
- A damaged browser cache can keep failed responses and partial downloads around, so embedded web content may repeatedly load incorrectly even though your network connection is fine
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.