- 1 Extract Set-Cookie lines
In Chrome DevTools Network, select the response, copy each
Set-Cookieheader, or open the HAR and copy the header values. One cookie per line, with or without theSet-Cookie:prefix. - 2 Convert on this page
Paste the lines. Detection is Set-Cookie. Output JSON Array keeps
Domain,Path,Secure,HttpOnly,SameSiteandExpires/Max-Age. - 3 Import or replay
Import in CookieMan on the host that issued the cookies, or switch output to Netscape for curl. Do not commit the HAR.
Set-Cookie attribute mapping
| Set-Cookie attribute | JSON field | Parser behaviour |
|---|---|---|
name=value (first pair) | name, value | Required |
Domain= | domain, hostOnly: false | A leading dot is added if missing |
Path= | path | Defaults to / |
Expires= | expirationDate | Parsed as a HTTP date, stored as Unix seconds |
Max-Age= | expirationDate | Now + seconds (computed at parse time) |
Secure / HttpOnly | booleans | Presence flags |
SameSite=None|Lax|Strict | sameSite | None → no_restriction |
Partitioned | — | Recognized and ignored — no topLevelSite in the header |
Partitioned attribute without a partition key cannot be stored. CHIPS cookies copied as Set-Cookie will import unpartitioned and may not be sent in the third-party context you expect. Use CookieMan’s JSON export from the live jar instead — partitioned cookie export. Why the whole HAR is rejected
A HAR is JSON, but it is not a cookie array and not a name→value map of cookies. Pasting the file yields Could not detect cookie format or a JSON map of unrelated keys. That is the same message as any unknown blob — fix detection errors. Copy Set-Cookie lines only.
Set-Cookie: session_id=abc123; Domain=.example.com; Path=/; Secure; HttpOnly; SameSite=Lax
Set-Cookie: theme=dark; Domain=.example.com; Path=/; SameSite=Lax