Apps
CurseForge
Built on Electron, CurseForge stores Chromium disk cache entries in Cache_Data, V8 code cache files in Code Cache, GPU process data in GPUCache, and rotating launcher logs under logs while it renders the mod browser, embedded web views, and app UI. Those files speed up image loading, JavaScript startup, and hardware-accelerated rendering, but they can become stale after app or graphics driver updates. Kudu removes these temporary browser-style caches and log files without touching installed modpacks, game instances, account sign-in data, or app settings.
Why clean CurseForge?
- Invalidated V8 bytecode after a CurseForge update can make the launcher open slowly or sit on a blank window before the interface rebuilds
- Corrupted Chromium disk cache entries can leave mod thumbnails, category pages, or in-app web content stuck loading even though your internet connection works
- Stale GPUCache data from a graphics driver update can cause black panels, flickering, or missing rendered elements in the Electron interface
- An oversized Cache_Data folder can waste gigabytes on old images and web resources, especially after browsing many modpacks and project pages
- Accumulated log files can grow during repeated startup failures or addon sync errors, filling AppData and making troubleshooting harder because current errors are buried in old noise
- Cached API and webview assets that no longer match CurseForge's current frontend can produce broken buttons, partial page rendering, or endless spinners in the browse view
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/CurseForge/Cache/Cache_Data |
%AppData%/CurseForge/Code Cache |
%AppData%/CurseForge/GPUCache |
%AppData%/CurseForge/logs |
Frequently asked
Common questions about CurseForge
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.