Unicode Normalizer

Paste text to compare canonical and compatibility normalization. See NFC, NFD, NFKC, and NFKD output with code point-level differences.

Input textNFC · NFD · NFKC · NFKD

NFC

Café Å ①
ChangedInput 8 code pointsOutput 8 code points
#InputNFC
5Å U+212BÅ U+00C5

NFD

Café Å ①
ChangedInput 8 code pointsOutput 10 code points
#InputNFD
3é U+00E9e U+0065
4 U+0020́ U+0301
5Å U+212B U+0020
6 U+0020A U+0041
7① U+2460̊ U+030A
8∅ U+0020
9∅① U+2460

NFKC

Café Å 1
ChangedInput 8 code pointsOutput 8 code points
#InputNFKC
5Å U+212BÅ U+00C5
7① U+24601 U+0031

NFKD

Café Å 1
ChangedInput 8 code pointsOutput 10 code points
#InputNFKD
3é U+00E9e U+0065
4 U+0020́ U+0301
5Å U+212B U+0020
6 U+0020A U+0041
7① U+2460̊ U+030A
8∅ U+0020
9∅1 U+0031

About this tool

Unicode Normalizer helps developers, localization testers, and data cleanup teams convert text into NFC, NFD, NFKC, and NFKD forms while showing exact Unicode code point differences. Use it for accent composition checks, compatibility character cleanup, search indexing, slug preparation, and text debugging workflows where invisible normalization changes matter.

Use cases

  • Compare composed and decomposed accents before debugging why two visually identical strings fail equality checks.
  • Convert compatibility characters such as circled digits, full-width forms, or Angstrom symbols into NFKC or NFKD output for indexing and cleanup notes.
  • Copy normalized Unicode forms into tests, fixtures, documentation, or support tickets.

FAQ

What does Unicode Normalizer output?

It returns NFC, NFD, NFKC, and NFKD versions of pasted text, plus code point lists and differences from the original input.

When should I use NFC versus NFD?

NFC prefers composed canonical characters, while NFD decomposes canonical characters into base characters and combining marks when possible.

What is compatibility normalization?

NFKC and NFKD also fold compatibility characters, which can change symbols such as circled numbers or presentation forms into more ordinary text.