Troubleshooting Cookie Editor guide

Cookie Edits Not Saving? Why Changes Revert After Reload

You save the new value, reload, and the old one is back. Here is how to tell whether the site rewrote it, the scope was wrong, or the value was rejected.

Illustration of a cookie value flipping back after a page reload arrow loops

You changed a cookie's value, saved it, reloaded, and the old value is back, as if you never edited anything. This is the most common Cookie Editor frustration, and it is almost never the extension failing to save. Something put the old value back, or your edit landed on a cookie the page does not read. The checks below separate the causes in the order you should test them.

What is happening: Many sites write their preference cookies fresh on every page load, from a server-side setting, an account profile, or a default in their code. Your edit was saved, then overwritten a second later. How to confirm: Note the value and expiry before reloading, then compare after. If the value reverted *and* the expiry moved to a fresh time, the site rewrote it. What to do: Change the setting through the site's own controls (that updates the source the rewrite comes from). If you are testing, edit and then verify *before* reloading, or test on a static page the site does not re-render.

What is happening: Two cookies share the name but differ in domain or path. You edited the one for / while the page reads the one for /account (or the subdomain's copy). How to confirm: In the panel, list every entry with that name and compare domain and path against the page URL you are testing. What to do: Edit the entry whose domain and path match the page, and re-test. Scope rules are explained in Cookie Fields Explained.

Cause 3: The site rejected your value's format

What is happening: The site expects a value in a specific format, true rather than 1, a language code it recognises, a number in range. On the next load it finds an invalid value and resets it to the default. How to confirm: Use the site's own control to set the preference, then read the cookie to learn the exact format it uses. What to do: Re-edit using a value in that same format, changing only the part you intend to test.

What is happening: Some cookies are re-sent by the server with each page response (look for values that also reset when you simply navigate). A browser-side edit cannot win against a server that always sends its own copy. How to confirm: Delete the cookie entirely and reload, if it returns immediately with the same value, the server is setting it. What to do: Accept that this cookie is server-controlled; for testing, use your own test page or a staging environment where you control the responses.

A clean test procedure

  1. Export a backup of the site's cookies so you can restore the starting state.
  2. Record the target cookie's name, value, domain, path and expiry.
  3. Edit the value only, save, and check the panel again before reloading, the new value should be listed.
  4. Reload once and compare all five fields, not just the value.
  5. Use the table of causes above to match what changed: value+expiry moved (rewrite), nothing moved but behaviour unchanged (scope), value snapped to a default (format), cookie returned after deletion (server-set).

The two-minute diagnosis

Before changing strategy, run this exact sequence once. Open the page, open Cookie Editor, and note the cookie's name, value, domain, path and expiry in writing. Make your edit and save. Reload the page fully. Reopen the panel and compare all five fields, not just the value. Then close and reopen the browser and compare again. The step where the value changes back tells you who rewrote it: a change on reload points at the page or its server; a change only after a browser restart points at expiry, profile or browser cleanup settings. Diagnosis first, fix second, every time.

The server always wins, and why that is fine

Some state genuinely lives on the site's servers, attached to your account, and the cookie is just a key that points at it. Editing the key does not edit the record. You see this most with account preferences: change the value, reload, and the site politely writes back the value from your account. That is not Cookie Editor failing; it is the architecture showing itself. For testing, the correct move is to change the preference through the account's own settings, or to test signed out, where the cookie is the only memory the site has of you.

Where did the value change back?
Changed back whenLikely writerNext step
Immediately on reloadThe page's own code or its serverCheck whether the state is account-held
After the browser restartedExpiry, or clear-on-exit settingsRead the expiry; check browser cleanup settings
Only on one part of the siteA second cookie with the same nameCompare domain and path on both entries
Never, but the page ignores itThe site stores the setting elsewhereCheck local storage via DevTools

Frequently Asked Questions

Does a reverted edit mean Cookie Editor is broken?

Almost never. In the large majority of cases the site rewrote the cookie or a different same-name cookie is in play. The pre-reload check in step 3 proves the extension saved your edit.

Why does my edit work on one page of the site but not another?

Path scope. The working page and the failing page sit under different paths, and each reads its own cookie. Compare the path field on both pages.

Can I stop a site from rewriting a cookie?

Not from the browser side in any reliable way, the site's code runs on every load. Change the underlying setting, or test on infrastructure you control.