Skip to content

Choose your path

Built around the job you need to finish

Decode complete U+ or Unicode-escape notation with explicit syntax, scalar validation and surrogate pairing, preserving encoded controls and refusing silent fragment loss.

Support engineer

Recover text only when every supplied token is understood.

Try U+0041 lost U+110000 U+0042, correct the token sequence and inspect output.

Unknown text and invalid scalars fail explicitly rather than disappearing.

Internationalization tester

Decode astral and combining sequences faithfully.

Select escapes, compare paired UTF-16 with braced notation and test an unpaired surrogate.

Valid forms decode equally; incomplete pairs are refused.

Mobile fixture reviewer

Review encoded whitespace and keep a recoverable source.

Import notation, remove a file BOM explicitly, inspect control labels and export beyond one page.

Encoded whitespace is retained while syntax separators are not added to output.

Was this tool helpful?

Reference & details

How it works

Parse the whole source

U+ mode accepts 4–6 hexadecimal digits per token. Escape mode accepts fixed four-digit or braced 1–6-digit Unicode escapes, not arbitrary JavaScript or JSON.

Validate scalar values

U+ and braced forms refuse surrogates and values above U+10FFFF. Fixed high surrogates require an immediately adjacent low-surrogate escape.

Review exact decoded text

Syntax whitespace separates tokens; encoded whitespace becomes output. BOM and controls are retained when explicitly encoded, labeled in the scalar table and included in full text export.

Updated: August 2026

Example Scenarios

Recover text only when every supplied token is understood. Try U+0041 lost U+110000 U+0042, correct the token sequence and inspect output.

Decode astral and combining sequences faithfully. Select escapes, compare paired UTF-16 with braced notation and test an unpaired surrogate.

Review encoded whitespace and keep a recoverable source. Import notation, remove a file BOM explicitly, inspect control labels and export beyond one page.

Common Mistakes to Avoid

Assuming unmatched source can be ignored

Correct every malformed token; partial recovery would silently lose data.

Using visual spaces to encode output spaces

Use an explicit space code point. Formatting whitespace between tokens is syntax only.

FAQ

All source must match the chosen syntax. Words, commas and unknown escapes are not silently discarded, even when other tokens are valid.

Yes, in Unicode escapes mode. U+ mode is separate; surrounding quotes and general escapes such as backslash-n are not accepted.

Use U+000A or U+0020, or their Unicode escape equivalents. Whitespace between notation tokens is only a separator.

Not as U+ or braced scalar values. Fixed UTF-16 escapes accept a valid immediately adjacent high/low pair; lone or separated pairs fail.

UTF-8 import retains a file BOM, which can be removed explicitly with undo. Encoded U+FEFF remains data. Download requests a UTF-8 text file containing the complete decoded result, not just visible rows; verify the actual saved file.

About Unicode to Text

Recover text from an explicit notation, not from whatever fragments happen to match. Choose the syntax, correct every reported error and inspect the decoded scalars before exporting.