JSON Unescape

What is JSON Unescaping?

// Escaped input (copied from a log, quotes optional)
User said: \"it works!\"\nSession ended.

// Unescaped output — readable again
User said: "it works!"
Session ended.

// \uXXXX and surrogate pairs decode too
caf\u00e9 \ud83d\ude00  ->  café 😀

// JSON-in-JSON
{\"a\":1}  ->  {"a":1}

Key Features

Examples

"User said: \"it works!\"\nSession ended."

{\"event\":\"signup\",\"user\":{\"id\":42}}

caf\u00e9 \ud83d\ude00 r\u00e9sum\u00e9

function greet(name) {\n  return \"Hi \" + name;\n}

How to Use

1. 1

   Paste the escaped string

   Enter or paste a JSON-escaped string — with or without its surrounding double quotes. The decoded text appears instantly. Click 'Load example' to try a sample like an escaped log line or a \uXXXX-encoded string.

2. 2

   Read the decoded output

   Escape sequences become real characters: \n turns into line breaks, \" into quotes, and \uXXXX into Unicode. If the input is malformed, an error banner explains the problem so you can fix the offending backslash.

3. 3

   Copy or verify the result

   Click Copy to grab the readable text, or send it to the JSON Formatter to validate. Click Swap direction to re-escape it in place and confirm the round-trip matches your original.

Common Decoding Pitfalls

value: \q and \x41
// \q and \x hex are not valid JSON escapes -> error

value: \\q and \u0041
// literal backslash doubled; hex written as \u -> decodes

say "hi" there
// interior unescaped " breaks auto-wrapping -> error

say \"hi\" there
// interior quotes escaped -> decodes to: say "hi" there

path: C:\Users\Alice
// \U and \A are invalid escapes -> error

path: C:\\Users\\Alice
// doubled backslashes -> decodes to C:\Users\Alice

Common Use Cases

Decode Structured Log Fields

Copy a message field full of \n and \" out of a JSON log line and unescape it to read the real multi-line message exactly as it was emitted, instead of squinting at escape sequences.

Read JSON-in-JSON Payloads

Turn an inner JSON object that was stored as an escaped string field back into real JSON, so you can read it or paste it into a parser — common in webhook envelopes and audit logs.

Restore Unicode from ASCII-Safe Output

Decode \uXXXX-heavy output from a legacy system back into accented letters, CJK characters, and emoji, recovering the human-readable form of data that was forced to pure ASCII.

Un-flatten Code Snippets

Convert a script or query that was collapsed into a single JSON string (every newline as \n) back into properly formatted, multi-line, readable code.

Debug Double-Encoded Data

When a value looks like \\n or \\\", unescape once to inspect whether it was accidentally escaped twice upstream, then fix the producer — a frequent integration bug.

Inspect API Error Messages

Many APIs return error details as escaped strings inside a JSON envelope. Unescape the message to read stack traces and nested payloads that are otherwise hidden behind escape sequences.

Technical Details

Decoding Algorithm

The tool parses the input as a JSON string: if it is already wrapped in double quotes it is decoded as-is, otherwise the raw input is wrapped in quotes first so a bare escaped body still decodes. Each recognized escape (\n \r \t \b \f \" \\ \/ \uXXXX) maps to its character; this mirrors a compliant JSON parser, guaranteeing that any serializer-escaped string returns to its exact original.

Surrogate Pair Reconstruction

A \uXXXX escape yields a single UTF-16 code unit. When a high surrogate (\uD800–\uDBFF) is immediately followed by a low surrogate (\uDC00–\uDFFF), the two are combined into one code point above the Basic Multilingual Plane — so \ud83d\ude00 decodes to the single character 😀 rather than two broken halves.

Validation and Error Handling

If the input contains an invalid escape (a backslash followed by an unrecognized character, or a malformed \u sequence) or unbalanced quotes that break wrapping, decoding fails cleanly and an error banner is shown rather than emitting corrupted output. Valid input always produces the exact decoded string; invalid input never produces a misleading partial result.

Best Practices

Paste With or Without Quotes — Both Work

Do not waste time trimming surrounding quotes. The tool decodes "hello\nworld" and hello\nworld identically, so paste whatever you copied — including a fragment lifted from the middle of a larger document — and read the result.

Unescape Once, Then Check for Double-Encoding

If the decoded output still shows backslash sequences like \n, the original was double-escaped upstream. Unescape a second time to confirm, then fix the producer so it escapes only once rather than relying on repeated decoding.

Validate the Decoded JSON

After unescaping a JSON-in-JSON payload, run the result through our JSON Formatter to confirm it is valid and to pretty-print it. Unescaping recovers the text; the formatter confirms the structure.

Verify Round-Trips with Swap

Click Swap direction to re-escape the decoded text and check it matches the string you started with. A mismatch points to a malformed input or an unexpected escape, surfacing data problems before they propagate.

Frequently Asked Questions