The browser cache is a folder on your computer or phone where your web browser keeps copies of files from sites you visit: images, stylesheets, scripts and sometimes whole pages. On your next visit the browser reuses those copies instead of downloading them again, so the site opens faster and uses less data.
How the server tells the browser what to keep
The browser does not decide on its own. Every file a server sends comes with HTTP headers, and the most important one here is Cache-Control. A value like max-age=31536000, immutable says "keep this for a year and do not even check". no-cache, despite the name, means "you may keep it, but ask me before using it". no-store means never save it at all.
When a stored file has expired, the browser can revalidate instead of re-downloading. It sends the file's ETag (a fingerprint) or its last-modified date, and if nothing has changed the server answers with a short 304 Not Modified response. That saves the full download while still confirming the copy is current.
Example: "I updated my site but nothing changed"
A yoga teacher swaps the homepage photo and tells a friend, who sees the new photo. On her own laptop the old one keeps appearing. Her browser is still using its saved copy because the image had a long lifetime and kept the same file name. A hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on a Mac) or opening a private window shows the real current version. The lasting fix is for the site to give updated files a new name, which most modern build tools do automatically by adding a content hash.
When browser cache matters for your site
For returning visitors, a well-set cache is the difference between a page that loads almost instantly and one that downloads everything again. It also matters when troubleshooting: before reporting that a change "did not work", check with the cache bypassed. Browser cache is separate from cookies, which store small pieces of data like logins, though both are often cleared from the same settings screen.
Browser cache mistakes
- Telling customers to clear their cache. If they must, the site's headers are wrong. Version file names instead.
- Caching HTML for a long time. Visitors will not see new content or links to new files until it expires.
- Using no-store everywhere. It makes every visit a full download.
- Confusing it with the CDN. Clearing your browser does not clear a CDN, and purging the CDN does not reach copies already sitting in visitors' browsers.
Related terms
- Caching: the general idea and the other layers.
- CDN: the shared cache between browser and server.
- Cookie: a different kind of browser storage.
- Web browser: the software that manages this cache.