3 min read

Cookie-Editor alternative that still exports six formats

Cookie-Editor lists and edits cookies for the current tab; it is not an official Chrome product, and neither is CookieMan. Use CookieMan when you need to convert that JSON into cookies.txt, a Cookie: header, Set-Cookie lines or Base64, or to apply the same file in another Chromium profile.

This page does not read Cookie-Editor's storage. Export JSON from that extension first, then paste it here or into CookieMan's Import panel.

Cookie-Editor alternativeCookie-Editor ChromeCookie-Editor JSON exportCookieMan
  1. 1
    Export JSON from Cookie-Editor

    Open Cookie-Editor on the target site and export the cookie list as a JSON array. The objects use name, value, domain, path, expirationDate, hostOnly, httpOnly, secure and sameSite.

  2. 2
    Paste into this converter

    Paste the export below. Detection treats it as a JSON array — the same shape EditThisCookie used. Set the output to JSON Array to keep every attribute, or Netscape if the next consumer is curl.

  3. 3
    Import in Chrome or feed a CLI

    In CookieMan, open the destination site, Import → paste → preview → Apply. For curl, switch output to Netscape and save as cookies.txt, then run curl -b cookies.txt.

Cookies are credentials. Conversion stays in this page — delete the file when you are done.

Cookie-Editor (the Chrome/Firefox extension commonly listed as “Cookie-Editor”) is a popup inspector: list, edit, delete, import and export JSON. CookieMan is a separate Manifest V3 editor. The overlap is the JSON array. The extra job CookieMan takes is conversion and live apply — this website never attaches to another extension’s cookie jar.

JobCookie-EditorCookieMan
List / edit cookies on the current tabYesYes — live list, badge count
JSON array import / exportYesYes — same field names
Netscape cookies.txtNot the primary exportImport, export, and this converter
Header / Set-Cookie / Base64NoSix formats, auto-detected
Partitioned (CHIPS) partitionKeyDepends on buildRead and written on JSON array
Official product of the other vendorNo — third-party extensionNo — do not treat this as Cookie-Editor’s site
Cookie JSON is a session credential. Do not paste a live export into a ticket. This converter runs in your browser; delete the file when the task is done.

JSON field mapping that actually round-trips

On import, sameSite values lax, strict, none and no_restriction all parse. Expiry values larger than 1e12 are treated as milliseconds and divided to Unix seconds. A missing domain is defaulted to localhost with a warning — that cookie will not authenticate on example.com until you fix the domain.

            {
  "name": "session_id",
  "value": "abc123",
  "domain": ".example.com",
  "path": "/",
  "secure": true,
  "httpOnly": true,
  "sameSite": "lax",
  "expirationDate": 1789200000,
  "hostOnly": false
}
          

Questions people ask

Is CookieMan the official Cookie-Editor replacement?
No. Cookie-Editor is a different extension. CookieMan is an independent Manifest V3 cookie editor that reads the same JSON array shape so you can keep working after an export.
Can I import Cookie-Editor JSON into Chrome with CookieMan?
Yes. Open the destination site, click Import, paste the JSON, check the preview and Apply. The parser is the same engine as this page.
How do I turn Cookie-Editor JSON into cookies.txt?
Paste the JSON into the converter on this page and set output to Netscape cookies.txt. HttpOnly cookies are written with the #HttpOnly_ prefix curl expects. See EditThisCookie JSON to cookies.txt for the same job from that exporter.
3 min read

EditThisCookie JSON to cookies.txt

Paste an EditThisCookie JSON export and download a tab-separated cookies.txt with #HttpOnly_ prefixes and Unix-second expiry, ready for curl or yt-dlp.

EditThisCookie JSON to cookies.txtEditThisCookie export Open the guide
3 min read

JSON Array vs cookies.txt Field Mapping

Side-by-side mapping of CookieMan JSON Array fields to Netscape cookies.txt. SameSite, partitionKey and store metadata never survive the seven-column file.

JSON vs cookies.txtcookies.txt field mapping Open the guide
3 min read

curl -b cookies.txt from JSON Export

Turn a Chrome JSON export into the Netscape file curl -b and -c expect: tabs, #HttpOnly_ prefixes, Unix-second expiry and a trailing newline.

curl cookies.txtcurl -b cookies Open the guide

Apply this on live cookies

The converter rewrites files. The extension reads and writes the jar in Chrome, including HttpOnly cookies.

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