๐Ÿ”’ Runs in your browser โ€” nothing is uploadedโœ“ Free, no signup

Cookie & Set-Cookie Parser

Paste a Cookie request header, document.cookie or Set-Cookie response headers to see every cookie decoded, with expiry times and security warnings.

Cookie or Set-Cookie header

Detected: Cookie request header

4 cookies

NameValue (decoded)
session_id8f2a1c9e7b
themedark
cart{"items":3}raw: %7B%22items%22%3A3%7D
_gaGA1.2.1234567890.1700000000

JSON

{
  "session_id": "8f2a1c9e7b",
  "theme": "dark",
  "cart": "{\"items\":3}",
  "_ga": "GA1.2.1234567890.1700000000"
}

When should you use the Cookie Parser?

  • Debugging login and session problems
  • Reading cookies copied from DevTools or a HAR file
  • Checking Set-Cookie attributes like SameSite and Secure before release

How to use the Cookie Parser

  1. 1

    Paste cookies

    A Cookie header, document.cookie output, or Set-Cookie headers (one per line).

  2. 2

    Check the type

    The header type is detected automatically, or choose it yourself.

  3. 3

    Read the results

    Values are URL-decoded; Max-Age and Expires are shown as durations.

  4. 4

    Fix warnings

    Missing Secure, HttpOnly or SameSite problems are flagged.

Examples

Cookie header

Header

Cookie: session=abc%20def; theme=dark

Parsed

session  abc def
theme    dark

Common errors and how to fix them

SameSite=None requires Secure
Browsers reject SameSite=None cookies that aren't Secure. Add the Secure attribute and serve over HTTPS.
Several Set-Cookie headers were merged
Put each Set-Cookie header on its own line โ€” they can't be split on commas because Expires dates contain commas.
Related tools:ย JWT Decoder ยท URL Encoder & Decoder ยท CORS Header Generator

More from Web & Network

Free tools that run in your browser โ€” no signup, nothing uploaded.

Cookie Parser FAQ

Set-Cookie is sent by the server to create a cookie, with attributes like Path and Expires. Cookie is sent by the browser back to the server and contains only name=value pairs.

It controls whether the cookie is sent with cross-site requests: Strict (never), Lax (top-level navigation only โ€” the default) or None (always, but requires Secure).

It hides the cookie from JavaScript (document.cookie), which protects session cookies from theft by XSS.

Both set a lifetime. Max-Age (seconds) takes priority. Without either, the cookie is deleted when the browser session ends.

Name prefixes that make browsers enforce rules: __Secure- requires Secure; __Host- also requires Path=/ and no Domain.

No. Everything runs in your browser, so your cookies never leaves your device.