- 1 Copy the header from Postman
In the request, open Headers and copy the
Cookievalue, with or without theCookie:prefix. Alternatively copy from the Code snippet (“cURL”). - 2 Convert on this page
Paste into the converter. Output is JSON Array so you can edit
domainper cookie. Switch to Netscape only after domains are real hosts, notlocalhost. - 3 Set domains, then import or send
Replace
localhostwith the API host (leading dot if subdomains should receive the cookie). Import in CookieMan on that origin, or export Netscape forcurl -b.
What a Cookie header cannot carry
| Attribute | In Postman Cookie header | After JSON conversion |
|---|---|---|
| name / value | Yes | Preserved |
| domain | No | localhost + warning |
| path | No | / |
| secure / httpOnly / sameSite | No | false / unspecified |
| expirationDate | No | Session cookie |
| hostOnly | No | true |
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. Cookie header vs the Set-Cookie pane
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": "/" }
]