Internet & Web
A clear, friendly guide to what your browser cache is, why clearing it fixes common problems, and how to do it without losing what matters to you.
Clearing your browser cache means deleting the local copies of images, scripts, and stylesheets your browser saved to load sites faster. It fixes one specific class of problem: a single site showing you a stale, broken, or half-updated version of itself. In almost every desktop browser you start the same way — press Ctrl+Shift+Delete (Cmd+Shift+Delete on a Mac) — and the one setting that matters is ticking "Cached images and files" while leaving cookies and passwords alone.
That last distinction is where most people go wrong, so it is worth getting straight before you touch anything.
Your browser stores at least three separate things, and the clearing screen lets you remove them independently:
The single most common mistake is ticking everything, wiping cookies and passwords along with the cache, and then being annoyed at getting logged out of a dozen sites for a problem that only needed the cache cleared. If your goal is fixing a broken layout or an outdated page, clear the cache only.
Why does a cache go stale in the first place? When a server sends a file, it attaches HTTP headers like Cache-Control: max-age=86400, which tells your browser "reuse this copy for 24 hours without asking." If the site pushes a fix inside that window, your browser keeps serving the old file until the timer expires or you force the issue. A related header, the ETag, lets the browser ask "has this changed?" and get a lightweight 304 Not Modified back — efficient, but occasionally the reason a supposedly updated page will not budge.
Before clearing anything, try a hard refresh, which forces the current page to re-download its files while leaving the rest of your cache and all your logins intact.
A hard refresh solves the majority of "this one page looks wrong" cases in a single keystroke. Another zero-risk diagnostic: open the site in a private/incognito window (Ctrl+Shift+N in Chrome and Edge, Ctrl+Shift+P in Firefox). Private windows ignore your existing cache, so if the site works there, you have confirmed the cache is the culprit and can clear it with confidence.
Chrome and Edge run on the same Chromium engine, so the steps are nearly identical.
Safari hides its cache-only option. Turn on the developer tools first: Safari > Settings > Advanced > tick "Show features for web developers." Then use Develop > Empty Caches (Cmd+Option+E). The everyday Safari > Clear History command also wipes cookies and history, so reach for Empty Caches when you want to keep your logins.
Wiping your entire cache to fix one misbehaving site is overkill — it slows down every other site while their caches rebuild. Target the offender instead. In Chrome or Edge, click the tune or padlock icon at the left of the address bar > Site settings > Delete data. Or open DevTools (F12), right-click the reload button, and choose Empty Cache and Hard Reload. That command clears only the current site's cached files and reloads it fresh, leaving everything else untouched. If you keep DevTools open, ticking "Disable cache" in its Network tab stops the browser caching at all while you test.
If every site is slow, the cache is almost certainly innocent; look at your Wi-Fi, router, or connection. If one site is down for everyone (check a status page or ask someone else to load it), clearing does nothing on your end. And the browser cache is not the same as your DNS cache — a "server not found" error is a DNS or network issue, cleared separately at the operating-system level.
The sneakiest case is a Progressive Web App (PWA) or any site running a service worker — a background script that caches whole pages so the site works offline. A normal cache clear often leaves the service worker running, so the stale version comes right back. To truly reset it, open DevTools > Application > Service Workers > Unregister, or use DevTools > Application > Storage > Clear site data. Web apps like X, the Spotify web player, and many news sites rely on service workers, which is exactly why they sometimes seem immune to an ordinary cache clear.
No — as long as you tick only "Cached images and files" and leave passwords and cookies unchecked. Saved passwords live in a separate store. You only lose them if you deliberately select the passwords option on the clearing screen.
Not if you clear the cache alone. Logins are held in cookies, which are a different checkbox. If you also tick "Cookies and other site data," then yes, expect to sign back in almost everywhere.
Only when a specific site misbehaves — a broken layout, an outdated page, or a form that will not submit after the site was updated. There is no benefit to doing it routinely, and it slows browsing while caches rebuild.
Try a hard refresh, then check for a service worker (DevTools > Application > Service Workers > Unregister) or use "Clear site data." Confirm the site is not down for everyone, restart the browser, and make sure it is up to date. If the trouble survives all that, the problem is on the site's end, not yours.
Priya translates the fast-moving world of AI and the internet into things you can actually use and understand. She's curious but skeptical, quick to separate genuine progress from hype, and keen to help readers use new tools wisely rather than fearfully.
Keep reading
A crowded inbox drains attention all day. Here is a calm, repeatable system to clear the backlog and keep your email tidy without living inside it.
Priya Nadar
Forgotten subscriptions quietly drain money every month. Here is a calm, practical way to find every one of them, cancel cleanly, and keep the list short.
Priya Nadar