font.zmize®
waking engine…

TYPEFACE FORENSICS · — FAMILIES INDEXED · 5 DETECTORS

Every font leaves a fingerprint.

Drop a binary. The engine unmasks renames, subsets and substitutions — then finds its open-source kin.

0families indexed
0detectors
0sper query, ×10⁻¹
01

Identify a binary

TTF, OTF, WOFF or WOFF2 — renamed, subsetted, it doesn't matter. Five detectors read the outlines, the pixels and the metadata, then vote.

Drop a font file or

ttf · otf · woff · woff2

02

The library

Every family the engine has fingerprinted, rendered live. Search it, filter it, set your own proof line.

03

Compare two families

Stack any two corpus families glyph on glyph. Where the inks agree the overlay reads white; where a design diverges, colour bleeds through — and the detectors put a number on it.

  1. 1 type in slot A and pick from the list — or press enter
  2. 2 same for slot B (or hit a ready-made pair below)
  3. 3 read the glyphs: white = agreement, colour = divergence
  4. 4 the bars below quantify it, detector by detector
A
B

default glyphs = the engine’s fingerprint charset · overlap reads white

04

Resolve a name

System fonts ship no binary to fingerprint. Hand the engine a declared font-family stack and it maps the name to open-source equivalents instead.