The Universal Unicode Normalizer & Character Decomposition Suite on RiazHub.com is a high-performance, 100% browser-based utility designed to standardize multilingual text into official Unicode Consortium standards (UAX #15). Seamlessly convert between NFC (W3C Web Standard Canonical Composition), NFD (Canonical Decomposition), NFKC (Compatibility Composition), and NFKD (Compatibility Decomposition) to resolve string comparison bugs ("é" !== "é"), eliminate search indexing mismatches, and fix database unique key bypasses. The suite features an advanced diacritic stripper, invisible zero-width character purger (stripping \u200B, \u200C, \u200D, \uFEFF, and bidirectional marks), typographic ligature expander (ﬁ ➔ fi), fullwidth ASCII converter (Ａ-Ｚ ➔ A-Z), a real-time side-by-side 4-form comparison matrix, and a deep byte-level glyph inspector with instant JSON and TXT export. Built with client-side Web APIs, all data remains strictly private inside your browser with zero server transmission.

W3C & Unicode UAX #15 Standard

Universal Unicode Normalizer & Character Decomposer

Standardize multilingual text into official Unicode forms (NFC, NFD, NFKC, NFKD), purge invisible zero-width characters, strip accents, and inspect byte-level codepoints in real time.

Active Form

NFC

Canonical Composition

Codepoints Count

0 ➔ 0

0 codepoints delta

UTF-8 Byte Size

0 B ➔ 0 B

0 bytes delta

Normalization State

✅ Standardized

Strings match

Presets:

Source Input

Drop .txt, .md, .csv, .json, .log, .xml or click to browse

Normalization Form (UAX #15)

NFC Web Standard Canonical Composed (e.g. e + ◌́ ➔ é) NFD Decomposed Canonical Split (e.g. é ➔ e + ◌́) NFKC Compatibility Fixes ligatures & fullwidth + composes NFKD Compat. Decomp. Compatibility split + diacritics split

Hygiene & Sanitization Rules

Purge Hidden Zero-Width Characters Strip ZWSP, ZWNJ, ZWJ, BOM, LTR/RTL marks (\u200B-\u200F, \uFEFF)

Strip All Combining Accents / Diacritics Remove marks (e.g., é ➔ e, ñ ➔ n, ü ➔ u, ç ➔ c)

Convert Fullwidth ASCII Characters Map Ａ-Ｚ, ０-９ and fullwidth punctuation to standard ASCII

Expand Typographic Ligatures Replace typographic symbols (ﬁ ➔ fi, ﬂ ➔ fl, œ ➔ oe, æ ➔ ae)

Normalize Line Breaks (CRLF ➔ LF) Standardize Windows/Mac newline characters to Unix LF (\n)

● NFC (Canonical Composed)

0 Codepoints | 0 Bytes

● NFD (Canonical Decomposed)

0 Codepoints | 0 Bytes

● NFKC (Compatibility Composed)

0 Codepoints | 0 Bytes

● NFKD (Compatibility Decomposed)

0 Codepoints | 0 Bytes

Showing 0 glyphs

#	Glyph	Unicode Codepoint	Decimal	UTF-8 Hex Bytes	Classification
No text to inspect. Paste text in the source editor.

Visualized representation of invisible control codes, zero-width spaces, and decomposed diacritic marks in your current text:

Unicode Normalization Standards & UAX #15 Reference

In Unicode, the letter é can be represented in two completely valid but binary-distinct ways: as a single precomposed character (U+00E9 in NFC), or as the base letter e (U+0065) followed by the combining acute accent (U+0301 in NFD). Although both look identical on screen, direct byte-level string comparisons (e.g. in JavaScript, SQL databases, or authentication systems) will fail without normalizing both strings to a common form first.

Canonical Equivalence (NFC / NFD): Preserves the fundamental visual and semantic meaning of characters. It only combines or decomposes precomposed accented letters.

Compatibility Equivalence (NFKC / NFKD): Goes a step further by breaking formatting variants down to their standard counterparts. For example, typographic ligatures like ﬁ become fi, superscripts like ² become 2, fractions like ½ become 1/2, and fullwidth Asian ASCII characters like ＡＢＣ become standard ABC.

Unnormalized Unicode input is a notorious attack vector in web applications. Attackers can inject invisible zero-width characters (like \u200B or \uFEFF) into usernames to bypass duplicate username checks or filter blacklists. Similarly, homograph attacks exploit visually identical characters across Cyrillic, Greek, and Latin scripts. Applying NFKC and stripping zero-width characters eliminates ghost bypasses and hardens database indexing.

All string normalization, regex sanitation, byte encoding computations, and file exports occur entirely within your web browser using modern ECMAScript standard methods (String.prototype.normalize() and TextEncoder). Zero text data, documents, or keys are ever sent across a network or stored on any external server.

Copied to clipboard!