Edit, Delete or Clear? Choosing the Right Cookie Fix
Editing changes one value, deleting removes one site's cookies, clearing wipes site data in the browser. Picking the right size of fix saves your other sign-ins.
When a site misbehaves, the instinct is to “clear cookies”, but that phrase covers three very different operations, and picking the biggest one logs you out of things you never meant to touch. Work from the smallest fix upwards: edit a value when you know the setting, delete one site's cookies when that site's state is suspect, and reserve the browser's full site-data clearing for when the targeted tools have failed.
The three operations compared
| Operation | What it changes | What it costs you | Reach for it when |
|---|---|---|---|
| Edit one cookie (Cookie Editor) | One value, e.g. theme back to light | Nothing else changes | You know which preference is wrong and want to correct or test it |
| Delete one cookie (Cookie Editor) | That single record is removed | The site recreates a default, or that one feature resets | One cookie is corrupt, stuck, or you are testing how the site behaves without it |
| Delete all cookies for one site (Cookie Editor) | Every cookie for that domain | You are signed out of that site; its preferences reset | A site is in a broken state and targeted fixes failed |
| Clear site data (browser settings) | Cookies plus cache, local storage and other site data for one site, or all sites | Sign-outs and resets for every site you include | The problem involves stored data beyond cookies, or you are wiping a device |
A decision path that works
- Name the symptom precisely: wrong preference, stuck sign-in, page error, or “the site just acts weird”.
- Wrong preference → edit the value (or change it in the site's own settings). Stuck single feature → delete that one cookie and reload.
- Site-wide weirdness → export a backup, then delete all of that site's cookies in Cookie Editor and reload.
- Still broken → clear the site's data in browser settings, which also removes local storage and cache that Cookie Editor does not manage.
- Only if problems span many sites should you consider clearing all sites' data, and expect to sign in everywhere again.
What Cookie Editor cannot clear
Cookie Editor manages cookies. Sites also store data in local storage, IndexedDB and the cache, which survive a cookie-only cleanup and can recreate the very behaviour you were trying to reset. If a full cookie deletion changed nothing, that other storage is the prime suspect, your browser's “site data” or “clear browsing data” screens are the tools for it, per site where possible.
Three worked examples
- “The site forgot my language every visit.” The language cookie turned out to be a session cookie because of a site bug. Smallest fix first: nothing to edit, the diagnosis itself (via the expiry field) is the bug report. Clearing everything would have hidden the evidence.
- “I am stuck in a redirect loop after logging in.” Classic corrupt session state. Deleting just that site's cookies in Cookie Editor, not the browser's whole history, fixed the loop and kept every other sign-in intact.
- “The banner will not stop asking about cookies.” The consent cookie was being blocked by an over-strict browser setting, so the site never saw the recorded answer. Editing could not help; the fix was the browser's site-data permission for that one site.
Three scenarios, three right answers
The preference that will not change. A site's theme control seems broken; whatever you pick, the old theme returns. The cookie holds a stale value the page keeps trusting. Edit the one value, or delete the one cookie so the site writes a fresh default. Clearing everything would work too, the way demolishing a house fixes a door, and would cost you every other sign-in for no benefit.
The consent banner loop. A site asks about cookies on every visit, as if it never heard your answer. Its consent cookie is being blocked, expired instantly, or written for the wrong domain. Deleting will not help; the fix is the browser's site-data permission for that site, or accepting that a strict setting you chose has this side effect. Diagnosis before deletion, again.
The borrowed computer. You signed in on a shared machine and want every trace gone. This is the one case where the widest tool is right: use the browser's own 'clear cookies and site data' for the period you used it, because your goal is not fixing one site's state, it is leaving nothing behind. Match the size of the tool to the size of the job; that sentence is the whole article in miniature.
What clearing everything actually costs
People underestimate the clear-all button because its cost is spread over the following week: every site signed out, every preference reset, every consent banner back, every 'this device is trusted' check to redo, some with two-factor prompts. None of that is dangerous, and sometimes it is exactly what a situation needs, but as a first response to one misbehaving site it is wildly oversized. Start with the smallest tool that can work, Cookie Editor's single deletion, and escalate only when the evidence says the problem is bigger than one cookie.
Frequently Asked Questions
Why did the site still remember me after I deleted its cookies?
It recognised you another way: local storage, a signed-in browser profile sync, or simply because you signed in again and it set fresh cookies. Check the site's entry in your browser's site-data screen.
Is it bad to clear all cookies regularly?
It is mostly inconvenient rather than harmful: you will re-do consent banners, preferences and sign-ins constantly. Targeted, per-site fixes give you the same control without the churn.


