GlyphIndexCompose an accent
NFC combines this U+0065 U+0301 sequence into its canonical composed form.
Input text é Result é — U+00E9
Unicode Normalizer
See exactly what normalization would change before you apply it. Your original text stays in the input.
Your text is processed on your device. This tool has no third-party scripts, and GlyphIndex never reads your clipboard automatically.
9 / 10,000 UTF-16 units Some characters count as two units.
JSON includes your input and the result. Keep the file private if the text is private.
CSV contains all inspection records. If the output exceeds 10,000 UTF-16 units, those records describe the input. Formula-leading cells start with an apostrophe; JSON keeps the exact text.
Inspection
Choose a grapheme cluster to see its code points.
| Character | Code points | Standard name | UTF-8 bytes | UTF-16 units |
|---|
Try an example
Decompose an accent
NFD exposes the base letter and combining accent. The number of code points changes even when the display looks similar.
Input text é Result é — U+0065 U+0301
Review compatibility changes
NFKC replaces mathematical bold A and MICRO SIGN with compatibility-equivalent values. Review whether those changes fit your task.
Input text 𝐀 µ Result A μ — U+0041 U+0020 U+03BC
A minus sign stays a minus sign
NFKC does not replace the minus sign with U+002D hyphen-minus. Normalization is not a general lookalike replacement.
Input text − Result − — U+2212, unchanged
Preview before applying
Choose a form, then Preview. Compare the original and proposed text along with their code points. Choose Apply when you want to use the result; copying and downloads then use that output.
| Form | Primary distinction |
|---|---|
| NFC | Canonical decomposition followed by composition. |
| NFD | Canonical decomposition. |
| NFKC | Compatibility decomposition followed by composition. |
| NFKD | Compatibility decomposition. |
Editing the input or changing the form clears the previous result. Run Preview again after either change, even if the text still looks the same.
Review the meaning of a change
Use the form required by your editor, application, or data workflow. Normalization cannot recover every damaged string or decide which distinctions you intended to keep.
The input limit is 10,000 UTF-16 units. Unpaired surrogates are rejected. Your browser performs the normalization; the Unicode name database supplies reference information rather than the normalization rules used at runtime.
Sources and method
- Unicode Standard Annex #15: Normalization Forms — Canonical and compatibility normalization and their limits.
- Unicode: UTF-8, UTF-16, UTF-32 and BOM — How Unicode values are represented in UTF-8 and UTF-16.