This guide outlines general fact-checking steps for reference only. It is not legal advice. If you've received a demand letter or a settlement request, talk to a qualified attorney. How the law applies depends on the facts and where you are.
Understanding Font Copyright Inquiries and Licensing Letters
Foundries, legal representatives, and licensing audit agencies occasionally send formal inquiry letters demanding proof of license acquisition for fonts detected on commercial websites, software bundles, or marketing collateral.
When receiving such communications, teams should avoid reactive panic. Instead, conduct a methodical review of your asset acquisition trail and determine whether the assertion involves actual font software replication.
Font Software vs Typeface Design: The Legal Distinction
In the US and many other jurisdictions, courts and copyright offices have generally drawn this distinction:
- Typeface Letterform Design: Historically, the purely artistic design of letterforms is generally not subject to copyright protection under US statutory copyright. Rasterized bitmaps and vector curves rendered into static marketing graphics or printed publications rarely constitute copyright infringement on their own.
- Font Software Program: Digital font files (
.ttf,.otf,.woff2) are legally recognized and protected as computer programs or software code. Copyright liability typically hinges on whether an unauthorized copy of the digital font program was installed, reproduced, or transmitted.
4-Step Checklist for Responding to Inquiries
Step 1: Identify the Specific Typeface Used
- Verify whether the typography in the flagged collateral actually matches the claimed proprietary font.
- Audit agencies occasionally mistake open-source sans-serif typefaces (such as Pretendard, Inter, or Roboto) for proprietary commercial typefaces due to automated optical recognition tools.
Step 2: Trace the Font File Acquisition Trail
- Audit internal design repositories, git commits, and dependency trees.
- If the font was obtained under an open-source license (such as SIL OFL 1.1 or Apache 2.0), reference the official open-source license grant and foundry release notes.
Step 3: Determine Work Ownership (In-House vs Vendor Deliverables)
- Check whether the assets were produced by in-house employees or delivered as finished raster/vector artwork by an external creative agency or contractor.
- If an external contractor properly licensed their desktop tools and delivered finished flat artwork (PDF, PNG), that is evidence the client did not copy the font software itself. Liability can still depend on your contracts and the facts.
Step 4: Issue a Factual, Documented Written Response
- Reply formally with verified factual evidence rather than speculative arguments:
- Precise font family name and version used.
- Licensing framework governing the font (e.g., SIL OFL 1.1 with repository link).
- Production records demonstrating that no unauthorized desktop font files were installed or shared.
Proactive Governance Best Practices
- Standardize on Clear Open-Source Licenses: Selecting typefaces governed by SIL OFL 1.1 makes license checks simpler across product teams.
- Maintain a Font License Ledger: Record verified dates, license types, and upstream download URLs for all brand and UI typographic assets.
