Use the keyboard shortcut Ctrl+Shift+Delete in Microsoft Edge to open the Clear browsing data panel, tick Cached images and files, and press Clear now. That works on every current Edge build on Windows, macOS and Linux. What trips people up is the scope: the panel starts on the last hour, so a third of users wipe an hour of data, notice nothing changed, and conclude the feature is broken. The second tripwire is deleting cookies and site data in the same click, which signs you out of every account and forces you to redo two-factor authentication on each one.
This guide covers five routes into the same cache, the exact checkbox combinations, the synced-history exception most tutorials skip, and the numbers that tell you whether clearing did any good. Browsers cache aggressively and well, so for most people the point of clearing is fixing a specific misbehaving page, not routine housekeeping.
The Ctrl+Shift+Delete Shortcut Opens the Right Panel in Four Seconds
Press Ctrl+Shift+Delete on Windows or Linux, or Command+Shift+Delete on macOS, with Edge focused. The Clear browsing data dialog appears as a floating panel anchored to the toolbar, not a settings page, so you never lose the tab you were working on. On Edge 127 and later the panel presents time range, checkboxes and a Clear now button with no additional confirmation step. The entire operation takes about four seconds before the deletion begins.
Watch the time range dropdown first. It defaults to Last hour, a choice Microsoft made so a quick cleanup does not accidentally destroy months of autofill. For a stubborn site problem, switch to Last 24 hours or Last 7 days depending on when the page started misbehaving. Anything older needs the All time option, which is the only selection that clears the full cache footprint on disk.
Now tick Cached images and files. On its own it is safe: it removes stored copies of pages, images and scripts and nothing else. Leave Browsing history, Cookies and other site data, and Download history unticked unless you specifically want those gone. Download history is metadata only; your downloaded files stay on disk. Press Clear now and the panel closes on its own.
If the shortcut does nothing, another application is intercepting the keystroke. Screen-recording tools, presentation software and some remote-desktop clients grab Ctrl+Shift+Delete before Edge sees it. Open the same panel from the menu instead β three dots, Delete browsing data β and check the shortcut category in edge://settings/system for conflicts. On managed work machines, a group policy can also disable data clearing entirely, which brings us to the error message that looks like a bug but is not.
The Three-Dot Menu Path Is the Same Panel Without the Keyboard
Click the three horizontal dots in the top-right corner, hover over Delete browsing data, then choose Clear browsing data now. Edge opens the identical dialog the shortcut produces, with the same Last hour default and the same checkbox list. This route matters when keyboard interception fails or when you are on a touch device where a hardware shortcut does not exist. On Edge for Android and iOS the path is similar but lives under Settings, Privacy and security.
Number your expectations here: the menu route takes roughly twice as long, about eight seconds versus four, purely because of the mouse travel. That is the only practical difference. The panel itself behaves identically, so any tutorial that treats these as two separate features is padding.
One variation exists for Edge on Windows when you use the menu inside InPrivate windows. The dialog appears the same but offers a narrower set of checkboxes, because an InPrivate session keeps no browsing history to clear in the first place. Cached images and files still appear and still get deleted from the session's temporary store. If you rely on InPrivate specifically to avoid leaving traces, remember that closing the window performs the same cleanup automatically.
The panel also remembers your last selections during the current browser session. If you clear cache-only once, reopen the panel five minutes later and the Cached images and files box is still ticked while cookies remain unticked. That memory resets when Edge restarts, which is why the next-day default looks different from yesterday's careful setup.
What Each Checkbox Deletes, and Which One Wipes Your Logins
The four checkboxes do very different things, and mixing them up is the single biggest source of "I cleared my cache and lost everything" complaints. Browsing history records URLs and timestamps. Cookies and other site data store login sessions, preferences and tracking identifiers. Cached images and files hold page assets so sites load faster on repeat visits. Download history is a list, not the files. Autofill and site permissions live in separate sections entirely.
| Checkbox | What it deletes | Signs you out? | Typical size on a daily-use profile |
|---|---|---|---|
| Browsing history | URL and visit timestamps, search terms in the address bar | No | 1β30 MB of database records |
| Cookies and other site data | Session tokens, preferences, tracking cookies | Yes, on most sites | 50β400 MB depending on cookie lifespan |
| Cached images and files | Page assets, scripts, images, fonts | No | 250 MB to 1.5 GB |
| Download history | The list of past downloads only | No | Under 5 MB |
A Microsoft support note on Edge storage puts the cache on a typical daily-use profile in the hundreds-of-megabytes range, growing toward a gigabyte or more with heavy video streaming. The cookie column is the one that costs you time rather than disk space: a signed-out user on a two-factor account spends two to five minutes per site re-authenticating, a cost that dwarfs whatever space the cookies occupied.
Here is where the professional habit differs from the casual one. Tick cached images and files alone for a broken page. Tick cookies alone when a login loop refuses to resolve. Tick both only when a site is thoroughly corrupted and you accept the re-login tax. Never tick Browsing history just because it sits at the top of the list.
One edge case deserves its own warning. Cookies and other site data includes the site permissions you granted β camera access for a video call, notification approval for a messaging app. Clearing the box erases those grants along with the logins, so the next visit re-prompts for microphone access mid-meeting. If you have a small set of permission-sensitive sites, revisit edge://settings/content after any cookie clear to confirm nothing important got reset.
Delete What Edge Already Downloaded From edge://settings/clearBrowserData
Type edge://settings/clearBrowserData into the address bar and press Enter. This URL opens the exact same panel as the shortcut and menu, but it survives being bookmarked. Pin it to the favorites bar and cache clearing becomes a one-click routine instead of a three-step hunt. Power users on Edge 127 and later report this as the fastest repeatable method because the panel remembers selections within a session.
The clearBrowserData page also gives you a diagnostic shortcut. The time range dropdown lists Last 15 minutes, Last hour, Last 24 hours, Last 7 days, Last 4 weeks and All time. Microsoft added the 15-minute option for the specific scenario of "something just broke on this one site." Choose 15 minutes, tick only cached images and files, and you scrub the last quarter-hour of assets across all sites without touching the session you have been logged into since morning.
Deletion speed depends on how much data you selected. Clearing a 600 MB cache on a machine with a mid-range SSD takes about two to five seconds; the panel shows a spinner and closes when the deletion commits. On mechanical drives with a two-gigabyte cache, expect closer to ten seconds. If the panel closes instantly with no spinner, nothing matched your selection β usually because the time range was too narrow.
If the spinner never resolves, a process is holding a lock on the cache files. Close all other Edge windows, then reopen the clearBrowserData page in a single tab and try again. Antivirus real-time scanning can also stall deletion by inspecting each file as it is removed; a temporary exclusion for the Edge user-data folder resolves this for users on older machines. That folder's location varies by platform and profile, so confirm the path on Microsoft's Edge support site rather than guessing.
Three Layers of Cache Sit Behind the Checkbox, and One Refuses to Go
Edge keeps cache in three separate stores. The HTTP cache under the profile folder holds page assets and is what the checkbox targets. The code cache holds compiled JavaScript for fast startup. The GPU shader cache stores graphics programs. Clearing cached images and files wipes the HTTP cache and the code cache but does not touch the GPU shader cache, which is why some rendering glitches survive a clear and only a full browser restart fixes them.
The sync layer is the exception that defeats tutorials. If you have Sync turned on under your Microsoft account, browsing history is uploaded to the cloud and downloaded to every signed-in device. Clearing Browsing history on your laptop clears the local copy, but the next sync pull can restore synced entries. Cached images and files are never synced, so cache clearing itself behaves as expected across devices. Cookies, however, can return through sync on some configurations, which sends users into a sign-out loop they cannot explain.
To break that loop, open edge://settings/profiles/sync, toggle History and Open tabs off, wait for the confirmation that sync data is being removed from the cloud, then clear locally. Microsoft's own Sync documentation confirms that turning off history sync deletes the synced copy from the servers, not just the device. Re-enable sync afterward only if you want cloud history back.
The shader cache lives outside the clearBrowserData panel entirely. On Windows, Edge rebuilds it automatically; the folder location changes between Windows 10 and Windows 11 builds, so check Microsoft's Edge support page for the current path before deleting anything manually. Rebuilding the shader cache takes thirty seconds to a few minutes of stutter the next time you launch a graphics-heavy site. Most users should leave it alone unless a specific rendering bug persists after a full restart.
Clearing Just One Site's Cache Beats the Nuclear Option
Go to edge://settings/content/all, type a site's name in the search field, and Edge shows per-site storage including cookies, cache and local storage for that origin. Click the entry and choose Delete. This removes that site's data without touching logins or cache anywhere else. On Edge 127 and later the per-site view also shows the storage breakdown by category, which reveals whether a bloated cache belongs to one site or is spread thin.
This is the correct answer for the most common real-world case: one site serving stale content. A news site stuck on yesterday's homepage, a web app refusing to load a new feature, a streaming service throwing playback errors β all typically resolve after clearing that origin alone. You keep every other login, every other cached asset, and any site permissions you granted elsewhere. The whole operation takes about fifteen seconds.
Pair this with a hard reload when you only need a fresh copy right now. With a page open, press Ctrl+F5 on Windows or Command+Shift+R on macOS. Edge re-fetches the page assets from the server and revalidates the cache, bypassing what it already stored. It is not a deletion; it is a one-time reload that leaves the old cache in place for later use. For a transient glitch, hard reload is faster than any menu path.
The per-site method has a limitation worth naming: it only clears data Edge associates with the exact origin. Sites that pull assets from a shared CDN domain keep that CDN's cache intact unless you clear the CDN domain separately. Advertising scripts load from entirely different origins. If a problem persists after clearing the visible site, open the developer tools Network panel on Edge 127 and later, check which domain is serving the stuck asset, and clear that domain by name in the same all-sites view.
Cached Images and Files Is the Only Box Needed for a Broken Page
Start with the narrowest possible fix. For a page loading stale content, clear only cached images and files for the Last hour. For a web app failing to save, clear only that site's cache through the all-sites view. Cookie clears come last, because they cost you re-authentication. This order resolves the majority of cache complaints without touching a single password.
The symptom-to-fix mapping matters more than any tutorial checklist:
Stale homepage or old article content: clear cached images and files, Last hour, that site only. Web app hanging at a spinner: hard reload first (Ctrl+F5), then per-site cache clear. Persistent rendering glitch: clear cached images and files, then close and reopen Edge to rebuild the shader cache. Login loop that tolerates no fix: clear cookies for that site only, then re-authenticate. Wrong currency or region shown: clear cookies for the domain, since geolocation often rides on a cookie rather than the cache.
Each fix maps to a specific storage layer. Applying the wrong one wastes a re-login for nothing. Applying two at once obscures which one worked, so you cannot learn for next time. Narrow first, then widen only if the problem survives.
One exception runs the other way: a shared machine where you need to leave no trace. There, cookies and cache both go, and you accept the re-login tax on your own accounts because you are signing out anyway. The narrow-first rule assumes the machine is yours.
Pressing Clear Often Costs You Load Time, Not Speed
Clearing the cache makes the next load of every frequented site slower, because Edge re-downloads what it already had. On a home connection that difference is imperceptible β tens of milliseconds per asset β but on a shared office network or a mobile hotspot the first load after a full clear can run three to five times slower. This is the reason "clear your cache" is bad routine advice. For a healthy browser, the cache is a performance feature, not clutter.
Edge itself manages cache size automatically. The browser evicts old, unused entries when the cache reaches its threshold, so leaving it alone rarely causes problems. The cache only misbehaves when a specific site's assets are corrupted or stale. Clearing it globally fixes a single broken site at the cost of re-downloading everything else, and it does not free meaningful disk space on a modern machine β hundreds of megabytes out of a terabyte drive is noise.
By the numbers: a 600 MB cache cleared on a 100 Mbps connection takes roughly five seconds to refill on the first visit to your five most-used sites, based on arithmetic from those figures, while a 5 Mbps connection takes about a hundred seconds. The cache clear itself is nearly instant; the recovery time is where the cost lives, and it depends entirely on what you visit next and how fast your line runs. For most users, that recovery is well worth paying once to fix a broken site. Paying it weekly out of habit is pure waste.
If disk space genuinely is the problem, cache clearing is the wrong tool. Check the download folder, old Windows update caches and system restore points before touching a browser that has already optimized its storage. On a Chromium browser the cache rarely exceeds a couple of gigabytes.
When Clear Now Does Nothing, These Four Causes Explain It
The panel closes, the spinner flashes, and the broken page still loads stale. Four causes account for nearly every "clearing doesn't work" report. Systematically rule each out before assuming the feature is broken.
1: Your profile is managed by an organization. Work or school machines can enforce Cache deletion policies that silently override user actions. Check edge://policy and look for ClearBrowsingDataOnExit or related entries. If a policy is set, the browser obeys it regardless of what you click. 2: The extension holds its own cache. Extensions like ad blockers, password managers and language tools maintain their own storage outside Edge's main cache. Disable the extension and reopen its settings to trigger a fresh fetch, or remove and reinstall it. 3: The site is a web app with local storage or IndexedDB. Progressive web apps store data outside the browser cache, and clearing cached images and files leaves it untouched. Use the per-site view under edge://settings/content/all, which lists local storage and IndexedDB alongside cookies. 4: The page is served from a service worker. Service workers intercept requests and can serve cached responses even after the main cache is cleared. On Edge 127 and later, developer tools Application tab shows active service workers; unregister the one for the misbehaving site.
The fifth rare case is a Windows profile sync issue that restores browser data from a backup. If none of the above resolves it, create a fresh Edge profile, confirm the problem disappears there, then migrate your bookmarks and settings to the new profile rather than chasing the corrupted one.
Rule each out in order: policy first (it explains everything else silently), then extensions, then local storage, then service workers. Each step takes two to three minutes, and the policy check alone resolves the majority of enterprise complaints before anyone touches a setting.
FAQ
Does Ctrl+Shift+Delete clear my whole cache or just the last hour?
Just the last hour, by default. Edge sets the time range dropdown to Last hour specifically to protect against accidental mass deletion. Select All time before pressing Clear now to remove the entire cache. Users who close the panel believing they cleared everything are the most common source of complaints on Microsoft's support forums.
Will clearing the cache sign me out of anything?
No, as long as you leave Cookies and other site data unticked. Cached images and files contain no session credentials. Your accounts stay signed in and two-factor codes stay valid. The moment you tick cookies, you sign out globally and must re-authenticate every site, which costs two to five minutes per protected account.
Does clearing browser history remove the cache on my other devices?
Only with caveats. Cached images and files never sync between devices, so clearing them on one machine leaves the other machines untouched. Browsing history does sync under your Microsoft account, and clearing it locally can be undone by the next cloud sync pull. Toggle history sync off at edge://settings/profiles/sync first to prevent that restoration.
Why does Edge still remember my site after clearing cookies?
Local storage and IndexedDB survive a cookie clear, which is how sites remember preferences without cookies. The per-site view at edge://settings/content/all lists both alongside cookies and lets you delete them together. Service workers can also serve a cached response; unregister the site's worker from the developer tools Application tab if data persists.
How often should I clear the cache to keep Edge running well?
Rarely, if ever. Edge manages cache size automatically and evicts old entries, so routine clearing only slows your next page loads by forcing re-downloads. A 600 MB cache on a 100 Mbps line takes roughly five seconds to rebuild on your first five visits. Clear only when a specific page misbehaves or you need to free space on a constrained drive.
Is clearing the cache the same as using InPrivate mode?
No. InPrivate mode starts with a clean session and discards everything when the window closes, without touching your main profile's cache. Clearing the cache within InPrivate affects only that session. For lasting removal from the main profile, use the clearBrowserData panel on a normal window, not an InPrivate one.
What is the difference between a cache clear and a hard reload?
A hard reload (Ctrl+F5 or Command+Shift+R) re-fetches the current page's assets from the server and revalidates stored copies, but leaves the existing cache entries for future use. A cache clear deletes those entries entirely. Hard reload is the faster fix for a one-page glitch; a cache clear is right when you want the old copy gone for good.
Does Edge sync cache across devices through my Microsoft account?
No. Microsoft's Sync service transfers favorites, passwords, history, open tabs, settings and extensions β the cached image files and code cache stay local to each machine. That is one reason cache issues on one device are never mirrored to another, and why a broken site on your laptop can load fine on your phone.
Deletion of cached data is a low-risk maintenance operation, but managed devices can enforce policies that override user actions and work profiles can restrict which data may be removed. If this is a corporate or school machine, confirm with your IT administrator before clearing anything beyond the cache; nothing here is a substitute for your organization's data-retention rules.