How to use Font-Stack Text Coverage Checker
- Choose Actual TTF or OTF files and select up to four supported standalone fonts in the intended fallback order. The selection order is the stack order.
- For a range-only plan instead, select Optional declared-range plan and enter Label | U+0041-005A style lines. Those labels do not identify verified font files.
- Enter the exact text and run the check. Review each font’s mapped/missing code points and the first stack entry assigned to each character.
- Export the report if needed, then test actual glyph rendering and shaping separately. A nonzero cmap mapping does not prove that text looks right.
Example: Font-Stack Text Coverage Checker
Select the optional declared-range plan to run this entered-data example.
Options
- Declared coverage
- One line per stack entry as "Label | U+0041-005A, U+00A0-00FF". The label is only a name for your own list and is not checked against any real font. Up to 4 entries and 200 ranges each.
- File coverage
- Supported cmap records are inspected without rendering the font. Glyph zero is treated as missing under the documented mapping rules.
- Coverage source
- File mode reads the real cmap tables and treats a code point that maps to glyph 0 as missing. Optional declared ranges are a plan.
- Font files
- Up to 4 standalone sfnt fonts, 8 MiB each. WOFF, WOFF2, collections and web URLs are refused. The stack order is the order you choose them.
- Text to check
- Up to 2000 characters and 500 distinct code points.
Supported inputs and limits
- Up to four standalone sfnt fonts, 8 MiB each; text up to 2,000 characters and 500 distinct code points.
- Declared mode accepts 200 ranges per entry with a 300,000-code-point scan cap.
- File checks support a Unicode cmap 0/4/6/12 subset and maxp glyph bounds; glyph zero is missing.
- WOFF/WOFF2, collections, remote URLs, variation selectors and the stated shaping controls are refused.
- No font installation, rendering, ligature/combining-layout check or license approval.
More details
Declared ranges remain a plan, not verified font coverage.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Mapped characters may still render poorly
A cmap mapping does not establish shaping, readable glyph design or correct combining-mark placement. Variation selectors and complex scripts need separate rendering tests. Keep the exact text and stack order with the report before deciding that a fallback is adequate.
Questions about Font-Stack Text Coverage Checker
Does declared mode inspect a font?
It checks the ranges you entered and labels them as a plan.
Does a cmap match guarantee readability?
No. Glyph appearance, shaping and combining behavior are not tested.
Will font licenses be checked?
No. Permission to use a supplied font needs separate review.