Features / Proofing and QA
Font-wide validation
Checking the font as a whole against the OpenType specification and platform requirements: tables, names, metrics and encoding. Checks of glyph outlines count under Outline proofing.
How it works
A font file is a set of tables, each with its own job: cmap maps characters to glyphs, name holds the family and style names, and hhea and OS/2 hold metrics such as line spacing. Validation checks that each table follows the OpenType specification and that tables agree with each other. For example, glyph 0 must be the .notdef glyph shown for missing characters, and the platform and encoding IDs in the name table should match those in the cmap table, or the font will not load in Windows. Other checks compare data that must agree, such as glyph counts in the loca and maxp tables.
Platforms and distributors add their own requirements: the open-source checker Font Bakery has profiles for the specification and for particular distributors.
Why it matters
A font can look right in the editor and still fail elsewhere: not load, show wrong names in font menus, or have glyphs cut off. Windows GDI, for example, clips any part of a TrueType glyph above the usWinAscent value in the OS/2 table.
What to check
- Whether it checks font-wide data, such as names, metrics and layout tables, as well as glyphs (see Outline proofing); a short fixed list of font-wide checks is the Partial level below.
- Whether each report explains the problem and shows where it is.
- Whether it checks the exported font file or only the source.
- Whether you can choose which requirements to check against.
Read more
- Recommendations for OpenType fonts, Microsoft
- OS/2 usWinAscent, Microsoft
- OpenType profile, Font Bakery
Editors
- Full
- Checks font-wide data, such as tables, names and metrics, as well as glyphs, and explains each problem.
- Partial
- A short fixed list of font-wide checks. Glyph outline checks alone count under Outline proofing.
| Editor | Support | Evidence |
|---|---|---|
| FontForge | Full | Bundled fontlint checks tables, names, metrics and glyphs; GUI window mostly glyphs.Checked 2026-10-25 · developer documentationSource |
| BirdFont | Partial | Export only checks that five required name fields are filled in.Checked 2026-10-29 · developer documentationSource |
| FontLab | Partial | Font window flags name-Unicode mismatches and unrecognized names; no table or metric checks documented.Checked 2026-11-10 · developer documentationSource |
| Fontself Maker | Partial | Warnings cover vertical metrics and glyph clipping; duplicate-font check on Mac Illustrator.Checked 2026-10-26 · developer documentationSource |
| Glyphs | Partial | Georg Seifert (developer): Validate Font checks component alignment and duplicate Unicodes.Checked 2026-10-25 · developer documentationSource |
| FontCreator | Not supported | The wizard checks glyphs only (outlines, components, points, interpolation); no font-wide checks.Checked 2026-10-30 · developer documentationSource |
| Fontra | Not supported | Code: no validation panel or command; only interpolation and FEA compile errors shown.Checked 2026-10-30 · developer documentationSource |
| FontStruct | Not supported | Editor code has no font validation or checks.Checked 2026-10-29 · developer documentationSource |
| Glyphr Studio | Not supported | Code: Quality Checks cover only four point issues; nothing checks font-wide data.Checked 2026-10-30 · developer documentationSource |
| iFontMaker | Not supported | Not in iFontMaker's FAQ, App Store text or websites (read 12 Nov 2026).Checked 2026-11-12 · developer documentationSource |
| RoboFont | Not supported | Not in RoboFont's documentation; no extension in Mechanic 2 or the Extension Store does it.Checked 2026-11-12 · developer documentationSource |