Unlicensed font use
It usually starts with something that feels completely normal
Most unlicensed font use doesn’t feel like a problem when it begins.
A font is:
Activated in a design tool
Used in a project
Shared with a team
Deployed on a website
Everything works. Nothing breaks.
So it’s reasonable to assume everything is covered.
Why this happens
Modern font platforms are designed to feel frictionless.
You click once, and the font is available:
In your design software
In your files
In your workflow
It feels like you have the font.
In most cases, you don’t.
What you have is access to use it under specific conditions.
Those conditions are not always visible at the point of use.
Where Adobe workflows create problems
Adobe Creative Cloud is widely used in agencies and design teams.
It works extremely well for design.
But the licensing model is often misunderstood when work moves beyond that environment.
Client websites
If you build a website for a client using Adobe Fonts:
The font is linked to your Adobe account
The client does not automatically have the right to use it
The website is expected to run under the client’s own subscription
In practice, this means:
The client must set up and maintain their own Adobe subscription to continue using the fonts.
If that doesn’t happen, the setup is not stable.
Ongoing dependency
Adobe Fonts are typically:
Served from Adobe’s systems
Linked to an active subscription
Dependent on continued access to the service
If the subscription changes or stops:
Fonts may no longer render
Projects may need to be reconfigured
No transfer of ownership
In most cases:
You cannot transfer the font to your client
You cannot host it independently
You cannot pass it on as part of a brand system
This is where many organisations assume they are covered—but aren’t.
Why this becomes a compliance issue
At first, everything works.
The issue only appears when something changes:
The client asks for full ownership
Procurement reviews the setup
Legal checks licensing
The website is handed over
At that point, the question becomes:
Who actually holds the licence?
If the answer is unclear, the setup needs to be corrected.
The broader industry reality
This isn’t limited to one platform.
Across the industry, licensing models often include:
Restrictions that are not obvious at the point of use
Permissions that change depending on context
Terms that require interpretation later
In some cases, organisations are contacted about usage they didn’t realise was restricted.
This can include:
Embedded fonts in documents
Fonts bundled with software
Legacy assets still in use
These situations are usually administrative—but they still require time and resolution.
Common signs something isn’t aligned
You may want to review your setup if:
Fonts are tied to individual user accounts
Client projects depend on third-party subscriptions
Font files are not held by the organisation
There is uncertainty about who licensed what
The setup would be difficult to explain to procurement
These are all common, and fixable.
A simple way to check
1. Where is the font used?
Website
Product or app
Brand assets
Documents
2. Who controls the licence?
An individual designer
An agency
A platform subscription
The organisation itself
3. Would the setup still work if that changed?
If the subscription ended
If the project was handed over
If procurement reviewed it
If the answer is uncertain, it’s worth clarifying.
A more stable approach
The simplest way to avoid these situations is to use a licence that reflects how organisations actually operate.
That means:
The organisation holds the licence
Fonts can be used across all media
Teams and partners can work with them
There is no dependency on external platforms
This removes the gap between “what works” and “what is licensed”.
How Newlyn approaches this
Newlyn licences are based on Business Size.
Each licence:
Covers the entire organisation
Allows use across all media and applications
Can include distribution to third parties working with you
Does not depend on a third-party platform to function
This means:
No subscription dependency
No ambiguity about ownership
No need to reinterpret usage later
If you think your setup might not be correct
You don’t need to map everything out first.
Most situations are straightforward once they’re clearly defined.
If you’d like a second opinion, we’re happy to take a look.
Just drop me an email.
Related
To understand how licensing works:
For compliance:
If you’re reviewing your setup:
For enterprise use: