All 141 tools / International and inclusive design
Find which scripts your text needs and which listed fonts cover them, with a Noto family for each gap
Font coverage checkFreeFor designers and developers
25/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
text: Hello, Привет, Γειά, مرحبا, שלום, नमस्ते, สวัสดี, こんにちは, 你好, 안녕, Xin chào, 😀 fonts: Inter, Noto Sans JP, Georgia, sans-serif
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
FONT COVERAGE CHECK Characters analysed: 64 Unicode blocks present: Basic Latin: 22 (H e l o , X) [Latin] Cyrillic: 6 (П р и в е т) [Cyrillic] Devanagari: 6 (न म स ् त े) [Devanagari] Thai: 6 (ส ว ั ด ี) [Thai] Arabic: 5 (م ر ح ب ا) [Arabic] Hiragana: 5 (こ ん に ち は) [Japanese kana] Greek and Coptic: 4 (Γ ε ι ά) [Greek] Hebrew: 4 (ש ל ו ם) [Hebrew] CJK Unified Ideographs: 2 (你 好) [Han] Hangul Syllables: 2 (안 녕) [Hangul] ... full output on the tool page
What you get
Unicode blocks present with counts, scripts needed, per-font coverage, gaps, and suggested Noto families
What it cannot do
Font coverage comes from a small table of common fonts, so unlisted fonts show as unknown.
Who it is for
- Designers
- Developers
Free and Pro
| Free | 25 runs a day per IP address, up to 100,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called check_font_coverage. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/font-coverage -H 'content-type: application/json' -d '{"text":"Hello, Привет, Γειά, مرحبا, שלום, नमस्ते, สวัสดี, こんにちは, 你好, 안녕, Xin chào, 😀","fonts":"Inter, Noto Sans JP, Georgia, sans-serif"}'
Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in international and inclusive design
- Localisation stress test
Predict how far UI strings grow in eight languages and flag the ones that overflow their space.
- Localisation readiness
Check source strings for translation problems and project how long each will be in other languages
- RTL readiness
Find the left and right CSS that will break in Arabic or Hebrew, with the logical property to use instead
- Date and number format review
Find dates, numbers, currency and units in UI text that read differently in other locales
- Text expansion planner
Plan how much longer each UI string gets in other languages and flag the ones that overflow
- Name field check
Find name inputs that reject real names: short maxlength, A to Z patterns and forced first and last fields