Escaped JSON string
"Hello \"team\"\nLine two"
What this tool does
JSON Unescape decodes escaped JSON string literals back into human-readable text. It turns sequences like \" and \n into the underlying characters you actually want to inspect.
That makes it easier to debug payloads where the real problem is hidden inside an escaped string field.
Common use cases
- Reading escaped text copied from API logs.
- Inspecting serialized string values from databases.
- Checking request body fragments with heavy escaping.
- Understanding webhook payloads that contain embedded text blobs.
Input and output example
Readable text
Hello "team" Line two
How to use this tool
- Paste a valid quoted JSON string into the input.
- Click Unescape JSON String.
- Review or copy the readable output.
- Use Escape for JSON if you need to turn the text back into a JSON-safe string literal.
Your text is processed in your browser and is not uploaded to our servers.
Common errors
- Plain text is not the same as an escaped JSON string, so it will fail if pasted into the unescape action.
- Broken quotes around the string literal stop JSON parsing.
- Invalid backslash sequences can make the input malformed.
- Large escaped payloads can be hard to spot without first isolating the exact string value.
Related tools
FAQ
Do I need surrounding quotes in the input?
Yes. The unescape action expects a valid JSON string literal, including quotes.
Can I use this for multiline values?
Yes. Escaped newline sequences are decoded back into readable line breaks.
Why do some strings fail to decode?
They may not be valid JSON strings, or they may contain broken escaping.
Can I copy the decoded text directly?
Yes. After decoding, you can copy the result from the output panel.