Using Cookie Editor Cookie Editor guide

How to Create and Delete Cookies With Cookie Editor

Add a test cookie from scratch, delete one cookie or a whole site's set, and know exactly what each action does.

Illustration of adding a new cookie and deleting an unwanted cookie in a browser panel

Creating and deleting are the two ends of cookie management. Creating is how testers plant a known preference before a page loads; deleting is how you remove one site's cookies without the nuclear option of clearing your entire browser. Cookie Editor does both from the same panel, here is how to use each safely.

  1. Open the target site first

    Cookies belong to a domain, so load the site the cookie is for, then open Cookie Editor.

  2. Choose the create / add control

    Use the panel's add (plus) control to start a blank cookie for the current site.

  3. Fill in name and value

    Give it a name you will recognise, such as demo_theme, and a simple value such as light. Avoid spaces in names.

  4. Check domain and path

    The panel pre-fills the current domain and path /. Leave both unless you are deliberately testing a sub-path.

  5. Set an expiry if it must survive a restart

    A cookie with no expiry is a session cookie and vanishes when the browser closes. Set a future date if your test needs it to persist.

  6. Save and verify

    Save, then search the list for your new name. Reload the page and confirm the entry is still there.

To delete one cookie, expand its entry in the panel and use the delete control, then reload the page to see the effect. To remove everything a site has stored, use the panel's delete-all / clear option for the current site: every cookie for that domain goes at once, which signs you out of that site and resets its preferences, but leaves other sites untouched. Compare that with the browser's own site-data clearing in Edit, Delete or Clear?

What deletion cannot undo

  • Deleting a cookie does not delete your account or data on the site's server, it only removes your browser's local copy.
  • If the site sets the cookie again on the next visit (many do for defaults), the entry reappears with a fresh value. That is the site behaving normally, not a failed deletion.
  • Deleting a session cookie ends that sign-in session in this browser. Expect to log in again.
  • Other browsers and profiles keep their own copies, deletion here affects only this browser profile.

Which cookies are safe to delete?

A practical cleanup rule: preferences and consent cookies are always safe to delete (the site re-asks or resets them), analytics-style IDs are safe too (the site issues a fresh one), and anything whose name suggests a session, token, auth or checkout should be treated as “deleting this signs me out or empties a basket”. If you cannot tell what a cookie does from its name, delete it in a test profile first, or export the set before deleting so you can restore it. The point of a per-cookie tool is that you never have to gamble: one deletion, one reload, one observation.

Cleanup confidence guide
Cookie name looks likeDeleting it usually meansSafe to try?
theme, lang, region, consent, prefsThat preference resets to the defaultYes
_ga, analytics, visitor, uidThe site treats you as a new visitor next timeYes
cart, basket, checkoutThe basket may emptyOnly if the basket does not matter
session, token, auth, loginYou are signed out in this browserOnly when you mean to sign out

Give every cookie you create a name that announces itself, such as test_theme or qa_banner, and put the date or your initials in the value if the test lasts more than a day. Future you, returning to a list of forty cookies, will not remember which innocent-looking entry was a test and which one the site needs. A clear name also protects other people: if a colleague or a family member opens the same browser, a name like test_ makes it obvious the entry is safe to remove, while a name that imitates a real setting invites confusion.

Deleting a whole site's set, carefully

Sometimes the right move is to remove every cookie for one site, a corrupt state, a stuck loop, a consent choice you want to re-test from zero. Do it deliberately: export the set first if there is anything you might want back, then delete the site's cookies, then reload and watch what the site rebuilds. A healthy site recreates its defaults and asks for consent again; anything that does not come back was state you were carrying, and noting what changed is the fastest diagnosis of what the site was remembering about you.

Create or delete?
SituationBetter moveWhy
Testing one preference stateCreate or edit one cookieSmallest change, easiest to undo
A cookie is corrupt or stuckDelete that one cookieThe site rebuilds a clean default
Consent flow needs a fresh runDelete the site's whole setReturns the site to first-visit state
Learning how the tool worksCreate a named test cookieZero risk to real settings

Recovering from a deletion you regret

It happens to everyone once: you delete a cookie and immediately realise it held something you wanted, a carefully built basket, a game's progress, a preference you cannot remember choosing. Be honest about the recovery options, because they are thin. If you exported the set beforehand, import it and the cookie returns exactly. If the browser is still open and the site has not been revisited, there is no undo button to reach for; the record is gone. Signing in again restores account-held state, and preferences can be re-chosen in seconds. The lesson is the one threaded through this whole category: export before you delete anything you cannot trivially rebuild, and deletions stop being scary.

Frequently Asked Questions

Can I delete cookies for a site I am not on?

Cookie Editor works on the active tab's site. Open the site first, or use your browser's site-data settings, which list every site.

Is there an undo after deleting?

Not inside the panel. If the set mattered, export a backup before deleting (JSON export takes seconds) and re-import it to restore.