Cookie to JSON

Q: Can it parse Set-Cookie response headers?

It focuses on name=value lists. Full Set-Cookie attributes (Path, Domain, Expires) are not the focus of this page.

Processed locally

app.cookie.view

You can also load data via #data={"name":"Ada"} or #url=... It is cleared from the address bar after it is read.

How to use

Turn name=value; theme=dark Cookie strings like this into a JSON object so you can inspect, edit, and copy them back. When debugging a login session, that is faster than hunting for a key in a long semicolon-separated list. HttpOnly cookies are not exposed to the page; this tool only processes the text you paste.

One field per name

Each Cookie name becomes a field. Fragments without an equals sign are treated as flags so you can scan which items are present.

Values are URL-decoded, so cookies with non-ASCII text are easier to read.

Debug login state

Faster than searching a long semicolon-separated list for a key. Some sites store a JWT in a Cookie—convert to JSON first, then decode it.

Do not send a full session Cookie to a chat tool or an unknown website.

Local conversion

Strings that contain a session ID are not uploaded either. Refresh the page and they disappear from memory.

After converting, redact values before sharing the structure. Do not share real session values.

Example

Cookie string

sessionid=abc123; theme=dark; lang=zh-CN

JSON

{
  "sessionid": "abc123",
  "theme": "dark",
  "lang": "zh-CN"
}

Can I read HttpOnly cookies?

The browser does not expose HttpOnly cookies to page scripts. This page only processes the text you paste.

How does this relate to JWT?

Some sites store a JWT in a Cookie. Convert to JSON first to extract the token, then go to JWT decoder Can I read HttpOnly cookies?

Can it parse Set-Cookie response headers?

It focuses on name=value lists. Full Set-Cookie attributes (Path, Domain, Expires) are not the focus of this page.

Will it change cookies already in the browser?

No. It only converts the string you paste and does not call document.cookie to write them.

Recommended workflow

Copy the Cookie string from DevTools Application or the request headers.
Paste it here and inspect which keys appear in the JSON.
If it contains a JWT, extract it and decode the Payload on the JWT page.
Before sharing a structure, redact session IDs on the clean/redact page.

A Cookie is equivalent to a session credential. This page helps you inspect structure; it does not replace secure storage or HttpOnly policies.