Clear Cache For One Site In Chrome - 3 Fast Methods

If you need to clear cache for one site in Chrome, you are in the right place. A single page can show old content or odd bugs while other sites look fine. You do not need to wipe everything. In this quick guide I share three reliable options that target only one site.
Try the first method, and if the problem stays, move to the next.
When to clear cache for only one site
-
The page shows an old version after a change
-
You get stuck logged out on just one site
-
Styles look broken on one domain
-
A script keeps failing on one page but other sites are fine
Method 1: Hard refresh to bypass cached files
This is the quickest test. It forces Chrome to fetch fresh files, but it does not erase cookies or storage.
Windows and Linux
-
Press Ctrl + F5
-
Or press Ctrl + Shift + R
macOS
-
Press Command + Shift + R
If the page fixes itself, you are done.
Method 2: Clear data for one site with chrome://settings/content/all
Use this when you need a clean reset for a single domain. It removes that site’s cookies and storage. You will likely need to log in again.
-
Open a new tab and go to
chrome://settings/content/all
-
Use the search box at the top right, type the site name or domain
-
Click the trash icon next to the exact host you want to reset
-
Reload the page for that site
Tips
-
Match the exact host name. If the site uses www or a subdomain, clear that version
-
If the site uses a redirect chain, clear data for each host in the chain
Method 3: Disable cache in DevTools Network while testing
Good for active debugging. This does not delete anything, it only tells Chrome to skip the cache while DevTools is open.
-
Open the problem page
-
Open DevTools with F12, or Ctrl + Shift + I on Windows and Linux, or Command + Option + I on macOS
-
Click the Network tab
-
Check Disable cache
-
Keep DevTools open, then reload
What gets deleted vs kept in each method
Method | What changes | What stays |
---|---|---|
Hard refresh | Bypasses cached files for this load only | Cookies, local and session storage, service workers |
Settings: chrome://settings/content/all | Deletes that site’s cache, cookies, and storage | Other sites’ data; service worker may remain until it updates or is unregistered |
DevTools: Disable cache | Skips cache while DevTools is open, nothing is deleted | Cookies, storage, service workers; cache returns when DevTools closes |
Quick fixes if the page still misbehaves
Open the site in Incognito to rule out an extension
Keep Disable cache on and watch the Console for errors as you reload
If the site uses a subdomain or redirect, clear data for that exact host name in chrome://settings/content/all
If a corporate proxy or VPN is in use, test on a different network
What I reach for first
Hard refresh is my first move. It is fast and safe. If that fails, I clear data for just the site with chrome://settings/content/all. During active fixes, I keep DevTools open and tick Disable cache so each reload pulls fresh files.
Keep this flow in mind. Hard refresh, clear site data in settings, then test with cache disabled. It fixes most odd bugs without wiping the rest of your browser.
If the issue looks like a network or name lookup problem, try clearing DNS cache on Windows.
More Chrome tips
About the author

Alex David Du
I’m Alex. I’m 28, born in Brazil, studied computer science, and writing is how I communicate best. I cover gaming, tech, simple ways to make money online, and other things I find interesting. I also love coding and building projects that bring ideas to life.
- Languages
- Portuguese, English
- Work Mode
- Freelancer - Remote
- Country
- Brazil
- hello@byalexdavid.com