JSON String Unescape
Example
Input:
He said \"hi\"\nNew line
Output:
He said "hi" New line
About this converter
Escaped strings confront you in logs, in debugger watches and in JSON-inside-JSON payloads (the dreaded stringified string). This unescaper applies the JSON string rules in reverse — all backslash escapes including \uXXXX — by parsing the value with a real JSON parser rather than a chain of replacements, so sequences interact correctly (\\n becomes backslash + n, not a newline — the distinction replacement chains always get wrong). Raw line breaks inside the input are pre-escaped leniently, because copied log fragments often contain them.
Frequently Asked Questions
Why did \\n not become a newline?
Because it should not: \\ is an escaped backslash, then a literal n. That is the correct parse, and exactly why a real parser beats find-and-replace.
Can it unescape a whole JSON document?
It processes the input as one string value. For a full document, the JSON Formatter shows it readably without unescaping games.