DEV Community

Anton P
Anton P

Posted on Originally published at tabvitals.com AI-assisted

How to Clear Cache and Cookies for One Website in Chrome Without Resetting Everything

When one website breaks in Chrome, “clear your cache and cookies” is a common support answer. It often works, but the browser-wide version is unnecessarily disruptive: it can sign you out of unrelated tools, remove useful site state, and turn a one-site problem into an all-browser cleanup.

The safer first move is to target only the affected website.

Start with the smallest fix

If the page is showing stale CSS, an old image, or an outdated script, try a hard reload first:

  • Windows/Linux: Ctrl + Shift + R
  • macOS: Cmd + Shift + R

A hard reload asks Chrome to fetch the page resources again. It usually leaves login cookies alone.

If the page is still broken, move to a site-data reset.

Clear data for one site manually

The shortest current-Chrome route is:

  1. Open the affected website.
  2. Select the site-controls icon beside the address.
  3. Open the site settings or on-device site data controls.
  4. Remove data for that domain only.
  5. Reload and sign in again if necessary.

You can also open Chrome Settings, go to Privacy and security, open the site-data list, search for the exact domain, and remove that one result.

Chrome changes labels from time to time, but the important rule is stable: select the domain. Do not use the browser-wide Delete browsing data flow for a one-site problem.

What a site-data reset can remove

Depending on the route you use, Chrome can remove the selected website’s:

  • cached assets
  • cookies and session state
  • local storage and IndexedDB
  • service-worker data
  • saved permissions

Unrelated domains stay outside the operation.

Will this sign me out?

It may sign you out of the website you are repairing. That site’s authentication cookie can be part of the deleted data.

It should not sign you out of unrelated websites when you target only the affected domain. Be careful with services that share a parent domain or a federated login.

If the site works in Incognito but not normal Chrome

That difference is useful evidence, not a diagnosis by itself. Incognito starts with a cleaner local state and usually runs a different extension set. The cause could be:

  • corrupted cookies or local storage
  • stale cached assets
  • a service worker
  • an extension conflict
  • a saved permission
  • a server, DNS, redirect, or CDN issue that appears differently by session

Clearing the selected site’s data tests the local-state branch. If it does not help, test extensions next and then separate browser-side issues from server-side ones.

A one-click option

I built two current-site actions into TabVitals because Chrome’s manual route is easy to forget and its labels move between versions:

  • Fix this site for the lighter first attempt
  • Full Reset for a deeper cleanup when the first step fails

TabVitals selects the active site automatically and keeps unrelated browser sessions outside the target. Full Reset can still sign you out of the selected site.

Disclosure: TabVitals is my product. The beta is currently free and available through the official Chrome Web Store.

When not to reset a site

Do not run a deep reset until you have saved unsent forms and confirmed that you can sign in again. A local reset is also the wrong tool when the same failure occurs on several devices or the website itself is down.

Quick decision tree

  1. Stale page only? Try a hard reload.
  2. One site broken in the normal profile? Clear that site’s data.
  3. Works only in Incognito? Test site data, then extensions and permissions.
  4. Broken everywhere? Check the service, network, DNS, and server/CDN state.
  5. Need the same one-site repair repeatedly? Consider a current-site tool, but verify its permissions and privacy behavior first.

FAQ

Can I clear only one site without deleting Chrome history?

Yes. Use the site controls or search for the domain in Chrome’s site-data list.

Will other accounts stay signed in?

They remain outside a correctly targeted domain reset. The affected site may sign out.

Does clearing local data purge a CDN cache?

No. Browser data and server/CDN cache are different layers.

Is a Chrome extension necessary?

No. The manual method works. A trustworthy extension can reduce the repeated steps, but it should explain its permissions and target only the selected site.


Originally published in the TabVitals guide. TabVitals is my product.

Top comments (0)