Omnikit
DevFilesMoneyAll toolsExams
Ctrl K
Dev toolsFile toolsMoney calculatorsAll toolsExams
HomeDeveloper toolsUnicode Normalizer: NFC, NFD, NFKC and NFKD Online

Unicode Normalizer: NFC, NFD, NFKC and NFKD Online

dev

Normalize text to NFC, NFD, NFKC or NFKD, see what changed, or strip accents

Runs in your browser. Nothing you type is sent anywhere. Checked against sources on 16 Nov 2026.
What this does
Normalize text to NFC, NFD, NFKC or NFKD, see what changed, or strip accents.
What it does not do
It does not need an account or a sign-in.
What leaves your browser
Nothing you type or open leaves your device. The page sends only a usage count: the tool’s name and the action, never the content.

Checked against the tool’s code on 18 November 2026. Figures read from their sources on 16 November 2026. What we collect

A Unicode normalizer rewrites text in one standard form so equal-looking strings compare equal. In the example, NFC joins the split "e" and its accent into one character, 15 code points to 14; NFKC also turns fullwidth letters, the "fi" ligature and a circled 1 into plain text, giving "Café Tea file 1" and 26 bytes down to 16.

The example "Café Tea file ①" in each form
FormWhat it doesCode pointsUTF-8 bytes
NFCjoins a letter and its accent into one character where Unicode has one15 to 1426 to 25
NFDsplits each accented letter into the letter and its combining accent15 to 1526 to 26
NFKCalso turns fullwidth, circled, superscript and ligature forms into plain characters, then composes15 to 1526 to 16
NFKDturns compatibility forms into plain characters and splits accents off15 to 1626 to 17
The input has "é" typed as e plus a combining accent, fullwidth Tea, the fi ligature and a circled 1. Computed by the tool itself.

Nothing is uploaded: this runs in your browser.

Next:
  • URL Parser & Query Editor Split a link into its parts, edit the parameters and rebuild it
  • Invisible Character Copy and Paste: Blank Text Copy a blank character in one tap: Hangul filler, braille blank, zero-width space

How to normalize Unicode text to NFC or NFKC

1

Paste the text into the box; an example with a split accent and fullwidth letters is already there.

2

Pick the form: NFC for storage and comparison, NFKC to fold fullwidth and styled forms too.

3

Read the table of changes: each character before and after, with its code points.

4

Press Copy result, or paste a second string under Compare with to see why the two do not match.

Why two strings that look the same do not match

Unicode often has two ways to write the same thing. The letter é can be one character, U+00E9, or two: a plain e followed by the combining acute accent U+0301. They look identical and print identically, but a database lookup, a file name check or a password compare sees different bytes and says they differ. Text pasted from a Mac, a PDF or a phone keyboard is a common source of the split form.

Normalization picks one spelling. NFC composes (one character where Unicode has one) and is what the web and most databases expect. NFD decomposes. NFKC and NFKD also fold compatibility forms, such as fullwidth T, the fi ligature, superscript ² and circled ①, into plain characters, which is right for search and user names but loses formatting.

In short

Question Answer
Forms NFC, NFD, NFKC and NFKD, as defined by Unicode Standard Annex #15
What it shows Each changed character before and after, with code points, and the byte counts
Remove accents Decomposes, drops the combining marks: "Crème brûlée à São Paulo" becomes "Creme brulee a Sao Paulo"
Compare Says whether two strings are equal as typed, after NFC, or only after NFKC
Where it runs In your browser, with its own Unicode tables; nothing is uploaded

Checked on 16 November 2026 against Unicode Standard Annex #15. Page last updated on 16 November 2026.

Which form to choose

Store and compare in NFC unless you have a reason not to. Use NFKC for search keys and identifiers, where a fullwidth or styled letter should match its plain twin. For lookalike letters from other scripts, which no normalization form changes, use the homoglyph detector; for hidden characters, the Invisible Character Detector.

Frequently asked questions

What does a Unicode normalizer do?

A Unicode normalizer rewrites text in one of the four standard forms, so the same text always has the same bytes. NFC joins a letter and its accent into one character; NFKC also turns fullwidth, ligature and circled forms into plain letters. Strings that looked equal then compare equal in code and databases.

What is the difference between NFC and NFD?

Both keep the meaning and the look. NFC composes: é is stored as the single character U+00E9. NFD decomposes: é becomes e followed by the combining accent U+0301. The example shows NFC turning 15 code points into 14. Most web pages, databases and Windows expect NFC.

What is the difference between NFC and NFKC?

NFKC does everything NFC does and also replaces compatibility characters with their plain equivalents: fullwidth T becomes T, the fi ligature becomes fi, ① becomes 1 and ² becomes 2. The example becomes "Café Tea file 1". Use NFKC for search and usernames, NFC for storing text as written.

Why do two identical strings not match in my code?

One of them probably holds a split accent or a compatibility character. Paste the first string in the box and the second under Compare with: the page says whether they are equal as typed, equal after NFC, or equal only after NFKC. Normalize both sides before comparing to fix the bug.

How do I remove accents from text?

Tick Remove accents. The text is decomposed and every combining mark is dropped, so "Crème brûlée à São Paulo" becomes "Creme brulee a Sao Paulo". Letters with no separate accent, such as ø or ß, are kept as they are, since Unicode does not split them.

Does normalization fix lookalike letters such as Cyrillic а?

No. A Cyrillic а (U+0430) is a different letter from the Latin a in every normalization form, so NFKC keeps it. Lookalike letters are found by a homoglyph detector instead, which compares characters against the Unicode confusables list and names the letter each one imitates.

How do I normalize Unicode in JavaScript or Python?

JavaScript has text.normalize('NFC'); Python has unicodedata.normalize('NFC', text); Java has java.text.Normalizer. This page uses the same JavaScript call, so the result here matches what your browser code produces. The table of changes helps when you need to see which characters a call altered.

Sources

  • Unicode Standard Annex #15, Unicode Normalization FormsThe four forms NFC, NFD, NFKC and NFKD and what each does

Last verified 16 November 2026.

Rates and rules change; check the source before you rely on a figure.

Still stuck? Ask about Unicode Normalizer: NFC, NFD, NFKC and NFKD Online and anybody who knows can answer. No account needed.

Same job, other tools: Remove Tracking Parameters – Strip utm, fbclid and gclid from a link before you share it · JSON Minifier – Strip whitespace from JSON for production · Base64 Decode – Turn Base64 back into text or a downloadable file · Base64 Encode – Turn text or a file into Base64.

On the related tools: JWT Decoder – Paste a token to read its header, payload and expiry.

On the same topic: Invisible Character Detector – Find zero-width spaces, odd spaces, bidi controls and lookalike letters, then clean them · Homoglyph Detector – Homoglyph detector: Cyrillic, Greek and styled letters posing as Latin in names and links · Invisible Character Copy and Paste: Blank Text – Copy a blank character in one tap: Hangul filler, braille blank, zero-width space.

Related tools

All developer tools
URL Parser & Query EditorSplit a link into its parts, edit the parameters and rebuild itInvisible Character Copy and Paste: Blank TextCopy a blank character in one tap: Hangul filler, braille blank, zero-width spaceJSON Formatter & ValidatorFormat, validate, minify and sort JSON with exact error positionsBase64 Encode & DecodeText and files to Base64 and back, with URL-safe mode and image previewJWT Decoder, Verifier & EncoderDecode any JWT, verify its signature, and sign new tokens, all in your browserPassword GeneratorStrong random passwords and memorable passphrases, generated on your deviceUUID GeneratorRandom v4 and time-ordered v7 UUIDs, up to 1,000 at once, plus a validatorUnix Timestamp ConverterUnix timestamps to dates and dates to timestamps, in any time zone
Was this tool helpful?
Omnikit

Small jobs, done in your browser. Free, fast and private. Files are never uploaded.

Files

  • Compress Image
  • Image to PDF
  • Merge PDF
  • Compress PDF
  • PDF to Word
  • Word to PDF

Dev

  • JSON Formatter & Validator
  • Base64 Encode & Decode
  • JWT Decoder, Verifier & Encoder
  • Password Generator
  • UUID Generator
  • Unix Timestamp Converter

Money

  • SIP Calculator
  • EMI Calculator
  • GST Calculator
  • FD Calculator
  • PPF Calculator
  • Lumpsum Calculator

Site map: Files · Dev · Money

GuidesQuestionsAboutHow we checkLaw library (beta)PrivacyTermsDisclosureContactMore: Exam practice (UGC NET, MH-SET, PhD entrance, CSIR NET)Runs in your browser. Nothing is uploaded. © 2026 Omnikit (theomnikit.com)