Desktop vs Webfont vs Broadcast Font License (2026): What Creators Need
- What sets the tier: the output medium, not the project budget. Static and motion design is desktop; live web text is webfont; embedded app text is app; television, cinema, and large streaming is broadcast.
- What most creators need: a desktop license, which covers using a font as a graphic asset in motion design, the standard monetized-video case.
- The shortcut: a free SIL OFL font clears every tier at once with no fees or caps.
Table of contents
- What are the font license tiers?
- How do the tiers stack and price?
- Do you need a broadcast license for YouTube?
- How do you choose the right tier?
- What triggers a license upgrade?
- How does the free OFL path avoid tiers entirely?
- What are the most common font-licensing mistakes?
- Frequently asked questions
Font licensing confuses creators because the marketplace sells tiers by medium, not by intuition. People assume a bigger project needs a bigger license; in fact a small monetized video and a large one usually need the same license, while moving from a video to a live website changes the tier entirely. This guide maps the four tiers to the work creators actually do, names the exact triggers that force an upgrade, and gives you a decision tree. To skip the reading and price a specific font, run it through our Font Licensing Calculator.
- Sources
- Published foundry EULAs (Adobe, MyFonts, Klim, Process Type) read directly
- Scope
- Creator-economy video, web, and static design use cases
- Not
- Legal advice; foundry EULAs vary and govern your specific font
- Conflicts
- FilmFont earns affiliate revenue on some marketplace links; tier guidance is medium-driven, not commission-driven
- Last verified
- May 2026
What are the font license tiers?
A font license tier is a permission scope tied to the medium in which the font appears, not to the size of the audience. Four tiers cover almost everything a creator does, and the boundaries between them are the part worth memorizing.
Desktop license. A desktop license lets you install the font and produce static and motion design. For most foundries this explicitly includes using the font as a graphic asset in motion design, which is the standard YouTube and social-video case. The price scales with the number of installs, not the audience.
Webfont license. A webfont license covers serving the live font files to a website so the browser renders selectable text via the CSS font-face rule. It usually scales with monthly pageviews and does not cover desktop or app use. A desktop license, conversely, does not cover serving font files on the web; the two are separate purchases.
App license. An app license covers embedding the font software inside a mobile or desktop application you distribute. This is the tier that catches developers off guard; a desktop license never covers shipping the font binary inside software.
Broadcast and video license. The broadcast tier is purpose-built for television, cable, theatrical cinema, and large-distribution streaming, and it typically scales with the number of video program items. According to Adobe's licensing documentation and most foundry EULAs, this is where audiovisual broadcast work lives when it exceeds the desktop tier's motion-graphic allowance.
The reason the medium sets the tier rather than the budget is worth pausing on, because it is the source of most confusion. A font license is a permission to use the font software in a particular technical context, and the contexts have genuinely different risk profiles for the foundry. A desktop install produces flattened output, an image or a rendered video, where the font software itself never leaves your machine. A webfont serves the actual font files to every visitor's browser, which exposes the foundry's software far more widely. An app embeds the binary inside distributed software. A broadcast feed renders the type live to a mass audience. Each context is a different exposure, so each is a different license, and a bigger budget within the same context does not change the permission you need.
This is also why a single project can need two licenses at once. A creator who burns a font into a video, and also serves the same font as live text on their channel's companion website, needs both a desktop license for the video and a webfont license for the site. The two are not interchangeable, and buying the more expensive one does not automatically grant the other; they are scoped to different mediums by design.
How do the tiers stack and price?
The tiers are not strictly a ladder, because they cover different mediums rather than escalating sizes, but a ladder view is the fastest way to see what each one unlocks and what it costs.
-
Free (SIL OFL)$0, no tiers
- Desktop, web, app, and video, all cleared at once
- No distribution caps, no per-view fees
- Only restriction: cannot sell the font alone
-
Desktop$15-80 per weight verified 2026-05-29
- Static design and motion-graphic export
- Standard monetized YouTube and social video
- Scales with install seats, not audience
-
WebfontScales with pageviews
- Live, selectable website text via font-face
- Does not cover desktop or app use
-
Broadcast / VideoPer program item; often 1-2x desktop
- Television, cable, cinema, large streaming
- Scales with the number of video items
Do you need a broadcast license for YouTube?
For standard monetized YouTube, the answer is usually no. A desktop license is consistently treated as covering the use of a font as a graphic asset in motion design, which is what a YouTube title card or animated lower-third is. The MyFonts Desktop EULA language about "static designs and as a graphic asset in motion design" is the clearest statement of this, and most foundries follow the same logic.
The broadcast tier becomes necessary when the work crosses into traditional television, cable, theatrical cinema, or very large distribution streaming. A film headed for festival theatrical screening or a series picked up for cable should clear the broadcast tier. The grey zone is large branded social campaigns; when a single video reaches broadcast-equivalent scale, read the specific EULA or ask the foundry. We cover the marketplace-by-marketplace version of this question in our marketplace comparison, and the thumbnail-specific version in our thumbnail font roundup.
How do you choose the right tier?
The decision is a short branch on the output medium. Walk it once and the tier is settled.
Price any font across desktop, webfont, broadcast, and cinema tiers in one pass.
Run my license check →What triggers a license upgrade?
A license upgrade is triggered by a change in medium or a crossed cap, not by a bigger budget. Most creators never trigger one. The specific triggers are short enough to memorize.
| You are doing | Base tier | Upgrade trigger | Upgrade to |
|---|---|---|---|
| Monetized YouTube titles | Desktop | Theatrical or TV pickup | Broadcast / Video |
| Static thumbnails and posters | Desktop | (none, stays desktop) | not applicable |
| Website with the font as live text | Webfont | Pageviews exceed plan cap | Higher webfont tier |
| Shipping a font inside an app | App | (none for the app itself) | not applicable |
| Festival or theatrical film | Broadcast | (broadcast is the ceiling) | not applicable |
The single most common real upgrade is the desktop-to-broadcast jump when an indie video gets theatrical or festival distribution. Plan for it at the budget stage of any project that might screen theatrically, because retroactively clearing a broadcast license after the fact is more expensive and more awkward than buying it upfront. The font-history side of these tier decisions, including why prestige films pay for premium foundry cuts, runs through our Trajan piece.
How does the free OFL path avoid tiers entirely?
The SIL OFL collapses all four tiers into one free permission. An OFL font is cleared for desktop, web, app, and video commercial use simultaneously, with no per-view fees and no distribution caps. The only restriction that binds is that you cannot sell the font file on its own. This is why Google Fonts is the simplest path for a creator who wants to never think about tiers, and why our thumbnail picks lead with OFL faces.
For the creator-workflow side of choosing and managing licenses across a channel, our sister desk LensPOV covers the production-pipeline view.
What are the most common font-licensing mistakes?
The most common font-licensing mistake is treating a "free for personal use" download as if it were cleared for commercial work. These two phrases look similar and mean opposite things: an OFL release is cleared for monetized commercial output, while a personal-use font explicitly is not, and using one on a monetized video or a client project is a license violation regardless of how prominently the download button said "free." The fix is a thirty-second habit of opening the license file before you use any font, not after.
The second common mistake is assuming a desktop license covers a website. It does not; serving live font files on the web is a separate webfont license, and a great many small sites quietly run in violation by uploading a desktop font file to their server. If your site renders the font as selectable live text rather than as a baked-in image, you need the webfont tier. The third mistake is the late broadcast scramble: an indie film clears desktop licenses during production, then lands a festival or theatrical slot and discovers the title face needs a broadcast tier it never budgeted for. Clearing broadcast upfront on any project that might screen theatrically is far cheaper than retroactively licensing after distribution is locked.
The throughline across all three mistakes is the same: the medium decides the tier, and the license file decides what is allowed. A creator who internalizes those two rules and reads the EULA once per new font almost never gets caught out, and the free OFL path sidesteps the question entirely for the large share of work that does not need a premium foundry cut.
The Marquee, weekly
One email a week. New title-design pieces, a licensing watchlist, and the AI typography tools worth watching.
Frequently asked questions
Do I need a broadcast font license for YouTube?
Usually no. Standard monetized YouTube work is consistently treated as covered by a desktop license, which includes the use of a font as a graphic asset in motion design. The broadcast and video tier becomes necessary for traditional television, cable, theatrical cinema, and very large distribution streaming. Foundries vary, so the safest move is to read the specific EULA.
What is the difference between a desktop and a webfont license?
A desktop license lets you install the font and use it to create static and motion designs that are exported as images or video. A webfont license is for serving the live font files to a website so the browser renders selectable text using the CSS font-face rule. A webfont license does not cover desktop or app use, and a desktop license does not cover serving font files on the web.
Does a desktop license cover video?
For most foundries, yes, a desktop license covers using the font as a graphic asset in motion design, which is the standard creator video case. The exception is broadcast and theatrical distribution, which many foundries gate behind a separate video and broadcast tier. Always confirm in the specific font's EULA before a broadcast or theatrical project.
What license do free Google Fonts use?
Almost all Google Fonts ship under the SIL Open Font License, which is a single permissive license that covers desktop, web, app, and video use commercially with no tiers, fees, or distribution caps. The only restriction is that you cannot sell the font on its own. This makes OFL fonts the simplest option for creators who want to avoid tier decisions entirely.
What to read next
Sources
- Adobe. Font licensing. helpx.adobe.com verified 2026-05-29
- MyFonts. End User License Agreement. myfonts.com/pages/eula verified 2026-05-29
- Process Type Foundry. Desktop, web, or app fonts. processtypefoundry.com verified 2026-05-29
- SIL International. SIL Open Font License. openfontlicense.org verified 2026-05-29
- MDN. CSS font-face. developer.mozilla.org verified 2026-05-29