Cookie Header Parser
Paste a Cookie request header or one or moreSet-Cookie response headers and get every cookie rendered as a clean table: name, URL-decoded value, detected JSON and all attributes such as Path, Domain, Expires,Max-Age, Secure, HttpOnly andSameSite. Nothing leaves your browser.
How to use the cookie header parser
- Open your browser's DevTools, go to the Network tab, select a request and copy the
Cookieheader from the request headers or theSet-Cookieheader(s) from the response headers.curl -ioutput works too. - Paste the header into the field above. The
Cookie:orSet-Cookie:prefix is optional. - Click Parse cookies to see each cookie as a row with its decoded value and attributes.
- Expand JSON output and click Copy JSON to reuse the structured result in tests, scripts or bug reports.
What the parser does
- Splits the header on semicolons and keeps
=characters inside values, so base64 and JWT tokens stay intact. - Strips surrounding double quotes and URL-decodes every value, showing the raw encoded value when it differs.
- Detects JSON objects and arrays stored in cookies and pretty-prints them.
- Recognises
Set-Cookieattributes and showsMax-Ageas a human-readable duration andExpiresin your local time. - Accepts multiple
Set-Cookieheaders, one per line.
Cookie header format reference
A Cookie request header is a list of name=value pairs separated by; (semicolon and space), as defined inRFC 6265:
Cookie: theme=dark; sessionId=abc123; prefs=%7B%22lang%22%3A%22en%22%7DA Set-Cookie response header defines a single cookie followed by optional attributes. Each cookie needs its own Set-Cookie header:
Set-Cookie: sessionId=abc123; Path=/; Secure; HttpOnly; SameSite=Lax; Max-Age=2592000Frequently asked questions
What is the difference between the Cookie and Set-Cookie headers?
Set-Cookie is sent by the server in an HTTP response to create or update a cookie, and may carry attributes such as Path, Domain, Expires, Max-Age, Secure, HttpOnly and SameSite. Cookie is sent by the browser in subsequent requests and only contains name=value pairs separated by semicolons.
How does this tool decide which header type I pasted?
If any segment after the first name=value pair is a known Set-Cookie attribute (Path, Domain, Expires, Max-Age, Secure, HttpOnly, SameSite, Partitioned or Priority) the line is treated as a Set-Cookie header. Otherwise every segment is treated as a separate cookie from a Cookie header. The optional "Cookie:" or "Set-Cookie:" prefix is removed automatically.
Are my cookies sent to a server?
No. Parsing happens entirely in your browser with JavaScript. Nothing you paste is stored, logged or transmitted, which makes it safe to inspect session cookies and authentication tokens.
Why are some values shown as JSON?
Many applications store URL-encoded JSON objects or arrays in cookies. The parser URL-decodes each value and, if the result is a JSON object or array, pretty-prints it so nested keys are easy to read. The raw encoded value is still shown underneath.
Can I parse several Set-Cookie headers at once?
Yes. Paste each Set-Cookie header on its own line, for example straight from your browser's DevTools Network tab or a curl -i response, and every cookie is listed with its own attributes.