Standard forms before optional cleaning
Text & encoding
How it works
Unicode can represent é as one code point or as e followed by a combining acute accent. Canonical normalization makes equivalent sequences consistent. NFC composes where possible; NFD decomposes. Neither is a spelling correction.
NFKC and NFKD also apply compatibility mappings, such as Ａ to A and ① to 1. This can remove meaningful distinctions. ASCII transliteration is a separate, lossy operation that approximates writing systems; it is not language translation.
What you can do
Choose any of the four standard forms and compare their output before optional cleaning. Mark removal decomposes text and removes combining marks while keeping variation selectors. Format-control removal keeps U+200C and U+200D joiners. ASCII transliteration can remove unsupported symbols.
How to use it
- Paste text or open a UTF-8 file and choose the normalization form.
- Leave optional cleaning off for standard normalization. Enable only the changes you need, then Apply and compare the standard-form previews.
- Copy or download the result. Use result as input to continue; Undo restores the prior input and settings.
Errors and limits
Removing marks can change words in Arabic, Indic and other scripts. Removing format controls changes bidirectional behavior. Keep an original copy before cleaning.
NFKC does not resolve every visually similar letter. A Cyrillic а and Latin a remain different characters. Inspect suspicious text instead of treating normalization as an anti-phishing guarantee.
Frequently asked questions
Which normalization form should I choose?
Use the form required by the receiving system. NFC is a common interchange choice; use compatibility forms only when those distinctions may be discarded.
Will normalization remove accents?
Standard normalization preserves accents. The optional mark-removal control removes them deliberately and can also affect other writing systems.