Skip to content

Font Inspector

Opens a font file to show its glyph coverage by block, Korean syllable count, weight, variable axes, embedding permission and licence name records.

Opens a font file and tells you what is inside it: the name records, the licence and embedding permission, the metrics, the variable axes, and which Unicode blocks it covers and how completely. Sample text is drawn with the actual file through the browser’s FontFace, so what you see is the font, not a picture of it. Nothing is uploaded.

🔒 Runs entirely in your browserfontinspectglyphspreview

Drop a TTF, OTF or WOFF file

Read in this tab only. The font file is not uploaded anywhere.

A hand-written OpenType parser reads the name·head·hhea·OS/2·post·maxp·cmap·fvar tables. The sample is drawn by registering the file with the browser’s FontFace, so it is the real font. A TTC is read as its first font, and a WOFF should be unpacked to TTF in the format converter first. WOFF2 cannot be read at all, because the browser does not expose Brotli to a page.

How to use it

  1. Drop the file

    TTF, OTF or WOFF. A TTC is read as its first font. Everything happens in this tab.

  2. Check the coverage before anything else

    The Hangul syllables row is the one that decides whether a font can carry Korean at all: 11,172 is complete, 2,350 is the KS X 1001 set, and a few hundred means it was subset for something else. The other blocks answer the same question for currency symbols, arrows and CJK punctuation, which is where a font usually turns out to be missing something.

  3. Read the licence records

    The name table carries the designer, the copyright, the licence text and often a URL, and the OS/2 fsType says what embedding the vendor permits. This is the fastest way to find out what a font on your disk actually allows before it ends up on a server.

  4. Type your own text into the sample

    The three prepared samples cover Hangul, Latin and a mixed line at five sizes. Your own string is what shows whether the digits line up, whether the mixed-script line sits on one baseline, and whether the small sizes hold.

Common questions

It will not open my WOFF2. Why?

WOFF2 is Brotli-compressed and the web platform does not expose a Brotli encoder or decoder to a page — `CompressionStream` has deflate and gzip and no more. So no in-browser tool can read one, this included. Convert it with `woff2_decompress` or fonttools on a desktop, or use the original TTF.

The sample text is not in my font. What went wrong?

The panel note says so when it happens: the parser read the file but the browser’s FontFace refused to register it, and the message from the browser is printed. That usually means the file is damaged in a way the parser tolerates and the font engine does not — a broken table checksum, or an sfnt structure the engine rejects.

Does it read every OpenType table?

No. It reads `name`, `head`, `hhea`, `OS/2`, `post`, `maxp`, `cmap` (formats 0, 4, 6 and 12), `fvar`, `loca` and `glyf`. The layout tables — `GSUB` and `GPOS`, which hold kerning, ligatures and script-specific features — are listed but not decoded, so this cannot tell you which OpenType features a font supports.

The variable font preview does not move.

The sample is drawn at the default instance. The axes are listed with their ranges and defaults so you can write `font-variation-settings` yourself, but this page has no slider for them — reading the axes and animating them are different jobs, and only the first one is here.

Feed it from

Next

These accept what this tool produces, so the result can go straight in.