So far we’ve explored why font licensing matters, common mistakes, and where to get fonts safely. Now it’s time to focus on real-world, client-facing scenarios.
You’re working on branding, marketing, or a website. The project needs a font—or maybe a few. So... who’s supposed to license it? You? The client? And what exactly should be included in your handoff?
Let’s clear that up right now—without legal jargon.
👩💻 Scenario 1: You’re Designing a Brand for a Client
The situation: You choose a font for their logo, social media, and packaging. They love it. Now what?
Who licenses the font?
➡️ The client should.
You, as the designer, can use the font temporarily during the design phase, but the client needs their own license to legally use it in ongoing work (web, print, etc.).
What you should do:
-
Tell the client the name of the font, where to buy it, and what kind of license they need.
-
Don’t send them the font file. That would be redistribution (unless the license allows it, which is rare).
-
Add a line in your contract or invoice like:
“Fonts used in your project are licensed separately. You are responsible for purchasing the appropriate font licenses before commercial use.”
🖼 Scenario 2: You’re Delivering Social Media Templates
The situation: You designed Instagram post templates in Canva, Photoshop, or Figma using a paid or free font.
Who licenses the font?
➡️ It depends. If the font is included in a platform like Canva Pro or Adobe Fonts, you're generally covered (but only inside that platform). If it’s an external font file you installed, the client may need their own license.
What you should do:
-
Stick to platform-native fonts when possible.
-
Document the font source in a handoff guide (e.g., “This template uses XYZ font from Google Fonts.”).
-
For downloadable templates sold on Etsy or Creative Market, make sure the font license allows redistribution or embedding.
🌐 Scenario 3: You’re Designing a Website
The situation: You select a font and embed it using @font-face or a webfont kit.
Who licenses the font?
➡️ The website owner (usually the client).
Webfonts are licensed based on monthly pageviews. The license should be in the name of the site owner.
What you should do:
-
Include a note in your deliverables:
“Font XYZ is licensed for web use at up to 50K pageviews/month. Please purchase this from [link].” -
Use services like Google Fonts or Adobe Fonts if your client doesn’t want to manage licensing.
🎮 Scenario 4: You’re Creating an App or eBook
The situation: Fonts are embedded into an app or digital product.
Who licenses the font?
➡️ The publisher or client—whoever is distributing the product.
What you should do:
-
Look for a license that explicitly allows app or eBook embedding.
-
Don’t assume a desktop or webfont license is enough—this is a different use case.
📂 What to Include in Your Font Handoff
✅ Font names
✅ Font sources (URL or foundry)
✅ License type (Desktop/Web/App/Open Source)
✅ Licensing responsibilities (who needs to purchase what)
✅ Any login requirements (e.g., Adobe Fonts via Creative Cloud)
A sample section for your project handoff might look like:
Fonts Used in This Project:
-
Main Typeface: Lato (Google Fonts) – Free for commercial use
-
Display Font: Morion by TypeMates – Requires a desktop license (~$49). Purchase here: [link]
-
License Notes: Client is responsible for licensing Morion before use in packaging or marketing.
🚧 What Not to Do
-
❌ Don’t zip and send font files unless explicitly allowed.
-
❌ Don’t assume clients will “figure it out” later.
-
❌ Don’t use pirated fonts or mystery downloads just because “they looked good.”
Summary: Make Font Licensing Part of Your Workflow
Licensing fonts for client work isn’t about making things harder—it’s about protecting both you and your clients. It’s also a great way to show professionalism and build trust.
Your next step?
Add a small section in your client onboarding form, contract, or style guide that covers font licensing responsibilities. It’s a small move that can save a lot of headaches.
Comments
Post a Comment