Reading an escaped JSON string
A strict serialiser escapes non-ASCII characters. Unescaping shows the real accented or emoji content.
Convert Unicode escape sequences back into readable characters in your browser.
Maintained by Roshan.
Converts escaped text to text in this tab, with nothing sent anywhere.
Find related browser-local tools for nearby tasks without starting another search.
Browse all developer and data toolsUnescaping reverses the process: it takes text peppered with backslash-u codes and turns them back into the characters they represent, so an accented word or an emoji stored as an escape sequence reads normally again. You meet escaped text wherever a file or a stream had to stay ASCII - JSON that a strict serialiser produced, a log line, a translation file, a value copied out of source code. Reading it in escaped form is nearly impossible past a word or two. This tool recognises both the standard four-hex-digit form and the brace form used for characters above the basic plane, converting each back to its real character, while leaving everything that is not an escape sequence exactly as it is.
A strict serialiser escapes non-ASCII characters. Unescaping shows the real accented or emoji content.
A string literal written with escapes converts back to what it actually contains.
Yes. Both the four-digit form and the brace form for high code points are converted.
It may be left as written rather than guessed at, since an incomplete escape is ambiguous.
No. Those are a different scheme with their own decoder. This handles backslash-u escapes.
Yes. With no escapes present, nothing changes.
Convert text into Unicode escape sequences in your browser, handling characters above the basic plane.
Decode HTML entities back into plain text in your browser, including numeric and named forms.
Convert hexadecimal back to text in your browser. Accepts spaced, joined and 0x-prefixed hex.