Localization engineer
See why an accented glyph or emoji has multiple components.
Encode emoji plus decomposed e-accent and compare scalar, UTF-16 and UTF-8 columns.
Combining marks and offsets are visible without normalization.
Text to Unicode
Inspect Unicode scalars, UTF-16 units and UTF-8 bytes. Encode text as U+ tokens or Unicode escapes, preserve hidden characters, and export complete notation.
Choose your path
Built around the job you need to finish
Inspect exact Unicode scalars and encode them as U+ notation, braced escapes or paired UTF-16 escapes without conflating glyphs, units and bytes.
Developer writing fixtures
Choose the notation expected by a receiving system.
Compare U+ tokens, braced escapes and fixed surrogate pairs; choose case and separators.
Astral characters remain valid pairs or scalar escapes.
Mobile text inspector
Find hidden characters without losing the complete source.
Import BOM/CRLF text, inspect labeled controls, page many scalars and restore a prior run.
Invisible data is labeled and complete output remains recoverable.
Authoritative checks for this tool
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
- Unicode scalar values and encoding formsUnicode Consortium · Scalar values exclude surrogate code points; UTF-16 units and UTF-8 bytes are distinct from visible grapheme clusters.
- Unicode escape syntaxEcma International / TC39 · Four-digit and braced Unicode escape forms. This tool parses only the disclosed notation, not arbitrary JavaScript or complete JSON strings.
- Encoding StandardWHATWG · UTF-8 byte encoding and fatal decoding, including explicit BOM handling; ASCII here is separately constrained to 0–127.
Was this tool helpful?
Related Tools
Tools you might need next
Unicode to Text
Decode complete U+ tokens or Unicode escapes into text. Validate scalars and surrogate pairs, inspect hidden characters, and refuse silently discarded input.
Operations
Binary to Text
Decode binary bytes with strict UTF-8 or ASCII validation. Choose token grouping and BOM handling, inspect every byte, and export the complete decoded text.
Operations
Morse Code to Text
Decode complete Morse tokens with explicit slash or line-break word boundaries. Refuse unknown signals, inspect character rows, and export the full transcript.
Operations
Reference & details
How it works
Updated August 2026
How it works
Updated August 2026Preserve scalar sequences
Validate paired UTF-16 source, iterate complete code points and retain combining marks, format characters and line endings.
Choose notation
U+ uses 4–6 hexadecimal digits. Braced escapes use scalar values; fixed escapes emit adjacent surrogate pairs for astral characters. Hex case and token separators are explicit.
Inspect units
Each review row is a scalar, not a grapheme cluster. It shows a visible label, U+ value, UTF-16 units, UTF-8 bytes and original UTF-16 offset.
Updated: August 2026
Example Scenarios
See why an accented glyph or emoji has multiple components. Encode emoji plus decomposed e-accent and compare scalar, UTF-16 and UTF-8 columns.
Choose the notation expected by a receiving system. Compare U+ tokens, braced escapes and fixed surrogate pairs; choose case and separators.
Find hidden characters without losing the complete source. Import BOM/CRLF text, inspect labeled controls, page many scalars and restore a prior run.
Common Mistakes to Avoid
Common Mistakes to Avoid
Reading scalar count as visible-character count
Check the individual components; a grapheme can contain several code points.
Pasting notation into a format without checking syntax
Choose the receiver's accepted escape format and add any required string-literal framing separately.
FAQ
A grapheme can contain several scalars, such as an accented letter or emoji family. Rows do not claim to count user-perceived characters.
Use U+ for code-point notation, braced escapes for scalar escape syntax, or fixed escapes when the receiver needs UTF-16 units. Verify the receiving format.
Astral scalars become an adjacent high/low surrogate pair. Unpaired source surrogates are refused.
No. It is notation only, without surrounding quotes or general string-literal escaping. Braced escapes are not JSON syntax.
No normalization or trimming is applied. Review rows are capped at 200 but full output is retained. Import/export are UTF-8 text; clipboard or textarea editing can normalize line endings.
About Text to Unicode
Make the structure of multilingual text visible. Select a notation and compare scalars, UTF-16 offsets and UTF-8 bytes without normalizing or trimming your source.