How to Clean Microsoft Edge Cache, Code Cache & Service Worker Bloat
Location & Quick Verdict
%LocalAppData%\Microsoft\Edge\User Data\Default\Cache and Service Worker\CacheStorage
Even if you use another primary browser, Windows 11 background widgets and WebView components populate Microsoft Edge's Cache and Service Worker folders.
How Embedded Chromium (Electron / CEF) Caches Bloated Microsoft Edge Cache, Code Cache & Service Worker Bloat
Modern web browsers and desktop apps built on Electron, Chromium Embedded Framework (CEF), or WebView2 run a full browser storage engine inside %LocalAppData%\Microsoft\Edge\User Data\Default\Cache and Service Worker\CacheStorage. Every inline video preview, animated sticker, PWA offline bundle, and compiled V8 JavaScript script is written into disk-backed Cache_Data, Code Cache, Service Worker CacheStorage, and IndexedDB LevelDB tables without strict disk quotas.
Over months of daily usage, Microsoft Edge Cache, Code Cache & Service Worker Bloat accumulates 1.5 GB – 8.0 GB of expired media blobs and stale Service Worker caches that are never evicted automatically. Clearing these cache subdirectories forces a clean storage state without deleting your saved passwords, active session cookies, bookmarks, or local databases.
# Inspect current disk footprint of Microsoft Edge Cache, Code Cache & Service Worker Bloat (Read-Only)
$target = "$env:LOCALAPPDATA\Microsoft\Edge\User Data\Default\Cache"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
Measure-Object -Property Length -Sum |
Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
Manual Cleaning Instructions
- 1 Close Microsoft Edge.
- 2 Press Windows Key + R, type %localappdata%\Microsoft\Edge\User Data\Default and press Enter.
- 3 Delete the 'Cache', 'Code Cache', 'GPUCache', and 'Service Worker\CacheStorage' directories.
Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.
Sub-Folders & Cache Locations Breakdown for Microsoft Edge Cache, Code Cache & Service Worker Bloat
Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside Microsoft Edge Cache, Code Cache & Service Worker Bloat are safe to purge and which files remain protected:
| Sub-Folder / Cache Location | Storage Role | Typical Footprint | Deletion Safety |
|---|---|---|---|
| %LocalAppData%\Microsoft\Edge\User Data\Default\Cache\Cache\Cache_Data | HTTP Disk Cache, Web Bundles & Static Media Chunks | 1.5 GB – 8.0 GB | 🟢 100% Safe |
| %LocalAppData%\Microsoft\Edge\User Data\Default\Cache\Service Worker\CacheStorage | Offline PWA Assets, Background Sync & Media Blob Storage | 500 MB – 6.5 GB | 🟢 100% Safe |
| %LocalAppData%\Microsoft\Edge\User Data\Default\Cache\Code Cache\js & wasm | V8 Compiled JavaScript & WebAssembly Bytecode Cache | 250 MB – 2.5 GB | 🟢 100% Safe |
| %LocalAppData%\Microsoft\Edge\User Data\Default\Cache\GPUCache & DawnCache | Chromium Skia/ANGLE/WebGPU Compiled Shader Cache | 200 MB – 2.0 GB | 🟢 100% Safe |
| %LocalAppData%\Microsoft\Edge\User Data\Default\Cache\Crashpad\reports | Historical Process Minidump (.dmp) Telemetry Files | 150 MB – 3.0 GB | 🟢 100% Safe |
| Cookies, Login Data, Bookmarks & Local Storage (leveldb) | Active Account Sessions, Saved Passwords & User Preferences | Protected | 🔒 Protected — Never Touched |
Frequently Asked Questions
Is it safe to delete Microsoft Edge Cache, Code Cache & Service Worker Bloat?
Yes, 100% safe. Reclaims gigabytes of hidden disk space without erasing saved passwords, favorites, or open tabs.
How much storage space will cleaning Microsoft Edge Cache, Code Cache & Service Worker Bloat free up?
Users typically reclaim 1.5 GB – 8.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %LocalAppData%\Microsoft\Edge\User Data\Default\Cache and Service Worker\CacheStorage.
Will clearing Microsoft Edge Cache, Code Cache & Service Worker Bloat sign me out of my accounts or delete my chat history?
No. Authentication tokens, cookies, and bookmarks live in separate profile files (such as Cookies, Login Data, and Local Storage). Cleaning the cache subfolders inside %LocalAppData%\Microsoft\Edge\User Data\Default\Cache and Service Worker\CacheStorage only removes temporary media and script caches.
Where is Microsoft Edge Cache, Code Cache & Service Worker Bloat located on Windows 10 and Windows 11?
It is stored at %LocalAppData%\Microsoft\Edge\User Data\Default\Cache and Service Worker\CacheStorage. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.
Manual File Explorer vs. 1-Click SWEEPR Cleanup
| Feature | Manual Deletion | SWEEPR Cleaner |
|---|---|---|
| Locked File Handling | Fails on locked processes | Safe background release |
| Accidental Deletion Risk | Moderate (easy to delete wrong folder) | Zero (strict rules & hashes) |
| Safety Undo Rollback | None (Shift+Del is permanent) | 7-Day Automatic Rollback |
| Time Required | 10–20 minutes per app | < 60 seconds across 40+ areas |
Related Windows Cleanup Guides & Hidden Space Hogs
Clean Microsoft Edge Cache, Code Cache & Service Worker Bloat Automatically
SWEEPR Cleaner safely clears Microsoft Edge Cache, Code Cache & Service Worker Bloat along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.