Claudecookie – convert, check, and mint Claude Code credentials from a cookie

Cookie converter

Convert cookies.

Without sending them anywhere.

Netscape cookies.txt ↔ JSON ↔ Cookie-Editor ↔ Puppeteer ↔ Cookie header

Runs entirely in your browser

Paste cookies here

Ctrl+V or drop files

Netscape · JSON · Cookie header

Processed locally in your browser

Output appears here

Paste on the left — the result appears here.

Need the same conversion from a script? Netscape, Cookie-Editor, Puppeteer, key-value and Cookie headers are on the public JSON API. API documentation

More tools

Questions

A plain text file with one cookie per line and seven tab-separated fields: domain, include-subdomains flag, path, secure flag, expiry, name and value. It was introduced by Netscape Navigator and is still what curl, wget and yt-dlp read and write today.

Converter input never leaves your device. The Check cookie and credential pages are different: the paste is encrypted in the browser, then sent to this site’s backend and to Anthropic. The site also records anonymous usage statistics — which formats are converted and how often — through Yandex Metrika. There is no Google Analytics.

Cookie-Editor if you are importing back into a browser extension. Puppeteer if you are feeding page.setCookie() or context.addCookies(). Key-value for a requests or axios session. Header if you just need something to paste after curl -H.

That prefix is how curl marks an http-only cookie in a cookies.txt file. It looks like a comment so older readers skip it safely, while curl and yt-dlp understand it. Cookies without the flag are written normally.

Both mean a session cookie — one that dies when the browser closes. Netscape files write 0, Puppeteer writes -1, and Cookie-Editor drops the field and sets session to true instead. All three are read correctly and converted to whichever spelling the target format expects.

They only store names and values. Domain, path, expiry, secure and http-only have nowhere to go. That is fine when you are attaching cookies to a single request, but you cannot convert back to a complete cookies.txt afterwards without supplying a domain.

Yes — that is the most common reason people land here. Export from Cookie-Editor as JSON, paste it in, and the output is a Netscape cookies.txt file you can pass to yt-dlp --cookies or curl -b.

Yes. POST /api/v1/convert, /api/v1/check and /api/v1/credential accept the same pastes as the website. No API key. The human docs are at /api/ and the OpenAPI file is /openapi.json.