Clearing Chrome’s cookies and cache is one of the most effective first steps for browser problems that appear out of nowhere — pages that won’t load, sites that keep logging you out, or content that looks wrong when you know it should have updated. But the approach matters: clearing everything at once solves some problems while creating new ones (you’ll be logged out of every site). This guide covers the targeted approach as well as the full clear, so you can choose based on what’s actually broken. If you want the full context, see our Chrome How-To Guides.
Quick decision: which type of data are you clearing?
Chrome stores several types of data that are often confused:
- Cache (temporary files): stored copies of images, CSS, scripts, and page resources. Speeds up loading by avoiding re-downloads. Goes stale over time. Doesn’t contain login information.
- Cookies: small data files sites use to remember your session, preferences, and login state. Deleting these logs you out of every site that uses cookies for authentication.
- Site data / localStorage: more complex data stored by web applications, often including offline capability data or large amounts of state.
If pages look wrong or stale: clear the cache only. You’ll stay logged in. If you’re having login problems (site doesn’t recognise you, you’re stuck in a logged-in loop): clear cookies for that specific site. If you want a fresh start: clear everything for all time, then expect to log back into every site you use.
Clearing the cache only (stay logged in)
Ctrl+Shift+Delete → ensure “Cached images and files” is checked → uncheck “Cookies and other site data” → change time range to “All time” → Clear data.
This removes locally stored copies of pages and resources, forcing Chrome to re-download everything fresh. Your login sessions are unaffected — cookies remain in place. This is the right first step for: pages that look outdated, images not loading, CSS that looks broken, or site functionality that’s working differently than expected.
Clearing cookies for a specific site only
Rather than logging yourself out of everything: you can delete cookies for one specific site. Navigate to that site → lock icon in the address bar → Cookies → see all cookies from that domain → “Remove all shown” → Done. Or from settings: chrome://settings/content/cookies → “See all site data and permissions” → search for the domain → delete.
This is particularly useful when: a specific site isn’t logging you in correctly, you want a site to “forget” your preferences, or you’re testing a site’s first-visit experience. Everything else stays logged in.
Full clear: cookies and cache together
Ctrl+Shift+Delete → check both “Cached images and files” and “Cookies and other site data” → set time range to “All time” → Clear data. This is the nuclear option — after this, you’ll need to log back into every website that uses cookie-based authentication. That includes email, social media, banking, streaming services, and any work tools you access via browser.
When to do the full clear: when troubleshooting a persistent problem that partial clearing didn’t resolve, when switching between user accounts on a shared computer, when you’ve inherited a browser profile with unknown data, or when security is a concern (someone else used your browser, or you’re worried about stored session tokens).
Using a hard refresh instead of clearing cache
For many “stale page” issues: a hard refresh is faster and doesn’t require going into settings. Ctrl+Shift+R (or Shift+F5) reloads the page while bypassing the cache for that one request. The cached data is still stored; Chrome just doesn’t use it for this load.
If the hard refresh fixes the problem: the issue was a stale cached version of that specific page. If it doesn’t: either the cache is fine and something else is wrong, or there are multiple layers of caching (service worker, CDN) that a hard refresh doesn’t bypass. In the latter case: DevTools → Application → Storage → Clear site data clears the deeper layers including service worker caches.
Scheduled cache clearing and browsing data settings
Chrome can automatically clear certain types of browsing data when you close the browser. chrome://settings/privacy → “Clear browsing data” → “On exit” tab → select what to clear automatically on close.
That same on-exit setting is the usual reason Chrome won’t save history at all — if browsing history is in the on-exit list, every session starts blank no matter how much you browse.
This is useful for shared computers or for users who want to start fresh each session. The trade-off: you’ll need to log in to sites again with each browser session. On a personal machine you use daily: this is usually more friction than it’s worth. On a public or shared machine: automatic clearing on exit is a sensible privacy practice.
Our guide on Chrome loading and performance issues covers page loading problems that sometimes relate to cache state, and our Chrome privacy settings overview covers the broader picture of what Chrome stores and how to manage it. For understanding Chrome’s cache architecture and service worker caches specifically, Chrome’s developer documentation covers the full caching stack that web developers work with.
What clearing doesn’t do
Common misconceptions worth clarifying:
- Clearing history doesn’t clear cache: browsing history and cache are stored separately. Clearing one doesn’t affect the other.
- Clearing cache doesn’t delete passwords: saved passwords are stored in Chrome’s profile data, not in the cache. They’re unaffected by cache clearing.
- Clearing cookies doesn’t remove the sites from your allowed/blocked lists: permission settings (notifications, location, camera) are separate from cookies and persist through cookie clearing.
- Clearing Chrome’s cache doesn’t clear DNS cache: for DNS resolution problems, chrome://net-internals/#dns → “Clear host cache” is the relevant action.
| Problem | What to clear | Logged out after? |
| Page looks outdated or images broken | Cache only | No |
| One site not recognising login | Cookies for that site only | From that site only |
| Login loops on multiple sites | Cookies for all time | Yes, everywhere |
| Site shows wrong version despite hard refresh | Cache + site data (DevTools method) | From that site |
| Privacy clean-up on shared computer | All browsing data, all time | Yes, everywhere |
Clearing Chrome’s cookies and cache takes under a minute and resolves a surprisingly wide range of browser issues. The targeted approach — clearing only what you need for the specific problem — makes the process less disruptive. The “clear everything” approach is useful for clean-slate situations but creates the expectation that you’ll spend 10 minutes logging back into things. Knowing which situation calls for which approach makes this a much less blunt instrument than it’s often treated as.
The DevTools approach for thorough cache clearing
Standard Ctrl+Shift+Delete doesn’t clear Service Worker caches. If a web app (Gmail, Google Docs, Notion, a PWA) shows outdated content even after clearing cache via settings: the Service Worker cache is still serving the old version.
F12 to open DevTools → Application tab → Storage (left sidebar) → “Clear site data” button at the top. This clears everything: HTTP cache, Service Worker caches, IndexedDB, localStorage, and cookies for that origin. More thorough than the settings dialog for specific sites that use Service Workers.
Alternatively: DevTools → Application → Service Workers → “Unregister” next to the active service worker → reload. This forces Chrome to download a fresh Service Worker on the next visit, which re-establishes the cache from scratch.
Cache size and storage usage
Chrome doesn’t cache indefinitely — it manages cache size automatically, evicting older entries when storage runs low. On devices with limited storage (small SSD laptops, Chromebooks): Chrome’s cache can be a meaningful fraction of free space. To check how much Chrome is using: chrome://settings/privacy → “Clear browsing data” → see the size estimate next to each data type.
If storage is a concern: clearing the cache frees that space immediately. Chrome will rebuild the cache as you browse, starting with whatever you visit next. The freed space is permanent until Chrome accumulates new cache data over time.
How long should you wait between cache clears
For most users on a personal machine: there’s no regular schedule needed. Cache exists to speed up browsing, and clearing it unnecessarily removes that benefit. Clear when you’re troubleshooting a specific problem, or when you want a fresh state for a reason.
If you use a shared computer: clearing on each session end (or automating this through Chrome’s “On exit” data clearing) makes practical sense for privacy. If you’re regularly accessing sites that update their content frequently (news, dynamic web apps): Chrome’s cache headers handle freshness automatically — sites that want fresh loads set short or no cache durations, so the browser fetches new content regardless.
Chrome’s memory cache vs disk cache
Chrome maintains two levels of cache: a memory cache (RAM) that holds recently-used resources for the current session, and a disk cache (stored files) that persists across browser restarts. Hard refresh (Ctrl+Shift+R) bypasses both. Standard Ctrl+Shift+Delete clears the disk cache. When Chrome is closed and reopened, the memory cache is gone but the disk cache remains — which is why some issues persist across Chrome restarts despite looking like fresh starts.
This distinction explains an occasional puzzling scenario: you close Chrome, reopen it, and the same “stale” behaviour persists. The disk cache still has the old data. A Ctrl+Shift+R hard refresh or a settings-level cache clear (targeting disk cache) resolves it, while just restarting Chrome doesn’t.
For the vast majority of cache-related issues: Ctrl+Shift+Delete with “All time” and “Cached images and files” checked, followed by a normal page reload, is sufficient. The more targeted methods here — DevTools service worker clearing, site-specific cookie deletion, the distinction between memory and disk cache — become relevant for persistent issues that survive the standard clear.
Cookies and third-party blocking
An important distinction as Chrome phases out third-party cookies: Chrome’s cookie settings include options to block third-party cookies even without clearing existing ones. chrome://settings/cookies → “Block third-party cookies” prevents sites from setting cross-site tracking cookies going forward, without affecting the first-party cookies that keep you logged in.
This is different from clearing — blocking stops new third-party cookies from being set, while clearing removes existing stored ones. For privacy purposes: enabling third-party cookie blocking is more impactful than periodic clearing, because it addresses the source rather than cleaning up after the fact. The two work well together: block third-party cookies for ongoing protection, and occasionally clear your existing cookie store for privacy clean-up.
When clearing doesn’t fix the problem
If you’ve cleared cache and cookies and the browser problem persists: the issue is likely not data-related. Other causes to investigate:
- Extension conflict: disable all extensions → test → if the problem resolves, an extension is the cause
- DNS cache: chrome://net-internals/#dns → Clear host cache (a separate cache from the browser data)
- Chrome profile corruption: create a new Chrome profile and test whether the problem exists there
- Server-side or CDN caching: the site’s own cache is serving old content and clearing your browser cache doesn’t affect it. Append ?v=2 to the URL to force a different cache key — if content changes, the server or CDN was the cache, not your browser.
Chrome’s Ctrl+Shift+Delete dialog is genuinely one of the most useful tools in the browser — fast, targeted, and effective for a wide range of problems. Understanding what each data type actually is (cache speeds things up, cookies maintain sessions, localStorage stores app state) turns “clear everything and hope” into a deliberate, targeted action that solves the right problem without creating new ones like unexpected logouts.
Automated cookie and cache management tools
For users who want more granular control than Chrome’s built-in tools provide: Cookie AutoDelete (Chrome extension) automatically deletes cookies from sites after you close their tabs, rather than accumulating cookies indefinitely. This is more targeted than Chrome’s “On exit” clearing — it removes cookies per-site as you finish with each site, rather than everything at once at session end. You can whitelist specific sites whose cookies you want to keep (banking, email, tools you use regularly) while all other sites’ cookies get cleaned up automatically.
An alternative approach: clear cookies at a longer interval (monthly rather than after each session) while using third-party cookie blocking for ongoing privacy. This balances staying logged into the sites you use with reducing the accumulation of tracking cookies from sites you visit less regularly. Our guide on Chrome Task Manager covers an adjacent issue.
The right approach depends on your actual usage: regular users of the same 10-15 sites benefit most from keeping cookies (staying logged in) and clearing cache only when troubleshooting. Users who browse a wide variety of sites and prioritise privacy benefit from more aggressive cookie management. The Chrome settings and extension ecosystem supports both approaches well. See also How to Clear Chrome Cache Safely for a related case.
