Cookie Header Parser
Example
Input:
session=abc123; theme=dark; ref=google%20ads
Output:
3 cookies: session = abc123 theme = dark ref = google%20ads (decoded: google ads)
About this converter
Cookie headers arrive as one dense semicolon string, usually copied out of DevTools or a server log while debugging sessions, consent state or A/B test assignments. The parser splits on the cookie boundaries (the first = splits name from value, so values may themselves contain = — base64 session tokens do), counts the cookies, and shows a percent-decoded view of each value alongside the raw one, because half of cookie debugging is realizing a value was encoded. It deliberately does not parse Set-Cookie attributes (Expires, Path, HttpOnly) — those live on the response side and deserve their own reading, attribute by attribute.
Frequently Asked Questions
Why can a value contain = signs?
Cookie syntax splits on the first = only; base64-padded session values legitimately end in = or ==.
Is it safe to paste a real session cookie here?
The page runs locally in your browser and stores nothing — but treat session cookies like passwords generally: do not paste them into random online tools that phone home. This one does not.