Unicode Normalization Checker

Compare normalization status, code-point counts, UTF-8 sizes, and normalized previews without silently changing the input.

Unicode 17 referenceGrapheme ≠ code pointUTF-16 / UTF-8 offsetsLocal inspection

Text to check

—NFC/NFD are canonical forms; NFKC/NFKD additionally apply compatibility mappings and can change presentation distinctions.

NFC/NFD/NFKC/NFKD code-point comparison

Compare all four Unicode normalization forms while keeping your input unchanged. Inspect code points, UTF-8 byte lengths and whether compatibility normalization changes the text representation.

Text

—NFC equals input

—NFKC equals input

—Input UTF-8 bytes

Form	Text	Code points	UTF-8 bytes

Normalization changes representation, not intended text

NFC/NFD and NFKC/NFKD can convert equivalent-looking Unicode sequences into standardized forms. Compatibility normalization can also change formatting distinctions, so do not apply it blindly to identifiers or data where the exact original code points are significant.

Compare all four normalization forms without rewriting input

NFC, NFD, NFKC and NFKD are compared with grapheme/code-point/UTF-16/UTF-8 metrics so canonical and compatibility changes are visible.

Unicode precision boundary

WebToolArc keeps grapheme clusters, Unicode code points, UTF-16 code units and UTF-8 bytes as separate measurements. Normalization follows the browser Unicode implementation; grapheme segmentation uses Intl.Segmenter when available. Property names shown by this tool are limited to the explicit local tables and JavaScript Unicode property escapes used by the page rather than claiming a complete Unicode Character Database name lookup.