Clearing cache in Edge takes under a minute: press Ctrl + Shift + Delete, set Time range to All time, tick Cached images and files, and click Clear now. That clears your browsing cache only. It leaves cookies, passwords, and site data untouched, so the command is safe for logins but useless when a stale sign-in token is the real problem. On Edge for Windows, Microsoft splits the Ctrl + Shift + Delete dialog and the Clear browsing data settings page into two separate interfaces with different defaults, and knowing which one you're in prevents the most common mistake: wiping cookies by accident and signing out of everything.
Why Edge Has Four Cache-Clearing Paths and Which One Your Problem Needs
Edge stores more than one kind of temporary data, and each has a dedicated erase route. The browsing cache lives in the Edge profile under the Cache folder; cookies and site data live in a separate store; the DNS cache belongs to Windows, not to Edge. If a page loads an outdated stylesheet, the browsing cache is the fix. If a site keeps rejecting a login, site data is the fix. If a domain refuses to resolve to its new IP, you need the Windows DNS flush. Match the symptom to the path before you click anything.
The standard dialog covers the first two categories, but only when you expand the checkboxes correctly. On Edge 116 and later, Microsoft moved the same controls to Settings > Privacy, search, and services > Clear browsing data, and the two interfaces can show different "Time range" values. The keyboard shortcut usually opens the panel whose Time range reads "Last hour" by default, while the Settings page may default to "All time" if you last changed it there. Check the dropdown on screen rather than trusting muscle memory.
Profile scope creates the second trap. If Edge has multiple profiles, each one has its own cache directory, so clearing cache on "Profile 1" leaves "Work" untouched. Open edge://version in the address bar and read the Profile path line to see exactly which folder is active. That line is the only reliable way to confirm you're clearing the profile whose browsing is misbehaving.
A third fork exists for people who don't want a cache-free state at all. Edge's InPrivate window and the newer Secure Network mode route traffic differently, and clearing cache in a normal window doesn't affect saved site data used by InPrivate sessions. Decide which state you want before clearing; if you plan to keep browsing the same site, identify whether a hard refresh handles it before you wipe anything global.
The 30-Second Keyboard Shortcut That Clears Only What You Tick
The fastest route is the direct dialog. It takes about 30 seconds if you already know which checkboxes you need, and it clears only the categories you tick, which is the entire point.
1: Open Microsoft Edge on the profile that's misbehaving. 2: Press Ctrl + Shift + Delete on Windows or Linux, or Command + Shift + Delete on macOS. The Clear browsing data panel opens as a floating dialog. 3: Open the Time range dropdown and choose All time. The default is usually Last hour, which will not clear older cached files. 4: Tick Cached images and files. Leave Browsing history and Cookies and other site data unticked unless you accept their side effects (sign-outs, lost form autofill, and cleared history). 5: Click Clear now. The dialog closes and the cache is empty.
Failure handling: if Ctrl + Shift + Delete opens nothing, your Edge installation may have a conflicting extension or the window isn't focused. Click inside the page first, then retry. If the dialog opens but the "Clear now" button stays greyed out, no checkbox is ticked. On managed work or school devices, a group policy may hide or disable the panel; check edge://policy and look for a ClearBrowsingDataOnExit or ClearBrowsingData policy entry before assuming a bug.
If the panel clears but the problem page still loads the old version, reload with Ctrl + F5 or Shift + F5 to force a fresh fetch. That combination bypasses the cached copy for the current tab only. If a hard reload fixes it, the global cache clear was unnecessary; the per-tab reload is the smaller, safer tool and should be your first move every time.
Settings > Privacy, Search, and Services: The Route With More Control
The dialog is a shortcut; the Settings page is the full control surface. It exposes the same categories plus extras the dialog hides, and it's the only place to confirm Google and Microsoft choice settings that influence what gets stored.
1: Click the three-dot menu in the top-right corner and choose Settings. 2: In the left sidebar, click Privacy, search, and services. 3: Scroll to the Clear browsing data section and click Choose what to clear. 4: Set Time range to All time. Leave all categories unticked except Cached images and files. 5: Click Clear now.
This page also hosts the "Clear browsing data on close" toggle. If it's enabled with cached files selected, Edge empties the cache every time you close the window, and nothing you see in the cache folder persists between sessions. That's a legitimate privacy setting, but it makes caching useless for speed, so the first page after every launch loads slower. If you've been wondering why your browsing feels sluggish each morning, check that toggle before chasing other causes.
Work or school accounts change this page. Enterprise policies can disable the Clear browsing data button or force clearing on exit regardless of your setting. The policy check is edge://policy, and the names to look for are ClearBrowsingDataOnExit and, in older builds, BrowserSignin-adjacent data controls. If the button is greyed, a policy is the likely reason and clearing via Settings won't work until an administrator changes it.
One practical difference between the two interfaces: the Settings page remembers your last Time range selection while the keyboard shortcut sometimes resets to Last hour. If you clear cache regularly, the Settings page is the more predictable home. Use the shortcut only when you need speed and will verify the range every time.
Cookies vs Cache vs Site Data: Which Checkbox Breaks Your Logins
The single most common complaint after a cache clear is "it signed me out of everything." That happens because Cookies and other site data was ticked, not because the cache clear went wrong. Edge stores session tokens in that cookie store, plus IndexedDB, localStorage, and service-worker data used by modern web apps. Clearing the cache does not touch these by default. Clearing "Cookies and other site data" does, and the result is a fresh-start browser in which every site asks you to log in again.
| What you tick | What gets deleted | What you keep | Who it's for |
|---|---|---|---|
| Cached images and files | Page copies, stylesheets, scripts, downloaded media fragments | Logins, autofill, history, bookmarks | Fixing stale pages, layout glitches, old scripts |
| Cookies and other site data | Session tokens, preferences stored in the browser, IndexedDB, localStorage | Passwords saved to the browser, bookmarks | Privacy cleanups and stuck logins on sites that don't allow resetting a session |
| Browsing history | Address-bar suggestions, recently closed tabs, visited URLs | Cached files, logins, bookmarks | Handing over a device, clearing suggestions |
| All three together | Everything the browser has stored in the profile | Synced passwords if sync is on, bookmarks, extensions | Device transfers, troubleshooting a corrupted profile, shared computers |
Cached files typically account for a few hundred megabytes to several gigabytes on a daily-driver profile; the exact figure varies by browsing volume and streaming habits, so verify in Windows explorer at the profile path rather than guessing. Cookies and site data are usually far smaller but do the heavier damage when deleted, because a sign-out is a visible cost and small storage is an invisible one. The affordable move when troubleshooting is to tick cached files first, test, and only then add cookies to the list.
One edge case demands the opposite order. If a website keeps redirecting in a loop even after a cache clear, its session cookie has gone corrupt, and clearing cookies for that one site fixes it while keeping your logins everywhere else. Open Settings > Privacy, search, and services, click Site permissions, find the site, and wipe its data only. That's more surgery than a blanket clear.
Hard Refresh Beats a Full Cache Wipe for Single Sites
Most cache problems are one page loading an old version of one file. A hard refresh fixes exactly that without touching the rest of your profile, and it takes one keystroke.
1: Open the misbehaving page and make sure the tab is focused. 2: Hold Ctrl and press F5, or hold Shift and press F5. Edge re-downloads the page and its assets, bypassing the cached copies. 3: On macOS, use Command + Shift + R. 4: If the page still looks wrong, open DevTools with F12, right-click the reload icon, and choose Empty cache and hard reload. That clears cached files for the current page and reloads.
Use the full dialog only when the problem spans sites, happens after an Edge update, or involves cached scripts inside a web app that won't refresh. Overuse of the global cache clear is a habit worth breaking: it makes the next visit slower and it costs you nothing to reset exactly the page that's stale. The drill-down in DevTools is the tightest feedback loop, and it's the one fix you can do confidently without thinking about cookies at all.
Failure case worth knowing: some enterprise Wi-Fi networks and content filters intercept cache instructions and re-serve their own copies. If Ctrl + F5 and Empty cache and hard reload both fail, the cache isn't on your machine. Try the same site on a different network or from InPrivate mode; if it loads fresh there, you've isolated the network, and no amount of Edge clearing will help. This is the one genuine reason a cache clear "doesn't work."
A hard reload also keeps the cache folder from growing during testing. Edge shrank the disk-cache size cap in recent Chromium builds compared to early Edge Chromium releases, so a profile is unlikely to balloon to multi-gigabyte caches unless media streaming is heavy. Verify actual disk usage in the Cache folder rather than assuming, because reports of "huge cache" are usually measuring the whole profile folder, including site data, not just cached images and files.
Windows-Level Caches Edge Can't Touch
Some stale-page problems stay after the Edge cache is empty because the cache isn't an Edge cache. Windows holds a DNS resolver cache, and it can point a domain at an old IP for the length of the TTL configured on the DNS record. Edge's clear-browsing-data panel doesn't reach it, and neither does Clear browsing data on exit.
1: Open Start and type cmd, then choose Command Prompt. 2: Run ipconfig /flushdns. The output confirms the resolver cache is flushed. 3: Clear the Edge cache if the page still misbehaves. 4: Restart Edge and reload the site.
If ipconfig /flushdns returns "Access is denied," you need an administrator command prompt. On networks with split-horizon DNS or VPN clients, resolved entries can reappear within seconds, so check whether the VPN is connected before blaming the browser. The name to remember is DNS cache: it maps hostnames to IPs and has nothing to do with which stylesheet Edge loaded.
The Windows Store and Microsoft Store apps keep their own caches too, but Edge's own tabs aren't served from those stores. Don't waste time running WSReset as a fix for a webpage that loads an old version. The other related cache is the graphics shader cache inside the GPU driver; a page with rendering glitches after clearing Edge's cache points at the driver, not the browser, and the fix lives in the driver's control panel. Clear only what matches the symptom.
If syncing across devices is in play, remember that a cache clear is local. Clearing history and cached data on one machine does not clear the same data on another signed-in device, and it doesn't affect synced history until the next sync cycle. On the other machine, you'll need to repeat the clear or wait for sync to run; the Edge sync page in Settings shows the last sync time when you need to confirm.
Where the Cache and Profile Folder Actually Live
You can verify a cache clear by looking at the filesystem, and that's the only evidence that beats the "feels faster" test. Open edge://version and copy the Profile path. In Windows, it usually looks like C:\Users\YourName\AppData\Local\Microsoft\Edge\User Data\Default. The Default folder is the primary profile; other profiles appear as Profile 1, Profile 2, and so on.
Inside that folder, the Cache directory holds cached images and files. The Code Cache directory holds compiled scripts, and the Service Worker directory holds offline-capable site data. The Cookies file sits alongside them. Deleting the Cache folder while Edge is closed is equivalent to the cached-files checkbox; deleting the whole profile folder is that plus history, cookies, extensions if you're unlucky, and every personalized setting. Do not delete the profile folder unless you mean to start over.
If you cleared cache but folder size barely changed, the cache was re-populated by open tabs the moment you returned to them. Close all tabs first, or quit Edge entirely, then measure. That's also the cheapest way to see actual cache size: right-click the Cache folder, choose Properties, and read Size on disk. Numbers come from your own profile, not from a published default.
Failure case: a profile folder marked read-only or pinned to OneDrive sync can throw access-denied errors during clearing. If a cache clear fails mid-process, check the folder's read-only state and whether OneDrive is syncing it. The clean route is Settings > Clear browsing data, not manual file surgery, unless you enjoy rebuilding settings.
Sync, Work Profiles, and Managed Devices Change the Rules
On a personal profile with sync on, clearing the browser cache is local-only. Your synced favorites, passwords, and history live in the Microsoft account, and clearing the local cache does not delete them. That's reassuring for most users and puzzling for people who expected "All time" to wipe every device. It doesn't. Syncing happens periodically, and when data is cleared on one device, Edge propagates the change only for synced types, not cached files.
Work or school profiles are a different animal. Microsoft Edge for Business separates personal and work data in some configurations with data-loss-prevention policies that control what can be cleared. A managed profile may prompt for a sign-in before clearing, block clearing of site data for approved work apps, or force a cache clear on every close via policy. Before promising a colleague that "the cache is now clear," check the profile's policy state and their account type; a managed profile that ignores your clear is behaving correctly.
Signing in and out of the profile also affects cache continuity. Edge syncs history and settings, not cached page assets, so clearing cache while signed in won't create sync conflicts. Signing out mid-clear can interrupt the process and leave a dialog frozen. Wait for Clear now to finish before touching the account menu.
On macOS, the path differs: the profile lives under ~/Library/Application Support/Microsoft Edge/, and Finder hides the Library folder by default. That's why "I can't find the cache" is almost always a macOS user who hasn't revealed the Library folder. The Settings dialog is unchanged and remains the sane way to clear without hunting.
What Actually Fills the Cache Back Up After You Clear It
A full clear is a state, not a permanent fix. Open three heavy sites and the cache begins refilling immediately, with cached images and files returning page by page. That's normal and desirable; the browser exists to load pages fast by keeping copies. The cache is a performance feature and only becomes a problem when a copy is stale or corrupt. Treat clearing as maintenance, not as a fix for every slow page.
Streaming on Netflix, YouTube, and similar services can leave cached media fragments in the cache folder. The uploaded cache size varies by service and by whether the site uses Media Source Extensions; there's no universal cap you should assume. Measure in the Cache folder if disk space is a concern. A profile with a two-gigabyte cache is not broken and doesn't indicate malware; it's a busy browser doing its job.
Set a sensible routine. Clear with cached images and files only when you have a reason: after major site redesigns, after browser updates, or when a page misbehaves and a hard refresh fails. Otherwise leave it alone. You can use Edge's built-in performance and sleep-tab settings to reduce memory pressure instead of blindly wiping cache, and if you clear history and cookies by reflex, you'll pay with sign-outs and slower page loads for no measurable gain. The 30-second shortcut is fast; fast doesn't mean frequent.
If you want Edge to clear cache on close, enable it in Settings > Privacy, search, and services and accept slower first loads every session. That's a privacy choice for shared or public machines. On a personal machine, the better setting is the default: cache stays, hard refresh handles individual pages, and the global dialog stays unticked except when a stale site leaves no other option.
FAQ
How long does clearing cache in Edge take? Usually under 30 seconds with the Ctrl + Shift + Delete dialog on an average profile, and up to a minute or more if the cache spans several gigabytes, because Edge must delete cached images and files for every site before reporting completion. The dialog gives no progress indicator on older builds, so a brief pause is normal. If nothing happens after two minutes, quit Edge, reopen, and retry, or use Settings > Clear browsing data instead.
Does clearing the cache delete my passwords in Edge? No. Saved passwords live in the browser's password store and are not part of the Cached images and files category; clearing cache keeps them unless you tick Passwords in the Clear browsing data list. The identical-looking browser dialog includes Passwords as an optional item, and volume-scale ticking is the usual route to accidental password deletion. If you've already cleared passwords, Edge sync can restore them if sync was on; otherwise reset from the site.
Why is Ctrl + Shift + Delete not working in Edge? The shortcut fires only when the Edge window has focus and no modal dialog is open, and it can be blocked on managed devices by a group policy that hides or restricts the Clear browsing data panel. Open edge://policy and check for a data-clearing entry, or open the Settings page as a workaround. Web apps that capture keyboard shortcuts in full-screen mode can also swallow it. Clicking inside the page before pressing the shortcut usually fixes the local case.
Do I need to clear the cache after every Edge update? No. Edge updates don't require a cache wipe, and the first launch after an update often feels slower because new code invalidates some cached scripts; it settles after one or two page loads. Wiping the cache after a Chromium update simply forces every site to redownload assets, so it costs time and changes nothing if pages already load correctly. Clear only when a specific page misbehaves after an update and a hard refresh fails.
Will clearing cookies fix a site that won't accept my login? Yes, that's the right tool for a corrupted session, but clear the site's cookies only rather than all cookies. Go to Settings > Privacy, search, and services > Site permissions, find the domain, and remove its data; then reload and sign in. A global cookie clear fixes the login but signs you out of every other site as well. Try this before clearing the browsing cache, because login loops rarely come from cached images.
How much disk space does Edge cache actually use? On a typical personal profile, the Cache folder is usually measured in hundreds of megabytes and can reach a few gigabytes with heavy video streaming, so check your own profile's Cache folder in Windows Explorer. The whole profile folder is much larger because it includes history, extensions, and site data. Dell and HP support documentation has historically quoted large ranges for browser cache across major browsers, and those are order-of-magnitude figures, not measurements of your machine.
Does clearing cache in Edge affect Google Chrome? No. Chrome and Edge use separate profile folders and separate caches even though both are Chromium-based. Clearing Edge's cache leaves Chrome's cached files and cookies intact, and vice versa. The same is true for Chrome Profiles versus Edge Profiles: each browser's cache clear is a per-browser, per-profile operation. If a page misbehaves in both browsers on the same machine, the problem is not the browser cache; check the network or the DNS instead.
What's the difference between clearing cache and clearing browsing history? Cache stores page assets for speed, and browsing history stores a list of the pages you visited. Clearing cache frees disk space and fixes stale pages but leaves the visited-URL list, autofill suggestions, and recently closed tabs intact. Clearing history wipes that record but leaves cached images and files, so the next visit is as fast as before. The two sit adjacent in the same dialog, which is why people tick one when they meant the other; tick Cached images and files alone unless you're handing over the device.