In the United States, the letter shapes are not what a foundry owns, the font file is. That file is a small program, and copying, installing, or serving it outside your license is software copyright infringement no matter how ordinary the typeface looks. This is why a font demand letter reads like a software audit notice rather than an argument about art.
Most font licensing infringement is a licensing gap, not piracy. A desktop font uploaded as a webfont, an app shipped with fonts nobody cleared, forty seats covered by a three-seat license, those are the facts behind most letters. Foundries generally want a true-up purchase, you pay for the licenses you should have bought, and their demands are negotiable. Here is how the rights divide, how foundries find unlicensed use, and what to do before or after a letter arrives.
A Font File Is Copyrighted Software Under US Copyright Law
The letterforms themselves have never been copyrightable here. The Copyright Office's regulations exclude typeface designs from copyright, and the Fourth Circuit upheld that position in Eltra Corp. v. Ringer in 1978. Design patents exist for typefaces but are rare and short-lived. In practice. That means a competitor can legally redraw a typeface, and almost nobody bothers, because the file matters more than the drawing.
The file is where the money is. The outline data, hinting instructions, kerning tables, and layout logic inside a TrueType, OpenType, or PostScript font add up to a computer program, and programs are copyrightable. In Adobe Systems v. Southern Software, a federal court in Northern California held in 1998 that scalable font programs are protectable as software even though the typefaces they render are not. Every font claim you will ever see is built on that distinction: the foundry says you copied, installed, distributed, or embedded its program without permission.
Two consequences follow. First, foreign foundries may claim more than US law allows. The UK and much of continental Europe protect typeface designs directly, so a letter from a European foundry may assert rights a US court would not recognize; where the use happened usually decides whose law applies. Second, the license agreement does most of the real work in these disputes. The copyright claim gets the letter opened. The EULA determines what you actually owe.
Desktop, Webfont, and Embedding Rights: Where Font Licenses Diverge
A font license is a scope agreement. You are not buying the font; you are buying permission for defined uses, and the categories rarely overlap.
Desktop licenses cover installation on a set number of machines, seats, and static output: print, packaging, logos, flattened images. Most desktop EULAs let you convert text to outlines for a logo. Few allow glyph modification, and web serving is rarely included.
Webfont licenses cover live text in a browser. The file sits on your server and is delivered to every visitor, which is reproduction and distribution a desktop license never grants. Webfont licensing is typically priced by domain and traffic, in pageview tiers usually measured monthly, with an obligation to upgrade when you cross a tier. Uploading a desktop TTF and pointing your CSS at it is the most common form of font licensing infringement foundries encounter, and it is trivially easy for them to spot.
Embedding rights are the quiet trap. Mobile and desktop apps, games, ebooks, PDFs with embedded fonts, and server-side rendering, a SaaS product that generates branded PDFs, for example, each usually require a separate license or add-on. Modern font files carry an embedding-permission field in their internal tables, but it is advisory metadata. The EULA governs, always.
Subscription font libraries bundle some rights, commonly desktop use plus web serving, but app embedding, server-side rendering, and embedding in products usually sit outside them. And when an agency hands off design files, its licenses do not transfer to you. If the work will outlive the engagement, buy your own licenses from day one.
Foundry Compliance Audits: How Unlicensed Fonts Get Found
Nothing about it is exotic. If a font is served from your website, anyone can download it, including a foundry's crawler. The file's internal name tables identify the family, style, version, and manufacturer, so identification takes minutes. Several foundries also embed subtle variations or hidden identifiers that tie a specific copy to a specific sale or channel, which is how a pirated file gets traced back to the purchase that leaked it.
Detection usually comes from one of four routes: crawlers watching CSS for @font-face references to their fonts; the same crawlers indexing pirate download sites; tips from departing employees, freelancers, or competitors; and rebrands, where a new agency opens an old brand system and finds fonts nobody can produce paperwork for. The major type houses run dedicated compliance programs and send letters in volume. Reading publicly served files is not hacking, a webfont your site hands to every visitor is not private, so an audit built from that evidence is entirely legitimate.
What a Font Demand Letter Actually Claims
Most letters follow a template. They assert that your company reproduced and installed the foundry's font software without a license, or beyond one: the file copied to fifty machines under a five-seat grant, or embedded in a product the license never covered. Distribution claims are common too, fonts passed to contractors, bundled into deliverables, shipped inside an app. Layered on top is breach of the EULA, and occasionally trademark claims over the font's name, an area where trademark and copyright pull in different directions.
The legal stick is US copyright: the exclusive rights in Section 106 of the Copyright Act, statutory damages under Section 504(c), $750 to $30,000 per work, up to $150,000 where the use was willful, and attorney's fees under Section 505. What the letter will not mention: statutory damages and fees generally require that the foundry registered the copyright before the infringement began, or within three months of publishing the font. Registration status shifts leverage in these negotiations more than anything else, and registration practices vary widely across the industry.
The demand is usually a retroactive license purchase, sometimes at list price, sometimes at a multiple, plus a deadline, often one to two weeks, and sometimes a request to audit your systems or sign a confidentiality clause. Read it as an opening position, not an invoice. It is a commercial cease-and-desist-style claim, not a DMCA notice, and the difference between the two shapes how you respond. These letters settle regularly; the realistic range sits between a properly scoped license true-up and the number on the page, and it shrinks the faster you engage credibly. For context on the worst case, it helps to understand how copyright infringement penalties stack up.
Font Licensing Hygiene That Prevents the Letter
Audit yourself before someone does it for you. The process is short and mechanical:
- Inventory every font in use, workstations, design files, templates, build systems, shipped products, and every @font-face rule in your CSS. Include contractor machines.
- Match each font to paperwork: an invoice, a license certificate, a subscription entitlement, or an open-source license file.
- Check scope, not just existence. A three-seat license on a forty-seat team is not a license.
- Close the gaps you find: true up seats, add the webfont or app license, or replace the font with something you can defend.
- Assign one owner for font purchases and keep the records indefinitely. Invoices are your proof if a letter ever names a font you bought frankly.
Watch the slow leaks, too. Pageview tiers creep upward with traffic. Subscription plans change terms at renewal. Rebrands inherit agency fonts and template fonts with no paper trail. The cheapest moment to fix all of this is a rebrand: every font in a new identity should arrive with a license file and an invoice, or be an open-source family, fonts under the SIL Open Font License permit web serving and app embedding under their terms, which makes them the low-risk default for growing teams.
Responding to a Font Demand Letter: The Practical Playbook
Preserve everything first. Copy the fonts, the design files, the purchase records, and the letter itself before anyone deletes or replaces anything mid-dispute. Destroying files after notice creates far worse problems than the notice.
Then verify. Is the font actually theirs? Typefaces have lookalikes, and the file in your design system may be a different product with different ownership. Pull the file the letter identifies and read its name tables against your inventory. Do you hold a license with different scope? Did a contractor or a template bring the font in? Every answer changes the resolution.
Scope the gap frankly: how many seats, how many fonts, how long, in what products. Price the true-up at list. That number, not the letter's, is your floor for negotiation.
Respond in writing before the deadline. Acknowledge receipt, dispute what is wrong, and propose a resolution. Silence is the worst move available: it invites escalation and hands the foundry its willfulness argument. While negotiating, remove the font from live use once you have preserved copies, continued use after written notice is what pushes statutory damages toward the willful end.
If the letter claims willfulness, cites six figures, or demands an audit with signed admissions, that is when to hire a copyright lawyer before signing anything. Whatever you settle, settle on paper: the payment should come with a written release covering past use, naming the fonts and the scope it resolves.
When Font Claims Escalate
Lawsuits happen, but they are the exception. Foundries litigate when the use is large, well documented, and continued after notice, because willfulness is the engine of the damages math. Without timely registration, a foundry is limited to actual damages and profits, which for a single font license are usually modest, one reason both sides tend to land on a number.
Smaller fights have a smaller forum. The Copyright Claims Board can hear copyright claims valued up to $30,000, though a foundry choosing that route is uncommon. Most font disputes end at the letter stage because the economics favor settlement.
If you are on the other side, a type designer or foundry whose fonts are being shared on download sites, enforcement looks like any other software piracy problem: identify the files, document the copies, and use DMCA takedowns to strip pirated font files from file lockers and warez sites. That is work our team at WebDMCA does for rights holders every day, and the evidence discipline is the same: dated captures, file records, and a clean chain from your registration to the infringing copy.
Font Licensing FAQ
Do I need a webfont license if I already bought the desktop font?
Yes, under nearly every EULA. Desktop rights cover static output, print, logos, flattened images. Live text in a browser is served from a copy of the font file on your server, which is reproduction and distribution a desktop license does not grant. A few foundries bundle both rights, but most sell a separate webfont license priced by domains and pageview tiers.
Can a foundry claim copyright in the letter shapes themselves?
Not in the United States. Typeface designs are excluded from copyright here, but the font file is protected as software, and that is what the claims ride on. The UK and much of continental Europe do protect typeface designs directly, so a foreign foundry may assert broader rights than a US court would recognize. Assume the file is protected everywhere.
What happens if I ignore a font demand letter?
Deadlines pass, demands grow, and continued use after written notice hands the foundry its willfulness argument, the route to statutory damages and attorney's fees. Ignoring also wastes the window to dispute the claims or negotiate the number down. Answered early and credibly, most of these letters resolve well below the opening demand.
Am I liable for fonts my agency or freelancer installed?
Often, yes. You are the party still using the deliverables, and agency licenses almost never transfer to the client. Handing off live-text design files or embedding fonts in a product usually requires you to hold your own licenses. If the contractor cut corners, your recourse runs against them under the contract, but the foundry's claim lands on the current user.
Are free font download sites safe?
Rarely, when they offer commercial typefaces at no cost. Those files are typically pirated software, and some carry the hidden identifiers foundries use to trace a leaked copy back to its original sale. Genuinely free fonts exist, SIL Open Font License families and the like, where the license travels with the file and permits web serving and app embedding.
Your Next Steps
- Inventory your fonts, machines, templates, shipped products, CSS, before someone else does it for you.
- Match every font to an invoice, a subscription entitlement, or an open-source license file.
- Check scope against reality: seats, pageview tiers, embedding, server-side rendering.
- Close the gaps now, true up seats, buy the webfont or app license, or swap to a defensible open-source family.
- Assign one owner for font procurement and keep purchase records permanently.
- If a letter has already arrived, preserve everything, verify the claims, price the true-up, and respond before the deadline, and get professional help if the ask has more digits than you expected.
WebDMCA is a professional takedown and content-protection service, not a law firm. If your fonts are being pirated, that is squarely our work. If you are staring at a six-figure demand, the right first call is a copyright attorney, then a licensing cleanup so it never happens again.