Unicode code point inspector

How to use this tool

Paste text to see each original code point as U+ notation, its decimal value and its UTF-8 byte sequence. The result shows UTF-16 length and all four normalized forms, using your browser’s Unicode implementation. Control characters are displayed as JSON-escaped strings.

NFC and NFD preserve canonical equivalence; NFD decomposes characters, while NFC composes them where a canonical form exists. NFKC and NFKD also apply compatibility mappings, which can remove distinctions such as fullwidth letters, ligatures and circled numbers. Review the result before replacing text with a compatibility form. Normalization is not case folding or a confusable-character security check.

A visible character can contain several code points, especially combining accents and emoji sequences. This tool counts code points, not grapheme clusters, and does not assign Unicode character names. Lone UTF-16 surrogates are identified explicitly because they are not valid Unicode scalar values.

Worked example

NFC converts e + U+0301 into é; NFD converts é into that two-code-point sequence. For Ａ fi ①, NFKC and NFKD produce A fi 1; NFC and NFD keep those compatibility distinctions.

References and method

• Unicode: normalization forms
• ECMAScript: String.prototype.normalize
• Unicode Standard Annex #29: text segmentation

Contifield is an independent utility site. Reference publishers do not endorse this tool.