Browser cache
Also known as: web cache, browser cache files, internet cache
A browser cache is a storage area where your web browser saves copies of website files, such as images, logos, stylesheets, and scripts, so pages load faster on your next visit.
Instead of downloading everything again, the browser reuses what it already has. While caching makes browsing quicker and saves data, outdated cached files sometimes cause pages to look broken or show old content, which is why 'clear your cache' is classic tech support advice.
Browser cache, explained at three levels
At home
A browser cache is like keeping a copy of a menu from your favourite restaurant at home. Next time, you don't need to go pick one up, so you decide faster.
At work
Caching makes web apps load faster for staff, but old cached files can cause display problems after updates.
At home
If a website looks broken, try a hard refresh with Ctrl+Shift+R, or Cmd+Shift+R on a Mac. If that fails, clear cached images and files in your browser settings.
At work
Websites control caching with HTTP headers such as Cache-Control. Developers use versioned file names so users get new code after updates without clearing caches.
At home
Clearing the cache doesn't log you out, but clearing cookies does. In my opinion, clear just the cache first when troubleshooting.
At work
Configure caching carefully for sensitive pages, since shared computers may retain cached data. Use no-store headers for confidential content, and plan cache-busting in deployment pipelines.
Real-world examples
At home
Nadia's online banking page looked jumbled after a website update. A hard refresh loaded the new files, and the page displayed correctly.
At work
Marcus supports an Edmonton company's web portal. After a release, he added version numbers to file names so staff stopped seeing the old layout.
How it compares
| feature | Browser cache | HTTP cookie |
|---|---|---|
| Stores | Website files like images and scripts | Small pieces of data like logins |
| Purpose | Speed | Remembering you |
| Clearing it | Pages load slower once | Logs you out |
| Privacy impact | Low | Higher |
Cache speeds up sites. Cookies remember who you are.
For analysts
In release planning, I'd include cache handling in testing. Many 'the update didn't work' reports are really cached old files.
History & origin
Early web browsers in the 1990s introduced caching because dial-up internet was slow and every saved download mattered. The HTTP/1.1 standard in 1997 defined detailed rules for how websites tell browsers what to cache and for how long. Content delivery networks, starting with Akamai in 1998, applied similar ideas across the internet. Modern browsers added service workers around 2015, letting web apps cache content to work offline. Browsers also began separating caches by website, a change Chrome made in 2020, to stop sites from using shared caches to track people. In my view, the browser cache is one of the quiet reasons the modern web feels fast.