Skip to content
Creative & media work

Can you use any font in a logo you sell? The drawing travels, the font file does not

Designers ask whether a font is "allowed" in a logo as though the answer lived in copyright law. It mostly does not. US copyright does not reach a typeface as a typeface, so the shapes you set are rarely the thing anyone can sue over. What creates exposure sits one level down: the program that drew them is licensed rather than sold, that licence has a defined scope, and the two things that break it are handing the file to somebody else and using it for something the scope never covered.

8 min readPublished How we write these

The short version

  • Usually yes. 37 CFR § 202.1(e) puts "typeface as typeface" outside copyright in the United States, so the letterforms in a wordmark are not, on their own, something anyone can claim against you.
  • The exposure is one level down. Font software is a computer program and is protected as one — Adobe Systems v. Southern Software (N.D. Cal. 1998) — and it reaches you through the licence you accepted, not through the design.
  • Do not put the font file in the handover folder. Desktop licences are counted in seats and are non-transferable, so sending the .otf to a client, printer or developer is the most common breach in client work.
  • Google Fonts is fine for commercial logos and merchandise. Almost all of it is under the SIL Open Font License, which permits selling what you make; the bars are on selling the font files themselves and on Reserved Font Names.

The letterforms are not what anyone can stop you drawing

The Copyright Office keeps a short regulation listing material not subject to copyright at all. Subsection (e) of 37 CFR § 202.1 is three words long: "Typeface as typeface." Circular 33, the Office's guide to what it will not register, says the same thing at more length — typeface, fonts, lettering, calligraphy and typographic ornamentation are all on the list.

That is not an oversight in the drafting. It was litigated. In Eltra Corp. v. Ringer, 579 F.2d 294 (4th Cir. 1978), a typesetting manufacturer sued to force registration of a typeface design and lost, the court treating typeface as an industrial design that cannot exist independently and separately as a work of art. The opinion also recorded that manufacturers had repeatedly asked Congress for protection and Congress had repeatedly declined, including in the run-up to the 1976 Act.

So a wordmark set in someone else's typeface is not, by virtue of its shapes, an infringement of anything.

What is protected is the program, not the picture

A font file is a computer program in the statutory sense: 17 U.S.C. § 101 defines one as a set of instructions used in a computer to bring about a certain result. The Copyright Office drew that line in its 1988 policy decision on digitised typefaces — the data depicting a typeface is not registrable, but an original program that generates typefaces can be.

A court then applied it. In Adobe Systems, Inc. v. Southern Software, Inc. (N.D. Cal. 1998), the defendant argued that font code held no protectable expression because the shapes dictated it. The court disagreed: choosing where to put the Bézier control points is a creative decision, and two designers working from the same images could produce indistinguishable output with almost no points in common. Copying the outline data was copying expression.

That split is the whole subject. Drawing letters that resemble a typeface is a design question with no copyright answer. Copying, installing, sending or embedding the file that draws them is a software question with a clear one.

Two different things reach you, and they reach different people

Copyright in the font software

  • Protects the program and its outline data
  • Binds anyone who copies the file, agreement or not
  • Says nothing about the typeface design itself

Acts caught by both

  • Installing it on a second machine
  • Emailing the .otf to a client or printer
  • Shipping it inside an app or a stylesheet

The licence on top

  • Counts seats, machines and page views
  • May price logo use separately
  • Binds only the person who accepted it
The middle column is why the design is rarely the argument. What goes wrong in client work is an act performed on the file, not on the shapes.

Copyright only stops you copying the file. The licence does more, because it is a contract and can define scope however the foundry likes — and read three side by side, the variation is the finding. Foundry5's desktop terms let you "create and distribute graphics, logos, and artwork for display on any surface", and count entitlement by users — a user being a single person or a single machine. Ornamental & Title Type sells logo use as its own tier: a Logo & Trademark licence for a wordmark or identity element that may be legally registered, with a further desktop or web licence needed if the font is used beyond the logo. Monotype's web font agreement caps use by page views instead.

So the honest answer to "can I use any font in a logo I sell" is that it is a per-font question, settled by a document you can read in four minutes. Not by copyright law, and not by what the last font allowed.

How far one ordinary desktop licence usually reaches

Sketching options
Outlined vectors, PDFs
Sometimes a separate tier
Web, app and app-embedding

Comps and internal drafts

Static artwork you deliver

A registrable logo or merchandise

The file itself moving on

The bands run from what every desktop licence covers to what almost none does. Where the line falls between the middle two is what varies by foundry, and the only part worth checking before you quote.

Graphic design contract template

Full template text, with deliverables, source files and third-party licensed elements written as separate clauses rather than one sentence about ownership.

Open

The case that tested a logo restriction, and what it actually decided

In Shake Shack Enterprises v. Brand Design Company (S.D.N.Y. 2023), the burger chain sued for a declaration that its lettering infringed nothing; the foundry, House Industries, counterclaimed that its desktop licence had long barred using the font software or the glyphs it generates in connection with logos. The counterclaim did not survive.

The reasoning is the useful part. The foundry could not establish that Shake Shack ever assented to the licence or used the font software, and to the extent the claim rested on the lettering merely resembling the typeface, it was a copyright claim in disguise. That is not a ruling that logo restrictions are unenforceable — it is a ruling that they are contract terms, binding the party that accepted them.

Does the client need to buy their own font licence?

It depends on one thing: whether what you hand over contains live font data. It has nothing to do with who owns the artwork, which is settled separately by assignment and covered in the logo ownership guide.

One question decides it

Does the handover contain usable font software?

No — flattened output

Outlined vectors, a PDF, a raster export, a printed piece. No program travels, so the client needs no licence of their own.

Yes — live font data

The .otf, a packaged layout folder, a self-hosted webfont in the CSS. That is a copy of the software, and the client needs a licence in their own name.

The right-hand branch includes the packaged design folder, which is where this goes wrong quietly: the package command collects the fonts so the file will open elsewhere.

This is why converting type to outlines before delivery works: it removes the software from the deliverable, so the client can print and reproduce the mark without licensing anything. What it does not do is retroactively permit a use your own licence never covered. Outlining is handover hygiene, not a cure for scope.

They do still need their own licence for everything after the logo — the website, the deck template, the packaging their printer sets. A brand guideline naming a typeface the client is not licensed for is a bill they receive later and blame you for.

Never put the font file in the handover folder

Desktop licences are almost uniformly non-transferable. Monotype's agreement is representative: transfer is allowed only if the recipient accepts the same terms, you destroy all your copies, and the scope of the rights granted does not change. A designer who means to keep using the font fails the middle condition, so that route is closed in practice.

Some foundries carve out a narrow exception. Foundry5 permits temporarily sharing fonts with a designer or printer on your job, provided they agree in writing to use them only for your work and keep no copies, and they count against your user total. Subscription libraries close the door entirely: Adobe's fonts cannot be packaged out, so a client who needs to edit the file needs their own.

What leaves your studio, and what never does

  • Send outlined vector artwork in the formats named in the contract, plus flattened exports for everyday use.
  • Send a written note of every typeface used, the foundry, and the licence tier the client will need for their own materials.
  • Do not send the .otf, .ttf, .woff2 or a packaged layout folder unless the licence expressly allows it and you have read the clause.
  • Do not upload a purchased font to a shared drive, a design tool's team library, or a repository the client can reach.
  • Where a mark will be registered, check whether that foundry sells logo use as a separate tier before the identity is signed off.

Is Google Fonts fine for commercial logos and merchandise?

Yes, and it is worth saying plainly rather than hedging. Most of the library is under the SIL Open Font License 1.1, which grants permission to use, copy, merge, embed, modify, redistribute and sell modified and unmodified copies of the font software. Selling is expressly in the grant.

  • The font may not be sold by itself. It can be bundled and sold with other software; it cannot be the product.
  • Copies you redistribute carry the notice and the licence. That binds the font files, not a poster set in them.
  • Reserved Font Names stay with the original. Modify a font and you must rename it, unless the copyright holder agreed otherwise.
  • The authors' names cannot promote a modified version, beyond acknowledging the contribution.
  • The font stays under the OFL — it cannot be redistributed under different terms.

None of those conditions touch your artwork. The OFL FAQ says logos are welcome and that you remain the author and copyright holder of the graphic you derive. Merchandise is the same analysis: you are selling a shirt, not selling fonts. Reading an open licence for what it actually restricts is the subject of the open-source compliance guide.

Write it down before the identity is built, not after

The clause this needs is short and nobody objects to it: the typefaces used, a statement that the studio holds licences for its own production use only, and a note that the client licenses them for theirs. Put it beside the deliverables list. If you are licensing your own work rather than assigning it, the scope questions are the same — see exclusive and non-exclusive licences and the licensing agreement template.

Font licensing feels dangerous because people look for the risk in the wrong object. The logo is not it; US law took the shapes off the table decades ago. The risk is a file in a shared folder three companies now have, under an agreement one person clicked through, for a use nobody checked. Two objects, one invoice, and only one was ever yours to pass on.

General information, not legal advice. This guide explains how these documents and rules generally work. Law varies by jurisdiction and changes, and none of it is applied to your circumstances here. For anything consequential, consult a licensed attorney where you are.

Frequently asked

Are fonts copyrighted in the United States?

The typeface design is not. 37 CFR § 202.1(e) excludes "typeface as typeface" from copyright, and the Fourth Circuit confirmed the position in Eltra Corp. v. Ringer in 1978. The font software is a different object: it is a computer program, and courts have held its outline data protectable. So the shapes are free and the file is not.

Can I use any font in a logo I sell to a client?

Legally the letterforms are not the obstacle, but the font licence can be. Some foundries permit logo use in a standard desktop licence; others sell a logo and trademark tier separately, particularly where the mark will be registered. It is a per-font question answered by that font's end user licence agreement, which takes a few minutes to read before you start.

Can I send the client the font file with the source files?

Almost never. Desktop licences are counted in seats and are non-transferable, and the transfer clauses that do exist usually require you to destroy your own copies. Send outlined vectors and flattened exports instead, and give the client a written list of typefaces so they can license anything they need in their own name.

Does converting text to outlines solve the licensing problem?

It solves the handover problem, not the scope problem. Outlining removes the font software from the deliverable, so nothing that is licensed to you travels to the client. It does not change what your own licence permitted you to make, and many agreements treat outlines as output governed by the same terms, so a restriction on logo use survives the conversion.

Is Google Fonts safe for commercial logos and merchandise?

Yes for almost all of it. The SIL Open Font License permits selling both modified and unmodified copies of the software, and expressly contemplates logos; the graphic you draw is yours. The restrictions are on the font files — no selling them alone, no reusing a Reserved Font Name on a modified version. Check each family, since a few use Apache 2.0 or the Ubuntu Font Licence.

Do the whole thing on your phone

Draft it, check it for risk, rewrite the clauses you do not like, sign it and send it — without opening a laptop.

  • 136 templates across 12 categories
  • AI review in plain English
  • Free every month — 3 documents, 2 reviews
Download on theApp Store
Free to download · no account

iPhone, iPad, Mac & Vision Pro · iOS 15.6+ · 76.1 MB
Premium from $1.99/week