- Step 1: The Incognito Test (30 Seconds)
- Step 2: Hard Refresh (5 Seconds)
- Step 3: Clear Cache for That Site
- Still Broken? Check Extensions
- Common Cache-Related Symptoms and Their Fixes
- The Site Is Your Own — Why Visitors See an Old Version
- When Cache Isn't the Problem
- Quick Diagnosis Checklist
- Frequently Asked Questions
- Step 1: The Incognito Test (30 Seconds)
- Step 2: Hard Refresh (5 Seconds)
- Step 3: Clear Cache for That Site
- Still Broken? Check Extensions
- Common Cache-Related Symptoms and Their Fixes
- The Site Is Your Own — Why Visitors See an Old Version
- When Cache Isn't the Problem
- Quick Diagnosis Checklist
- Frequently Asked Questions
A website that was fine yesterday suddenly has a broken layout. Images aren't loading. The navigation looks like it's from 2019. You ask a colleague to check it and they say it looks perfectly fine on their end.
You have a cache problem. Here's how to confirm it and fix it in the fewest steps possible.
Step 1: The Incognito Test (30 Seconds)
Before touching anything, do this one test. Press Ctrl+Shift+N (or Cmd+Shift+N on Mac) to open an Incognito window. Navigate to the problem site.
Incognito mode starts with no cached data and no extensions. If the site:
- Loads correctly in Incognito — you have a cache or extension issue. Continue with this guide.
- Still broken in Incognito — the problem isn't your cache. The server has a real issue, or there's a network problem. Skip to the "When Cache Isn't the Problem" section.
If the incognito test points to cache, you have two sub-possibilities: stale cached files, or a broken extension interfering with the page. We'll sort that out next.
Fix It in One Click
Once you've confirmed it's a cache issue, Clear Cache for Specific Site clears just the problem site without touching anything else.
Add to Chrome — FreeStep 2: Hard Refresh (5 Seconds)
If the Incognito test showed the site working, try a hard refresh on your main browser window first. This forces Chrome to ignore cached files for this one reload without deleting anything:
- Windows/Linux: Ctrl+Shift+R
- Mac: Cmd+Shift+R
- Or: Hold Shift and click the reload button
If the site looks correct after the hard refresh, you had a cache mismatch. The problem may or may not come back on the next normal visit depending on how the site manages its cache headers. If you want to fully clear the cached files so the problem doesn't recur, proceed to Step 3.
Step 3: Clear Cache for That Site
A hard refresh bypasses the cache temporarily but doesn't delete it. To permanently clear the cached data for one site:
Fastest Method: Extension
Navigate to the problem site, click the Clear Cache for Specific Site extension button in your toolbar. Done. Only that site's cache is cleared.
Built-In Method: Site Settings
chrome://settings/content/all in your address barStep 2 — Type the domain in the search box (just the domain, e.g.,
example.com)Step 3 — Click the matching entry
Step 4 — Click the trash icon or "Delete data" button
Step 5 — Reload the site
Alternative: DevTools Shortcut
While on the problem site, press F12 to open DevTools. Right-click the reload button (the circular arrow in the address bar) and select "Empty Cache and Hard Reload". This only works while DevTools is open.
Still Broken? Check Extensions
If clearing cache didn't help but Incognito works, a browser extension is interfering with the page. Extensions are disabled in Incognito by default, which is why the site works there.
To isolate which extension is causing the problem:
- Go to
chrome://extensions/ - Toggle off all extensions
- Reload the problem site — if it now loads correctly, an extension was the culprit
- Re-enable extensions one by one, reloading after each, until the problem returns
- The last extension you enabled before the problem came back is the one interfering
Ad blockers, privacy extensions, and script blockers are the most common culprits. They sometimes block resources that legitimate sites need to display correctly.
Common Cache-Related Symptoms and Their Fixes
| Symptom | Likely Cause | Fix |
|---|---|---|
| Old layout showing after site redesign | Stale CSS in cache | Clear cache for this site |
| Images not updating | Old image files cached | Clear cache for this site |
| JavaScript errors on recently updated site | Old JS conflicting with new HTML | Clear cache for this site |
| Site works for others, broken for you | Your cache has stale version | Clear cache for this site |
| Missing navigation items or buttons | Old HTML or CSS from cache | Clear cache for this site |
| Font looks different/wrong | Old font file cached | Clear cache for this site |
| Page content not updating | May be server-side caching | Clear cache + check if server has caching |
| Site completely down (500/404) | Server error, not cache | Not a cache issue — contact site owner |
The Site Is Your Own — Why Visitors See an Old Version
If you're a developer or website owner, cache problems are a constant part of the job. You push an update and check it in Chrome — but you're seeing the old version. Worse, you clear your cache and now it shows correctly, but users are reporting they still see the old one.
A few things to know:
Your CDN Might Be Caching the Old Version
Many sites use CDNs (Cloudflare, CloudFront, Fastly) that cache content at the edge. Clearing your browser cache doesn't clear the CDN cache. You need to purge the CDN separately — in Cloudflare this is in the Caching dashboard, in AWS it's a CloudFront invalidation.
Browser Cache Expiry (Cache-Control Headers)
How long browsers cache your files depends on your server configuration. If your CSS file is served with Cache-Control: max-age=31536000 (one year), users won't re-download it for a year unless you either change the filename or they manually clear cache.
The correct solution is cache busting at the file level: append a version hash to asset filenames. Most build tools (Vite, Webpack, Parcel) do this automatically.
Cache-Control: max-age=300, must-revalidate. This forces browsers to recheck the file every 5 minutes.
Service Workers Are Aggressive Cachers
If your site has a service worker (check DevTools > Application > Service Workers), it may be intercepting requests and serving cached responses independently of the browser's HTTP cache. Unregistering the service worker forces a fresh load.
The One-Click Cache Fix for Developers
When you're constantly clearing cache during development and testing, the Chrome settings route gets old fast. The extension handles it with one click per site.
Install Clear Cache for Specific SiteWhen Cache Isn't the Problem
If the Incognito test showed the site is still broken, cache isn't your issue. Here are the actual causes to check:
The Site Is Down
Check downforeveryoneorjustme.com or isitdownrightnow.com. If the site is down for everyone, there's nothing to fix on your end.
DNS Issue
If only specific sites are inaccessible and others work fine, you might have a DNS cache problem. Open Command Prompt (Windows) and run:
ipconfig /flushdns
This clears the local DNS cache, which is separate from browser cache.
Network or Firewall
Try a different network (phone hotspot vs. WiFi) or check if your firewall or VPN is blocking access.
Browser Profile Corruption
Rare, but browser profile data can become corrupted. Creating a new Chrome profile (Settings > People > Add person) and testing there can confirm or rule this out.
Quick Diagnosis Checklist
- Site broken? Test in Incognito window first
- Works in Incognito → cache or extension issue
- Broken in Incognito → server problem, not cache
- Try hard refresh: Ctrl+Shift+R
- Still broken → clear cache for this specific site
- Still broken → disable all extensions, test again
- Still broken → test in a different browser
- Still broken → flush DNS cache, try different network
Frequently Asked Questions
Why is a website not loading properly in Chrome?
The most common causes are stale browser cache (site updated but your browser is serving old files), an extension conflict, a corrupted cookie, DNS cache issues, or an actual server problem. Start by testing in Incognito — if it works there, it's a local cache or extension issue.
How do I know if it's a cache problem or a server problem?
Open the site in an Incognito window (Ctrl+Shift+N). If the site loads correctly in Incognito but not in your regular window, it's a cache or extension issue. If it's broken in both, the server has a real problem that no amount of cache clearing will fix.
My website is showing an old version after I updated it. How do I fix it?
First try a hard refresh with Ctrl+Shift+R. If the old version persists, clear the cache specifically for that site using Chrome's site settings or the Clear Cache for Specific Site extension. If you own the site and visitors see the old version, you may also need to purge your CDN cache.
Website loads fine on mobile but is broken on desktop Chrome. Why?
Your desktop Chrome has a cached copy of an older version of the site. Your mobile browser either never cached it or already expired the cache. Clearing the cache for that site in desktop Chrome resolves the discrepancy.
CSS is broken on a website — how do I fix it?
Broken CSS is almost always a cache mismatch. The browser loaded new HTML but is applying old style rules. Hard refresh first (Ctrl+Shift+R). If that doesn't work, clear the site's cache. You can verify the cause in DevTools Network tab — look for the CSS file and check if it's serving from cache.
Clearing cache didn't fix the website. What now?
Try: 1) Disable all extensions and reload. 2) Clear cookies for the site in addition to cache. 3) Test in a different browser. 4) Flush DNS cache with ipconfig /flushdns. 5) Try on a different network. If none of these work, the problem is server-side.
More Free Chrome Tools by Peak Productivity
