3 min read

Convert a Postman Cookie header to JSON cookies

A Postman Cookie header is a single Cookie: request line — paste it here to expand each name=value pair into a JSON cookie object. Postman is not affiliated with CookieMan; this page only rewrites the header text you already copied.

The header format has no domain, path, expiry, Secure, HttpOnly or SameSite. The parser therefore warns Header string format has no domain info; defaulted to localhost. Fix domains before you import into Chrome.

Postman cookiesPostman Cookie headerCookie header to JSONPostman to cookies.txt
  1. 1
    Copy the header from Postman

    In the request, open Headers and copy the Cookie value, with or without the Cookie: prefix. Alternatively copy from the Code snippet (“cURL”).

  2. 2
    Convert on this page

    Paste into the converter. Output is JSON Array so you can edit domain per cookie. Switch to Netscape only after domains are real hosts, not localhost.

  3. 3
    Set domains, then import or send

    Replace localhost with the API host (leading dot if subdomains should receive the cookie). Import in CookieMan on that origin, or export Netscape for curl -b.

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

What a Cookie header cannot carry

AttributeIn Postman Cookie headerAfter JSON conversion
name / valueYesPreserved
domainNolocalhost + warning
pathNo/
secure / httpOnly / sameSiteNofalse / unspecified
expirationDateNoSession cookie
hostOnlyNotrue
Importing this JSON unchanged writes cookies for localhost. They will not be sent to your API host. Edit domain first, or start from a Set-Cookie dump / JSON export that already has hosts. See Cookie missing domain, defaulted to localhost.

Postman’s request Cookie header is not the same as captured Set-Cookie response headers. Set-Cookie lines include Domain, Path, Secure, HttpOnly and SameSite — paste those instead when you have them. The Cookie header vs Set-Cookie guide is the field-level comparison.

            Cookie: session_id=abc123; theme=dark

# becomes (domains still localhost until you edit them)
[
  { "name": "session_id", "value": "abc123", "domain": "localhost", "path": "/" }
]
          

Questions people ask

Can I paste a full Postman collection JSON?
No. The detector looks for cookie formats, not a Postman collection. Copy the Cookie header (or Set-Cookie lines) out of the request/response and paste only that.
Why do converted cookies say domain localhost?
A request Cookie header has no Domain attribute. The parser must pick a host; it uses localhost and emits a warning rather than guessing example.com.
How do I send the result from Axios or fetch?
Convert to Header String and put the line in headers: { Cookie: ... }. That still will not set HttpOnly cookies in a browser. See Axios Cookie header from JSON.
3 min read

Axios Cookie Header from JSON Export

Convert a JSON cookie array to a Cookie header for Axios in Node. Browsers ignore this header. HttpOnly cannot appear on the wire.

Axios Cookie headerAxios cookies Open the guide
3 min read

Cookie Header vs Set-Cookie Conversion

A Cookie request header is name=value pairs. Set-Cookie response lines carry Domain, Path, flags and Expires. Convert each separately — they are not interchangeable.

Cookie vs Set-CookieSet-Cookie to JSON Open the guide
3 min read

Insomnia Cookie Jar to cookies.txt

Take cookies copied from Insomnia’s Cookie Jar or a Cookie header and write a Netscape cookies.txt curl and wget will load. Set domains before you save the jar.

Insomnia cookiesInsomnia cookie jar 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