Cookies vs Cache vs History: What Each One Actually Deletes (2026)
Every browser settings page offers a row of checkboxes and calls them "browsing data", as if they were the same substance. They are not. One logs you out of everything, one only makes the next page load slower, and one is a private list no website can read.
Here is what each data type actually stores, what clearing it changes, and how to pick the smallest switch that solves your problem.
The short version
| Data type | What it is | Clearing it does |
|---|---|---|
| Cookies | Small records: login tokens, carts, consent | Signs you out; may empty carts; consent banners return |
| Cache | Images, scripts, fonts stored for speed | First visit is slower; no logout |
| History | Local list of visited pages | Suggestions disappear; sites do not notice |
| Downloads | List of downloaded files, not the files | The list clears; files stay on disk |
| Form data | Autofill entries for forms | Autofill forgets names and addresses |
| Local storage | Per-site settings and drafts | Site preferences reset; unsaved drafts can vanish |
| IndexedDB | Structured app data, offline content | Web apps may lose local data or offline copies |
| Service workers | Background scripts and offline caches | Offline mode resets; site re-registers on next visit |
| Saved passwords | The browser's credential store | Passwords are removed; not part of "cookies" |
Cookies: the login layer
A cookie is a small key-value pair that a site asks the browser to store and send back on later requests. Session cookies expire when the browser closes; persistent cookies carry an expiry date and can last months. First-party cookies belong to the site you are visiting; third-party cookies belong to another domain embedded in the page.
Because the login token is usually a cookie, clearing cookies signs you out. Because the cart is often a cookie too, the cart may empty. Nothing about the cache or history is involved.
Cache: the speed layer
The HTTP cache stores copies of images, stylesheets, scripts and fonts. It exists so the second visit to a page is faster than the first. When a site looks stuck on an old layout after an update, the cache is the usual suspect — but clearing it has no effect on your account.
This is the safe switch to use when something is visually wrong and you do not want to log back into twenty sites.
History: the local diary
History is a local record of pages you visited, with timestamps. Websites cannot read it, and clearing it does not change how any site behaves. It affects your own conveniences: autocomplete in the address bar, recently closed tabs, and some search suggestions.
If you use browser sync, history may already exist on other signed-in devices. Clearing it locally does not erase those copies.
The storage you forgot
Modern web apps store more than cookies. Local storage holds preferences and sometimes drafts. IndexedDB holds structured data — offline documents, mail caches, progress in a course. Service workers run background code and keep offline copies of pages.
Clearing these can fix a broken app, and it can also delete work that was never sent to a server. This is why a cleaner should list them as separate switches instead of hiding them behind one "site data" label.
Nine switches, not one button
VKT CleanMate exposes nine data types independently: history, cache, cookies, downloads, form data, local storage, IndexedDB, service workers and saved passwords. Combined with the retention window and per-trigger scope, that means you can keep the last three days of history, drop the cache every two hours, and clean cookies only when the browser closes.
It also means the preview sheet can tell you the truth before anything is deleted: which sites were found, how many cookies, which types are active and what window applies.
A simple rule of thumb
- Login broken or wrong account → clear cookies for that one site.
- Stale layout or old script → clear the cache; no logout.
- Shared computer → history + cookies on close, with a protected list for the accounts you need.
- Web app misbehaving → local storage, IndexedDB and service workers for that origin.
- Changing a password → saved passwords are their own step; they are not cookies.
Delete the smallest thing that fixes it
Most browsing-data problems have a narrower fix than "clear everything". Learn which layer holds the symptom, and you keep your logins while still getting a clean browser.
FAQ
Does clearing the cache log me out of websites?
No. The cache holds files, not credentials. Logins live in cookies (and sometimes local storage or IndexedDB), so clearing only the cache keeps you signed in and merely makes the next page load slower.
Is browsing history visible to websites?
No. History is stored locally by the browser. A site cannot read the list of pages you visited. If you enable browser sync, the history is copied to your other signed-in devices, but it is still not exposed to websites.
Will clearing site data delete my saved passwords?
Not the ones in the browser's password manager. Saved passwords are a separate data type with separate controls. Chromium does not allow that store to be filtered per site, so it should be an explicit, deliberate step.
Why does one site ask for cookie consent again after I clear?
Consent is stored in a cookie (or local storage). Delete it and the site treats you as a first-time visitor, so the banner returns. That is expected behavior, not a bug.
More guides in the VKT blog; questions to [email protected].
