Unicode Decode: Fix Garbled Text in Logs and APIs

If you see text like \u00e9 or \u2014 in logs, you are looking at escaped Unicode, not the final characters. Decode it before you debug the message itself. Otherwise you might be chasing encoding noise instead of a real bug.

Use the Unicode Decoder to turn escapes back into readable text.

Quick steps

1. Paste the escaped string (from JSON, logs, or source code).
2. Decode it in the tool.
3. Copy the readable output and continue debugging.

What you are fixing

Escapes are common in JSON APIs, JavaScript string literals, and log pipelines that serialize Unicode for ASCII-safe transport.

Examples

ASCII word from escapes

Input:

\u0048\u0065\u006c\u006c\u006f

Output: Hello

Punctuation in a log line

Input:

Hello\u2014world

Output: readable text with an em dash between Hello and world

JSON string field (paste the escape sequence only, or the quoted value)

Input:

\u00e9

Output: é

If the whole payload is JSON, format it first with JSON Formatter, then decode individual string values.

Common mistakes

• Double-escaped strings. Some logs escape backslashes twice (\\u2014). You may need to decode more than once or unescape the source format first.
• Mixed encodings. If the string is already valid UTF-8 text, running a Unicode decoder may not change anything. That is expected.
• Wrong tool first. URL-encoded text (%C3%A9) needs URL Decode. Base64 blobs need Base64 Decode.

Verification checklist

• Confirm the output shows the characters you expect (accents, dashes, emoji).
• If output still looks wrong, check whether the upstream step used URL encoding or HTML entities (HTML Decode).

When to use something else

• Encode text to escapes: use Unicode Encoder.
• Invalid JSON structure: fix JSON before decoding nested fields.