How to Clean Microsoft Edge WebView2 Shared Runtime Cache (EBWebView)

🟢 100% Safe to Delete Typical Space Reclaimed: 1.5 GB – 9.0 GB

Location & Quick Verdict

%LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache

Windows 11 widgets, Microsoft 365 apps, and modern desktop utilities embed Edge WebView2, accumulating gigabytes of cached web data.

Safety confirmation: Reclaims hidden SSD space while keeping Windows Widgets and Office add-ins working normally.

How Windows Manages Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) on NTFS & NVMe Drives

Windows 10 and Windows 11 maintain hidden system directories and root-level allocation files at %LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache to handle shell thumbnail databases, prefetcher launch traces, hibernation power states, and user-profile scratch storage. Because many of these paths are marked with +H (Hidden) or +S (System) attributes or guarded by SYSTEM ACL permissions, standard folder size scans often miss them entirely.

Over time, orphaned temporary files, stale Explorer DataCache_* buckets, and uncompacted virtual storage allocations inside %LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache lock up 1.5 GB – 9.0 GB of primary C: drive space. Cleaning Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) using the proper administrative method restores drive headroom safely.

PowerShell Size Verification (Read-Only Check):
# Inspect current disk footprint of Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) (Read-Only)
$target = "$env:LOCALAPPDATA\Microsoft\EdgeWebView\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)}}
🛡️ What Stays 100% Protected User documents, desktop files, Windows registry hives, boot configuration, and active system locks remain 100% protected.
⚡ What Gets Safely Removed Unlocked temporary scratch files, stale Explorer thumbnail/icon caches, obsolete prefetch traces, and reclaimable system allocations.

Manual Cleaning Instructions

  1. 1 Close Widgets and Office apps.
  2. 2 Navigate to %localappdata%\Microsoft\EdgeWebView\User Data\Default.
  3. 3 Delete the 'Cache', 'Code Cache', and 'GPUCache' folders.

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 WebView2 Shared Runtime Cache (EBWebView)

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 WebView2 Shared Runtime Cache (EBWebView) are safe to purge and which files remain protected:

Sub-Folder / Cache Location Storage Role Typical Footprint Deletion Safety
%LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache Primary System Scratch, Thumbnail/Icon DB or Virtual Allocation 1.5 GB – 9.0 GB 🟢 100% Safe (Unlocked Files)
%LocalAppData%\Temp & C:\Windows\Temp Orphaned Installer Extraction & Session Scratch Files 1.5 GB – 18.0 GB 🟢 100% Safe
%LocalAppData%\Microsoft\Windows\Explorer (thumbcache_*.db) Cached File Explorer Image & Video Thumbnail Databases 250 MB – 3.0 GB 🟢 100% Safe (Rebuilds Automatically)
User Documents, Desktop & Registry Hives Personal Files, Boot Configuration & System Certificates Protected 🔒 Protected — Never Touched

Frequently Asked Questions

Is it safe to delete Microsoft Edge WebView2 Shared Runtime Cache (EBWebView)?

Yes, 100% safe. Reclaims hidden SSD space while keeping Windows Widgets and Office add-ins working normally.

How much storage space will cleaning Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) free up?

Users typically reclaim 1.5 GB – 9.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache.

Why does Windows say some files in Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) are "In Use" when I try to delete them?

Active background processes (such as explorer.exe, svchost.exe, or running desktop apps) hold open file handles to current session scratch files. Skipping locked files—or letting SWEEPR Cleaner clean unlocked items automatically—is normal and completely safe.

Where is Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) located on Windows 10 and Windows 11?

It is stored at %LocalAppData%\Microsoft\EdgeWebView\User Data\Default\Cache. 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 WebView2 Shared Runtime Cache (EBWebView) Automatically

SWEEPR Cleaner safely clears Microsoft Edge WebView2 Shared Runtime Cache (EBWebView) 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.

🛡️ Windows 10/11 First-Launch Walkthrough: Because v0.1.0 is a freshly compiled 5 MB native Rust app, if Windows SmartScreen appears: Step 1: Click "More info" → Step 2: Click "Run anyway".