When Fonts Aren't Embedded Properly, Your Whole Manual Turns into Tofu: A Prevention Playbook

I've seen this nightmare play out on the print floor too many times: a designer confidently sends over a PDF, the press fires up, the proof comes off, and an entire line of text has turned into empty boxes, with English copy rendered as □□□□

The problem isn't the press and it isn't the designer's computer either; it's that the fonts never traveled along with the file to the print shop

When a PDF goes to print without the fonts embedded or converted to outlines, prepress software that can't find the matching font typefaces falls back to a system default, making everything look like it's been hollowed out. That's the phenomenon commonly known as "tofu" blocks

It gets even trickier when the text isn't completely missing but partially substituted: strokes get swapped, line spacing drifts, punctuation lands in the wrong place. These half-broken states are the hardest to catch, and the client only blows up when the finished product is already in their hands

So before any file goes to print, font handling always has to come first. It's not an optional flourish

There are two major font format families, and each needs to be handled differently

・TrueType (TTF): the workhorse of Apple and early Windows, with complete font data but more limited advanced typography features

・OpenType (OTF): the successor format jointly promoted by Microsoft and Adobe, supporting more languages, larger character sets, and typographic features like ligatures and alternate glyphs

For print, OpenType is already the mainstream choice because a single font file can cover Chinese, English, Japanese, and Korean, letting designers handle multilingual catalogs without switching typefaces

But OpenType character sets routinely run into the tens of thousands of glyphs. Embedding the full file can balloon a PDF from a few MB to dozens or even over a hundred MB. Email becomes impossible, uploads crawl

That's where subsetting comes in: only the characters actually used in the document get packaged in

Adobe's Acrobat, Illustrator, and InDesign all ask during PDF export whether you want to subset embedded fonts. In general, selecting "Embed all (subset)" is the safest choice, unless the font license prohibits embedding

A lot of designers have heard the advice "just outline it," and they're only half right

Outlining means using Illustrator's "Create Outlines" or InDesign's "Convert to Curves" to turn each glyph from a "font reference" into a "vector path." At that point, even if the recipient doesn't have your font file, the print will still come out correctly

Sounds foolproof? There are three costs though

・Irreversible: once outlined, you can't edit the text, swap a word, or produce an accessible PDF (screen readers can't read it)

・Multilingual meltdown: when CJK and Latin text are mixed, every single character becomes a path, and the file balloons to absurd sizes

・Licensing landmine: some fonts (especially commercial ones) forbid embedding or distribution as outlines

The industry's rough decision tree goes like this: embed whenever you can, especially for multilingual catalogs, manuals, and instruction booklets; only consider outlining when the license explicitly forbids embedding, or when the file is being handed off to a third party you have no control over; and for a confirmed final version, outlining can lock the file down and prevent RIP-side disasters

In short, outlining is insurance, not everyday practice

When you're working on a product catalog or corporate manual, four-language rotation across Chinese, English, Japanese, and Korean is common

The problem is that many fonts claim to ship a "complete character set," and the moment they're embedded, the entire character set gets packaged in, even if you only used a few dozen characters

Looking at recent client projects, an 80-page multilingual manual mixing CJK and Latin scripts can easily produce a PDF of 80 to 150 MB if embedded with non-subset fonts. Email becomes impossible, and the printer's upload system chokes, dragging the turnaround time out significantly

There are three moves that can save you here

・Confirm subsetting is on: in Illustrator's "Save PDF" dialog under the Advanced tab, check that the font option is set to "Embed all (subset)."

・Share fonts across the document: use one font family with different weights for headlines, body copy, and subheads, so the subset character set stays compact

・Split languages across files: if a single font can't cover every script in your document, breaking it into multiple files is easier to handle than one bloated file

This pre-flight checklist is the bare minimum I've had both clients and our in-house designers run through on the print floor

・Check font embedding status in the PDF: in Acrobat's "Content → Fonts" list, confirm every font shows as "Embedded (Subset)" or "Embedded."

・Re-export fonts that failed to embed: re-export that specific font out of Illustrator/InDesign on its own, or swap in a font with a proper license

・Evaluate licensing: check the font's EULA. Can it be embedded for commercial print? If you're unsure, contact the type foundry first

・Slim down multilingual files: confirm subsetting is enabled, and avoid mixing too many font families within the same document

・Decide on outlining only for the final version: convert to outlines only after sign-off, so you don't lock yourself out of future edits

In practice, a lot of disasters trace back to that fifth step being skipped: the client revises the text three times, only remembers to send the file to print on the third pass, the outlined versions from rounds one and two are still sitting in the folder, and the moment it goes out, everyone realizes it's outdated

Font handling sounds like a small thing, but it's the last gate between a design on screen and a design on paper. Embed correctly, pick the right strategy, and a month's worth of design work won't be undone by missing glyphs at the finish line

If you want to apply this workflow directly to your own print project, or get a one-on-one audit on specific font licensing and complex multilingual documents, you can start with Minds Printing's custom prepress service, or book a consultation with the Minds College advisory team

・Printouts that show empty boxes, missing glyphs, or garbled text are caused by fonts not being embedded or subsetted properly in nine out of ten cases

・Embed whenever you can; outlining is endgame insurance, not a daily workflow

・For OpenType multilingual fonts, always turn on subsetting, otherwise PDFs balloon from megabytes into gigabytes

・When a license forbids embedding, contact the foundry to confirm the terms first; don't sidestep the rules by outlining

・Before sending to print, do a final pass through Acrobat's font list. Five minutes is enough to block out 80% of rejections

Font embedding is the lowest-cost, highest-leverage improvement point in the entire print supply chain. For a print shop, building an automated font-list check into the PDF intake workflow can compress the prepress rejection loop from a full day down to an hour. For brand-side teams, folding subsetting, embedding, and license auditing into design SOPs means the underlying font infrastructure carries over directly when you move into hybrid digital-plus-print, RFID-tagged, or AR-augmented catalogs down the road. And for SaaS and automation applications, the same principle applies to any document automation scenario, contracts, manuals, government tender documents alike. Whenever a file crosses devices or printing equipment, embedding and subsetting are non-negotiable standard steps

・The Complete Guide to Font Embedding in Print-Ready PDFs: Why Your Type Goes Missing on Press

・Sending a File to Print Without Embedding Fonts? A Senior Print Consultant on the #1 Cause of Rejections

・Outline or Embed? Risk Management Designers Need to Understand Before Sending to Print

・Minds Printing

・Minds College