Diacritic and Unicode Tools

Inspect, compose and transform text locally. Input stays in your browser. Each transformation is explicit, and copying preserves the chosen output exactly.

  • Remove diacritics : canonical removal with explicit limits.
  • Diacritics Keyboard : Compose text by inserting an exact character at the current selection. Search the pinned candidate corpus by name, code point, script or CLDR language evidence.
  • Combining Diacritics Builder : Build an experimental sequence from a base and an ordered list of marks. Add, move or remove marks, then choose exact, NFC or NFD output.
  • Unicode Normalizer : Compare all four Unicode 17 normalization forms and their exact scalar sequences. The original text stays available alongside the transformed output.
  • Diacritic and Character Inspector : Inspect exact scalars, Unicode names, UTF encodings, escapes, grapheme boundaries and the four normalization forms.
  • Unicode Text Comparator : Compare two strings by exact scalar sequence, canonical equivalence, compatibility equivalence and grapheme boundaries.
  • Grapheme Cluster Splitter : Split text at Unicode 17 extended grapheme boundaries and inspect every cluster without changing its contents.
  • Combining Mark Highlighter : Locate characters in Unicode 17's Diacritic-or-Mark union, showing their positions and exact code points beside the original text.

The font tester is held because missing-glyph heuristics do not establish correct shaping. Automatic accent restoration is not offered as a language-neutral operation.

Browse candidates · Choose a normalization form

Sources, versions and limits

Encoded properties
Properties use Unicode 17.0.0. Normalization follows UAX #15; grapheme boundaries follow UAX #29. Script associations describe encoded properties, not language use.
Language evidence
CLDR 48.2and the IANA registry dated 2026-08-08. Main and auxiliary exemplars are distinct. CLDR exemplars are not complete orthographies.
Review and limitations
The dataset is derived from the sources above. Editorial guides cite additional scoped authorities. No native or specialist orthography approval is implied. Release scope date: 14 September 2026. Historic or specialist usage needs separate evidence. Registry-only records have unknown orthography in this release.
Reproduction and corrections
Downloads and licences · Coverage and held routes · Suggest a source-backed correction