Unicode text normalization

How it works

Apply the selected Unicode normalization form. NFC/NFD use canonical equivalence; NFKC/NFKD also apply compatibility mappings.

Input definitions

Unicode text: Plain text; maximum 200,000 characters.
Normalization form: Choose NFC / NFD / NFKC / NFKD.

A worked example

Unicode text: é
Normalization form: NFC

Assumptions & limits

Plain Unicode text, at most 200,000 UTF-16 code units. Compatibility forms can change meaningful distinctions; preserve the original.

Sources & review

Maintained by AnsRio. Methods and examples use automated checks; this does not imply independent professional certification.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize ↗

Method updated 2026-10-17. Content checked against the stated method and examples. Our verification approach.

Common questions

Should I choose NFC or NFKC?

NFC combines canonically equivalent sequences while retaining compatibility distinctions. NFKC also folds compatibility characters, which may change intended typography or identifiers. Keep an original copy.

Can I paste formatted documents into this text tool?

The tool processes plain text. Styling, document structure and rich-text metadata are not preserved. Copy the result before closing the page.

How does the Unicode text normalization tool work?

Apply the selected Unicode normalization form. NFC/NFD use canonical equivalence; NFKC/NFKD also apply compatibility mappings.

What are the assumptions and limits of Unicode text normalization?

Plain Unicode text, at most 200,000 UTF-16 code units. Compatibility forms can change meaningful distinctions; preserve the original.