Cookie and Set-Cookie Header Parser
Break down a Cookie or Set-Cookie header into readable key/value pairs.
sessionIdabc123themedarkPath/HttpOnly✓Secure✓SameSiteLax🔒 100% client-side — no data sent
Break down a Cookie or Set-Cookie header into readable key/value pairs with their attributes (Domain, Path, Expires, Secure, HttpOnly, SameSite). Great for debugging sessions and authentication. Fully local parsing: your cookies stay in your browser.
What is it for?
- ▸ Debug a session or authentication issue
- ▸ Inspect Secure, HttpOnly and SameSite attributes
- ▸ Read a long Cookie header as a clear table
- ▸ Check a Set-Cookie's expiry date
FAQ
Difference between Cookie and Set-Cookie?
Set-Cookie is sent by the server to set a cookie; Cookie is sent back by the browser on each request.
What is the SameSite attribute for?
It controls whether the cookie is sent on cross-site requests, helping prevent CSRF (Strict, Lax, None).
What does HttpOnly mean?
It blocks access to the cookie via JavaScript, reducing session theft risk via XSS.