Chrome’s cache stores copies of website assets — images, scripts, CSS, fonts — so repeat visits to the same site are faster. The browser serves files from the local cache instead of downloading them again. Most of the time this works exactly as intended. When it doesn’t — when cached files are outdated, corrupted, or creating conflicts — clearing the cache restores the correct behaviour. If you want the full context, see our Chrome How-To Guides.
The fastest fix for most “site looks wrong” or “showing old content” problems: hard refresh. Ctrl+Shift+R (or Shift+F5). This forces Chrome to re-download everything for the current page without clearing the entire cache. Try this first. If the page looks correct after a hard refresh: the cache had stale files, and you’re done. Only proceed to clearing the full cache if the hard refresh didn’t help.
Clearing cache through Chrome settings
Ctrl+Shift+Delete → the “Clear browsing data” dialog opens → “Cached images and files” checkbox → ensure the time range is “All time” for the most thorough clear → “Clear data.”
This removes all cached files across all sites. Important: it doesn’t delete your browsing history (separate checkbox), doesn’t delete cookies or login sessions (separate checkbox), and doesn’t delete saved passwords (not in this dialog at all). Clearing cache only is a safe operation that won’t log you out of anything.
Clearing cache for one specific site
When only one site is misbehaving, clearing the entire cache is unnecessary. Site-specific clearing is more targeted:
While on the problem site: F12 (DevTools) → right-click the browser’s reload button → “Empty cache and hard reload.” This clears the cache specifically for that site’s origin and reloads fresh. Alternatively: DevTools → Application tab → “Clear site data” → this clears cache, localStorage, service workers, and cookies for that site specifically — more thorough than the standard cache clear for that one site.
Service worker caches — the layer that survives standard clearing
Standard cache clearing (Ctrl+Shift+Delete → Cached images) doesn’t clear service worker caches. Service workers are background scripts that manage their own cache for offline functionality and push notifications. Modern web apps (PWAs, Gmail, Twitter, Notion) typically use service workers.
If a site still shows outdated content after clearing Chrome’s standard cache: a service worker cache is serving the old version. To clear it: DevTools (F12) → Application tab → Service Workers → “Unregister” next to any active service worker → reload the page. Or: Application tab → Storage section → “Clear site data” button at the top, which clears all storage types including service worker caches in one action.
Cache and performance — the real relationship
A common misconception: clearing the cache “speeds up Chrome.” It doesn’t — it often makes Chrome temporarily slower. The cache exists to reduce loading times. Clearing it means Chrome has to re-download everything on the next visit to each site, which is slower than serving cached files. The benefit is accuracy (fresh content), not speed.
After clearing cache: Chrome rebuilds it automatically as you browse. Within a day or two, frequently-visited sites are cached again and loading at their normal speed. So there’s no harm in clearing, but it shouldn’t be done as a speed improvement measure. It’s a correctness fix for when cached content is causing problems.
Our guide on Chrome cookie and cache management covers the distinction between cache and cookies in more depth, and our Chrome performance troubleshooting covers actual speed improvements for slow Chrome. For service worker architecture and how PWAs manage caching, Chrome’s developer documentation covers the Cache API and service worker lifecycle that control progressive web app caching behaviour.
How much cache Chrome stores
Chrome manages cache size automatically, keeping the total size within limits based on available disk space. On most machines: Chrome’s cache uses between 100MB and a few GB, growing over time as you visit new sites. On machines with limited storage (32-64GB SSDs, Chromebooks): cache can be a meaningful fraction of available space.
To check current cache size: Ctrl+Shift+Delete → look at the size estimate shown next to “Cached images and files.” This gives an approximate figure. After clearing, the cache starts rebuilding from zero. If disk space is a concern: clear the cache to free space, though Chrome will slowly consume it again as you browse.
Cache and new vs existing sites
Cache issues only affect sites you’ve visited before — cached files from previous visits are what can become stale. First-time visits to a site always fetch everything fresh because there’s nothing cached to serve. If a site you’re visiting for the first time looks wrong: the problem isn’t cache-related; it’s the site itself, an extension, or another browser issue.
Diagnosing cache vs other issues
Before clearing cache: confirm it’s the likely cause. Cache problems typically produce specific symptoms:
- Site looks visually broken — missing images, unstyled text, layout that doesn’t match what it should look like
- Site shows content that you know was updated days ago but still shows the old version
- Login page loops even after entering correct credentials (a mix of cache and cookie issues)
- Error messages that appear on a site but disappear after hard refresh
Things that aren’t cache problems: slow page loading on a fast connection (network, not cache), Chrome itself being slow (extensions, memory — not cache), pages that never worked (never cached anything to clear), and authentication errors on first visit to a site.
| Problem | Cache-related? | Fix |
| Site shows old content | Yes | Hard refresh first; full cache clear if needed |
| Site visually broken | Possibly | Hard refresh; if persists, check in another browser |
| Login loops | Partially (also cookies) | Clear cookies for that specific site alongside cache |
| PWA shows wrong content | Yes (service worker) | DevTools → Application → Service Workers → Unregister |
| Chrome loads everything slowly | No | Check extensions, Memory Saver, hardware acceleration |
| First-visit site looks wrong | No | Different issue — extension, site error, or blocked content |
Cache clearing is one of those browser operations where understanding what it does and doesn’t do prevents a lot of unnecessary clearing. The hard refresh covers most use cases in one keystroke without touching anything else. The full cache clear is the right tool when multiple sites are affected or when the hard refresh alone isn’t sufficient. The service worker clear is for the minority of cases where standard clearing doesn’t reach the actual cached content causing the problem.
Keyboard shortcuts for cache operations
Useful shortcuts to keep in mind:
- F5: normal reload — uses cache
- Ctrl+R: same as F5
- Ctrl+Shift+R or Shift+F5: hard reload — bypasses cache for this page, doesn’t clear it
- Ctrl+Shift+Delete: opens clear browsing data dialog
The distinction between hard reload and cache clear matters: Ctrl+Shift+R bypasses the cache for the current page load but doesn’t delete cached files. If you reload again with F5 afterward: Chrome uses the cache again (because the hard reload didn’t clear it, just bypassed it for that one load). Cache clearing via Ctrl+Shift+Delete actually removes the stored files, so subsequent normal reloads also fetch fresh content.
Cache in Incognito mode
Incognito mode creates its own temporary cache that’s completely separate from your regular browsing cache. Cache cleared in normal Chrome doesn’t affect Incognito’s cache (which disappears when you close the incognito window anyway). Incognito cache cleared in the incognito window doesn’t affect regular Chrome’s cache.
This separation is useful for testing: if a site looks correct in Incognito but broken in normal Chrome (after both hard refresh and full cache clear): the issue isn’t the cache at all. The difference between Incognito and normal mode at that point is extensions (disabled in Incognito by default) and cookies (different set in Incognito), which points to an extension or cookie issue rather than a cache issue.
Automatic cache management
Chrome clears the cache automatically in two situations: when disk space runs critically low (Chrome evicts cache to free space), and when the cache entries exceed their TTL (Time To Live) — the expiry date set by the server that tells Chrome how long to consider the cached version fresh.
For static assets (images, fonts, code libraries) from well-maintained websites: cache TTLs are typically set to days, weeks, or months. For HTML pages and API responses: TTLs are usually much shorter or set to “no cache” to ensure freshness. This server-side configuration is why some assets look stale while others are always fresh — the server determines how long Chrome keeps each file type cached, and Chrome obeys those instructions until the TTL expires or you manually clear.
Developer-mode cache control
When developing or testing websites: Chrome’s DevTools allows disabling the cache entirely while DevTools is open. F12 → Network tab → “Disable cache” checkbox. With this on: every page load fetches everything fresh from the server, ignoring all cache TTLs. This ensures developers are always seeing the latest version of their code changes without manually clearing cache between tests.
For regular users: this option isn’t needed and leaving it off is correct. Cache makes browsing faster; disabling it permanently would make every page load slower. The DevTools cache disable is a development tool, not a privacy or correctness tool. Close DevTools when you’re done, and Chrome’s caching returns to normal behaviour automatically.
The cache is Chrome’s way of making repeat visits faster by not downloading the same files repeatedly. When it works as intended — which is the vast majority of the time — you never notice it. When it doesn’t (stale content, corrupted files, service worker conflicts), the fixes are fast and targeted: hard refresh for the common case, full clear for persistence, DevTools service worker unregister for PWA issues. Three tools covering effectively all cache-related browser problems.
Cache and enterprise / proxy environments
On corporate networks: content often passes through a proxy that has its own cache layer between Chrome and the internet. Clearing Chrome’s local cache doesn’t affect the proxy’s cache. If a site shows stale content that clearing Chrome’s cache doesn’t fix: the proxy is serving the old version to everyone on the network, not just you.
Signs this is a proxy cache issue rather than a local one: the stale content affects multiple people on the same network, clearing Chrome’s cache made no difference, and the content looks correct when accessed from a different network (home, mobile data). The fix requires IT to flush the proxy cache for that URL — a user-side action that won’t help here. Reporting to IT with the specific URL and description of the stale content usually resolves it within hours.
Cache clearing as troubleshooting step — when to include it
A practical note on where cache clearing fits in the Chrome troubleshooting sequence: it should be an early step when something visually wrong or stale-looking is the symptom, and a later step (or skipped) when performance, crashes, or functional issues are the symptom. “Page looks wrong or shows old content” → hard refresh, then cache clear. “Chrome is slow or crashing” → extensions and hardware acceleration, not cache. Matching the fix to the symptom category saves time and avoids unnecessary clearing.
For a comprehensive browser health check that includes cache alongside other common issues: hard refresh on any site that looks odd, extension audit (Shift+Esc for memory check), and permissions review (chrome://settings/content) cover the main maintenance areas. Cache clearing fits into this as one tool among several rather than the default response to any Chrome problem. Used selectively for appropriate symptoms: it’s quick, effective, and harmless. Our guide on Chrome Task Manager covers an adjacent issue.
One final note that often comes up: clearing Chrome’s cache has no effect on the DNS cache (the record of which IP addresses correspond to which domain names). For DNS-related issues — sites that worked but stopped being reachable after a domain change — the fix is chrome://net-internals/#dns → Clear host cache, which is separate from the browsing data cache. These two types of “cache” are completely independent systems with different clearing paths. Knowing the distinction prevents the frustration of clearing the browsing cache for a problem that’s actually in the DNS layer. See also Clear Chrome Cookies and Cache for a related case.
