Cache vs Cookies: The Difference, and Which One to Clear for Your Problem
Cache vs cookies explained in plain words: what each one stores, what clearing each does, and a quick table to pick the right one for a broken or looping site.
On this page · 10 sections
Cache vs cookies is the question behind most "should I clear my browser data?" moments. They sit next to each other in Chrome's delete window, so people tick both. But they do very different jobs, and clearing the wrong one either does nothing or signs you out of everything.
Here is the difference in plain words, a table to decide in five seconds, and how to clear just one of them.
The short answer#
- Cache = copies of files (images, scripts, styles) so pages load faster. Clearing it signs you out of nothing.
- Cookies = small notes about you, like "signed in". Clearing them signs you out.
- Old or broken page? Clear cache. Sign-in problem? Clear cookies.
- Only one site broken? Clear just that site.
What the cache is#
When you open a page, the site sends your browser the files it needs: the logo, photos, fonts, the scripts that make buttons work, the styles that lay it all out. Chrome keeps copies of these in its cache so the next visit can skip downloading them again. MDN's guide to HTTP caching explains how sites tell browsers how long each copy stays fresh.
Key facts:
- The cache is not sent back to the site. It is only used by your browser.
- It holds files, not information about you.
- It can go stale: if a site updates and your browser keeps an old copy, you see an old or half-broken page.
Clearing the cache costs one slower page load per site. That is it.
What cookies are#
Cookies are tiny pieces of text a site asks your browser to remember: a session ID that proves you signed in, the items in your cart, your language, whether you dismissed a banner. MDN's cookie guide describes them in detail.
Key facts:
- Cookies go back to the site with every request. That is how the site knows it is you.
- They hold information about you and your session.
- They can break: an old session, two accounts fighting, or too many cookies cause sign-in loops and errors.
Clearing cookies makes the site forget you. You are signed out, and preferences reset.
Cache vs cookies side by side#
| Cache | Cookies | |
|---|---|---|
| What it stores | Copies of images, scripts, styles, fonts | Small notes: session, cart, settings |
| Sent to the site | No | Yes, with every request |
| Typical size | Megabytes to gigabytes | A few kilobytes per site |
| Clearing it means | Slower first load | Signed out, preferences reset |
| Clear it to fix | Old version, broken layout, missing images | Login loop, wrong account, redirect errors |
| Privacy angle | Shows what you loaded | Can be used to track you |
And "site data"?#
Chrome's delete window says Cookies and other site data. The "other site data" part is storage that modern web apps keep in your browser: local storage, session storage, IndexedDB databases, Cache Storage and service workers. MDN's Web Storage guide covers the first two.
This matters because some site data behaves like a cache (service workers can serve old pages) and some behaves like cookies (some apps keep sign-in tokens in local storage). When a web app is stuck, clearing site data for that one site is often what fixes it. Our DevTools clear site data guide breaks down each type.
Which one should you clear?#
| Symptom | Clear |
|---|---|
| The page shows yesterday's version | Cache (and service workers) |
| Layout broken, images missing | Cache |
| Sent back to the sign-in page every time | Cookies |
| Signed in to the wrong account | Cookies |
| ERR_TOO_MANY_REDIRECTS | Cookies |
| "Request Header Or Cookie Too Large" | Cookies |
| A web app will not load after an update | Site data |
| You want privacy on a shared computer | Cookies and site data |
When in doubt, clear cache first. It never signs you out. Move to cookies only if the problem is still there. Guides for specific cases: Chrome showing an old version of a site, website login loop and request header or cookie too large.
Clear just one of them, for just one site#
Chrome's defaults push you toward clearing both, for every site. You can be much more precise:
- Cache only, all sites: Ctrl+Shift+Delete, tick only Cached images and files.
- Cookies, one site: the icon left of the address, then Cookies and site data, then Manage on-device site data.
- Either, one site, in one click: Cleaner, our free Chrome extension. Fix broken page clears that site's cache and service workers and keeps cookies. Sign out & reset clears its cookies and storage too.
How to see them for yourself#
You can look at both in a minute, which makes the difference stick:
- Open any site and press F12 (Command+Option+I on a Mac).
- Go to the Application panel.
- Under Storage, expand Cookies and click the site. Each row is one cookie: a name, a value, the domain it belongs to and when it expires.
- Under Storage, look at Local storage and Session storage for the site's key-value data.
- For the cache, switch to the Network panel and reload. The Size column says "(disk cache)" or "(memory cache)" for files Chrome reused instead of downloading.
Cookies are a short list of small text values. The cache is the much larger pile of files behind the page. Once you have seen both, the choice of what to clear is obvious.
Myths worth dropping#
- "Clearing cache speeds up Chrome." Usually the opposite, for the first visit to each site. Slowness comes from tabs and extensions. See why Chrome is so slow.
- "Cookies are viruses." They are plain text a site asked your browser to keep. They can be used for tracking, which is a privacy concern, not malware.
- "Clearing cookies deletes my passwords." Saved passwords live in Google Password Manager, separate from cookies.
Know which one you are clearing and why, and you will never sign yourself out of everything to fix one page again.
Frequently asked questions
What is the difference between cache and cookies?
The cache stores copies of files a site sent you, such as images, scripts and styles, so pages load faster next time. Cookies store small pieces of information a site wants to remember about you, such as that you are signed in or what is in your cart. Cookies go back to the site with every request; cache files do not.
Should I clear cache or cookies?
Clear the cache when a page looks old, broken or will not update. Clear cookies when the problem is about signing in: a login loop, the wrong account, or an ERR_TOO_MANY_REDIRECTS error. Start with cache, because it does not sign you out, and move to cookies only if the problem remains.
Is it safe to delete cookies and cache?
Yes. Neither holds your saved passwords, bookmarks or files. Clearing cache only makes the next visit to each site a little slower. Clearing cookies signs you out and resets site preferences, which is inconvenient but harmless. Clear only the site with the problem to keep everything else as it was.
What is site data compared with cookies?
Site data is the wider group that includes cookies plus other storage a site keeps in your browser: local storage, session storage, IndexedDB databases, Cache Storage and service workers. Chrome's Cookies and other site data option clears all of these together, which is why web apps reset completely after it.