How to Clear Cookies for One Site Only in Chrome and Edge (2026)
A test account you no longer need, a login stuck in a redirect loop, or a shared laptop where one shop should be forgotten — not the other fifty sites you rely on. Clearing everything is the wrong tool for all three.
Here are three ways to clear cookies for one site in Chrome and Edge: the built-in site settings, DevTools, and a cleaner with an explicit clean list. We also explain what else disappears when cookies go, so nothing important breaks.
Method 1: Chrome and Edge site settings
Both browsers keep a per-site list of stored data. It is the fastest no-install route:
- In Chrome, open
chrome://settings/content/all. In Edge, openedge://settings/siteData. - Search for the domain you want to forget.
- Open the entry and click the trash icon (Chrome: Delete; Edge: Delete).
- Confirm.
What it removes: cookies and site data for that origin. What it leaves behind: browsing history, the HTTP cache, and every other site. In many builds each subdomain is a separate entry, so shop.example.com and www.example.com may need clearing one by one.
The limitation is visibility. You cannot see how many cookies will go, you cannot schedule it, and you cannot tell the dialog to keep the last day of activity.
Method 2: The DevTools Application panel
If you want surgical control, open DevTools with F12, switch to the Application tab, and expand Storage:
- Cookies — pick the origin, then right-click and choose Clear to remove only that domain's cookies.
- Clear site data — removes cookies, local storage, session storage, IndexedDB, cache storage and service workers for the current origin.
This is precise and includes storage types the settings page hides. It is also easy to misuse: the button is one click away, there is no preview, and the HTTP cache still needs the browser-wide dialog. It is a developer tool, not a daily routine.
Method 3: An explicit clean list
VKT CleanMate flips the model. Instead of selecting what to delete after the fact, you keep a clean list of domains and the cleaner only touches those:
- Add a domain once. There is no cap on entries in the free tier.
- Press Clean now and a preview sheet opens first: which sites were found, how many history entries and cookies are in scope, which data types are active, and what retention window applies.
- Confirm, and the run is reported in a notification.
Domain rules are plain text, not regex: example.com also covers its subdomains, and a leading www. is stripped for you. Nine data types are separate switches, and the retention window can keep the last day, 3, 7 or 30 days, or everything.
One honest boundary: Chromium cannot limit history, downloads, form data or saved passwords to a single site. Those four are filtered only in full mode (a licence feature), and the interface says so. Targeted cleaning is for the data that really is per-domain — cookies, cache, local storage, IndexedDB and service workers.
What clearing cookies actually does
Cookies are small key-value records a site stores in your browser. They hold session tokens (your login), cart contents, language and consent choices. Delete them and the site treats you as a new visitor: you are signed out, the cart may empty, and consent banners return. Other sites are unaffected because cookies are scoped to a domain.
The cache is a different layer. It stores images, scripts and fonts so pages load faster. Clearing it does not sign you out; the next visit is just slower while the cache rebuilds. History is a local list of pages you visited — it is not sent to websites and clearing it does not change how any site behaves.
Two exceptions are worth knowing. Single sign-on providers live on their own domains, so clearing a site that relies on Google or Microsoft login may leave the provider cookie in place. And local storage or IndexedDB can hold unsaved drafts in web apps — clear those only when you know the app can rebuild them.
Which method should you use?
| Method | One-site scope | Preview | Scheduling | Technical level |
|---|---|---|---|---|
| Built-in site settings | Cookies and site data | No | No | Anyone |
| DevTools | Full site storage | No | No | Developer |
| VKT CleanMate | Cookies, cache, storage, workers | Yes, on manual runs | Five triggers | Anyone |
For a one-off logout, the built-in settings are enough. For a repeatable routine — clear these two sites every time the browser closes — a cleaner with a preview and a list is safer than remembering to do it by hand.
One site, one clean slate
Clearing everything because one login is stuck is like reinstalling your browser because one tab misbehaves. Pick the smallest scope that solves the problem: one origin, the data types that matter, and a preview so you know what leaves.
FAQ
Does clearing cookies for one site log me out of other sites?
No. Cookies are scoped per domain, so deleting one origin's cookies leaves other sites signed in. The exception is shared login providers: clearing a site that uses Google or Microsoft sign-in does not clear the provider's own cookie, and clearing the provider can affect every site that relies on it.
Can I clear the cache for just one site in Chrome?
The built-in Clear browsing data dialog is all-or-nothing for the HTTP cache. DevTools can clear a single origin's site storage, and a cleaner with a clean list can target the domains you choose. If the goal is a fresh copy of one site's files, DevTools is the precise tool.
Will clearing cookies delete my bookmarks or saved passwords?
No. Bookmarks and saved passwords are separate stores. Saved passwords are their own data type in Chromium and cannot be limited to a single site, so treat them as a full-mode operation and leave them off unless you really mean it.
Is it safe to let an extension clear my browsing data?
It can be, if the extension runs locally, previews the deletion before running, and asks only for the browsingData permission it needs. VKT CleanMate uploads nothing, shows the preview sheet on manual runs, and makes no network request unless you enter a licence key.
More guides in the VKT blog; questions to [email protected].
