Free JSON Unescape Tool
Turn escaped JSON back into readable text. Paste JSON full of backslash escapes, get clean JSON you can read, validate and use again.
Unescaped output
Your input never leaves this device — the conversion runs entirely in your browser.
What JSON escaping is and why text arrives escaped
Inside a JSON string, certain characters cannot appear literally. A double quote would end the string, a backslash starts an escape, and control characters such as a line break must be written as escape sequences. Escaping replaces each such character with a backslash followed by a code: a quote becomes an escaped quote, a line break becomes the two characters backslash and n, and a tab becomes backslash and t.
Text often arrives escaped because JSON was encoded twice. A server may return a JSON string whose contents are themselves JSON, a log file may record a response as one escaped line, or a database field may store JSON text inside another JSON document. In each case the outer layer adds backslashes, and the inner JSON looks unreadable until those backslashes are removed.
Unescaping reverses the process. It turns each escape sequence back into the character it stands for, so the inner text becomes readable JSON again. The tool handles the standard JSON escapes and reports invalid escapes instead of guessing, and it runs in your browser, so pasted text never leaves your device.
How to unescape JSON
Follow these steps to unescape JSON text:
- Paste the escaped text into the input area.
- Read the unescaped result in the output area. Line breaks, quotes and special characters should now appear as themselves.
- Copy the result and use it where the clean text is needed.
- If the result still shows escaped quotes and backslash sequences, the text was escaped more than once. Unescape the result one more time.
- Check the result with a JSON validator before using it as JSON, because unescaping only removes escapes and does not repair other errors.
Unescape only text that was actually JSON-escaped. If the text already reads normally, with real quotes and real line breaks, it has nothing to unescape, and running it through the tool can change backslashes that belong to the data itself.
Worked example: an escaped log line
The input below is a single escaped line, as it might appear in a log. The output is the same data after unescaping: the escape sequences are gone, and the real line breaks and quotes are back. Note that unescaping does not add indentation — to indent the result, use the pretty-print tool afterwards.
{\"name\": \"Ada Lovelace\",\n\"city\": \"Paris\",\n\"word\": \"caf\u00e9\",\n\"visits\": 3,\n\"active\": true,\n\"note\": null}{"name": "Ada Lovelace",
"city": "Paris",
"word": "café",
"visits": 3,
"active": true,
"note": null}Each escaped quote became a plain quote, each line-break escape became a real line break, and the unicode escape became the letter it stands for. The values are unchanged: the same fields, numbers, boolean and null.
Common JSON escapes and what each one stands for:
| Escape | Stands for |
|---|---|
\" | Double quote |
\\ | Backslash |
\/ | Forward slash |
\n | Line break |
\t | Tab |
\uXXXX | Character with that code point |
Rules and edge cases
Only recognised escapes are converted. A backslash followed by a character that is not a valid escape, such as x, is invalid in JSON and is reported as an error, so the source text can be fixed instead of silently changed. A backslash at the very end of the text, with nothing after it, is also an error. Single quotes need no escape in JSON, so a backslash before a single quote is not a valid JSON escape either.
Unicode escapes name a character by its code point, written as four hexadecimal digits. Characters outside the basic range are written as a pair of escapes that combine into a single character when unescaped. Control characters other than the named escapes must also use unicode escapes in strict JSON.
Unescaping does not validate the result. If the inner text was already broken, with a missing comma or bracket, the output will still be broken, only more readable. It also does not decode other encodings: percent encoding in web addresses and HTML entities are different systems and need different tools.
Common unescaping mistakes
- Unescaping text that was never escaped: backslashes in Windows file paths or regular expressions are not JSON escapes. Unescaping them can turn a path separator and a letter into a control character.
- Expecting unescaping to fix JSON: missing commas, unmatched brackets and trailing commas survive unescaping unchanged. Fix those in the clean text afterwards.
- Stopping after one pass on double-escaped text: text escaped twice still looks escaped after one pass. Run the result through again, once, and check each stage.
- Confusing JSON escapes with other encodings: web address percent encoding and HTML entities look different and follow different rules. Use the tool that matches the encoding in front of you.
- Pasting only part of an escaped string: a fragment may end mid-escape and report an error that the full text would not have. Paste the complete escaped value.
- Copying the result back into an escaped context unchanged: if the destination expects escaped JSON inside a string, the clean text must be escaped again by the program that builds that string, not by hand.
Frequently asked questions
What is the difference between unescaping and formatting JSON?
Unescaping removes backslash escape sequences and restores the characters they stand for. Formatting keeps the same JSON and only changes spacing and line breaks to make it readable. Escaped text usually needs unescaping first, then formatting.
What does double-encoded JSON mean?
It means JSON text was encoded as a JSON string value, so the inner quotes and line breaks became escape sequences. Unescaping once removes the outer layer and reveals the inner JSON text.
Why does my output still contain backslashes?
Either the text was escaped twice and needs a second pass, or the backslashes are literal characters in the data, such as doubled backslashes that unescape to a single backslash. Check whether the remaining sequences still look like escapes.
Does unescaping fix invalid JSON?
No. It only reverses escape sequences. If the underlying text has missing commas or brackets, those errors remain and must be fixed in the unescaped result.
What happens with an invalid escape?
It is reported as an error instead of being guessed. Fix the escape in the source text, or paste the complete value if the text was cut off mid-escape.
What happens to unicode escapes?
Each four-digit unicode escape becomes the character it names, and paired escapes that form one character are combined. Other text, including characters already written directly, is left unchanged.
Does my text leave my device?
No. Unescaping runs in your browser, and pasted text is not uploaded or stored.



