EditThisCookie Extension: Its 2026 Status and Safer Alternatives

If you searched for EditThisCookie recently and landed on a blank Chrome Web Store page, you’re not imagining it. The extension that a lot of developers, QA testers, and SEO folks relied on for years to view, edit, and delete cookies without opening DevTools appears to be gone from the store as of September 2026. This post covers exactly what’s live under that name now, what Cookie-Editor is and how it differs, how to install a cookie editor extension safely in Chrome, Firefox, Edge, Safari, and Opera, and the real risk you’re taking on any time you let an extension touch your cookies. It also covers where a cookie editor’s job ends and where something like BelayTab picks up — because editing cookies and losing the tabs you were testing in are two very different problems.

What Is EditThisCookie, and Is It Still Live on the Chrome Web Store?

EditThisCookie was a Chrome extension for viewing and modifying browser cookies directly from a toolbar panel, and its original listing is not functioning as a normal store page as of 26 September 2026. Instead of a name, description, icon, and install button, the canonical listing for the original extension ID resolves to what’s effectively an empty page — no content to load, no way to install it. That’s a distinct pattern from a listing that’s simply old or unmaintained; a live-but-neglected extension still shows its name and description, it just hasn’t been updated in a while. This one shows nothing.

Here’s the quick version for anyone trying to figure out what to actually install right now:

If your goal is “a cookie editor chrome extension search extension that works today,” the practical answer is either one of the two forks below or Cookie-Editor, not the original listing. We’ll walk through the difference so you’re not installing something blind just because it has a familiar name.

What Happened to the Original EditThisCookie Extension?

Nobody outside the original developer has published a clear explanation, and the listing itself doesn’t say either. What we can confirm is the current state: the store’s own canonical reference for that extension ID returns no name, no description, no icon, and no install button, which is the pattern you see with a removed or delisted item rather than one that’s merely gone quiet.

There’s a separate piece of context worth knowing, even though it isn’t proof of cause. Chrome enforced a long deprecation of Manifest V2 extensions through 2024 and 2025, disabling them by default across all channels by March 31, 2025, and disabling them entirely with no re-enable option as of Chrome 138 in July 2025. Any Manifest V2 listings still sitting in the store were permanently removed on August 31, 2026. If the original EditThisCookie extension had never been rebuilt on Manifest V3, that removal date lines up with when its listing would have disappeared. That’s a plausible explanation, not a confirmed one — treat it as background, not as the official reason.

Whatever the cause, the practical takeaway is the same: don’t try to reinstall the original EditThisCookie from an old bookmark or a cached search result. If the live store page shows nothing, there’s nothing safe to add.

What Are EditThisCookie (V3) and EditThisCookie (Fork)?

They’re two separate, unofficial extensions that reuse the EditThisCookie name, and both are live on the Chrome Web Store as of this writing. “EditThisCookie (V3)” and “EditThisCookie (fork)” are published under different extension IDs from the original and from each other, and both declare Manifest V3 in their published manifests with a minimum Chrome version of 88. In other words, they were built (or rebuilt) to run under Chrome’s current extension platform, which is a reasonable sign they’re at least maintained enough to function.

What neither one is, is a continuation from the original developer. They’re community forks — someone took the idea (and often the visible name) and republished it independently. That’s common enough in the extension world; plenty of useful tools live on this way after an original project goes dark. But it changes what due diligence looks like. You’re trusting a different, often anonymous or pseudonymous maintainer, not the person whose code the reviews and the reputation originally built up.

If you specifically need “the” EditThisCookie back, one of these two forks is the closest thing available. If you’re open to a different tool entirely, Cookie-Editor is worth a closer look, and it comes with a clearer paper trail.

What Is Cookie-Editor, and How Does It Compare to EditThisCookie?

Cookie-Editor is a separate, open-source browser extension for viewing, creating, editing, and deleting cookies, not a fork of EditThisCookie. It’s live on the Chrome Web Store, built on Manifest V3, and its own site describes it as “a browser extension focused on productivity that helps you manage your cookies with the least amount of clicks possible.” The developer, Christophe Gagnier (who goes by Moustachauve), publishes the full source code on GitHub, which means anyone can inspect exactly what it does before installing it — something you can’t do with a closed-source extension no matter how familiar its name looks.

Feature for feature, it covers the same ground people used EditThisCookie for: view the full list of cookies on the current page, create a new one, edit an existing value, delete a single cookie or wipe them all, and import or export the set either as a file or through the clipboard. If your workflow with EditThisCookie was mostly “open panel, tweak a value, refresh,” Cookie-Editor’s stated feature set covers that directly.

The publisher’s own site is also specific about who it’s built for: web development, QA testing, and SEO work. That’s a narrower, more deliberate framing than a general-purpose “bypass any site” tool, and it matches how a serious cookie editor should be pitched. This is a debugging instrument, not a shortcut.

How Do I Install a Cookie Editor Extension in Chrome?

You install it the same way you install any Chrome extension: find the live listing, click Add to Chrome, and approve the permission request. That process hasn’t changed regardless of which cookie editor you pick, but a couple of steps are easy to skip when you’re in a hurry.

That last step is one people skip constantly. Leaving an extension on “all sites” by default is convenient, but a cookie editor with all-sites access can be invoked on anything you visit, including sites where you’d rather not have a cookie-editing tool active at all. Restricting it to “when you select the extension” costs you one extra click per use and buys you a meaningful reduction in exposure.

If you’d rather learn the general extension-management flow first (pinning, disabling, removing, Developer mode) our guide to adding extensions to Chrome and the broader Chrome Web Store guide both cover that in more depth than we can here.

Does Cookie-Editor Work on Firefox, Edge, Safari, and Opera?

Yes — Cookie-Editor’s own site lists support across all four, plus mobile coverage that a lot of desktop-only tools don’t bother with. That cross-browser reach is one of the clearer advantages it has over chasing down an EditThisCookie fork that may only ever target Chrome.

One nuance worth flagging for anyone deciding where to do their cookie testing: not every Chromium browser handles third-party extension stores the same way. Opera lets you install a Chrome Web Store CRX file directly with no extra helper step. Edge, by contrast, shows a dialog asking you to allow extensions from outside its own store before the install proceeds. Neither is wrong, they’re just different defaults, and it’s the kind of small friction that trips people up when they’re following instructions written for a different browser than the one they’re using.

How Do I View, Edit, and Delete Cookies With a Cookie Editor?

You open the extension on the tab you’re testing, and it shows every cookie set for that page in one panel. From there, the core actions map directly onto the feature list Cookie-Editor’s own site describes: view, create, edit, delete, and import/export.

A word on the import/export step specifically: it’s genuinely useful for QA and development, where you want to reproduce “user in state X” without manually logging in and clicking through a flow every time. It’s a very different thing, though, to import a cookie file that represents someone else’s active session. We’ll get into exactly why that matters in the next section, because it’s the single biggest risk a cookie editor extension introduces.

Who Actually Needs a Cookie Editor Extension?

Most people don’t need one day to day, and that’s a fair thing to say plainly. Cookie-Editor’s own site frames its use cases narrowly: web development, software QA testing, and SEO work — not general browsing, and not getting past paywalled or gated content, which is a common but misguided reason people go looking for these tools in the first place.

If your job involves any of the following, a cookie editor is a legitimate part of your toolkit:

• Testing authenticated states without logging in and out repeatedly. Editing a session cookie’s value or expiration lets you simulate different user states quickly during development.
• Debugging cookie-based bugs. Seeing exactly what a site sets, and when, is faster with a panel than digging through DevTools’ Application tab every time.
• SEO auditing. Some SEO checks involve verifying which cookies a site sets for tracking, consent, or personalization, and a cookie editor makes that visible at a glance.
• QA regression testing. Resetting to a known cookie state between test runs, without wiping the whole browser profile, saves real time across a testing cycle.

If none of that describes what you’re doing, you probably don’t need this class of extension installed at all — every extension you add is one more thing with access to something on your machine, and the fewer you run, the smaller your attack surface. That’s not a knock on cookie editors specifically; it’s just good extension hygiene, and it applies just as much to a VPN extension or a volume-boosting extension as it does here. Install for a reason, remove when the reason’s gone.

Are Cookie Editor Extensions Safe to Use?

They’re safe when installed from a verified, live listing and used on sites you trust, but they carry a real and specific risk that’s worth understanding rather than glossing over. Google’s own Chrome Help documentation defines cookies as files that websites use to keep you signed in and remember your preferences. That’s not a minor detail here. It’s the whole reason cookie editors exist, and it’s exactly why they need to be handled carefully.

A session cookie can be an active login. Because a cookie can hold your active session for a site, any extension that can read or export cookies can, in principle, read or export a currently active login. Only use a cookie editor on sites you control or are authorized to test, and never import or paste cookie values from someone else’s session.

Chrome’s documentation also distinguishes first-party cookies, set by the site you’re visiting, from third-party cookies, set by embedded content like ads or trackers. A cookie editor shows you both, which is useful for debugging but means the panel in front of you can contain more than you’d expect from a page that “looks” simple. And a practical side effect worth knowing before you start clicking Delete: Google’s help page notes that clearing cookies may sign you out of sites that remember you, and the same applies to editing a session cookie’s value directly. You can accidentally log yourself out mid-task.

None of this means avoid cookie editors. It means use them the way you’d use any tool that can see credentials-adjacent data: on your own accounts and test environments, not shared or copied around casually.

What Should I Check Before Installing Any Cookie Editor Extension?

Check that the listing is live, who publishes it, what permissions it asks for, and when it was last updated — in that order. This is the same checklist that applies to picking any extension, but it matters more here because the data in question is your login state.

Before you click Add to Chrome (or the equivalent for your browser), run through this:

1. Confirm the listing loads fully. A name, icon, description, and reviews should all be present. An empty or placeholder page, like the original EditThisCookie’s current listing, is a hard stop.
2. Look at who publishes it. Cookie-Editor’s listing and site are transparent about its developer and link to public source code on GitHub. That’s a higher bar than an anonymous fork with no attribution.
3. Read the permission dialog Chrome shows you. Chrome’s own Web Store documentation explains that this dialog exists precisely so you can see what’s being requested before you approve it; the warning “doesn’t mean the app is dangerous, just that it can be.”
4. Set site access deliberately, not by default. Restrict the extension to specific sites, or to “when you select the extension,” rather than leaving it enabled everywhere automatically.
5. Run Chrome’s Safety Check periodically. It can flag extensions that later turn out to be risky, even ones you installed with good judgement at the time.

This same checklist is worth applying beyond cookie editors specifically. Our guide on managing Chrome extensions covers the ongoing side of this — reviewing what’s installed, disabling things you no longer use, and understanding what each one can see. If you want the general safety framework for the whole browser rather than one extension at a time, our security guide is the better starting point.

One more thing this checklist doesn’t cover, because it’s a different kind of risk entirely: what happens to your open tabs while you’re deep in a cookie-testing session with a dozen windows open across staging environments. Editing cookies is a session-state problem. Losing your open tabs to a crash, an accidental window close, or Chrome eating memory mid-test is a completely separate problem, and it’s the one BelayTab is built for. It runs on Chrome, Edge, Brave, Opera, Vivaldi, Arc, Firefox, and Safari on Mac, saves a window as a named session in one click, and keeps automatic snapshots every five minutes and whenever a window closes — so the forty tabs from a QA pass survive even if the cookie test itself goes sideways. It’s free, needs no account, and never touches page content or cookies, which is a useful contrast to keep in mind: your cookie editor manages what a site remembers about you, and BelayTab manages what you remember to come back to.