Short answer: there is no reliable industry-wide percentage showing exactly how often brands misuse desktop font licences.
It happens often enough to deserve a proper check, but the problem is usually less dramatic than deliberate piracy. Desktop font licence misuse commonly begins when a legitimate font purchase quietly travels beyond its original limits: more people install it, an agency shares it, a developer uploads it to a website or somebody adds it to an app, server or editable template.
A desktop licence is not a magic “use this font everywhere” receipt. It is permission to use font software under a particular agreement. The exact end-user licence agreement, or EULA, decides who may install the font, what they may create and whether another licence is needed when the brand moves into a new medium.
How common is accidental font licence misuse?
No credible study gives us a current percentage for brands specifically, so any figure should be treated with suspicion. An older Extensis survey of more than 2,250 self-selecting design professionals found that 32% said they would “locate” a copy of a font online. The same research found widespread font sharing without licence checks. That survey is not a census of businesses and does not prove that 32% of brands infringe font licences, but it does show how easily font files can enter a professional workflow without a clean purchasing record.
The more useful answer is this: accidental misuse becomes more likely whenever a project outgrows the person, device or medium covered by the original purchase. A one-person identity project becomes a twelve-person marketing team. A printed campaign becomes a live website. A static advert becomes an editable digital template. Nothing feels like a major change on Tuesday afternoon, but the licence position may have changed completely.
What does a desktop font licence normally cover?
A typical desktop font licence allows a stated number of users or computers to install the font and use it in desktop software such as Adobe Illustrator, Photoshop or InDesign. It will commonly cover the creation of print and static artwork, including packaging, posters, presentations and flattened images. “Typical” matters here: foundries write their own terms, and one EULA cannot be used to interpret another.
For example, my font EULA links permitted installation to the number of computers stated in the order and separates desktop use from webfont, app, electronic document, digital advertising, email and server use. Other suppliers structure their licences differently. Adobe also states that fonts installed independently in a computer’s Fonts folder remain governed by their own EULAs, not automatically by Adobe Fonts’ terms.
| Use | What is happening | Licence commonly needed |
|---|---|---|
| Print or static artwork | The font is used on licensed computers to create finished, non-editable artwork. | Desktop |
| Live website text | Font files are served to a visitor’s browser. | Webfont |
| Mobile or desktop app | The font software is embedded in an application. | App or software embedding |
| Commercial PDF or e-book | The font data is embedded so the document displays correctly. | Electronic document or ePub |
| HTML5 advert or HTML email | The font is loaded as live type rather than supplied as a flat image. | Digital ad or email |
| Automated platform or server | A system generates documents, graphics or personalised content using the font. | Server or custom licence |
This table is a guide, not a substitute for the EULA supplied with the font. Some licences bundle several uses together; others separate them or price them by users, apps, titles, page views, impressions or company size. Monotype’s overview of common licence types gives another useful comparison.
What are the most common desktop font licensing mistakes?
1. The team grows but the desktop allowance does not
A licence is bought for one designer. Six months later the font is installed on the brand manager’s laptop, two freelancers’ computers and an agency workstation. Nobody set out to misuse it. Everyone simply assumed that “we bought the font” meant the whole company could install it.
2. The agency and client assume the other one is covered
An agency may be licensed to create finished artwork for a client without giving the client a right to install the font software. If the client needs to edit files, produce new work or pass the font to another supplier, it may need its own licence. Adobe makes a similar distinction: a client can receive properly embedded or rasterised output, but needs its own entitlement if it requires direct access to the fonts for editing.
3. A desktop font is uploaded to a website
Using a font to create a JPEG for a website is not the same as loading the font as live HTML and CSS text. The first may fall within desktop use; the second normally requires webfont rights and suitable webfont files. Changing an OTF into WOFF2 does not create permission. It merely creates another file.
4. The font is added to a shared template platform
Uploading a font to a cloud design system, online template builder or digital asset platform can make the font available to users and systems beyond the licensed desktops. Whether that is allowed depends on the EULA and how the platform stores and serves the file. A desktop licence should not be assumed to cover it.
5. Static artwork turns into an app or product feature
A designer may use the font legitimately to mock up an interface. The trouble starts when the font software is bundled into the finished app, game or device. A mock-up is artwork. Embedded font software is part of the product. Those are different uses and are commonly licensed separately.
6. A supplier receives the actual font file
Packaging suppliers, printers, production studios and freelancers are often sent a folder containing everything, including the OTF or TTF. Some EULAs permit limited sharing with approved suppliers; others require those suppliers to hold their own licences or prohibit transfer. Sending a file is technically easy. Granting legal permission is the foundry’s job.
7. Nobody checks what happens after the rebrand
The original licence may have been correct on launch day. Then the brand adds an app, international sites, editable social templates, digital billboards and a second agency. Font licences rarely expand by telepathy. A new channel should trigger a new licence check.
A realistic example of accidental misuse
Imagine an agency buys a two-computer desktop licence while developing a new identity. It creates the logo, packaging and presentation artwork. So far, so sensible.
After approval, the client asks for the font files. The files are installed on eight company computers, uploaded to the website, added to an internal template system and embedded in the brand’s customer app. The original purchase was genuine, but it may now be short on desktop users and missing webfont, server and app rights. One font has quietly become four licensing questions.
This is why “Did we buy it?” is not enough. The better question is: “Does the licence we bought cover the way we use it now?”
Can a desktop font licence cover a logo?
Often, yes: many desktop licences allow a designer to use the font to create static logo artwork. But logo use does not automatically give the brand ownership of the font software, exclusivity over the typeface design or clearance to register and use the resulting mark in every territory. The EULA governs the font software; trade mark clearance is a separate question.
If exclusivity or a distinctive ownable typographic voice matters, a custom font or piece of custom lettering may be a cleaner route. The agreement should state who owns what, who may use the files and where the work can appear.
How do you audit a brand’s font licences?
- List the fonts in active use. Check logos, packaging, campaigns, presentations, websites, apps, emails, video, templates and internal systems.
- Find the source of each font. Keep the receipt, supplier, EULA version and purchaser together.
- Count the users and installations. Include employees, freelancers, agencies and suppliers with access to the actual font files.
- Separate static output from embedded use. A flattened image is not the same as a font loaded by a website, app or document.
- Check every third-party platform. Review cloud tools, template systems, servers and automated production software.
- Compare present use with the agreement. Do not rely on the licence name or what somebody remembers buying.
- Record an owner and review date. Make somebody responsible for checking the licence when the team, supplier or channel changes.
A yearly review is a useful baseline, but do not wait twelve months after launching an app or handing the files to a new agency. Review the licence whenever the use materially changes.
What should a brand do if the licence is wrong?
First, stop casually distributing the font file and establish exactly where it is installed or embedded. Then contact the foundry or authorised seller, explain the actual use and ask what additional coverage is required. In many cases the practical fix is simply to add users or purchase the correct licence extension.
Keep the revised licence, invoice and usage notes in one place. Removing a font from a new project does not retrospectively grant permission for past use, so obtain legal advice if the history is complicated or a claim has already been made. This article is general information for UK businesses, not legal advice.
Frequently asked questions
Does buying one desktop licence cover the whole company?
Not usually. Desktop licences are often limited by users, computers or workstations, although some suppliers offer company-wide terms. Check the order and EULA rather than assuming every employee is covered.
Can a designer’s desktop licence cover the client?
It may cover the designer creating and supplying finished artwork, but it does not automatically allow the client to install the font or create new editable work. The client may need a separate desktop licence.
Can I use a desktop font on a website?
You can commonly use desktop software to create a static image that appears on a website. Serving the font as live website text normally requires a webfont licence. Check the specific EULA.
Does converting text to outlines solve the licensing problem?
Outlining text can be an appropriate way to deliver fixed artwork, if the EULA permits it. It does not legitimise an unlicensed installation, allow the original font file to be shared or replace app, web, server or template rights where font software is still being used.
Can a desktop font be uploaded to Canva or another cloud platform?
Not automatically. Uploading a font to a third-party platform may involve remote storage, additional users or server-based use. Check both the font EULA and the platform workflow before uploading it.
How often should a company audit its font licences?
Review them at least annually and whenever there is a rebrand, website rebuild, app launch, new agency, larger creative team or new template system. The trigger is a change in use, not merely the date on the calendar.
Make the licence fit the work
Font licensing should not require a detective with a corkboard and a length of red string. It does require a few clear answers: who is using the font, where it is installed, whether the font software is embedded and what the EULA permits.
If you are choosing one of my retail fonts, select the desktop allowance and any additional use you need. For company-wide, server, games, broadcast or anything unusual, tell me about the project and I can quote for a licence that fits the actual job.