Use the free Unicode Escape Decoder below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
What unicode escapes are
If you have ever opened a file and seen \u00e9 where you expected an é, you have met a unicode escape. It is a plain-text code that stands in for a character. Instead of storing the character itself, the file stores a backslash, a letter u, and four hexadecimal digits. Those digits are the character’s code point, its address in the unicode system. When software reads the escape, it swaps the code back for the real character. The trick lets files carry any character in the world while using only basic keyboard characters.
Escapes show up in many places. Programmers use them in source code for characters that are hard to type or invisible. Data files in JSON format use them for the same reason. Exported spreadsheets, translation files and log outputs sometimes escape characters too. The result is text that looks broken to a human even though a machine reads it perfectly. A decoder closes that gap: paste the escaped text, and it hands you back the readable version.
How this decoder works
Paste your text into the box and press Decode escapes. The tool scans for three escape shapes. The first is \uXXXX, four hexadecimal digits after \u, which covers most everyday characters. The second is \u{XXXX}, the braced form, which also handles characters beyond the basic range, including emoji. The third is \xXX, a two-digit form used in many programming languages. It also understands the simple escapes \n for a new line, \t for a tab and \r for a carriage return.
Each escape it finds is replaced with the real character, and the tool reports how many escapes it decoded. Anything that is not an escape is left exactly as it is. If your text has no escapes at all, the count is zero and the text comes back unchanged. That makes the tool safe to run on any text: it never guesses, and it never changes characters it was not asked to change.
Where escaped text comes from
JSON data is the most common source. A JSON file may store the word café as Caf\u00e9. That is valid JSON, and any JSON reader displays it as café, but if you open the raw file in a plain editor you see the escape. The same happens with emoji: a smiling face may appear as a surrogate pair, two \u escapes side by side. The braced form \u{1F600} is the cleaner modern way to write the same character, and this decoder handles both.
Developers also write escapes by hand in code. A string that must contain a quote mark uses an escape so the quote does not end the string early. A string with a newline uses \n. When you copy such a string out of code and into a document, the escapes come along, and the document shows backslashes instead of line breaks. Decoding first gives you the text the original author actually meant.
Common mistakes to avoid
One common mistake is decoding twice. If your text already contains a literal backslash followed by u, for example in a Windows file path or a regular expression, decoding will eat that sequence and replace it with a character you did not want. Always check the result, and keep a copy of the original until you are sure. Another mistake is assuming every backslash sequence is an escape. Only the shapes listed above are decoded; an unknown sequence is left alone rather than guessed at.
It also helps to know that not every character has a short escape. Characters outside the basic multilingual plane, including most emoji, need the braced form or a surrogate pair. If a decoder only handled four-digit escapes, an emoji written as a pair would decode into two meaningless halves. This tool handles the braced form directly, so emoji decode in one step.
When decoding helps most
Translators meet escaped text constantly, because translation files often escape accented letters. Decoding a file before translating makes the work faster and reduces errors, since the translator sees real words instead of codes. Support teams use decoders to read logs and error messages that contain escaped characters. Students use them to turn copied code strings into readable text for essays and notes.
Writers who paste content between tools also benefit. A snippet copied from a developer console, an API response or a data export often arrives fully escaped. One decode pass turns it into clean text ready for an article, an email or a document. Because the tool runs entirely in your browser, nothing you paste is uploaded anywhere, so even private text is safe to decode here.
Tips for clean results
Work on a copy, not the original file, until you have checked the decoded output. Watch out for double backslashes: a doubled backslash in the source means a literal backslash, and this decoder treats it as one, not as the start of an escape. If your text mixes escapes with real characters, decode it once and read the result carefully before using it anywhere important.
Finally, remember the direction of travel. Encoding turns characters into escapes; decoding turns escapes back into characters. If you need to go the other way, you need an encoder, not this tool.