Here's an honest admission from City Graphics after thirty years in this trade: fonts can be an issue, and even after all that time, the licensing side of it isn't fully intuitive. Sometimes you have to buy a font to use it, sometimes you don't, and it's not always obvious which is which. If it confuses people who've been doing this for decades, it's not going to be obvious to you on the first try either.
What this means for your order: a font issue almost never shows up as an error message — it shows up as something looking "off" once your file is proofed. Catching it before that point, by embedding or outlining your fonts, saves a round of back-and-forth.
Why do some fonts cost money?
A font isn't just a shape you can copy freely — it's licensed software, the same category as an app or a piece of design software. Whoever designed that typeface controls how it can be used, and different licenses cover different things: using it on your own desktop is one kind of license, embedding it on a website is another. That's why the same font can be free for one kind of use and require payment for another.
There are, though, plenty of fonts that are free to use, including commercially, under an open license — Google Fonts is a well-known source of these, licensed so they're free for personal and commercial use alike.
What actually goes wrong when there's a font issue?
Generally, nothing does — most jobs run through without a hitch. But every now and then, something looks weird in the proof, or a customer says "hey, that doesn't look right." That's usually a font problem showing up: the file was built with a font the printer's system doesn't have, so something else got substituted in without anyone intending it to.
When that happens, the fix is usually to hunt down a substitute font, or ask for the file to be saved differently — sometimes handed over as a properly packaged file that bundles the fonts along with everything else the design needs.
How do I avoid this before it ever gets to the proof stage?
There are two common fixes, though which one fits can depend on your specific font's license:
- Embed the font. This bundles the actual font data into your PDF, so the file carries what it needs instead of assuming the next computer has the same font installed. The good news: in most design tools, this happens automatically when you export to PDF — InDesign, Illustrator, and Canva's PDF Print option all embed fonts on export as long as the font's license allows it. In Word, it's a setting you turn on: File → Options → Save → check "Embed fonts in the file" before saving as PDF. To confirm it worked, open your finished PDF in Adobe Acrobat and look at File → Properties → Fonts — each font should say "(Embedded)" or "(Embedded Subset)" next to its name.
- Outline the font. This converts your text into shapes (essentially tiny vector drawings) instead of live, editable text. In InDesign or Illustrator: select your text, then go to Type → Create Outlines. In Affinity tools it's called Convert to Curves. (Word, PowerPoint, and Canva don't have an outline function — for those, rely on embedding instead.) Once it's outlined, there's no font to substitute at all — it just looks like your text, permanently, because it no longer "is" text in the technical sense. The tradeoff is that outlined text can't be edited as text anymore, so do it on a copy of your file, and only once your design is truly final.
If you're working in InDesign, using the Package feature bundles your fonts and linked images together into one folder for the printer — a save-for-printer workflow that avoids the substitution problem from a different angle: instead of embedding or outlining, it hands the printer the actual font files your layout depends on.
Do I need to worry about this with free fonts too?
It's still worth a check either way. Google Fonts, the best-known source of free fonts, is licensed for personal and commercial use. Fonts that come with your computer or design tools are covered by those products' licenses — for unusual uses, the font's license is the source of truth. But "free" isn't automatically the same thing as "no licensing questions" — when you're not sure what a font's license actually allows, checking it directly is the safer move than assuming. The bigger practical risk with any font — free or paid — is whether the printer's system actually has that exact font installed. Embedding or outlining solves that regardless of where the font came from.
What this article can't tell you
Whether your specific printer's proofing process will catch a font substitution automatically, or whether it depends on someone noticing it looks off, varies by shop. This article can tell you how to avoid the problem at the file-prep stage; it can't guarantee every possible mismatch gets caught downstream. Building the file right the first time is still the most reliable move.
Building a file with fonts you're not sure about? Get a quote and we can flag anything that needs a second look before it prints.
Next steps: