Cache vs Cookies vs Browsing Data Explained
Short answer
Cached images and files is safe to clear — it only costs you a slower first visit to each site. Cookies and other site data signs you out of every website and wipes site preferences. Passwords and Autofill are separate boxes and should almost never be ticked. Clearing the cache alone fixes most display problems without any of the disruption.
On this page
The advice “clear your cache and cookies” is given as if it were one action. It is two, they have nothing to do with each other, and only one of them is free.
The cache is a performance copy of files the site already sent you. Cookies are your identity on every site you use. Deleting the first costs you a few seconds; deleting the second costs you an afternoon of signing back in to things.
Here is what each checkbox in Chrome’s delete dialog actually removes, so you can tick the one you need and leave the rest alone.
What each one stores
| Data type | What it is | Cost of clearing it |
|---|---|---|
| Cached images and files | Local copies of images, CSS, scripts | Slower first visit to each site. Nothing else |
| Cookies and other site data | Session tokens, preferences, offline app data | Signed out everywhere, site settings reset |
| Browsing history | The list of URLs you visited | Address bar stops predicting, synced devices lose it too |
| Download history | A list of what you downloaded | Nothing. The files stay on disk |
| Passwords | Saved credentials | You need them written down elsewhere, or they are gone |
| Autofill form data | Addresses, card numbers, form entries | Retyping everything |
Chrome’s dialog lives at chrome://settings/delete-browsing-data, with
Basic and Advanced tabs. The Advanced tab is where passwords and
autofill appear, and the reason they are hidden there is that almost nobody
should be ticking them.
The cache: safe, and the one you usually want
Every image, stylesheet and script a site sends gets stored on disk so the next visit does not have to download it again. That is the entire mechanism. The cache holds no identity, no preferences and no logins.
Clearing it is the correct move when:
- A page renders with broken layout or missing images.
- A site has pushed an update and you are still seeing the old version.
- A web app fails in a way that looks visual rather than logical.
What it costs: the next visit to every site re-downloads its assets. On a decent connection that is a few extra seconds per site, spread across a day as you revisit things. There is no ongoing penalty and nothing to rebuild manually.
What it does not do, despite the folklore: it does not free up meaningful disk space on a modern machine, it does not speed up the browser, and it does not reduce memory use — the cache lives on disk, not in RAM. If you are here for memory reasons, what Chrome’s memory use actually means covers why the two are unrelated.
Chrome caps the cache at a fraction of your free disk space and evicts old entries automatically. It does not grow forever, so there is no maintenance case for clearing it on a schedule.
Cookies and site data: the expensive one
A cookie is a small piece of text a site asks your browser to store and send back on every subsequent request. That is how a website knows you are still the person who signed in three minutes ago. Delete it and you are a stranger again.
“Other site data” is the larger half, and it is why clearing cookies sometimes removes hundreds of megabytes:
- localStorage — site preferences, draft text, interface state.
- IndexedDB — proper databases. A webmail client caching messages for offline use keeps them here.
- Service worker caches — the offline copy of a progressive web app.
Ticking this box signs you out of every site, resets cookie-consent choices so every banner comes back, clears site-specific preferences like dark mode and language, and removes offline data for any web app you use.
Do it when you have a genuine reason: a sign-in loop on one site, a consent banner that will not stay dismissed, or a web app in a corrupted state. Not as routine hygiene.
Clear one site instead of all of them
This is the part most people miss. You almost never need to clear cookies globally.
Open the problem site, click the icon to the left of the address bar, then Cookies and site data → Manage on-device site data → Delete. That removes everything for that one domain and leaves every other site signed in.
If a site keeps forgetting you even when you have not cleared anything, the cause is usually a setting rather than a cleanup, and why Chrome keeps logging you out of websites covers the clear-on-exit and third-party cookie cases.
Browsing history: syncs, unlike the others
History is the list of pages you visited, visible at chrome://history. Chrome
uses it to predict addresses as you type, which is the main thing you lose.
The important distinction: history and passwords sync; cache and cookies do not. So clearing history on your laptop while signed into Chrome removes it from your phone too, within a minute or so. Clearing cookies on your laptop leaves your phone’s sessions entirely alone.
Deleting history also does not make you anonymous. Your network provider, your employer if you are on a work machine, and every site you visited all have their own records. Local history is a convenience feature, not a privacy control.
Passwords and autofill: leave these alone
Do not tick Passwords unless you are certain the credentials exist somewhere else. If Chrome is the only place a password is stored and you are not signed into Chrome sync, clearing it destroys the only copy. There is no undo and no recovery short of a password reset on each affected site.
Before ever touching that box, open chrome://password-manager and check what
is in there. Export it if you are moving to something else.
Autofill is lower stakes but equally pointless to clear casually — it is addresses, phone numbers and card details you will retype by hand. If autofill has stopped working, clearing it is not the fix; what to check when Chrome autofill stops working goes through the actual causes.
What to tick, by symptom
| Problem | Tick this | Leave alone |
|---|---|---|
| Page looks broken or outdated | Cached images and files | Everything else |
| Sign-in loop on one site | That site’s data only, via the address bar | The global dialog |
| Consent banners keep reappearing | Cookies and other site data | Passwords, autofill |
| Selling or handing over the machine | Everything, then sign out of Chrome | — |
| Chrome feels slow | None of them | All of it |
That last row is deliberate. Clearing data to fix slowness is the most common mistake in this area, and it reliably makes things slightly worse for a day without addressing the cause. The actual causes are in Chrome slow even with few tabs open.
What to expect
Clearing the cache: a few seconds of extra loading per site for a day, and usually a fixed rendering problem. Low risk, worth trying early.
Clearing cookies: an hour or two of signing back into things, plus re-dismissing every cookie banner on the internet. Worth it for a specific stuck site, rarely worth it otherwise, and almost never worth doing globally when the per-site option exists.
The honest summary is that browser data is not something that needs managing. Chrome evicts old cache entries on its own and cookies expire on their own schedule. The only reason to open that dialog is a specific symptom you are trying to clear.