Font Coverage Checker
Check exactly which Unicode blocks a font can render. This tool reports full, partial, or missing coverage per block so you know before publishing whether text will display correctly or fall back to another font.
Why coverage matters
When a font is missing a character, browsers substitute a fallback font for that specific character. This causes visual inconsistency — differing baseline, weight, and metrics. For multilingual sites, layout audits, or typeface licensing decisions, coverage checking is essential before you commit to a font.
Frequently asked questions
What counts as full coverage?
80% or more of a Unicode block's codepoints are present. Many blocks contain reserved codepoints that no font implements, so 100% is rare even for full support.
What happens if coverage is missing?
Browsers fall back to the next font in the CSS font-family stack. If none is available, users see tofu (missing glyph boxes) — a critical accessibility and UX failure.
What is tofu?
Tofu is the square box that appears when a font cannot render a character. It signals missing coverage and is a strong indicator of poor font selection for the content.