Font licensing is the set of terms that says where, how and by whom a typeface may be used, and it is usually split by use: desktop, web, app and document embedding. Owning a copy of a font file rarely means permission for every use.
Licence choices sit alongside the visual decisions covered in typography basics, but they work on different rules: type choice is about design, while a licence is a legal agreement with the rights holder.
Why a font comes with a licence
A font file is software, and the designs inside it are the work of the type designer or foundry. A purchase or download normally grants permission to use that software under stated conditions rather than ownership of the design. Those conditions come in an end-user licence agreement, or in an open licence published with the font.
That is why the same family can be fine for a printed poster, restricted on a website and different again inside a mobile application. Each of those uses is a separate act: installing a file on a computer, serving a file to visitors, or packaging a file inside software. A licence may cover some of them and ignore the rest.
This page gives general information only and is not legal advice. When a use is not clearly covered, read the actual licence text and ask the rights holder, which is usually the foundry or the designer named in the font file.
Desktop licences
A desktop licence covers installing the font on computers so that designers can set type in layout, illustration and image-editing software. Typical terms limit the number of computers or users, and many separate personal, commercial and agency use. What a desktop licence does not usually include is permission to copy the font file onto a server or to hand the file to other people.
The output of the software is often treated differently from the font file itself. Microsoft states in its font FAQ that it views creating graphic files as being essentially the same as printing from an output device, which is why a poster or logo made with a Windows-supplied font is treated like print output. That statement applies to the fonts supplied with Windows and is not a rule for other foundries, whose terms vary.
Print and image work, such as the layouts shown in a presentation mockup, normally involves only the rendered result. Delivering the editable file to a client is different, because the working file may contain the font itself. Many licences expect the client to hold their own licence in that case.
Web licences
A web licence covers serving the font to browsers. In the Microsoft FAQ’s words, web fonts are fonts that are hosted on a web server, and the same page says a Windows licensee has no right to copy fonts from a Windows installation to a web server or to convert a font to the formats typically associated with web fonts, such as WOFF or WOFF2.
The point carries beyond Windows. A desktop licence and a web licence are separate grants, and converting a desktop font into a web format for a site can fall outside the first one.
Open licences handle this differently. The SIL Open Font License answers the question directly: in the OFL FAQ, fonts may be used to make webpages, and loading the fonts dynamically as webfonts through CSS @font-face declarations is described as a much better method than asking visitors to install them. The same FAQ adds that a change in font format normally is considered modification, and that Reserved Font Names cannot be used for modified versions, though WOFF and WOFF2 compression can be done without counting as modification when the original font data is left unchanged.
Font choice also affects the page’s speed, a subject treated in the guide to variable fonts, where one file can replace many separate style files.
App and software licences
Putting a font inside an application is a form of redistribution, because every copy of the app carries the font. Commercial foundries therefore usually sell a separate app licence, with terms that depend on how the font is packaged, how many apps use it and how many installs there are.
Open licences can be more permissive here. The OFL FAQ says fonts under the licence can be sold as part of a software package, and lists text editors, word processors, design and publishing applications, training and educational software, games and entertainment software, and mobile device applications as examples of bundling it makes possible. The reason for the limit is spelled out in the same document: the intent is to keep people from making money by simply redistributing the fonts, so a font cannot be sold on its own.
Where an app only displays text in a system font, the situation is different again. The font belongs to the operating system, and the app’s maker is relying on the platform’s licence rather than shipping the file. Apps that ship their own font file need their own permission.
Embedding in documents
PDFs, slide decks and word-processor files can carry a font so the reader sees the intended design. Whether that is allowed is recorded inside the font itself. The OpenType specification’s OS/2 table defines embedding levels. Under installable embedding, the user of the remote system acquires the identical rights, obligations and licences for that font as the original purchaser. Under restricted licence embedding, the font must not be modified, embedded or exchanged in any manner without first obtaining explicit permission of the legal owner.
Between those sit preview and print embedding, where the document opens read-only, and editable embedding, where the recipient can change the text. Microsoft explains in its font FAQ that applications such as Word and PowerPoint follow these flags, so those programs check what a font permits before embedding it.
Embedding is not the same as extracting. The same FAQ warns that hidden fonts, which may be embedded in code, should not be extracted and used. The OFL treats embedding as a special case too, noting that a font embedded in a document does not change the licence of the document itself.
Comparing the licence types
The table summarises typical differences. Every foundry writes its own terms, so treat each row as a starting point for questions to put to the rights holder, not as a promise.
| Use | What the licence usually covers | Questions to ask |
|---|---|---|
| Desktop | Installing the font on computers to set type in design software | How many users or computers, and is commercial work included? |
| Web | Serving the font to visitors through CSS | Are there limits on page views, domains or self-hosting? |
| App | Packaging the font file inside software | Does it cover each app and every install? |
| Document embedding | Storing the font inside a PDF or office file | Does the embedding flag allow preview, print or editing? |
| Open licence | Broad use, with conditions on redistribution and modification | May the font be sold alone, and may it be renamed or modified? |
For the open licence row, the OFL FAQ says authors allow the font software to be used for any kind of design work, and that you remain the author and copyright holder of the graphic or object you make with it.
Reading a licence before you choose a typeface
The licence belongs in the selection process, early, because switching typeface after a layout is approved is costly. A short routine helps:
- Note every place the font will appear: print, a website, an app, documents sent to others.
- Match each place to a licence type in the table above.
- Check whether the studio, the client or both will hold the licence.
- Keep the licence text and purchase record with the project files.
Pairing decisions come into this too. A project that combines a serif and a sans serif needs a licence for each family, so the cost of a pairing is the sum of its parts. The comparison in serif vs sans serif covers the design side of that choice.
Frequently asked questions
Does a desktop licence cover a website?
Not necessarily. Desktop and web are usually separate grants, and the Microsoft FAQ gives an example of a desktop-installed font that may not be copied to a web server or converted to WOFF or WOFF2.
Can the same font be used in a logo?
That depends on the licence. Some licences allow logos explicitly, some restrict them, and open licences such as the OFL list logos among permitted uses. Read the terms and ask the rights holder if the wording is unclear.
Do clients need their own licence?
If the client receives the font file, or will use the font on their own computers, website or app, they typically need their own licence. If they receive only finished artwork, the font is normally not part of the delivery.
What does the embedding flag in a font mean?
It is a setting inside the font file that tells software whether the font may be stored in a document and how the recipient can use it, from restricted to editable. Applications that follow the specification read the flag before embedding.
