Font Unicode coverage
Check supplied static fonts for each Unicode code point, without installing fonts or using fallback.
- 1Add input
- 2Review and run
- 3Get your result
Tool input and files are processed in this browser without being uploaded.
Before you start
Select static TTF/OTF files and enter required text. Read complete per-font glyph IDs and missing code points. Coverage checks cmap, not shaping or rendered emoji sequences.
How to use this tool
- Choose fonts and enter required text.
- Review per-font coverage and selected cmap metadata.
- Download full JSON/CSV; compare glyph IDs without system fallback.
Supported inputs and limits
20 files;10 MiB each;80 MiB total. Text1 MiB,10,000 unique code points and100,000 font–code-point pairs. Complete JSON/CSV outputs are limited to20 MiB each.
Uncompressed static SFNT TTF/OTF only. Validate table checksums/ranges and glyph bounds; reject TTC/WOFF/WOFF2, variable fonts and variation-sequence maps. Select cmap12 before4, Windows before Unicode ties. Glyph0 is missing.
Worked example
Example input
A中📹?A plus ZWJ in two self-generated fonts.
Example options
{}Example output
5 unique code points ×2 fonts =10 rows; A/中/📹 map, question mark/ZWJ do not.
When something does not work
Use ordinary static TTF/OTF files, remove malformed or unsupported containers and reduce text/pair budgets.
Frequently asked questions
Does coverage guarantee correct display?
No. Combining, ligatures, script shaping and emoji sequences need a renderer. A mapped code point alone does not certify any sequence.
Documentation & further reading
Related tools
Convert text encoding
Choose the right text encoding and save a readable TXT file.
Merge text files
Put several text files together in the order you choose.
Word counter
Words, characters, and paragraphs at a glance.
Case converter
Change letter case to suit your text.