Cookie Parser

Parse cookie headers and check them against the rules browsers enforce. Paste a Cookie request header to see each name and value, or Set-Cookie response headers to see every attribute — Domain, Path, expiry, Secure, HttpOnly, SameSite — with warnings for problems like SameSite=None without Secure or a misused __Host- prefix. Copy the result as JSON. It's free, runs in your browser, and your cookies never leave your device.

Set-Cookie attributes

AttributeEffect
SecureOnly sent over HTTPS
HttpOnlyHidden from JavaScript
SameSite=StrictNever sent on cross-site requests
SameSite=LaxSent on top-level navigation only (default)
SameSite=NoneAlways sent; requires Secure
Max-Age / ExpiresLifetime; none means session cookie
__Host- prefixMust be Secure, Path=/, no Domain

When to use it

  1. Work out why a browser is ignoring a cookie your server sets.
  2. Audit session cookies for Secure, HttpOnly and SameSite.
  3. Read the cookies a request is sending, decoded.
  4. Check a __Host- or __Secure- cookie meets its prefix rules.

How to Use

  1. Paste a Cookie header, or Set-Cookie headers one per line.
  2. Read each cookie's value and attributes.
  3. Fix anything flagged as an error or warning.
  4. Copy the result as JSON if needed.

Features

  1. Cookie and Set-Cookie parsing
  2. All standard attributes
  3. Browser rule checks: SameSite, __Host-, __Secure-, Partitioned
  4. Max-Age to expiry date
  5. URL-decoded values
  6. JSON output
  7. 100% client-side

FAQs

Why is my cookie being rejected?

Common causes: SameSite=None without Secure, a __Host- cookie with a Domain or a Path other than /, or a Secure cookie set over plain HTTP. The tool flags the first two.

What's the difference between Cookie and Set-Cookie?

Set-Cookie is sent by the server to create or change a cookie, with attributes. Cookie is sent by the browser and contains only names and values.

What does HttpOnly do?

It hides the cookie from JavaScript, which protects session cookies from being stolen through XSS.

What if SameSite isn't set?

Browsers treat it as Lax: the cookie is sent on top-level navigations from other sites but not on cross-site subrequests.

Are my cookies sent anywhere?

No. Parsing happens in your browser.

Technical Details

A request's Cookie header is a list of name=value pairs separated by semicolons; a response's Set-Cookie header is one cookie followed by attributes, and servers send one Set-Cookie line per cookie. The parser tells the two apart from the input, splits the cookie pair from its attributes, strips optional quotes and URL-decodes values for display while keeping the raw form. Domain, Path, Expires, Max-Age, Secure, HttpOnly, SameSite, Partitioned and Priority are recognized; Max-Age is converted to an absolute expiry and takes precedence over Expires, as RFC 6265 specifies. The checks follow what browsers enforce: SameSite=None without Secure is rejected; cookies named __Host- must be Secure with Path=/ and no Domain; __Secure- cookies must be Secure; Partitioned requires Secure. Softer warnings flag a missing Secure or HttpOnly, note that a missing SameSite defaults to Lax, and identify session cookies and headers that delete a cookie by expiring it. Parsed results can be copied as JSON.

Developer Tools

Developer Tools

  • Dockerfile Generator
  • Nginx Config Generator
  • README Generator
  • Dockerfile Linter
  • SSH Config Generator
  • .dockerignore Generator
  • README Badge Generator
  • JSON to Zod