Does CookieMan store cookies as Base64 internally?

No. Base64 is an export format. The live jar is the browser’s cookie store. The converter never uploads the blob.

Why not JSON.parse the Base64 directly?

You must decode first. Pasting Base64 into a JSON parser throws. Detection tries Base64 before Netscape when the alphabet matches.

Can I Base64-encode cookies.txt?

Yes — decode still works if the inner text is Netscape. Exporting Base64 from this tool always wraps a JSON array, not Netscape.

Base64 Cookie Export to JSON Array

Decode a Base64 cookie blob back to JSON

A Base64 cookie export is usually a JSON array wrapped so chat apps and CI variables do not mangle quotes; paste the blob here to decode it and re-emit JSON, Netscape or a header. The warning Decoded from Base64 (inner format: json-array) tells you what was inside.

The encoder uses UTF-8 (btoa(unescape(encodeURIComponent(json)))) so non-ASCII values survive. URL-safe Base64 (- / _) is accepted on decode.

Base64 cookiesdecode cookie Base64Base64 JSON cookiescookie export Base64

1
Get the Base64 string
From CookieMan Export → Base64, a CI secret, or a chat paste. Whitespace is ignored.
2
Decode here
Paste the blob. If it is valid Base64 wrapping cookies, detection reports the inner format. Output JSON Array unless the next tool wants Netscape.
3
Import or store as text
CookieMan Import accepts the JSON (or the original Base64). Prefer JSON on disk; Base64 is for hostile text fields only.

Paste Base64 cookie payload

Output format

Output

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

What the Base64 wrapper can contain

Inner text after decode	innerFormat warning	Then
JSON array	`json-array`	Full attributes
JSON map	`json-map`	localhost defaults
Netscape file	`netscape`	SameSite lost already
Cookie header / Set-Cookie	those formats	Same limits as raw paste

Base64 is encoding, not encryption. Anyone who has the string has the session. Do not treat a Base64 export as safe to post in a public issue.

When decode throws

Invalid Base64 payload means the alphabet check failed or atob threw. Decoded Base64 content is not a recognized cookie format means the bytes decoded but the inner text was not JSON, Netscape, a header or Set-Cookie. Both surface as detection failure if you paste the blob as-is — Could not detect cookie format.

            W3sibmFtZSI6InNlc3Npb25faWQiLCJ2YWx1ZSI6ImFiYzEyMyJ9XQ==
# inner: [{"name":"session_id","value":"abc123"}]

Related guides

August 5, 2026 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

July 20, 2026 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

August 11, 2026 3 min read

Fix: Could not detect cookie format

CookieMan emits this warning when the paste is not JSON, Netscape, Cookie header, Set-Cookie or Base64. Strip the BOM, extract cookie text, then convert.

Could not detect cookie formatcookie format detection failed Open the guide