Five checks before anything reaches you.
Finding a font file on a website is easy. Proving that it is a trial build, that it is still there, and that it is actually in use takes more work. This is that work.
The verification flow
From candidate to evidence
-
Web-scale scan finds candidate sites
We look across millions of websites for fonts that might be trial or demo builds of commercial typefaces. This step casts a wide net. Nothing found here goes to a foundry on its own.
-
Live re-check fetches the font the site serves now
We load each candidate site again and download the actual font files it serves today. Sites change. In one earlier pass, about a third of newly found candidates were no longer serving the trial file by the time we re-checked: it had been swapped, removed, or the site was gone. Those never become leads.
-
The trial marker is read from inside the font
Every font file carries a name table: the family name, the style, the version, the copyright line. Trial builds usually say so there, with words like "Trial", "Demo" or "Unlicensed". We read that table directly from the file.
Where a foundry names its trial files in a recognisable way, that naming counts as a marker too. It is a weaker signal, and we grade it that way.
-
We check the font is in use
A file sitting on a server is not the same as a font in use. Where we run an in-browser check, we confirm the trial font is applied to visible text on the page, such as headings, navigation or body copy, and the dashboard says so for that lead.
-
Dated evidence: file fingerprint and screenshot
We keep the date of the check and a hash of the exact font file served, plus a screenshot of the page wherever the site allows one to be captured. The hash lets anyone confirm later that the file we describe is the file the site delivered.
Evidence strength
Every lead is graded
Not all evidence is equal, and we do not pretend it is. Each lead shows which marker we found, so you can start with the clearest cases.
| Strength | What we found | Share of latest pass |
|---|---|---|
| Strong | The font's own name table identifies it as a trial, demo or unlicensed build. | 94% |
| Supporting | The file matches the foundry's own trial file naming. | 5% |
Shares from 23,908 leads re-checked live between 13 and 15 November 2026: 22,030 with a name-table marker, 1,273 with a trial file-name marker.
What a lead is not
A potential issue, not a verdict
A trial font on a live site is a strong sign that a licence conversation is needed. It is not proof that anyone has done anything wrong. Plenty of site owners bought a full licence and simply uploaded the trial file by mistake. Some have a private agreement we cannot see.
That is why we never call a lead a breach. You compare it with your own sales records. Then you decide what to do, or authorise us to do it for you.
We also leave out what we cannot stand behind. Development, staging and preview sites are filtered out, and a site that serves the same trial font on several addresses counts once.
Want to see the evidence for your fonts?
We will set up a free, locked preview of your foundry's dashboard.