Frequently Asked Questions
Common issues and practical answers based on current behavior.
Which formats can I import for glyph browsing?
ttf, woff, and woff2 are supported in the import flow.
Why did my existing glyph list disappear after importing another file?
Import currently replaces the active session data. If you need comparison, open another workspace window and load a different font there.
Why can I not generate a subset from multiple loaded fonts?
Subset generation is currently designed for exactly one source font at a time.
Which subset outputs are supported?
Subset output supports WOFF2, WOFF, and TTF.
Why does subset generation fail on some fonts?
Current subset output only supports TrueType-outline fonts. Fonts that rely on unsupported outline/table structures may fail with validation or unsupported-format errors.
What does “Generate Web Package” produce?
It generates a package folder with:
fonts/(WOFF2+WOFF)- one CSS file (
@font-face,unicode-range) demo.htmlpreview page
Are variable fonts supported?
Yes. Variable fonts are detected in the inspector and can be exported as variable fonts. The current build does not provide axis-based static-instance baking/export.
Why do I see warnings after generation?
Warnings come from built-in validation checks (for example missing cmap mappings, size regressions, or OpenType layout table consistency checks). Outputs may still be written when only warnings are present.
Does WebFont upload my font files?
No. Font processing is local. See the privacy page for details.