JSON Parser
Parse JSON or an escaped JSON string online — unwraps double-encoded payloads, formats the result and reports structure and duplicate keys.
About this result
What It Does
This parser turns JSON text into a structure you can read, and accepts the two shapes people actually paste: a JSON document, or a JSON string — the quoted, backslash-escaped form a log line or an API field stores. A string is unwrapped first, as many times as it was encoded, and the result is formatted with a summary of what is inside: the top-level type, how many keys, objects and arrays, and how deeply it nests. Duplicate keys, which every parser silently collapses, are flagged.
When to Use It
- A log line contains a request body as an escaped string and you need to read it.
- An API returns a field whose value is itself JSON encoded as a string, sometimes twice.
- You want to know how deep and how large a payload is before writing code to walk it.
- You suspect a payload has duplicate keys and want to know which value a parser will keep.
Worked Examples
"{\"user\":{\"id\":42,\"roles\":[\"admin\"]}}"
An escaped string, as it appears in a log. It is unwrapped once and formatted as a real object with a nested user.
{"id":1,"name":"Ada","id":2}
Valid JSON with a duplicate key. The parser keeps id: 2 — the tool tells you a value was silently dropped.
[{"a":{"b":{"c":[1,2,3]}}}]
The structure line reports four levels of nesting — useful before writing a recursive walker.
Features
How to Use
1. Paste your input into the top box. 2. Adjust the options if the page has any — the result updates as you type. 3. Read the notes under the result, then copy it.
Common Mistakes
- Editing the result by hand and breaking the escaping. If you need to change the content, change the input and run it again — a single stray backslash makes the whole value invalid.
- Assuming the browser preserved Windows line endings. A pasted CRLF becomes LF in any text box, so a byte-exact comparison with the original file can still differ.
- Trusting that two documents are equal because they look equal. Key order, whitespace and number formatting differ between serializers; compare parsed values, not text.
Frequently Asked Questions
Related Tools
Everything runs in your browser. Your JSON is never uploaded, logged or stored.