Bring your font
Select one or many TTF, OTF, WOFF 1.0 or TTC files. Inspection reads limited local slices, never uploading or modifying the original files.
PIXELOKAY / FONT UTILITIES
Font Metadata Inspector
Discover the metadata hiding inside a typeface: real names, glyph counts, OpenType tables, variable axes and Unicode character coverage. Without uploading a single file.
◎ Private by design▤ Table-level insight✳ Unicode-aware
Inspect a font YOUR WORKSPACE
◈ Nothing leaves your browserInspect typography, precisely.
Add one font or a whole collection to begin.
Files0In workspace
Faces0Parsed
Mapped characters0Across faces*
Needs attention0Partial or failed
Font library
Choose fonts to see their technical profile.
Inspecting…
Files are waiting to be inspected.
Your typefaces, decoded.
Add a font to explore the names, character coverage and data stored inside.
FONT PROFILE
Your font
Unicode character coverage
Derived from a supported Unicode cmap subtable. Blocks are overlapping categories of code points, not proof of language support.
Can this font map your characters?
Test a short string against this font's character-to-glyph map. A mapped character may still require shaping or a fallback at render time.
OpenType table directory
Offsets, compressed storage sizes and original table sizes. Presence does not prove table validity.
Optional: compare recorded checksums with local table bytes (not a security signature).
Preview on this device
Uses your browser's font renderer, which is separate from the metadata parser. Preview can fail for an otherwise inspectable font.
Preview is not loaded.
Sphinx of black quartz, judge my vow. 0123456789
Your system might replace unsupported glyphs with fallback fonts. The character checker in Coverage provides cmap-based evidence. A TTC/OTC collection preview is limited to its first face; other faces are not previewed to avoid showing the wrong design.
KNOW YOUR TYPE
Everything a font can tell you.
Font files are more than curves and letters. Their metadata describes names, design-space axes, OpenType layout capabilities, Unicode maps and embedding declarations.
Explore its structure
Review family records, table tags, glyph counts, mapped Unicode blocks and variable font axes.
Check and export
Test text against a Unicode cmap and download detailed JSON or a CSV summary for documentation and QA.
Frequently asked questions
Does this tool support WOFF2 fonts?
It identifies WOFF2 signatures but does not decode transformed Brotli tables. TTF, OTF and WOFF 1.0 metadata are parsed; font collections (TTC/OTC) are also supported. Preview availability varies by browser.
Is Unicode coverage the same as language support?
No. Unicode cmap tables list code-point mappings. Language support also depends on glyph quality, text shaping, substitutions, mark positioning, variation selectors, composition, and font rendering behavior.
Is the embedding permission authoritative?
Not necessarily. The OS/2 fsType field declares embedding flags, but the licensing agreement governs permitted uses. Review the font license before redistribution, subsetting, or web embedding.
Are my font files sent to PixelOkay?
No. Inspection happens locally in JavaScript, with no upload or backend. The optional preview loads a temporary object URL on your device. Files are retained only in the browser page until you remove or close them.
Why does a malformed font sometimes produce a partial report?
Fonts can contain damaged or unsupported individual metadata tables. The inspector will show available evidence with warnings where possible, or a clear error if structural validation fails.