The latest articles on DEV Community by Anton P (@antonp_tabvitals). https://dev.to/antonp_tabvitals https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4121075%2F9eb483f3-d4c6-4646-b4b2-171e4dcea666.png https://dev.to/antonp_tabvitals en Anton P Fri, 11 Sep 2026 14:19:32 +0000 https://dev.to/antonp_tabvitals/how-to-clear-cache-and-cookies-for-one-website-in-chrome-without-resetting-everything-49bh https://dev.to/antonp_tabvitals/how-to-clear-cache-and-cookies-for-one-website-in-chrome-without-resetting-everything-49bh <p>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.</p> <p>The safer first move is to target only the affected website.</p> <h2> Start with the smallest fix </h2> <p>If the page is showing stale CSS, an old image, or an outdated script, try a hard reload first:</p> <ul> <li> <strong>Windows/Linux:</strong> <code>Ctrl + Shift + R</code> </li> <li> <strong>macOS:</strong> <code>Cmd + Shift + R</code> </li> </ul> <p>A hard reload asks Chrome to fetch the page resources again. It usually leaves login cookies alone.</p> <p>If the page is still broken, move to a site-data reset.</p> <h2> Clear data for one site manually </h2> <p>The shortest current-Chrome route is:</p> <ol> <li>Open the affected website.</li> <li>Select the site-controls icon beside the address.</li> <li>Open the site settings or on-device site data controls.</li> <li>Remove data for that domain only.</li> <li>Reload and sign in again if necessary.</li> </ol> <p>You can also open Chrome Settings, go to <strong>Privacy and security</strong>, open the site-data list, search for the exact domain, and remove that one result.</p> <p>Chrome changes labels from time to time, but the important rule is stable: select the domain. Do not use the browser-wide <strong>Delete browsing data</strong> flow for a one-site problem.</p> <h2> What a site-data reset can remove </h2> <p>Depending on the route you use, Chrome can remove the selected website’s:</p> <ul> <li>cached assets</li> <li>cookies and session state</li> <li>local storage and IndexedDB</li> <li>service-worker data</li> <li>saved permissions</li> </ul> <p>Unrelated domains stay outside the operation.</p> <h2> Will this sign me out? </h2> <p>It may sign you out of the website you are repairing. That site’s authentication cookie can be part of the deleted data.</p> <p>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.</p> <h2> If the site works in Incognito but not normal Chrome </h2> <p>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:</p> <ul> <li>corrupted cookies or local storage</li> <li>stale cached assets</li> <li>a service worker</li> <li>an extension conflict</li> <li>a saved permission</li> <li>a server, DNS, redirect, or CDN issue that appears differently by session</li> </ul> <p>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.</p> <h2> A one-click option </h2> <p>I built two current-site actions into TabVitals because Chrome’s manual route is easy to forget and its labels move between versions:</p> <ul> <li> <strong>Fix this site</strong> for the lighter first attempt</li> <li> <strong>Full Reset</strong> for a deeper cleanup when the first step fails</li> </ul> <p>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.</p> <blockquote> <p><strong>Disclosure:</strong> TabVitals is my product. The beta is currently free and available through the <a href="https://chromewebstore.google.com/detail/ljimhionelboehpfhipedoepaiiamdof" rel="noopener noreferrer">official Chrome Web Store</a>.</p> </blockquote> <h2> When not to reset a site </h2> <p>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.</p> <h2> Quick decision tree </h2> <ol> <li> <strong>Stale page only?</strong> Try a hard reload.</li> <li> <strong>One site broken in the normal profile?</strong> Clear that site’s data.</li> <li> <strong>Works only in Incognito?</strong> Test site data, then extensions and permissions.</li> <li> <strong>Broken everywhere?</strong> Check the service, network, DNS, and server/CDN state.</li> <li> <strong>Need the same one-site repair repeatedly?</strong> Consider a current-site tool, but verify its permissions and privacy behavior first.</li> </ol> <h2> FAQ </h2> <h3> Can I clear only one site without deleting Chrome history? </h3> <p>Yes. Use the site controls or search for the domain in Chrome’s site-data list.</p> <h3> Will other accounts stay signed in? </h3> <p>They remain outside a correctly targeted domain reset. The affected site may sign out.</p> <h3> Does clearing local data purge a CDN cache? </h3> <p>No. Browser data and server/CDN cache are different layers.</p> <h3> Is a Chrome extension necessary? </h3> <p>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.</p> <p><em>Originally published in the <a href="https://tabvitals.com/clear-cache-for-one-website" rel="noopener noreferrer">TabVitals guide</a>. TabVitals is my product.</em></p> webdev productivity tutorial chromeextension