Migration

An EditThisCookie alternative that still works in Chrome

EditThisCookie was a Manifest V2 extension, and Chrome has retired that platform. CookieMan is a free, open-source Manifest V3 cookie editor built for the same job — and it reads the JSON exports you already have.

Install the MV3 replacement Compare features
Manifest V3 Imports old JSON exports No network code
CookieMan popup listing cookies for a site, with search, add, import and export controls.

What actually happened to Manifest V2

Chrome extensions used to be built on Manifest V2, which allowed long-lived background pages and remotely-loaded code. Manifest V3 replaced it with service workers and a tighter security model, and Google phased out the old platform: from 2024 onwards Chrome began disabling Manifest V2 extensions, and they are no longer distributed through the Chrome Web Store.

For cookie tooling this hit hard, because the category was full of long-standing V2 extensions. If your cookie editor vanished from the toolbar, or the Web Store page returned nothing, that is the reason — not your profile.

When a well-known extension name disappears, look-alikes appear in its place. Before installing any cookie tool, check three things: it declares Manifest V3, its permission list has a justification for each entry, and its source is public. Those checks apply to this extension as much as to anything else — the code is on GitHub.
Feature by feature

What you used, and where it is now

Honest mapping, including the two things this extension deliberately does not do.

What EditThisCookie did CookieMan Notes
List every cookie for the current site Yes Live list, updated as cookies change
Edit name, value, domain, path, expiry Yes One form, applied in a single write
Toggle Secure, HttpOnly, SameSite Yes Plus host-only and partitioned (CHIPS)
Add a cookie by hand Yes + Add, with the same field set
Delete one cookie or all of them Yes Per row, or clear the whole domain
Search / filter cookies Yes Filters by name, value or domain as you type
Import / export JSON Yes Same JSON array shape, plus cookies.txt, header, Set-Cookie and Base64
Protect (lock) a cookie against changes Not implemented Open an issue if you relied on it
Cookie blocking / filtering rules Not implemented Out of scope — this is an editor, not a blocker
Three steps

Bringing your cookies across

  1. 1 Install CookieMan (about two minutes)
  2. 2 Open the site those cookies belong to
  3. 3 Import → paste your old JSON export → preview → Apply

The JSON array EditThisCookie produced uses the same field names this parser expects, so no conversion step is needed. To feed curl or yt-dlp instead, convert that JSON to Netscape on EditThisCookie JSON to cookies.txt. Coming from Cookie-Editor rather than EditThisCookie? See the Cookie-Editor alternative. If your file came from somewhere else — a cookies.txt from curl, a Cookie: header, a Base64 blob — paste it anyway: the format is detected, or run it through the online converter first.

Import panel with pasted cookie data, the detected format and a preview before applying.

Migration questions

Why did EditThisCookie stop working?
It was built on Manifest V2. Chrome has been phasing that platform out since 2024, and Manifest V2 extensions no longer run in current Chrome or ship through the Chrome Web Store. The extension itself was not broken — the platform underneath it was withdrawn.
Is CookieMan a Manifest V3 extension?
Yes. Version 1.1.0 uses Manifest V3 with a service worker background script, so it is not affected by the Manifest V2 shutdown.
Can I import my old EditThisCookie JSON export?
Yes. EditThisCookie exported a JSON array of cookie objects — the same shape this extension reads, including expirationDate, sameSite, hostOnly and httpOnly. Paste the file into Import; the format is detected automatically.
Does it need the same broad permissions?
It needs host access, because Chrome scopes the cookies API by host and there is no way to read a site's cookies without it. What it does not have is any network code: no fetch, no analytics, no remote config. The permission rationale lists every permission and why it exists.
Is it free and open source?
Yes — MIT-licensed, and the source is on GitHub. There is no account, no paid tier and no telemetry.
What about other cookie extensions?
Several exist and some are good. The checklist that matters is the same for all of them: Manifest V3, a permission list you can justify, source you can read, and no server in the data path. Apply it to this one too.

Pick up where EditThisCookie left off

Manifest V3, the same JSON format, and six ways to move cookies in and out.

Install CookieMan Open the converter

Free and MIT-licensed · Chrome, Edge and other Chromium browsers · Nothing leaves your machine