DocomintNormalize Unicode
Convert text to a standard Unicode normalization form (NFC, NFD, NFKC, or NFKD).
What is a Normalize Unicode?
The same visible letter can be stored as different byte sequences in Unicode — a precomposed é versus an e followed by a combining accent mark, for instance — which can silently break string comparisons or search. Normalizing to one consistent form (NFC is the web's default) fixes that.
How to use the Normalize Unicode
- Paste text that may contain composed or decomposed characters
- Pick a normalization form
- The normalized text appears instantly, on your device
Example
An é typed on some systems is one codepoint (U+00E9); on others it's two (e + combining accent, U+0065 U+0301). NFC output always uses the single-codepoint form, so both versions become identical, comparable strings.
Frequently asked questions
Which normalization form should I use?
NFC (composed) is the web's recommended default and what most browsers and databases already expect. Use NFD/NFKD if you specifically need decomposed characters for a downstream process like accent stripping.
Is my text uploaded anywhere?
No — Normalize Unicode runs entirely in your browser using JavaScript/WebAssembly. Your text is never sent to a server.
How would this actually cause a bug, in practice?
A search feature comparing user input against stored text can silently fail to match — the visible characters look identical, but if one was typed as NFC and the other stored as NFD, a strict string comparison says they're different, even though no human would notice.