Most agencies think font licensing is straightforward. You buy a font, you use it. Simple, right? Not quite.
The hard truth is that the vast majority of creative agencies are operating with a dangerous blind spot when it comes to font licensing. This isn't about accidentally using a font without buying it; it's about fundamentally misunderstanding what you actually *buy* when you acquire a typeface.
1. The "One License Fits All" Fallacy
You bought a font. Great. But did you buy it for desktop use? For web use? For embedding in an app? For use on a client's internal server? For use on social media ads that might run indefinitely?
Most designers and even many account managers assume a single font purchase grants broad usage rights. This couldn't be further from the truth.
Desktop vs. Web vs. App Licenses
A desktop license allows you to install and use a font on your computer for design and production. That's the baseline.
A web license is different. It's typically based on page views or unique visitors and allows the font to be displayed on a website. Using a desktop font file on a live website without a proper web license is a violation.
App licenses are even more specific, covering embedding fonts within mobile applications or software. Each of these requires a distinct purchase or agreement.
The Hidden Costs of Over-Reliance
Many agencies use the same set of desktop-licensed fonts across all their digital outputs, assuming it's fine. This assumption can lead to:
- Unexpected audit fees from foundries.
- Demands for back-payment, often at inflated rates.
- Legal action, which is rare but devastating.
- Reputational damage if a client is involved.
It's a ticking time bomb that can explode at the worst possible moment.
2. Misunderstanding "Unlimited" and "Perpetual"
Foundries use terms like "unlimited" and "perpetual" to sound generous. But these terms are almost always qualified.
An "unlimited" desktop license usually means unlimited *users* on your *internal network*. It doesn't mean unlimited *projects* or unlimited *client use* outside your direct employment.
A "perpetual" license means you own the right to use that version of the font forever. But it doesn't mean you can use it for *any purpose* forever. A perpetual desktop license does not grant perpetual web or app rights.
The "One-Off Project" Trap
Many agencies grab a font for a specific client project. They pay for the desktop license, use it in the design files, and deliver. Then the client asks for a new website, or wants to use the branding on merchandise.
Suddenly, that initial desktop license is woefully inadequate. The agency either has to:
- Go back to the client and ask them to purchase new, expensive licenses for their own ongoing use.
- Try to retroactively purchase the correct licenses themselves, often at a premium.
- Risk non-compliance.
This is a failure of foresight. The license needs to cover the *entire lifecycle* of the asset, not just the initial design phase.
3. Not Tracking Font Usage Across Clients and Projects
This is the operational black hole for most agencies. Where are your fonts actually being used?
- Which clients are using which specific fonts?
- Are those fonts licensed for their *current* usage (web, print, app, internal docs)?
- Who purchased the license? The agency or the client?
- When does the license expire (especially for subscription-based or usage-limited web fonts)?
Most agencies have no centralized system for this. Font files are scattered across servers, cloud storage, and individual designer machines. License agreements are buried in email archives.
This lack of visibility is the primary reason licenses are violated. You simply don't know what you don't know.
The "It's the Client's Responsibility" Excuse
This is a common deflection. "The client should have bought the license." While clients *are* ultimately responsible for their own brand assets, agencies are the gatekeepers of design and production. You are the expert they rely on.
When an agency delivers work using improperly licensed fonts, the fallout often lands on the agency first. It reflects poorly on your professionalism and due diligence.
4. Failing to Account for Variable Fonts and Variable Licensing
Variable fonts are powerful. They allow a single font file to contain a range of styles (weights, widths, optical sizes) controlled by a slider. This is fantastic for responsive design and efficient web performance.
However, licensing for variable fonts can be complex. Some foundries treat them as a single product, while others might license based on the *range* of variations used.
More importantly, the *usage* of a variable font still matters. Is it on the web? In print? For an app? The underlying licensing principles remain the same, but the specifics around variable font implementation can add another layer of complexity.
5. Ignoring Embedded Fonts and Sub-licensing
What happens when you design a PDF for a client, and that PDF contains embedded fonts? Or when you create an app? Or a digital advertisement that uses a custom font?
Embedding a font in a document or application is a form of distribution. Most standard desktop licenses do *not* permit this without specific embedding rights or a separate license.
Similarly, if you're designing for a client who then hands off your work to another vendor or agency, you need to ensure that vendor has the appropriate license. This is sub-licensing, and it's rarely covered by a basic desktop purchase.
The Risk of Customization
Even modifying a font (e.g., creating custom ligatures, altering characters) can fall into a licensing grey area or even require a specific custom license from the foundry.
Where Revue Fits In
Managing font licenses is fundamentally a workflow and asset management problem. It requires clarity, traceability, and control.
Revue can't magically grant you new font licenses, but it can bring the visibility and control needed to *manage* the ones you have effectively.
Imagine a world where:
- All your client projects are centralized.
- All creative assets, including links to or details about licensed fonts, are associated with those projects.
- Revision histories clearly show which fonts were used and approved at each stage.
- Final deliverables have associated metadata about the assets used, including licensing considerations.
This level of organization is crucial for auditing your font usage, identifying potential compliance gaps, and communicating license responsibilities clearly with clients. It moves font management from a chaotic afterthought to an integrated part of your quality control process.
Final Thought
The creative industry thrives on visual assets. Fonts are foundational to visual identity. Treating font licensing as anything less than a critical, ongoing operational concern is not just negligent; it's a direct threat to your agency's financial health and reputation. Are you truly managing your type, or is your type managing you?
Frequently asked questions
What's the difference between a desktop and a web font license?
A desktop license allows you to install and use a font on your computer for design and production. A web license is specifically for displaying the font on a website, often priced based on traffic or page views. Using a desktop font file on a live website without a web license is a violation.
Can I use a font I bought for one client on another client's project?
Generally, no. Licenses are typically tied to a specific client or project. If you use a font for Client A, and then decide to use the same font for Client B, you usually need to purchase a separate license for Client B, especially if the license was client-specific or project-specific.
What happens if my agency is audited by a font foundry?
If a font foundry audits your agency and finds unlicensed usage, they will typically demand payment for the licenses you should have purchased. This often includes back-payment for the period of unlicensed use, sometimes at a significantly higher rate than the original license cost. Failure to comply can lead to legal action.
Do I need a special license to embed fonts in a PDF or app?
Yes, most standard desktop font licenses do not automatically grant embedding rights for PDFs or inclusion in applications. Embedding or app usage typically requires a specific license from the font foundry, often referred to as an 'embedding license' or 'app license'.