How to use Font File Metadata Inspector
- Choose a local TTF or OTF font file.
- Inspect the names, metrics and supported character-map report.
- Download the report and consult the font’s actual license before use.
Example: Font File Metadata Inspector
A font containing a family name and a glyph-count record.
You add
Synthetic metadata.ttf: five sfnt tables, name Synthetic sfnt metadata, unitsPerEm 1000 and weight class 400.
You get
TrueType sfnt: 5 tables and 1 name records. Sample rows: unitsPerEm | 1000; glyphs | 1.
Options
- Font file
- Select one standalone TTF or OTF. WOFF, WOFF2 and collections need another workflow; renaming their extension does not convert the bytes.
- Metadata records
- Names, metrics and cmap format labels are stored information. A licence string or embedding flag is reported without a legal conclusion.
Supported inputs and limits
One sfnt TTF or OTF up to 8 MiB, 128 tables, 256 name records and 32 character-map subtables. Metadata inspection only; no font rendering, WOFF conversion, shaping test, malware certification or license approval.
Where your input is processed
This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.
Metadata does not show how text will render
The tool does not load glyphs, test shaping or verify that a specific passage is covered. A stored family name and glyph count cannot prove readable output in another application. Review the font’s licence and test the actual text where it will be used. The JSON report preserves the inspected metadata without fetching stored licence URLs.
Questions about Font File Metadata Inspector
Does this preview the font?
No. It reads metadata without installing or rendering the font.
Does a license field prove I can use it?
No. Read the actual license and confirm your intended use.
Can I inspect WOFF files?
No. This tool accepts supported sfnt TTF and OTF files.