Browse the guides
Docs

Preview and apply text normalization

See what each normalization form changes. Compare the preview with your original text, then apply the result you want to keep.

ON THIS PAGE
  1. Choose a form for a specific purpose
  2. Compare a canonical-equivalence example
  3. Review compatibility changes carefully
  4. Apply the reviewed result

Choose a form for a specific purpose

Open Unicode Normalizer, paste a short sample, and choose a form. Select Preview to compare the proposed text with the original. Nothing becomes available to copy or download until you choose Apply.

FormOperationReview focus
NFCCanonical decomposition followed by composition.Canonical equivalents can converge on a composed representation.
NFDCanonical decomposition.A precomposed letter may become a base letter and combining marks.
NFKCCompatibility decomposition followed by composition.Review lost compatibility distinctions, including some styled characters.
NFKDCompatibility decomposition.Review both compatibility changes and decomposed sequences.

Compare a canonical-equivalence example

Copy this decomposed e + combining acute accent. Its code points are U+0065 U+0301.
é
The two results may look the same while using different sequences.
FormResult for the sampleCode points
NFCéU+00E9
NFDéU+0065 U+0301

Read the output values as well as the glyph. If the counts are unfamiliar, compare code points and grapheme clusters. “Unchanged” means the selected form left this input as it was; it does not validate the text for every application.

Review compatibility changes carefully

Copy this sample, choose NFKC, then Preview. Expected output: é A μ −.
é 𝐀 µ −
OriginalNFKC resultDecision to make
𝐀 — U+1D400A — U+0041Is losing the mathematical bold character appropriate here?
µ — U+00B5μ — U+03BCDoes the destination require this exact normalized sequence?
− — U+2212− — U+2212The minus sign is not turned into U+002D hyphen-minus by NFKC.

The first two examples change under compatibility normalization. That can be useful for a defined comparison task, but it is not a reason to rewrite a document without review. The last example prevents a common assumption: normalization does not replace every similar-looking mark with a familiar keyboard character.

NFKC preview shows the original and normalized code points with Apply separate from Copy.
Actual browser before Apply: the original input is retained and copying and downloads remain disabled.

Apply the reviewed result

  1. Preview

    Run the chosen form and compare the original and output code points.

  2. Review

    Read the compatibility warning for NFKC or NFKD and check whether each change is appropriate.

  3. Apply

    Use the separate Apply action when the proposed result is the one you want.

  4. Copy or export

    Copy the reviewed result or save it locally, while retaining the original separately if needed.

Changing the source text or selected form requires a new preview. Do not rely on an old result after editing the input. If you need to compare a result in more detail, copy that result into Unicode Inspector and look at its individual code points.

Sources and method

Copy manually

Couldn’t copy automatically. Select the text below and use your device’s Copy command.

Use your device’s Copy command, then paste the text where you need it.

Character details

Code points
UTF-8 bytes
View character details

Appearance can vary by font.

Your saved symbols

Save symbols for another visit in this browser. They won’t appear on your other devices or browser profiles.