What is Unicode Decode?

Source code and JSON files are full of escape sequences like "\u0048" standing in for real characters. The Unicode Decode tool resolves those escapes, turning "\u0048\u0065\u006c\u006c\u006f" into "Hello". The \u prefix followed by four hex digits is how JSON, JavaScript, Java, and many other formats represent any Unicode character using only ASCII.

You meet these escapes whenever data crosses a system boundary: an API returns "\u00e9" instead of "é", a Java properties file stores internationalized strings as escapes, or a minified script hides readable text behind \u sequences. Decoding reveals what the data actually says without running any code.

How to use

1. Paste the escaped text into the input. It can be a single escape, a JSON string value, or an entire file of escaped content.
2. The decoder finds every \uXXXX sequence (four hex digits) as well as the uppercase \UXXXXXXXX eight-digit form used by some languages.
3. Click decode. Each escape is replaced with its character; everything else — quotes, commas, plain text — passes through unchanged.
4. Copy the readable result for inspection, editing, or pasting back into your project.

Common use cases

• Reading API responses: APIs that escape non-ASCII characters return JSON full of \u sequences. Decode a response to verify the actual content during debugging.
• Editing i18n files: Java resource bundles and similar localization files store translations as escapes. Decode them to review wording in the real script.
• Analyzing minified code: Obfuscated JavaScript hides strings behind escapes. Decoding exposes URLs, messages, and identifiers for analysis.
• Cleaning data exports: Database dumps that escaped Unicode become human-readable again, making manual review and correction possible.

Example

Input:  Caf\u00e9 \u2615 — \u4e2d\u6587
Output: Café ☕ — 中文

FAQs

What is the difference between \u and \U escapes?

\u takes four hex digits and covers the Basic Multilingual Plane (the first 65,536 code points, including most everyday scripts). \U takes eight digits for characters beyond that range. The decoder handles both forms.

How are emoji decoded?

Emoji live outside the four-digit range, so they appear as surrogate pairs — two \u escapes back to back, like "\uD83C\uDF89" for 🎉. The tool recognizes valid pairs and combines them into the single intended character automatically.

Does it touch other escapes like \n?

No. Only Unicode escapes (\uXXXX, \UXXXXXXXX) are converted. Control escapes such as \n, \t, and \" are left exactly as written, so JSON structure stays valid and untouched.

Will it corrupt my JSON?

Decoding inside string values is safe, but running it over an entire JSON document converts escapes everywhere — including any inside keys. For whole-document work, decode, verify the result parses, and keep a backup of the original.