Input
Mode:
Output
Formatted result will be displayed here
Unicode to text decoding walks the input and replaces any \uXXXX sequence with the character at that code point, combining surrogate pairs where they appear so supplementary characters like emoji come out intact. This tool tolerates a mix of escaped and literal content, so you can paste a JSON value or a JavaScript source fragment directly and get the readable form back, including proper handling of \n, \t, and other common control escapes.
Old logging pipelines emit non-ASCII as \u escapes; decode to see which language or user the event really came from.
Production JavaScript often escapes strings for safety. Decode a suspicious literal to understand what it actually contains.
Resource bundles shipped as escaped text become reviewable once decoded, making typos and wrong characters easy to spot.
Decoding an escape confirms whether the character is a Latin A or a Cyrillic one, which matters for security reviews.
Standard \uXXXX and ECMAScript \u{XXXXX} for codepoints above the BMP, plus common single-letter escapes like \n and \t.
Yes. Two consecutive \uXXXX that form a valid surrogate pair are combined into the astral-plane codepoint they represent.
The bad sequence is left intact and a warning is shown so you can track down the source before shipping.
Yes. Decoding and re-encoding with the same settings reproduces the original input byte-for-byte.