About JSON Unescape String

Reverse JSON escape sequences back to raw text. Part of the DevTools Surf developer suite. Browse more tools in the JSON collection.

Use Cases

• Backend developers debugging double-encoded JSON strings in API responses
• Frontend devs extracting readable text from escaped JSON log entries
• Data engineers cleaning JSON string fields before loading into databases
• QA testers verifying that API responses contain correctly escaped content

Tips

• Paste a JSON-escaped string to get the raw text with real newlines and quotes
• Handles \n, \t, \", and Unicode escapes like \u00e9 automatically
• Use it to read double-encoded JSON strings from API responses

Fun Facts

• JSON requires only 4 characters to be escaped in strings: backslash, double quote, and control characters U+0000 through U+001F. Forward slash escaping is optional.
• The \uXXXX escape sequence in JSON uses UTF-16 encoding — characters outside the Basic Multilingual Plane (like emojis) need surrogate pairs: two \uXXXX sequences.
• Douglas Crockford discovered JSON in 2001 by observing that JavaScript object literal syntax could serve as a data interchange format — he 'found' it rather than invented it.

FAQ

When would I unescape a JSON string?

When you've got a log entry where someone logged the JSON payload as a stringified value, or a Terraform output that wrapped JSON in quotes. Unescape gives you back the original JSON.

Does it validate the output?

Yes — if the unescaped result isn't valid JSON, you'll get a warning. The unescape runs even on invalid input so you can inspect partial output.

What if the input has nested escapes?

The tool unescapes one level at a time. Run it twice for doubly-stringified input — common when a log line was re-serialized on the way out.

Is this the same as URL decode?

No. URL decode handles %XX percent-encoding; JSON unescape handles \n, \uXXXX, and \" backslash-escapes. Different encoding schemes for different contexts.