Method & sources
Where the character names, code points, and tool results come from.
Pinned standard data
Character names and properties come from a fixed Unicode Character Database 18.0.0 snapshot. The source package records the download locations, retrieval dates, and file hashes. It includes names, aliases, categories, combining classes, bidirectional classes, and the derived properties used by the tools.
Standard names, control aliases, and explanatory labels are shown separately. A label for private-use, unassigned, noncharacter, or invalid-surrogate data is not presented as an official Unicode name. Algorithmic names are derived from the same fixed data.
Calculation and runtime behavior
| Information | Method and boundary |
|---|---|
| Code points | Read the actual input sequence, with isolated surrogates identified. |
| UTF-8 bytes | Encode well-formed text; do not silently show replacement bytes for invalid original units. |
| UTF-16 units | Count JavaScript string units, separately from code points. |
| Grapheme boundaries | Use the running browser’s Intl.Segmenter implementation. |
| Normalization | Use the running browser’s NFC, NFD, NFKC, or NFKD operation after explicit selection. |
| HTML references | Use the vendored WHATWG named-reference mappings with documented strict scalar and semicolon rules. |
Your browser may support a different Unicode version from the reference database. That can affect grapheme boundaries and newer sequences. If a required feature is unavailable, the tool explains the limitation instead of displaying an invented count.
Original content and comparisons
Examples explain a particular use, and comparisons show the actual encoded differences between similar shapes. A currency sign needs an identifiable currency, and a checkbox character in a text example remains a static mark.
The reference contains 123 symbol or letter-family pages, 18 collections, six tools, six Blog articles, and six Docs guides. Category pages, hubs, and site information help you navigate those entries.
Verification and its limits
Checks cover exact values for heart variants, joined emoji, combining accents, spaces, normalization, invalid input, and literal markup. Browser checks also exercise copying, favorites, exports, and page layouts. Those results describe the tested cases and environments.
Check both the text and its appearance where you will use it. Matching code points confirm the sequence; a visual check can reveal a missing font, a changed glyph, or an awkward line break.
Sources and method
- Unicode Character Database 18.0.0 — Pinned source for assigned character names, properties, and aliases.
- Unicode: UTF-8, UTF-16, UTF-32 and BOM — How Unicode values are represented in UTF-8 and UTF-16.
- Unicode Standard Annex #29: Text Segmentation — Background for grapheme boundaries. Runtime segmentation is supplied by the browser.
- Unicode Standard Annex #15: Normalization Forms — Canonical and compatibility normalization and their limits.
- WHATWG HTML: Named character references — Named-reference mappings. The converter uses an explicitly stricter text-only error policy.
- Unicode License V3 — Unicode data retains its copyright and permission notice.