$ JSON Unstringify & Unescape
Paste an escaped JSON string like "{\"id\":42}" and get the original, readable JSON back.
Stringified input
Paste an escaped JSON string to get the original JSON back.
Parsed output
The original value, pretty-printed.
{
"event": "user.created",
"user": {
"id": 42,
"name": "Ada"
},
"tags": [
"beta",
"eu"
]
}Why use an online JSON unstringify tool
JSON Unstringify reverses JSON.stringify: you paste an escaped JSON string such as "{\"id\":42}" and get the original object back, pretty-printed. It is the quickest way to read JSON copied from logs, database text columns, queue messages or Lambda event bodies, where every quote shows up as \".
The tool parses the string literal first and then keeps parsing while the result is still a string that contains JSON. That handles double- and triple-encoded payloads in one step, and it also accepts escaped JSON pasted without its surrounding quotes.
It never strips backslashes with search-and-replace. A real JSON parser decides which backslash belongs to which layer, so Windows paths, regexes and quotes inside values survive intact.
JSON unstringify tool use cases
JSON unstringify tool examples: input and output
Unescape a JSON string
Escaped JSON without the outer quotes
Escaped plain text
Common JSON unstringify tool errors and how to fix them
cause:JSON.parse was called on text that is an escaped string, not an object, or the outer quotes were removed by hand.
fix:Paste the value as-is: the tool accepts it with or without the outer quotes and decodes the right number of times.
cause:A backslash is followed by a character that JSON does not allow, often because the value was copied from a source that already removed one layer of escaping.
fix:Copy the raw value again from the original source rather than from a rendered view.
cause:The value was truncated, which is common with long log lines.
fix:Retrieve the full value; a truncated escaped string cannot be decoded reliably.
How developers use the JSON unstringify tool in practice
Unstringifying is ideal for reading a payload. If your own API produces escaped JSON, remove the extra serialization step at the source instead of decoding on every consumer.
The status line tells you how many levels were decoded. More than one level usually means something in the pipeline stringifies twice.
When not to use the JSON unstringify tool
JSON unstringify tool limits and implementation notes
Decoding stops after five nested layers, which is far beyond what real systems produce, to avoid surprises with adversarial input.
Escapes from other languages, such as single-quoted strings or \x41 hex escapes, are not valid JSON and will be reported as errors.
Related guides
Standards & references
Related developer tools
Frequently asked questions about the JSON unstringify tool
What does unstringify mean?
It is the reverse of JSON.stringify applied to a JSON document: the escaped string is parsed back into the original value. In code it is JSON.parse on the string, repeated if the content is still a JSON string.
How do I remove backslashes from JSON?
Paste the escaped value into this tool. It parses the string with a real JSON parser instead of deleting backslashes, so quotes and backslashes that belong to the data are kept correctly.
What is double-encoded JSON?
JSON that was stringified twice, so the result is a string containing an escaped string containing the object. You see it as \\\" sequences. The tool decodes every layer and reports how many it removed.
Do I need to include the surrounding quotes?
No. Escaped JSON pasted with or without the outer double quotes is accepted.
Is my data sent to a server?
No. Decoding runs entirely in your browser with the native JSON parser.