Unicode Text Normalizer

Unicode normalization is the process of converting text into a canonical form. Many Unicode characters can be represented in multiple ways (e.g., “é” as a single precomposed character or as “e” + combining acute accent). Normalization ensures consistent representation, essential for searching, sorting, and data matching.

• NFC – Canonical Composition: composes characters into their precomposed forms where possible.
• NFD – Canonical Decomposition: decomposes characters into base letters and combining marks.
• NFKC – Compatibility Composition: applies compatibility decomposition (e.g., ligatures, fullwidth letters) and then composes canonically.
• NFKD – Compatibility Decomposition: applies compatibility decomposition without recomposing.

Use NFC for most web/text applications; NFKD when you need lossy normalization (e.g., removing ligatures like “fi” to “f” + “i”).

Use NFC for general text storage, web content, and user-facing strings (it’s the default on the web). NFD is useful when you need to strip diacritics, sort with locale-aware collation, or process individual base characters. macOS filenames, for example, are stored in NFD.

NFKC and NFKD replace compatibility characters (e.g., ligatures “fi”, circled letters, fullwidth Latin) with their plain counterparts. This may change visual appearance but is essential for search, security, and data consistency. For example, “ℌ” (U+2118) becomes “H” under NFKC.

Absolutely. All processing happens locally in your browser using JavaScript’s String.prototype.normalize(). No text is ever sent to a server or stored. You can even use this tool offline after the page loads.

Combining characters (like U+0301 combining acute accent) attach to a preceding base character to form a composite grapheme. In NFD, “é” is decomposed into “e” + U+0301. Showing code points with our tool makes these invisible characters visible.

Yes! Emoji sequences (including ZWJ, skin tones, and flag letters) can be normalized. Canonical forms (NFC/NFD) generally preserve emoji meaning, while compatibility forms (NFKC/NFKD) may lose variation selectors and transform text-style presentation.

Unlike many online converters, this tool offers live normalization as you type, an optional code point viewer, and supports all four standard forms without sending your data anywhere. The clear side‑by‑side layout makes it easy to understand transformation differences.

All modern browsers (Chrome, Edge, Firefox, Safari, Opera) fully support String.prototype.normalize(). This tool works perfectly on desktop and mobile devices.

Typical use cases include: ensuring consistent text before comparing passwords or usernames (NFKC to normalize homographs), preparing data for database indexing, removing invisible variation selectors, or standardizing filenames across different operating systems.