How a Trial Font Ends Up on Your Favourite Coffee Shop's Website
Six very human routes from "just testing" to "live in production", and how to close each one
Abstract. Our verified pass found 23,303 potential licence issues across 22,289 websites, and almost none of them look like deliberate piracy. They look like six ordinary workflow gaps, from a designer's test file that ships to a licence that was bought but never actually uploaded.
Key findings
- 23,303 potential licence issues on 22,289 websites, across 150 foundries.
- Six recurring routes explain how trial fonts reach production.
- 95% of cases carry a trial marker inside the font itself, so the file is announcing what it is. Nobody's reading it.
- The median affected site serves 2 trial styles; about 1 in 10 serves 7+.
- 1,160 cases (~5%) are variable-font trials.
- Food and drink makes up 13% of classifiable cases, second only to software and AI (16%).
- In an earlier pass, about two thirds of ~13,000 re-checked candidates were still serving the trial. Once it lands, it stays.
Picture it
Your favourite coffee shop. Lovely flat whites, a sourdough situation that sells out by
- Their website is gorgeous: chunky, characterful display serif on the menu, a little wink of a script on the "Visit us" button.
There's a real chance one of those fonts is a trial file.
Not because the owner is a criminal mastermind. Because somewhere between "we need a website" and "it's live!", a trial font slipped through a gap nobody knew existed. Food and drink is 13% of the cases we could classify by industry, so this isn't a hypothetical vibe. It's a pattern.
Here are the six routes we see, over and over.
Route 1: The designer's test ships
The classic. A designer is exploring options for the brand. They grab trials of three or four display faces, drop them into the mockup, and the client falls in love with one.
Then the build starts. The developer takes the font files from the design folder, because that's where the fonts are. Nobody stops to ask "is this the licensed version?" because nobody realises there's a difference.
Launch day. Trial font, live, forever.
Close the gap: when a font is picked, buying the licence is part of picking it. Same day.
Route 2: The licence was bought, but the wrong file went up
This one deserves real sympathy. Someone did everything right. They bought the licence. The licensed files are sitting in their downloads folder.
Right next to the trial files. With nearly the same name.
They upload the wrong one. The site looks identical, so nobody notices. Technically they're covered, practically they're serving a trial build.
This is exactly why we never call a case a "breach". It's a potential licence issue, and for some site owners the fix is a two-minute file swap of something they already paid for.
Close the gap: delete trial files the moment you buy. Or keep them in a folder literally called "TRIALS DO NOT SHIP".
Route 3: The agency starter kit
Agencies love a good starter kit, and fair enough: a reusable project template with sensible defaults, components and, yes, some fonts already wired in.
If one of those fonts was a trial when the kit was made, every site built from that kit inherits it. One trial file, copied into project after project.
Close the gap: audit the starter kit, not just the client site. Fix it once, fix it everywhere downstream.
Route 4: Templates and themes
Similar story, different source. Someone buys or downloads a website template or theme, and it ships with fonts bundled in. The buyer reasonably assumes "it came with the theme, so it's fine".
Sometimes it is. Sometimes the theme's demo used a trial build and nobody swapped it.
Close the gap: treat bundled fonts like any other asset you didn't make. Check where they came from.
Route 5: The full-family (or variable) trial
Some trials are generous: the whole family, every weight, sometimes as a variable font. That's brilliant for testing and dangerous for shipping, because once you've got Thin through Black on tap, you use them all.
This is where you get sites serving 7 or more trial styles (about 1 in 10 affected sites). And with 1,160 variable-font cases in our data, a single file can quietly stand in for an entire family licence.
Close the gap: decide the styles you actually need before you build, then license those. You'll often find you only needed three.
Route 6: Nobody owns fonts
The quietest route, and maybe the biggest. In lots of teams, fonts aren't anybody's job. The designer thinks the developer handled it. The developer thinks the client bought it. The client thinks the agency's fee covered it. The agency has moved on to the next project.
Everyone's acting in good faith. The font just falls between the chairs.
Close the gap: give fonts an owner. One person, one line in the launch checklist: "fonts licensed for web, licensed files uploaded".
The six routes at a glance
| Route | What happens | Five-minute fix |
|---|---|---|
| Designer's test ships | Trial from the mockup goes to the build | License the font when it's chosen |
| Wrong file uploaded | Licence bought, trial file deployed | Delete trials after purchase |
| Agency starter kit | Trial baked into a reusable template | Audit the kit once |
| Templates and themes | Trial bundled with a theme | Check bundled font sources |
| Full-family / variable trial | Every weight used, all trial | Pick styles, then license them |
| Nobody owns fonts | Everyone assumes someone else did it | Add fonts to the launch checklist |
Why it sticks around
Trial fonts don't break. The site looks great, so nothing nudges anyone to check. In an earlier pass, around 13,000 new candidates were re-checked and about two thirds were still serving the trial. These things live a long time.
And the clue is usually right there. In 95% of our cases the font's own internal name says "Trial", "Demo" or "Unlicensed". It's like a jumper with the shop tag still hanging off it. Obvious once you look, invisible until you do.
If you're the coffee shop (or their designer)
Open your site's font files, or ask whoever built it. If anything says Trial or Demo:
- Check whether you already bought the licence. If yes, swap in the licensed file. Done.
- If not, buy the web licence that covers the styles you use. Type designers will love you for it.
Methodology
- Window: data checked 13 to 15 November 2026, single FontRights verified pass.
- Base: 23,303 potential licence issues on 22,289 distinct websites across 150 foundries.
- Verification: web-scale scan; live re-download of the served font (about a third of candidates drop out here); trial marker read from the font name table, or foundry trial file naming as a weaker signal; in-browser check that the font draws visible text; dated file hash and screenshot. Dev/staging filtered, duplicates counted once.
- Routes: the six routes summarise the recurring patterns behind cases; they're qualitative, not a measured breakdown.
- Industry share: of the roughly half of cases that could be classified.
- No sites, fonts or foundries are named.
How to cite: FontRights (2026). How a Trial Font Ends Up on Your Favourite Coffee Shop's Website. Software Automated Ltd. Data checked 13-15 November 2026.
Foundry folks: curious how many of these routes lead back to your fonts? Take a look at the free locked dashboard preview (counts, evidence mix, list value, sites masked). Email max@fontrights.com or visit fontrights.com.
Published by FontRights (https://fontrights.com), revenue recovery for type foundries. Contact: max@fontrights.com


