Upscayl
Built on Electron, Upscayl accumulates Chromium web cache entries, V8 compiled code in Code Cache, GPUCache data, Dawn/WebGPU shader pipeline blobs in DawnCache, and rotated log files while rendering its interface and running GPU-accelerated upscaling sessions. Those caches exist to speed up UI loading, script execution, and graphics pipeline creation, but they can go stale after app, driver, or runtime changes. Kudu clears only these disposable cache and log folders so Upscayl can rebuild them cleanly, while your image databases, saved settings, models, and queued work remain untouched.
Why clean Upscayl?
- Invalidated V8 bytecode after an Upscayl or Electron update can make the first launch hang on a blank or half-drawn window until Code Cache is rebuilt
- Stale GPUCache entries after a graphics driver update can cause rendering glitches, black panels, or sluggish scrolling in the Upscayl interface
- Outdated DawnCache shader and pipeline blobs from an older WebGPU or Direct3D state can trigger stutter when starting an upscale job or switching processing options
- Corrupted Chromium Cache_Data files can leave thumbnails, icons, or embedded UI assets missing even though the app itself is still installed correctly
- Large settled log folders keep growing after repeated failed jobs, model load errors, or backend crashes, wasting disk space and making troubleshooting folders harder to review
- A cache built against previous GPU capabilities can lead to inconsistent startup behavior, including sudden window closes or delayed job initialization, until fresh GPU artifacts are generated
Cache paths Kudu targets
Windows
%AppData%/Upscayl/Cache/Cache_Data |
%AppData%/Upscayl/Code Cache |
%AppData%/Upscayl/GPUCache |
%AppData%/Upscayl/DawnCache |
%AppData%/Upscayl/logs |
Common questions about Upscayl
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.