About GlyphView

Data sources

Character facts come from the Unicode Character Database (UCD) published by the Unicode Consortium. Facts on this property are frozen at Unicode 18.0: an assigned codepoint's name, block, script, category and encodings do not change between releases, and the pages state the version they were built from. The reference layer is rebuilt on each annual Unicode release.

Font coverage comes from a snapshot of a large public font catalog. The current snapshot was built on 21 October 2026 and covers 137,179 fonts (a font is one style of a family). Every count on the site is exact for its snapshot and is displayed with the snapshot date — counts are never rounded, capped or estimated.

The written-language pages take their character sets (the standard, additional and punctuation exemplars for each language in its script) and their population figures from the Unicode CLDR.

What changed in recent releases

The reference layer is frozen at the current release, Unicode 18.0. The characters each recent release added are listed in full, grouped by block: Unicode 18.0 (13,007 new characters), Unicode 17.0 (4,803 new characters) and Unicode 16.0 (5,185 new characters). The emoji of the two newest releases are also gathered on one page — New emojis in 2026 — each with the font support it has so far.

How counts and the glyph wall work

For each font in the snapshot, the character set of its current file version is recorded. Inverting that data gives, per character, the list of fonts that include it. Byte-identical files uploaded more than once are deduplicated inside the snapshot, so a character's count always equals the number of tiles on its glyph wall. Each wall tile renders the character in that font and links to the font family's home.

Impartiality

GlyphView is reference infrastructure, not a store. It carries no advertising, no affiliate links, no rankings for sale and no editorial steering: characters are presented in codepoint order, fonts in the catalog's rank order, and the only outbound links on a character page are the factual attributions on its glyph wall tiles. Nothing here is personalized. The interactive tools run in the visitor's browser: a visitor's own font list and font files are never transmitted anywhere, and text pasted into the Analyzer never leaves the device. Site usage is measured in aggregate, as described under Measurement below.

Measurement

GlyphView uses Google Analytics to count page views and a small set of interaction events: searches (the term typed, how many results it returned, and which result was chosen), copy actions, glyph-wall paging and tile clicks, uses of the Analyzer (a coarse count of how many characters were pasted — never the text itself), and the system-font check (the character checked, and how many fonts were verified and installed in total — never font names). The events exist to show which parts of the reference are actually used. What the tools work on stays local: font lists and font files are read on the device and never leave it, the Analyzer's text is processed in the browser, and every count, wall and character fact on the site is a static file from the dated snapshot.

Data access for machines

The same data that powers the pages is published as stable, versioned JSON: per-block character shards, per-character font counts, and per-character wall data, all stamped with the Unicode version and the snapshot date. Responses carry the canonical character URL so answers built on this data can cite the character's page. Access is per-character by design; the full coverage store is not offered as a bulk download.