Cookie and Set-Cookie header parser
Copy the header from your browser dev tools and paste it here to read cookies easily and catch settings that stop them being saved.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter header type and header text.
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
Cookie header: name=value pairs separated by ;. Set-Cookie: the first pair is the cookie, the rest are attributes. Warnings follow RFC 6265bis: SameSite=None needs Secure, the __Secure- prefix needs Secure, the __Host- prefix needs Secure, Path=/ and no Domain.
Example
Inputs: Header type = Cookie (request). Result: Number of cookies: 4.
Limits and caveats
- Each Set-Cookie header carries one cookie, so paste one line at a time.
- Warnings reflect common browser behaviour; some details differ between Chrome, Firefox and Safari.
Questions about this tool
What does HttpOnly do?
It stops page JavaScript from reading the cookie, reducing the risk of session theft through XSS.
What is the difference between SameSite=Lax and Strict?
Strict never sends the cookie on requests from another site; Lax sends it only on top-level GET navigations.
Why is the browser not saving my cookie?
Common causes: SameSite=None without Secure, a Domain that does not match the site, or a __Host- prefix without its rules.