How to clear cache in Edge

You open Microsoft Edge to start your workday and notice pages loading slowly, web apps behaving oddly, or repeated sign-in prompts. These common IT issues are often caused by a build-up of cached files, which include temporary images, scripts, and service workers. While these files are meant to speed up browsing, they can sometimes create errors and slowdowns. Whether you’re on a single device or managing dozens in a managed enterprise IT environment, stale cache can cause frustrating problems.

Clearing it safely restores performance without affecting passwords, bookmarks, or site permissions. In this blog, we will guide you through the easiest manual methods and the most efficient automated PowerShell approach to clear Edge cache effectively.

» Trying to figure out what’s wrong with your PC? Here’s how to run a PC diagnostics report

What to know before clearing cache in Microsoft Edge

Before clearing cache in Microsoft Edge, it helps to understand how the browser stores and reuses data, especially in managed or enterprise environments. Edge is built on Chromium, which means cached data is designed to persist across sessions and improve performance. However, when browser state, identity, or policy changes, this same cache can start working against you. Common issues caused by cached data include:

• Repeated login prompts or authentication loops: Expired or corrupted cookies and tokens can cause SSO failures, forcing users to sign in repeatedly or re-complete MFA challenges.
• Broken or outdated page layouts: Old CSS or JavaScript files stored in the HTTP cache may override updated assets, leading to missing buttons, layout shifts, or non-functional features.
• Web apps failing after updates: SaaS platforms that deploy frequent updates may conflict with previously cached logic, especially when versioned assets are not reloaded correctly.
• Inconsistent behavior across sessions or devices: Persistent storage such as service workers or IndexedDB can cause issues that survive refreshes and browser restarts, making problems difficult to reproduce.

Cache types most likely to interfere with modern web applications

Different types of cached data affect applications in different ways. Knowing what each cache type does makes troubleshooting far more precise.

• HTTP cache (images, scripts, and stylesheets): This cache stores static assets used to load web pages faster. When it becomes stale, Edge may continue serving outdated files even after a web application has been updated.
• Cookies and site storage: Cookies and local storage hold session data, authentication tokens, and user preferences. In enterprise environments, these are closely tied to identity providers such as Azure AD, Okta, or SAML. Corruption or expiration here often results in login loops or access denials.
• Service workers: Service workers run in the background and control how network requests are handled. If an outdated service worker remains active, it can continue serving old content or logic even when the page is refreshed, causing persistent application errors. The Chromium Project highlights that service workers account for 40% of persistent errors in enterprise PWA.

How to clear cache in Microsoft Edge

Clearing Edge’s cache can fix slow pages, outdated content, and sign-in issues. You can do it manually through the browser or use PowerShell to handle it across multiple devices in managed enterprise environments. Both methods safely remove temporary files without touching passwords or site settings.

Method 1: Clear cache through Edge settings

This method uses Microsoft Edge’s built-in settings and is the safest option for most users. It allows you to remove cached files without accidentally deleting important data like saved passwords, autofill details, or site permissions.

Follow these steps:

1. Open Microsoft Edge

2. Click the three-dot menu (top-right) and select Settings

3. Go to Privacy, search, and services and click clear browsing data

4. Under Clear browsing data, click Choose what to clear

5. Select Cached images and files. Optionally select Cookies and other site data if you’re experiencing sign-in issues

Set Time range to:

• Last 24 hours for routine issues
• All time only for persistent or long-standing problems

DO NOT SELECT Passwords, Autofill form data, or Site permissions. Selecting these will erase saved logins, form entries, and site-specific settings, which can be inconvenient and require you to re-enter information on websites.

6. Click Clear now

Take note: Microsoft confirms that cached files persist across sessions by design and may cause rendering or authentication issues after web app updates.

Method 2: PowerShell

In managed enterprise IT environments, administrators often need to clear Microsoft Edge cache across multiple devices without relying on users to do it manually. This can be done safely and efficiently using PowerShell or scripting, which is especially useful in environments where GUI access is restricted, devices are shared, or profiles roam across virtual desktops.

Edge stores cache per profile in %LOCALAPPDATA%\Microsoft\Edge\User Data\<Profile>\, with important folders including Cache, Code Cache, GPUCache, and Service Worker.

Deleting these folders makes Edge rebuild its temporary files when it opens again, which clears out old data that can slow things down or cause website issues.

Follow these steps:

1. Search PowerShell in the search bar and click “run as administrator”

2. Copy and paste this code into PowerShell:

Close Edge 
 Get-Process msedge -ErrorAction SilentlyContinue | Stop-Process -Force 
 Set profile path 
 env:LOCALAPPDATA\Microsoft\Edge\User Data\Default" 
 Define folders to delete 
 $cacheFolders = @("Cache", "Code Cache", "GPUCache", "Service Worker") 
 Loop through each folder and remove contents 
 foreach ( 
 cacheFolders) {
 profilePath -ChildPath  
 fullPath) {
Remove-Item -Path "$fullPath*" -Recurse -Force -ErrorAction SilentlyContinue
}
} 
 Optionally restart Edge 
 Start-Process "msedge.exe

» Find out how to paste in PowerShell

IT teams don’t have to run these scripts manually on every device. They can deploy them using Group Policy, Intune, or Atera’s RMM platform. With Atera, you can push remote PowerShell scripts from a central console, schedule them to run after updates or reboots, and even track which devices ran them successfully. This makes rolling out cache-clearing (or any maintenance task) much smoother, reduces the need for hands-on troubleshooting, and frees up your time for other priorities.

Even better, AI Copilot, which sits on top of Atera’s RMM and ticketing tools, can turn plain-language instructions into ready-to-run scripts in seconds. You don’t have to worry about writing the commands yourself, just say something like, “clear Edge cache for all users on this device,” and AI Copilot generates the script for you. It’s like having a smart assistant that handles the tricky scripting details for you.

How to keep Microsoft Edge cache under control

After clearing the Microsoft Edge cache, it’s easy for temporary files, scripts, and service-worker data to build up quickly again. The goal is to control cache growth without affecting logins, app functionality, or performance.

• Limit cache size: Using Group Policy or Intune, you can cap how much storage Edge uses for temporary files. This prevents cache from growing uncontrollably, which can slow down browsers and increase disk usage.
• Session-based cache clearing: Configure policies to automatically clear temporary cache at the end of a session. This keeps old files from accumulating, especially on shared devices or VDI setups.
• Enable selective “Clear cache on exit”: You can automatically clear temporary files when users close Edge, but exclude cookies for trusted apps that use SSO. This keeps users logged in while still reducing cache buildup.
• Encourage good browser habits: Closing unused tabs and avoiding extremely long sessions prevents temporary files and scripts from piling up unnecessarily.
• Scheduled maintenance scripts: Running PowerShell or command-line scripts regularly can remove leftover cache safely without user intervention. This ensures Edge starts fresh for users while preserving critical data.

» Check out this list of essential scripts to use

Simplify Edge cache management with Atera

Clearing Edge cache doesn’t have to be a headache, even when you’re managing lots of devices. With PowerShell scripts combined with Atera’s RMM and AI Copilot, IT teams can automate the cleanup, fix stale data issues, and keep browsers performing smoothly.

In managed enterprise environments, this makes maintenance faster, reduces repeated helpdesk tickets, and ensures consistent performance across the organization.

» Sound good? You can try Atera for free