EditThisCookie Is Gone: What Happened and What to Use Instead
The original EditThisCookie listing is an empty page now, and the replacements using its name are forks by other publishers. Here is the safe way forward.
If you have searched for EditThisCookie recently and landed on a blank Chrome Web Store page, you are not imagining it. The long-running cookie manager's original listing stopped working as a normal store page in September 2026, no name, no description, no install button. This page explains what that means, why the extensions now using the EditThisCookie name deserve caution, and how to switch to a maintained editor without losing your workflow.
What happened to EditThisCookie
EditThisCookie was a Manifest V2 extension, and Chrome spent 2024–2026 retiring that platform: MV2 extensions were disabled by default, then disabled entirely in Chrome 138 (July 2025), and remaining MV2 store listings were removed on 31 August 2026. Whether the listing's disappearance was the final step of that retirement or a separate delisting, the practical state is the same: the original extension cannot be installed from its store page, and an old bookmark or cached link will not bring it back.
About the listings now using the name
At the time of writing, extensions calling themselves “EditThisCookie (V3)” and “EditThisCookie (fork)” are live on the Chrome Web Store. They are separate projects by different publishers, using different extension IDs from the original. A familiar name is not a safety guarantee: any extension that can read your cookies can read your sessions, so an unknown fork asking for the same powerful permissions deserves real scrutiny before it goes anywhere near a signed-in browser.
The maintained alternative: Cookie-Editor
Cookie-Editor, the extension this whole site documents, is the straightforward replacement for most EditThisCookie users. It is open source, actively published for Chrome, Firefox, Edge, Safari and Opera by its original developer, and it covers the same core jobs: view, search, create, edit and delete cookies, with import and export in JSON, Netscape and header formats. The Chrome install guide takes about a minute, and the panel will feel familiar within one session.
Move your workflow over
- Before removing anything, export any cookie sets you rely on from your old setup, if it still opens, JSON is the most portable format.
- Install Cookie-Editor from the official listing for your browser (homepage downloads link to each store).
- Import the JSON export on the matching site and verify a couple of entries by name and value.
- Re-pin the icon and repeat your usual test once, a theme preference is a safe first check.
- Remove the dead or untrusted extension afterwards so only one editor holds cookie permissions.
What about other cookie editors?
The honest landscape: your browser's own DevTools (Application or Storage tab) can view and edit cookies with no extension at all, and for occasional use it may be all you need, see the comparison in How to View Cookies for a Website. Beyond that, the store shelves hold many small editors of varying age and provenance. Judge any of them the way you would judge a password manager: who publishes it, is the code public, how long has it been maintained, and does it ask for more permission than the job needs. An editor that fails those tests is not worth the risk to your sessions, however familiar its name sounds. Cookie-Editor passes them, which is why this site documents it, but the tests themselves matter more than the brand.
How the original disappeared
EditThisCookie was built for an older extension platform. Chrome announced the end of that platform (Manifest V2) years in advance, and extensions that were not rebuilt for the current platform were removed from the Web Store; by the end of August 2026 the old listings were gone, and the original EditThisCookie page had become an empty listing before disappearing from search results. Nothing about that story is a scandal: software built on a retired platform retires with it, unless its maintainers rebuild it, and the original's maintainers did not. Understanding this matters because it tells you no update, petition or setting will bring the original back.
Judging any replacement, a five-point check
- Publisher: Is there a named developer or organisation with a history, or a fresh account with one extension?
- Open code: Can you read the source? Cookie-Editor's is public, which is the strongest signal available for a tool with this much access.
- Permissions: Do the requested permissions match the job, cookies and site access, without unrelated extras?
- Maintenance: When was the last update, and does the listing answer its reviews?
- Footprint: How many users, over how long? A small new tool is not automatically bad, but it has earned less trust than a long-maintained one.
Run that check on any editor, including the one this site documents, and you will make a better decision than any 'top ten alternatives' list can make for you. The check also travels: it works for password managers, download helpers and every other extension category that asks for broad access to your browsing.
Moving your habits, not just your tool
Most EditThisCookie users were not attached to the name; they were attached to a workflow, a panel, a search box, a quick edit before a reload. That workflow survives the tool. Cookie Editor's panel covers the same ground, view, edit, create, delete, import, export, with the same keyboard-friendly list, so the honest adjustment is an afternoon of small unfamiliarities rather than a new skill. If your old workflow used EditThisCookie's import from a file or its cookie search dozens of times a day, spend ten minutes repeating those two actions in the new panel on a test page, and the migration is done.
Frequently Asked Questions
Are the EditThisCookie forks safe?
They are published by other people, not by the original developer. Judge them as you would any new extension with cookie access: publisher history, reviews, open code. This site does not recommend them.
Will Cookie-Editor read my EditThisCookie exports?
Cookie-Editor imports JSON exports, and EditThisCookie's JSON format is the common interchange format, import on the matching site and verify the entries, as in the steps above. The import and export guide covers formats in detail.


