Read a font's metadata locally - family, style, version, units per em, glyph count and more. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Every font file carries a wealth of metadata in its internal tables: the family and style name, the version and copyright string, the design grid (units per em), how many glyphs it contains, the vertical metrics (ascent, descent, line gap) and whether it is a variable font with adjustable axes. This information lives in the 'name', 'head', 'maxp', 'OS/2' and related sfnt tables, but no everyday tool shows it plainly. This page reads those tables and writes a clear, readable report.
It works on the common desktop and web formats - TrueType (TTF), OpenType (OTF), WOFF and WOFF2 - because they are all sfnt containers underneath. The WOFF and WOFF2 wrappers are unpacked first, then the font is parsed and its key fields are collected into a single text report you can read, archive or paste into a bug report or licence check. Nothing about the font is changed; the original file is only inspected.
Everything runs entirely locally in your browser (no upload, even offline) - the font, which may be a paid or unreleased typeface, never leaves your device. Honestly framed: this is a metadata reader, not a glyph editor or a validator; it reports what the font declares about itself. A file that is not a recognisable font, or is corrupt, is rejected with a clear message instead of a misleading report.
| Input formats | TTF, OTF, WOFF, WOFF2 |
|---|---|
| Output format | TXT |
| Batch processing | Yes |
| Processing | Locally in your browser (WebAssembly) |
| File upload | None |
Limitations: Reads a font's declared metadata - family, subfamily/style, full and PostScript name, version, copyright, units per em, glyph count, vertical metrics, bounding box and variable-font axes - and writes a plain-text report. Works on TTF, OTF, WOFF and WOFF2 (the WOFF wrappers are unpacked first). It is a reader, not an editor or a licence validator; it reports what the font declares. A non-font or corrupt file is rejected with a clear error.
No. The font is unpacked and parsed entirely locally in the browser - even offline. It never leaves your device.
TTF, OTF, WOFF and WOFF2. The WOFF and WOFF2 wrappers are unpacked to the underlying sfnt before the metadata is read.
No. The font is only inspected; the original file is left untouched. The output is a separate text report.
Yes. The report states whether the font is a variable font and lists its variation axes (such as weight or width).