Unicode Normalization: NFC, NFD, NFKC and NFKD
Quick copy
Details for U+0065 U+0301
LATIN SMALL LETTER E + COMBINING ACUTE ACCENT
Exact sequence: é
U+0065 U+0301
Details for U+FB00
LATIN SMALL LIGATURE FF
Exact sequence: ff
U+FB00
Click a character to copy it. Use Details for its technical record.
Choose normalization according to the distinctions your application needs to preserve. NFC, NFD, NFKC and NFKD are explicit transformations, never hidden steps in copying.
NFD applies canonical decomposition and ordering. NFC also composes eligible pairs. Canonically equivalent input can therefore produce different scalar counts before normalization, while producing the same normalized result.
NFKD additionally applies compatibility decomposition. NFKC applies compatibility decomposition and canonical composition. These forms can remove distinctions such as a ligature or fullwidth presentation. The ligature ff becomes two f characters under compatibility normalization.
The table below shows exact scalar results using pinned Unicode 17 data. Compare the originals before choosing a transformation. Normalization does not restore missing accents, translate text or prove spelling correctness.
Exact examples
Details for U+FF21
Exact sequence
Exact sequence: Ａ
U+FF21
Details for U+3070
Exact sequence
Exact sequence: ば
U+3070
| Original code points | NFC | NFD | NFKC | NFKD |
|---|---|---|---|---|
U+0065 U+0301 | éU+00E9 | éU+0065 U+0301 | éU+00E9 | éU+0065 U+0301 |
U+FB00 | ffU+FB00 | ffU+FB00 | ffU+0066 U+0066 | ffU+0066 U+0066 |
U+FF21 | ＡU+FF21 | ＡU+FF21 | AU+0041 | AU+0041 |
U+3070 | ばU+3070 | ばU+306F U+3099 | ばU+3070 | ばU+306F U+3099 |
Try the normalizer · Split clusters · Inspect encoded candidates · Precomposed and combining text
Sources, versions and limits
- Encoded properties
- Properties use Unicode 17.0.0. Normalization follows UAX #15; grapheme boundaries follow UAX #29. Script associations describe encoded properties, not language use.
- Language evidence
- CLDR 48.2and the IANA registry dated 2026-08-08. Main and auxiliary exemplars are distinct. CLDR exemplars are not complete orthographies.
- Review and limitations
- The dataset is derived from the sources above. Editorial guides cite additional scoped authorities. No native or specialist orthography approval is implied. Release scope date: 14 September 2026. Historic or specialist usage needs separate evidence. Registry-only records have unknown orthography in this release.
- Reproduction and corrections
- Downloads and licences · Coverage and held routes · Suggest a source-backed correction