Cookie Parser

📖 Tool Introduction

The Cookie string you copy out of your browser devtools is usually one long semicolon-joined blob: sessionid=38afes7a8; logged_in=true; theme="dark mode"; and so on. Reading it with the naked eye, it is surprisingly hard to match every name with its value and to tell where one pair ends and the next begins. This parser turns that blob into a clean table in one click: the string is split on semicolons, each segment is divided at its first equals sign into a name and a value, and any pair of surrounding double quotes is stripped off the value while inner spaces and symbols are preserved. Segments without an equals sign, such as HttpOnly and Secure flags, are kept in the table and tagged as flags instead of being silently dropped. Once parsed, the result can be copied as tab-separated text or downloaded as a TSV file, which drops neatly into test cases, logs or tickets. Because all parsing happens locally in your browser, the kind of sensitive session material that cookies always contain never touches any remote server, and the tool stays usable even on locked-down networks. Ctrl+Enter runs a parse so you can work hands-free from the keyboard after pasting.

When you are reproducing a bug that a customer only sees when logged in, handing your teammate a wall of semicolon-separated text forces them to eyeball each value by hand. A parsed table makes it obvious at a glance which cookie carries the session, which one toggles a theme, and which flags are simply on or off. The TSV export fits straight into a spreadsheet, where columns sort and filter the way analysts expect, and because the parse is local, even production cookies can be inspected without leaving a log of them on some third-party server. The first-equals-split rule means values that themselves contain equals signs, such as base64 tokens, stay intact instead of being truncated mid-way.

✨ Key Features

• Smart splitting: split on semicolons, then at the first equals sign; values may keep their own equals signs
• Quote handling: outer paired double quotes are removed, while inner spaces and symbols stay intact
• Type tagging: segments with = become key-value pairs, bare segments become flags like HttpOnly or Secure
• Summary banner: after parsing, the count of pairs and flags is shown at a glance
• Flexible export: results copy as TSV text or download as a .tsv file
• Local only: cookies are processed in browser memory and never uploaded

📝 How to Use

1. Copy the full Cookie request header from your browser devtools or a packet sniffer
2. Paste the whole string into the text area
3. Click Parse and read the generated key-value table below
4. Verify each row's name and value, checking that quotes and flags were handled correctly
5. Use Copy table or Download to export the result as TSV when you need to keep it

⚠️ Notes

• Sensitive data: cookies usually carry session credentials, so never share parsed results in public channels
• Request vs response: the tool targets the Cookie request header; Set-Cookie response attributes like Path and Expires are shown as plain rows
• Quote rule: only the outermost paired double quotes are removed; inner quotes stay as they are
• Empty segments: blanks left by double semicolons or leading/trailing semicolons are skipped automatically
• Fully local: no network request is made; parsing works completely offline