3 min read

Convert EditThisCookie JSON to Netscape cookies.txt

Convert EditThisCookie JSON to cookies.txt by pasting the array below and leaving the output on Netscape — this page rewrites tabs, the #HttpOnly_ prefix and Unix-second expiry; it does not install EditThisCookie.

EditThisCookie itself is Manifest V2 and no longer runs in current Chrome. If you still have an old JSON export, that file is enough. The EditThisCookie alternative page covers installing CookieMan as the editor; this page is only the conversion job.

EditThisCookie JSON to cookies.txtEditThisCookie exportconvert EditThisCookieNetscape cookies.txt
  1. 1
    Get the JSON export

    Use an existing EditThisCookie export file, or export JSON from any editor that uses the same object shape (expirationDate, hostOnly, httpOnly, sameSite).

  2. 2
    Convert to Netscape on this page

    Paste the array into the converter. Output is preset to Netscape cookies.txt. Copy or download the file — conversion is local.

  3. 3
    Hand the file to curl or yt-dlp

    Save as cookies.txt and run curl -b cookies.txt https://example.com/ or yt-dlp --cookies cookies.txt URL. Do not commit the file.

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

Which EditThisCookie fields survive cookies.txt

EditThisCookie JSONNetscape columnLost?
domain1 — domainNo
hostOnly2 — TRUE/FALSE include-subdomains (inverted)No
path3 — pathNo
secure4 — TRUE/FALSENo
expirationDate (seconds)5 — Unix seconds; 0 if sessionNo
name / value6 / 7No
httpOnly#HttpOnly_ prefix on the domain fieldNo — if the reader understands the prefix
sameSiteYes. Netscape has no SameSite column.
storeId / idYes. Ignored on parse.
partitionKeyYes. CHIPS cannot round-trip through cookies.txt.
sameSite is dropped on purpose. If the destination is another Chrome profile, keep JSON Array instead — see JSON Array vs cookies.txt.

What the rewritten file looks like

            # Netscape HTTP Cookie File
# https://curl.se/docs/http-cookies.html

#HttpOnly_.example.com	TRUE	/	TRUE	1789200000	session_id	abc123
          

The serializer always writes the magic header and a trailing newline. curl’s own jar writer does the same. A file that still uses spaces between fields will be repaired on the next paste — see Skipped invalid Netscape line.

Questions people ask

Does EditThisCookie JSON need conversion before Chrome import?
No. CookieMan Import detects the JSON array and applies it. Convert to cookies.txt only when the next tool is curl, wget, yt-dlp or another Netscape reader.
Why is sameSite missing after conversion?
The Netscape format has seven tab-separated fields and no SameSite column. Re-importing cookies.txt into Chrome leaves sameSite unspecified. Keep JSON when you need Lax/Strict/None.
Will #HttpOnly_ lines be treated as comments?
Not by this parser or by curl. Naive scripts that skip every line starting with # drop the session cookie. Use a reader that strips the prefix, or stay on JSON.
3 min read

Cookie-Editor Alternative for Chrome (MV3)

Cookie-Editor is a cookie inspector. CookieMan is a Manifest V3 editor that imports the same JSON and converts it to cookies.txt, headers or Base64.

Cookie-Editor alternativeCookie-Editor Chrome 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
3 min read

yt-dlp cookies.txt from Chrome Export

Convert Chrome JSON or a browser dump to the Netscape file yt-dlp --cookies expects, with tabs, Unix seconds and #HttpOnly_ session cookies intact.

yt-dlp cookies.txtyt-dlp --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