Unicode tools
Unicode Normalizer
Make canonically equivalent text consistent while keeping compatibility changes explicit.
Tool overview
How canonical and compatibility normalization differ
Unicode Normalizer uses the browser Unicode normalization implementation. NFC composes canonical sequences, NFD decomposes them, and NFKC or NFKD also apply compatibility mappings that may change width, typography, or meaning. Optional whitespace, line-ending, BOM, and combining-mark changes are independent and visible in the comparison.
Standardize canonically equivalent text
- Standardize accented text before matching
- Compare composed and decomposed strings
- Normalize full-width compatibility characters
- Prepare predictable line endings for text exchange
Choose and inspect a normalization form
- Paste text containing the Unicode forms you want to standardize.
- Choose NFC, NFD, NFKC, or NFKD.
- Optionally normalize line endings, selected spaces, or BOMs.
- Review counts and changed positions before copying the result.
Canonical, compatibility, whitespace, and marks
- NFC is the conservative composed form commonly used for stored text.
- NFD keeps canonical characters decomposed into base characters and marks.
- NFKC and NFKD apply compatibility mappings and can alter visual or semantic distinctions.
- Combining marks are removed only when the explicit destructive option is enabled.
Compose a combining sequence with NFC
Café Full
Café Full
Compatibility changes and removed diacritics
- Normalization does not translate, case-fold, or visually confusable characters.
- Compatibility forms can replace full-width and presentation variants.
- Removing combining marks can remove accents and other meaningful notation.
- Changed-position comparison aligns code points by index rather than performing linguistic diffing.
Browse all unicode tools tools →
Questions
Unicode Normalizer FAQ
Which form should I choose for ordinary text?
NFC is usually the safest starting point because it preserves canonical meaning while composing common sequences.
Why is compatibility normalization highlighted as destructive?
NFKC and NFKD can replace characters chosen for width, style, or semantic distinction with compatibility equivalents.