Original examples · Glyph Studio · public alpha
How to test a font exported from Glyph Studio
Test notes updated October 10, 2026 · by thecreatingco
A font export is only the beginning: test character coverage, spacing, naming and rendering in the applications where you will use it. Missing letters can fall back to another font even when the exported file itself is valid.
A real, deliberately small Glyph Studio export
This downloadable TTF came from our published Glyph Studio verification. We drew an A and exported the file. The parsed A contains 72 outline commands; the export is 1,536 bytes. Its Macintosh and Windows naming records matched and contained no control characters in that check.
Download the A-only test font · Download the spacing worksheet
This is an original test drawing, not a finished type family. Only A was verified as drawn. The example above displays that character through the actual exported file; it does not imply alphabet coverage, platform installation success or production-quality typography. Original maker metadata remains in the font.
Build a small specimen before a whole alphabet
- Draw H and O to establish straight and curved proportions, then A, V and T for diagonals and overhangs.
- Compare repeated strings such as
HHHOHHHandOOOHOOO. Check side bearings before adjusting individual pairs. - Try
AV VA TA AT Toto spot pairs whose visual gap differs from their measured spacing. - Add
n o a v t, digits and punctuation only as you need them. List drawn characters explicitly so fallback cannot disguise gaps. - Save the editable .glyph project separately. Export a font, load that exact file into your destination application and compare at 16, 32 and 72 pixels.
The downloadable worksheet is plain text for your review notes. It is not an importable .glyph project and does not contain pre-drawn letterforms.
Glyph Studio vs Luma Font Maker
| Workflow | What it fits | What to watch |
|---|---|---|
| Standalone Glyph Studio | Drawing letterforms, refining curves, comparing metrics and kerning, keeping a .glyph project | Export still needs destination-app checks and a coverage review. |
| Glyph in Luma’s menu | Simple straight-segment lettering and font experiments inside an image workflow | The embedded tool does not provide curve fitting, hinting, kerning or a complete accented family. |
Both experiences are distinct. Choose based on your editing task rather than assuming a shared name means shared capability.
Troubleshoot the exported font
Some letters look unrelated: compare your drawn-character list with the text. A missing character can be rendered by fallback. Draw the needed glyph or reduce the specimen to known characters.
Pairs look uneven: first inspect each glyph’s advance width and side bearings. Pair adjustments cannot make an inconsistent basic spacing system predictable.
The old version still appears: confirm the exported filename and family name, check which font the application selected, and close/reopen that application if needed. Keep versions identifiable when comparing revisions.
Font installation fails: preserve the exported file and its exact error. Naming records, character mappings and outlines are separate parts of the format. Our metadata check covers one original file; it does not certify all exports or OS versions.
The OpenType naming table stores family, style, version and other strings; its platform records affect compatibility. Source: Microsoft OpenType naming-table specification. The original A-only font above is the downloadable fixture from our first-party export check; its maker metadata was inspected in that check.
Reuse the examples
These are original learning fixtures. You may reuse and modify them, including commercially. Read the fixture notes and limits. Keep originals and inspect actual exports before delivery.