Local-first
Font bytes and preview content stay in browser memory.
Built for real font files
Fast enough for a preview. Deep enough for a handoff.
WOFF2 Font Preview exists because a local webfont check should not require an install, a signup, an upload, or a maze of unrelated conversion tools.
The product idea
One clear job, handled thoroughly
The primary job is to open a WOFF2 file and see what it will do. That starts with custom text, not a technical report. But when something looks wrong, the next questions arrive quickly: Is the character included? Is this the variable file? Which family name does CSS need? Does the file contain a web embedding note?
This tool keeps the file picker and live specimen first, then makes glyphs, axes, features, metadata, metrics, and CSS available without sending the font away.
Typography-first
Controls use the vocabulary designers and developers actually need.
Progressive depth
Immediate preview first, detailed inspection when needed.
Honest limits
Metadata and embedding flags are clues, never legal certification.
How it works
Standards-based rendering, local inspection
The browser FontFace API is used for the specimen. Fontkit reads supported OpenType data, including WOFF2 compression, cmap characters, glyph outlines, variation axes, metrics, and layout feature tags.
| Layer | Purpose | Where it runs | What leaves your device |
|---|---|---|---|
| FontFace API | Render the selected font in the live specimen | Your browser | Nothing |
| Fontkit | Read supported WOFF2/OpenType structures | Your browser | Nothing |
| GA4 | Measure coarse site and feature usage | Google Analytics | No font content or local names |
| Cloudflare | Deliver static site files and protect the service | Edge network | Normal web request data |
Have a font to inspect?
Start with the file. No account and no font upload.