You don't walk to the shop every time you want milk in your tea. You keep some in the fridge. A cache is the fridge.
Every time you want a cup of tea, you could walk to the shop for milk. Or you could keep a bottle in the fridge. Much quicker. The only catch: sometimes the fridge milk is past its best.
A cache is the fridge. It’s a saved copy of something kept nearby, so it can be used again quickly. Your browser, your phone and websites all use caches.
Where caches are
- your browser keeps copies of logos, pictures and pages you've visited
- apps keep copies of things they've already loaded
- websites keep ready-made pages, so they don't have to build them each time
- a CDN keeps copies in cities around the world
When it goes wrong
The saved copy can be out of date. That’s why “clear your cache” is classic advice when a site looks broken: it throws out the old copies and fetches fresh ones.
What it isn’t
It isn’t a cookie. A cache stores copies of things, like pictures and pages. A cookie stores a small note about you.
Where the comparison breaks down
You know when you last bought milk. Caches use expiry dates set by the website. You can’t easily see them.
How the words fit together
A cache keeps copies near you. A CDN is a giant shared cache around the world. Both make websites faster.
If a website looks out of date or broken, try a hard refresh (Cmd+Shift+R on a Mac, Ctrl+F5 on Windows). It skips the cache and fetches a fresh copy.

When you'll hear it
“Clear your cache.” Delete the saved copies so you get fresh ones.
“It's cached.” A copy has been saved nearby, so it loads fast.
“The cache is stale.” The saved copy is out of date compared with the real thing.
“When we update something, how long might people still see the old saved copy?”

