You never buy a typeface. You buy a permission, and the foundry sells several of them separately. The invoice that covers your presentation deck does not cover your website. The one that covers your website is metered on how many people visit it. The one that covers your product interface is a third purchase, and none of them expire the way a subscription does.
This is the line item that surfaces late, usually when a developer asks for the web files and discovers they were never bought, or when traffic grows past a tier nobody knew existed.
Everything below comes from license texts and from official documentation, not from design convention. One widely repeated belief turns out not to be supported by any of them.
A foundry sells permissions, not files
The catalog looks like it is selling typefaces. The contract is selling use cases.
One foundry’s enumeration, in its own words. “Desktop licenses allow you to install fonts on computers for use in print or static image formats. Webfont licenses allow you to embed fonts into websites. Digital ad licenses allow you to use fonts in emails and HTML5 digital ads. Embedded licenses let you distribute fonts as part of physical products like medical devices and cars, as well as in software programs. Application licenses allow you to embed fonts in phone/tablet apps and SaaS products. ePub licenses cover font usage in commercial publications. Server licenses allow non-licensed desktop users to use fonts on company platforms.”
The distinction that catches everyone. Asked whether a desktop license covers a website, the same foundry answers no, and explains why: “you might use a desktop license to create a static image (like a .jpeg) you upload to your website”, whereas “a web font license facilitates the implementation of the font in the actual code of your website.”
So the test is not where the font appears. It is whether the font file is being read by the visitor’s browser. A screenshot of type is a desktop use. The same words rendered as live text are a web use.
And each category is metered on its own unit. Another foundry prices desktop per user, web per page view, advertising “based on monthly impressions (as per your media buy)”, broadcasting “based on production budget or audience size”, and OEM “based on number of devices”.
Which means “how much is this font” has no answer until someone lists where the brand will actually appear. That list is a procurement document, and almost nobody writes it before buying.
One caution the foundry itself prints. “The information included here pertains to Monotype font licenses only. Other foundries may have unique requirements or restrictions in their contracts. Always read your licensing agreements closely.” Nothing in this article is a substitute for reading the specific agreement.
The web license is billed on traffic, and traffic grows
This is the clause that turns a one-off purchase into a recurring exposure, and it is written in units most companies do not track.
The unit, defined. “A ‘Page View’ is one request for the viewing of a page on your Website.”
And the measurement rule, which is the part that bites. “The average monthly traffic of Your Website, measured in Page Views over the span of three consecutive months, must not exceed the amount shown on Your Sales Receipt. If it does, You must purchase a licence upgrade for the increased Page View amount.”
A three-month average, not a spike. One viral month does not breach the license. A sustained quarter of growth does, which is precisely the situation a company running acquisition is trying to create.
The license is also bound to a domain. “The Fonts may be used for styling text on Your Website via the CSS @font-face rule for the Domain specified on Your Sales Receipt.” A second brand domain, a campaign microsite or a knowledge base on a different host can each fall outside it.
And to a file format. “Only the WOFF2 … files provided by Klim may be used. The use of alternate formats (such as TTF, SVG, or OTF) is expressly prohibited.” Converting a desktop file you already own into a web format is not a workaround, it is the breach.
One clarification worth having. At that foundry, “all fees are one-off, and all licences have no expiry”, so the meter is traffic rather than time. Other foundries structure this as an annual subscription. The unit differs; the need to check it does not.
What that means operationally. Put the licensed page view figure next to your analytics, and review it whenever traffic steps up. It is the only brand asset whose cost is a function of marketing success.
The open licenses are genuinely free, with two real conditions
Open-licensed families are not a downgrade, and the terms are short enough to read in full. Two clauses matter.
The one condition that surprises people. Under the SIL Open Font License 1.1: “Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.” Selling the font is prohibited. Everything else is permitted, and the grant says so explicitly, including the word sell: permission is granted “to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software”.
The name is reserved even when the design is not. “No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder.” You may fork the typeface. You may not keep calling it by its name.
And the clause that settles the question everybody actually asks. “The requirement for fonts to remain under this license does not apply to any document created using the fonts or their derivatives.” Your brochure, your website and your logo are not infected by the license. This is stated twice in the text, once in the preamble and once in clause 5.
Failure is total, not partial. “This license becomes null and void if any of the above conditions are not met.”
On the largest open library. Its FAQ is unambiguous on commercial use: “Yes, you can use them commercially, and even include them within a product that is sold commercially.” Self-hosting is permitted and documented, with three stated tradeoffs: full file size rather than subsets, no automatic per-browser format optimization, and manual updates.
And a boundary worth knowing. Not every typeface a large company uses is in its open library. Product Sans, for example, is described as owned by Google and “only available for use in Google products, by Google.” Seeing a typeface in the wild does not mean it is offered.
The logo question, and the answer that is not the one you expect
The received wisdom is that using a typeface in a logo requires a special license. Across the foundry documentation examined, that is not what the terms say.
Logo use sits under the ordinary desktop license. One foundry’s desktop terms cover “the creation of logos and logotypes”. Another states that a desktop license permits “the creation of static or moving files like images and videos. This includes the use of Fonts for the creation of logos and broadcasts.” A third confirms directly that its openly licensed families may be used “within any logo.”
A subscription library says the same. “You can use the fonts in any desktop program (such as Adobe Photoshop) to create images or vector artwork, which you can then use for any purpose.”
So the real constraint is a different one, and it is about what you can own. From the same source: “you can copyright or register the logo as a trademark. However, the fonts or typeface designs used in the logo cannot be copyrighted or registered as a trademark.” You own the mark. You never own the letterforms.
The second constraint is about who else needs a license. A foundry states the working practice plainly: “The simplest way to supply a logo to a client is to convert it to outlines in a drawing program. This saves the client from needing to license and install fonts, and it guarantees that the logo will appear exactly as you designed it. If your client needs to install and use the fonts themselves, they’ll need to license the fonts for their own use.”
Which is why logos are delivered as outlines. Not for print reliability, though it helps. Because outlined type is artwork, and artwork travels without a license attached, whereas live editable type does not.
And it explains the handoff rule. Your client “does not need a separate font license if you provide them with graphics or documents that contain rasterized or properly embedded font data, such as PDFs, JPEGs, or PNGs.” Send the outlined file. Do not send the font.
Subscription libraries are the most common route into a brand typeface, and the answer on cancellation is split rather than simple.
What survives. “Any file that embeds the font data, such as PDF or image formats, and any text that has been rasterized or outlined will continue to display correctly. These types of files may be reproduced and distributed independent of your subscription status.”
What does not. “Documents that reference live, editable fonts, such as an InDesign or Word document, will show a missing fonts warning and use a default font from the program in place of the one from Adobe Fonts. You would need to purchase a new font license.”
So the exposure is your working files, not your published ones. Your logo, your PDFs and your exported images are fine. Your template library, your editable decks and every layout the team still opens are not.
And several uses are outside the subscription entirely. Embedding in a mobile or desktop application, installing on a server, packaging fonts for a print bureau, letting customers apply the fonts to their own text, and products made from individual glyphs are each documented as not permitted.
The practical implication for a brand system. If your identity depends on a subscription typeface, keep an inventory of which deliverables are outlined and which are live. That inventory is the real cost of switching, and nobody maintains it until the renewal is refused.
The legal frame is not the one most people assume, and knowing it explains why the industry sells licenses rather than relying on copyright.
The regulation is blunt. Among material not subject to copyright, 37 CFR 202.1 lists “(e) Typeface as typeface”, alongside “mere variations of typographic ornamentation, lettering or coloring”.
And the Copyright Office leaves no room. “As a general rule, typeface, typefont, lettering, calligraphy, and typographic ornamentation are not registrable … The Office typically refuses claims based on individual alphabetic or numbering characters, sets or fonts of related characters, fanciful lettering and calligraphy, or other forms of typeface. This is true regardless of how novel and creative the shape and form of the typeface characters may be.”
What can be registered is the program. “The Office may register a computer program that creates or uses certain typeface or typefont designs, but the registration covers only the source code that generates these designs, not the typeface, typefont, lettering, or calligraphy itself.”
Which is the whole explanation for the licensing model. The design is not protected. The file is software, and software is licensed by contract. That is why the terms are long, why they are segmented by use, and why breaching them is a contract matter rather than an infringement claim.
And it clarifies the logo answer from the other direction. You cannot be prevented from using letterforms, and you also cannot claim them. What you can own is the specific mark you drew from them.
Before buying, write down where the brand will appear: print, website, product interface, ads, apps, documents sent to clients. That list maps one to one onto license categories, and it is the only way to price the decision.
For the website, find the licensed page view figure and put it next to your analytics. Set a review whenever traffic steps up, because a three-month average is what the license measures, not a peak.
For the logo, deliver outlines and keep the editable source internally. That single habit removes the client licensing question, the handoff question and most print problems at once.
And if an openly licensed family covers the need, use it without apology. The terms permit commercial use and sale, and the only real prohibitions are selling the font itself and reusing its reserved name. Whichever way the licence goes, record it in the guidelines next to the typeface, because an identity documented down to what each asset may legally be used for is the version a new agency can pick up without buying anything twice.
Usually not. Foundries sell desktop and webfont rights as separate products. One states it directly: a desktop license lets you install the font for use in design programs, while a web font license facilitates implementation in the actual code of your website.
How are webfont licenses billed?
On traffic, not on time. One foundry defines a page view as one request for the viewing of a page on your website, and requires that your average monthly traffic over three consecutive months not exceed the licensed amount.
Do I need a special license to use a font in my logo?
No foundry examined requires one. Logo use falls under an ordinary desktop license. What you cannot do is claim rights in the letterforms themselves, which is why logos are delivered as outlines.
Can a typeface be copyrighted in the US?
Not the design. US regulation lists 'typeface as typeface' among material not subject to copyright, and the Copyright Office says this holds regardless of how novel and creative the characters are. The software that generates it can be registered, but the registration covers only the code.