Browsers
Microsoft Edge
Built on Chromium, Microsoft Edge stores several layers of temporary browser data under its profile, including HTTP disk cache entries, Media Cache files, GPUCache data, Code Cache bytecode for JavaScript and WASM, and service worker cache storage used by web apps. These files speed up page loads, video playback, and script startup, but they can become oversized or stale after browser, site, or graphics driver changes. Kudu removes Edge’s disposable cache data while leaving bookmarks, passwords, cookies, history, extensions, and account information untouched.
Why clean Microsoft Edge?
- Corrupted HTTP cache entries can make sites load with missing images, broken CSS, or old page content even after a normal refresh
- An oversized Media Cache can consume gigabytes of disk space and show up as unexpectedly large browser storage on systems with limited SSD space
- Stale GPUCache data after a graphics driver update can trigger black boxes, flickering pages, or WebGL rendering glitches until Edge rebuilds the cache
- Invalidated Code Cache bytecode after an Edge or site update can cause unusually slow first loads of heavy web apps while JavaScript and WASM are recompiled
- Broken service worker cache storage can leave installed web apps serving outdated assets, causing login loops, blank shells, or pages that refuse to update
- Damaged cache index files can lead to repeated redownloads, spinning tabs, or ERR_CACHE_READ_FAILURE and similar page load errors
- Cache and internal SQLite database files can become page-fragmented over time; VACUUM rewrites the database pages without deleting your saved data, which can reduce wasted space and improve cache metadata access
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/Microsoft/Edge/User Data |
macOS
~/Library/Application Support/Microsoft Edge |
Linux
~/.config/microsoft-edge |
Frequently asked
Common questions about Microsoft Edge
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.