What Is a Cache and Why Does Clearing It Fix Things?
Short answer
A cache is a stored copy of something your device already fetched, kept so it does not have to fetch it again. Clearing it helps in one specific situation: when the stored copy is stale and the fresh version differs, such as an updated page showing old content, or a broken layout. It is not a general-purpose fix and it will make things slower first.
On this page
A cache is a copy of something you already fetched, kept somewhere closer so you do not have to fetch it again. That is the whole idea, and it appears at every level of computing because fetching things is slow and fetching the same thing twice is wasteful.
Your browser caches images and scripts so a site’s second page loads in a fraction of the time. Your phone caches thumbnails so the gallery scrolls smoothly. Your CPU caches memory because reading from RAM is glacial by its standards.
“Clear your cache” became the universal first suggestion in tech support, which has given it a reputation as a general remedy. It is not. It fixes one narrow class of problem well and does nothing for everything else.
What a cached copy avoids
When you load a web page, the browser fetches an HTML document plus perhaps fifty other files: stylesheets, scripts, fonts, images. Most of those are identical on every page of the site.
The cache stores them with an expiry the server specified. On the next page, the browser checks its cache first. A valid entry is read from disk in a millisecond or two instead of crossing a network in a hundred or more. On a slow or metered connection the difference is dramatic.
Caches exist in layers, and the word covers all of them:
| Cache | Holds | Cleared by |
|---|---|---|
| Browser cache | Images, scripts, stylesheets, fonts | Browser settings |
| App cache | Thumbnails, downloaded media, prepared data | App settings |
| DNS cache | Domain-to-address lookups | ipconfig /flushdns or a restart |
| OS file cache | Recently read disk blocks | Restart; managed automatically |
| CPU cache | Memory contents in use right now | Nothing, hardware managed |
Only the first three are ever worth clearing manually, and the third one for different reasons from the first two.
Why a cache goes wrong
A cache is a bet that the stored copy still matches the original. It fails when that bet is wrong, and there are three ways that happens.
The server set a long expiry and then changed the file. A site publishes a
stylesheet with a one-year cache lifetime, then updates the design. Your browser
has no reason to re-check for a year, so you get the new HTML with the old
stylesheet and the layout falls apart. Competent sites avoid this by changing
the filename on every release, as in style.a7f3c.css, so a new version is a new
URL that was never cached. Not every site does this.
The cached file is corrupt. An interrupted download, a disk error, or the browser closing mid-write leaves a truncated entry. The browser trusts it and the page half-loads.
The cache contains a response that should not have been cached. An error page, a redirect, or content meant for a logged-out user, stored and served back after you sign in.
All three produce the same signature: the site works for everyone else, works in a private window, and works on your phone, but is wrong in your browser. That signature is the one reliable indicator that clearing the cache is the right move.
When clearing genuinely helps
- A page shows old content you know has been updated.
- Layout is visibly broken, with unstyled text, overlapping elements.
- A site works in an incognito window but not normally. This is the single best test, and it takes ten seconds. It also tests extensions, so if incognito fixes it, disable extensions before assuming the cache.
- An app shows stale data after a change made elsewhere.
- A site resolves to the wrong address after a domain moved. That is the DNS cache, not the browser’s, and flushing DNS is the fix.
When it does not help, despite being suggested
- A slow computer. The cache is on disk and is not consuming memory. Clearing it makes browsing slower while it rebuilds. The real causes are elsewhere, and working out what is actually using the CPU or disk is the productive route.
- High RAM usage. Different resource entirely.
- Free disk space. A browser cache is typically a few hundred megabytes and it rebuilds. If you need space, go after the things that actually fill a C: drive.
- Login problems. Those are cookies. Clear cookies for the site, not the cache.
- Connectivity failures. Nothing cached is involved in a connection that will not establish.
- CAPTCHA loops. Clearing makes them worse, because the history being discarded was the evidence vouching for you.
Clearing it precisely
The blunt route clears everything for all time and signs you out of the entire internet. Rarely what anyone wants.
One page, in any browser: Ctrl+Shift+R (Cmd+Shift+R on Mac) forces a reload bypassing the cache. Try this before anything else, since it resolves most stale-page cases without touching stored data.
One site, in Chrome: Settings → Privacy and security → Third-party cookies → Manage on-device site data → find the site → delete.
Everything cached, in Chrome: Settings → Privacy and security → Delete browsing data → tick Cached images and files only. Leave cookies and passwords unticked unless you specifically intend to sign out everywhere.
A phone app:
- Android: Settings → Apps → the app → Storage → Clear cache. Do not tap Clear data or Clear storage, because those reset the app to a fresh install and delete anything stored locally, and the distinction matters most on messaging apps.
- iPhone: no system-wide equivalent. Some apps offer it in their own settings; otherwise offloading the app removes its cache while keeping documents and data.
DNS: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on
macOS. Toggling airplane mode on a phone achieves it.
Realistic expectations
Clearing a browser cache takes a few seconds and makes the next visit to every site measurably slower until it rebuilds, which happens over a day or two of normal use. The cache returning to a few hundred megabytes is correct, not a problem.
If clearing fixed the symptom and it returns within a week, the cause is the site’s caching configuration rather than your browser, and there is nothing to do at your end but keep using the hard refresh. If clearing did not fix it, clearing again will not either — the answer is somewhere else, and the ten seconds spent testing in a private window will point at it faster than any amount of further clearing.