Unicode Normalizer
Unify equivalent forms via NFC, NFD, NFKC or NFKD
NFCsame as input0 / 0
—
Canonical composition: combines what it can, so é becomes one code point. The default for the web and filenames.
NFDsame as input0 / 0
—
Canonical decomposition: é splits into e plus a combining accent. Use it for per-character work or stripping accents.
NFKCsame as input0 / 0
—
Compatibility composition: the fi ligature becomes fi, ① becomes 1, full-width becomes ASCII. Formatting is lost, which suits search and matching.
NFKDsame as input0 / 0
—
Compatibility decomposition: apply compatibility mappings, then decompose everything. The most aggressive form.
The same character can be written more than one way: the é in café is either U+00E9 or e plus combining U+0301 — identical on screen, unequal under ==, which is why searches miss and filenames duplicate. Canonical forms (NFC/NFD) only move between these spellings without changing meaning. Compatibility forms (NFKC/NFKD) also replace ligatures, circled digits and full-width characters with basic ones, which is lossy — good for normalizing before a search, not for storing the original.
All processing happens locally in your browser. Your data is never uploaded to a server.