Cromite
Built on Chromium, Cromite writes the same kinds of local browser cache data as other Chromium-based browsers: HTTP disk cache entries for pages, images, scripts and media, GPUCache files for Skia and shader-related data, Code Cache bytecode for JavaScript and WASM, and temporary storage left by service workers and site storage layers. Over time those files can become oversized or stale after browser, site, or graphics driver changes, leading to broken rendering or odd load behavior; Kudu removes only disposable cache data from Cromite’s profile while leaving bookmarks, passwords, cookies, history, extensions, and settings alone.
Why clean Cromite?
- Corrupted HTTP cache entries can make sites load with missing images, broken CSS, or old page content even after a normal refresh
- Stale Code Cache bytecode after a Cromite update can cause one-time slow launches, script errors, or pages that feel stuck before they rebuild
- GPUCache data invalidated by a graphics driver update can trigger black rectangles, flickering video, or visual glitches until Chromium regenerates it
- Oversized media and resource cache files can consume several gigabytes under the profile folder, leaving users wondering why Cromite keeps growing on disk
- Outdated service worker and temporary site cache data can keep a web app serving an older offline copy, so changes on the site do not appear when expected
- Bad cached network responses can cause endless reload loops, login pages that never finish rendering, or sites that work in a private window but not in the normal profile
- SQLite-backed storage used by browser components can accumulate page fragmentation over time; VACUUM rewrites the database file to compact free pages without deleting your saved rows
Cache paths Kudu targets
Windows
%LocalAppData%/Cromite/User Data |
macOS
~/Library/Application Support/Cromite |
Linux
~/.config/cromite |
Common questions about Cromite
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.