I want to clear the cache for a specific domain name in Chrome. Is there an extension or other method that I can use to do this?

  • 2
    The problem with this is that it is not as simple to clear the cache as you would think. When a browser caches files, it does so based on its URL. The complication is that many sites share common files like Google API scripts, Gravatar icons, etc. How would you go about clearing the cache for only a specific site? Should the common files it loads be deleted as well (and thus partially clearing the cache for other sites)? Or should they be left intact? (probably the most “correct” solution). – Synetech Aug 7 '13 at 1:12
  • 3
    Honestly, none of these answers really "answer" the question for me. These are developer answers. The root question is how a regular person would do this. It would be unreasonable to ask a non-developer to do these things. – Will Strohl Apr 21 '14 at 14:46
  • It's times like these when I switch back to Firefox for a day. – User Nov 8 '14 at 2:02
  • 2
    No one has really answered this question about how to clear cache for a specific domain – DiverseAndRemote.com Aug 26 '15 at 14:43
  • Since F12 developer tools is built into Chrome, using them is open to everyone, not just "Developers" for clearing specific items. – Fiasco Labs Feb 17 '16 at 2:33

UPDATE: As of Chrome version 52.0.2743.116 m, you can perform the following steps:

F12 > Chrome Developer Tools > Application tab > Clear storage in left tree > Select the data items to clear, then click Clear site data.

This may be a quicker/simpler way:

  • Press F12 to open Chrome Developer Tools (will pop up from bottom)
  • Click settings "gear" icon in top-right corner
  • Under General check Disable cache
  • Reload page and re-enable caching by un-checking this box
| improve this answer | |
  • 7
    Thanks, this actually works unlike the other answers which confuse cache and cookies ;-) – Peter Jenkins Dec 3 '12 at 13:58
  • 3
    But does it actually clear the cache for the page or just load it without using the cache? That is, if you open the cache directory, are any files related to that page gone after you reload? – Synetech Aug 7 '13 at 1:10
  • 3
    That's a pretty manual way of doing it and can get annoying if you have to do it multiple times. Fortunately there's an easier and faster way: superuser.com/a/598260/83619 – Tom Auger Jan 30 '14 at 17:52
  • 3
    Currently Chrome Developer Tools seems to disable cache only while DevTools is open without actually clearing it. – Jaak Kütt Feb 21 '14 at 15:26
  • 5
    alt ⌥ + cmd ⌘ + i on Mac to open Chrome Developer Tools – Yves M. Mar 4 '15 at 16:23

After opening up the developer tools (usually by pressing F12) Click + Hold on the "Reload Page" button. From the popup list, choose "Empty Cache and Hard Reload".

Not sure this clears the cache for the entire domain. But probably satisfies 90% of the use cases of people that visit this SE question.

Note: In some cases this will NOT open the popup list. This is because the page isn't cached at that time, so the menu is not invoked.

| improve this answer | |
  • 3
    Doesn't seem to work on mac. – Benjamin Crouzier May 22 '13 at 7:27
  • 4
    Try having the Developer Toolbar open first - hit F12 (or CMD+SHIFT+C for Console). I haven't tested on a Mac. – Tom Auger May 22 '13 at 15:16
  • thanks @Hashbrown for the edit. I should have amended my answer. – Tom Auger Aug 14 '13 at 18:59
  • no worries. this solution is just faster than the selected answer, and less drastic than just disabling the cache altogether. I feel this needs to be up the top, and the only way it'll get upvotes is if people test it and it works for them – Hashbrown Aug 14 '13 at 23:21
  • 1
    Use right-click on GNU/Linux to open the pop-up menu instead of a long click. – z0r Mar 2 '15 at 2:32

Here's how to delete Chrome's cookies selectively by domain or subdomain:

  • go to chrome://settings/content/cookies
  • type the domain name in the search box
  • click delete

More details here:


This can't however select cookies by web folders, e.g. www.domain.com/folder1.

| improve this answer | |
  • 2
    Welcome to Super User! It would be nice to include the essential parts of the answer here, and provide the link only for future reference. – slhck Jun 26 '11 at 13:11
  • 41
    The question was about clearing the cache, but you answered how to clear cookies. – Daniel Serodio Nov 28 '12 at 12:28
  • Found cache also from within the same details tab. – Jaak Kütt Feb 21 '14 at 15:25
  • Just to add to the confusion - this worked for me for something that I'm pretty sure is "cache" AND the chrome settings include something called "local storage" so I believe that the term "browser cache" may be too general. My point is that this answer worked for me. – ssaltman Dec 1 '15 at 2:52
  • 1
    For Chrome v65 to clear COOKIES, go to Settings > Advanced > Content settings > Cookies > See all cookies and site data > use "search cookies" field to find website and then delete that cookie – Lars Nordin Apr 12 '18 at 18:58
  1. Press control shift i (or command shift i on OS X) to open Dev Tools.
  2. Right-click the reload button next to the address bar.
  3. Choose: "Empty Cache and Hard Reload".
| improve this answer | |

To delete all data (cache + cookies) for all subdomains of a domain:

  1. Go to chrome://settings/siteData
  2. Type domain name in search box (not the one at the top, the small search box top right)
  3. Either:
    1. Click the trash icon button for each result
    2. Click 'Remove All Shown' button

This will delete all site data for those sites, including cookies and cache.

Nice thing about this technique is that you can easily clear site data for all subdomains of a domain.

The other way to access this setting screen is:
Three dots menu > Settings > Advanced (at bottom) > Content Settings (under Privacy and Security) > Cookies (yes, name is misleading) > See all cookies and site data

| improve this answer | |

In three steps:

  1. F12 (open developer tools)
  2. F1 (go to settings)
  3. Under Preferences / Network uncheck Disable cache (while DevTools is open)

Note that you can un-dock the DevTools if you would rather keep them as a separate window while open.

| improve this answer | |
  • This one is working well if you need to refresh external assets such as js or css – RafaSashi Feb 20 '18 at 4:47
Wrench -> Preferences -> Under the Hood -> 
Use DNS pre-fetching to improve page load performance

Disable it - thus dumping the whole application cache - reload the affected page - and then re-enable. If this happens often or doesn't clear the issue, some cache upstream from chrome is the problem and you should probably leave chrome's disabled.

Selective invalidation of an application layer cache (which is done strictly for application speed) since chrome has "no business" taking over for the system is might be an answer to some issue, but it isn't a very good answer.

(Lest you get huffy about my "no business" statement, I use pre-fetching myself as I like the zippiness, proper or not)

| improve this answer | |
  • 2
    Despite your parenthetical objections and the correctness of your solution, I'm huffy anyway. – Blomkvist May 4 '11 at 12:39
  • This answer is incorrect. Disabling DNS prefetching does not clear Chrome's HTTP cache. – duskwuff -inactive- Jan 20 '19 at 5:47

Deleting the history entries will work in many cases: (Mac)

  1. Cmd+Y (Open History)
  2. Search for your domain
  3. Check all the entries. Unfortunately there's no check all button at the moment. You don't have to click the checkboxes though, clicking on the time works too.
  4. Click Remove selected items
| improve this answer | |

Webpack was caching a previous project for me and I need parts of the caching to work so I couldn't use incognito. The top 3 solutions didn't work for my case. What did work and was quick enough to implement was clicking Resources tab in Developer tools, unfolding Cache Storage, and right-clicking to delete the cached data.

| improve this answer | |

Not the answer you're looking for? Browse other questions tagged or ask your own question.