ENRU

Unicode Unescape

You see \u00e9. I see é.

Input

Paste a response full of \u escapes. I’ll make it readable.

Ctrl+Enter runs · drop a file on this pane

Every \u is a letter in disguise. I don’t do disguises.
— JSON Statham
OutputText
Example: \u00fc in, ü out. Nothing else changes.
Waiting for text with \u escapes.
Ln 1, Col 11:10 Blocal

Paste text full of \uXXXX escapes — a response body from the DevTools Network tab, a log line, a Python repr — and read it as plain text. Only the escapes change: spacing, key order and numbers stay byte for byte, so valid JSON stays valid. It runs in your browser; nothing is sent.

How to convert Unicode escapes to text

  1. Copy the response in DevTools (Network, then Response) and paste it here. Escapes switch the direction to To text on their own.
  2. Read the result. Quotes, backslashes and control characters stay escaped so the JSON stays valid; invisible characters stay as \u and are named.
  3. Copy it, download it, or open it in the Formatter to indent it. Swap turns the text back into \uXXXX escapes.

Why DevTools shows \u0430 instead of letters

The server escaped them. PHP json_encode does it unless you pass JSON_UNESCAPED_UNICODE; Python json.dumps does it while ensure_ascii is on; Java and .NET serializers often escape everything outside ASCII; Go escapes <, > and & as \u003c, \u003e and \u0026. The JSON is valid and means the same thing — it is just unreadable. Turn those options off at the source, or read it here.

Unicode unescape FAQ

Does it change anything besides the escapes?

No. The text is not parsed and printed again: each escape is replaced where it stands, and every other character stays where it was. A surrogate pair such as \ud83d\udcaa becomes one character, an emoji.

Why are some escapes still there?

Some characters can’t appear raw inside a JSON string: quotes, backslashes and control characters such as \u000a. Invisible ones — zero-width spaces, the BOM, text direction marks — stay escaped too, so you can see them; turn off Keep invisible to decode them. Half of a surrogate pair is not a character at all, so it stays as written.

What about \\u0418, \xd0\x9f and \U0001F600?

Double-escaped text — JSON inside a JSON string — is decoded one level deeper when it has no ordinary escapes. \x escapes, as in nginx logs and Python bytes, are read as UTF-8. \U0001F600 from Python and C and \u{1F600} from JavaScript are decoded too.

Is my text sent anywhere?

No. The page works in your browser and makes no requests to our API. Usage statistics tied to a random device ID record how many characters were decoded, never the text. Format in Formatter is your call: it hands the text to the Formatter, which uses our API.

Other tools

Keyboard shortcuts

Everywhere
Ctrl+EnterRun the page’s main action
Ctrl+OOpen a file
Ctrl+SDownload the result
F8 / eJump to the error
/Focus the input
wWrap lines
cCopy the output
qAnother quote
?This help
EscClose

Keys like c, q, w work when the cursor isn’t in an editor.