Fonts not embedded: the rejection, explained and fixed

By Tracy Atkins, founder of BookDesigner.ai and BookDesignTemplates.com · 15+ years of print files, 70,000+ authors · Updated July 19, 2026

What the rejection actually means

A PDF can carry its fonts in one of two ways. It can embed them, tucking the actual letterforms inside the file, or it can merely name them and assume the reading device already has them. On your own screen the second way looks fine, because your computer does have the font. On a commercial press it does not. When the press system meets a named-but-missing font, it substitutes the closest thing it has on hand.

Substitution is where the damage happens. A different font has different letter widths, so line breaks move, pages reflow, and carefully set headings shift. In the worst cases the text renders as blank boxes or garbled characters. Printers reject unembedded fonts precisely because they cannot promise your book will look like your book if they let it through.

How to check embedding, in one minute

You do not have to guess. In Acrobat, and in most full PDF viewers, the answer is a couple of clicks away:

1. Open the PDF and go to File → Properties.
2. Click the Fonts tab.
3. Read the note beside each font. Embedded or Embedded Subset is what you want. "Embedded Subset" simply means only the characters you used were included, which is normal and good.

If a font appears with no embedding note, or is shown as a substitute for something else, that font is your problem. Note its name before you move on, because the fix depends on which font it is.

Why Word can quietly let one through

Word tries to help. Its PDF export embeds most fonts automatically, and there is a separate setting, File → Options → Save → Embed fonts in the file, that controls embedding inside the DOCX itself. That DOCX setting is useful when you send an editable file to someone else, but it is not the same thing as embedding into an exported PDF.

The trap is licensing. Every font carries an embedding permission flag set by whoever made it. If a font is flagged as restricted, Word's export cannot legally embed it, so it skips that font. It does not stop, it does not warn you, and the resulting PDF looks perfect on your machine. You find out only when the printer's preflight flags it, or, worse, when a proof arrives set in the wrong typeface. This silent skip is the reason so many authors are baffled by the rejection: they never touched a setting, so nothing seems to have gone wrong.

The common culprit

In my experience the offender is almost always a decorative display font pulled from a free-font site, often used for a chapter title or a drop cap. Free fonts vary enormously in quality and licensing, and a good share of them ship with embedding turned off, either deliberately or through carelessness by the maker. A workhorse body font from a reputable foundry rarely causes this; a flashy free headline font frequently does.

Three ways to fix it

1. Choose an embeddable font

The cleanest fix is to swap the offending font for one that permits embedding, then re-export and re-check the Fonts tab. Well-established body and display families from reputable sources almost always allow it. If you love a particular free font, check its license for embedding permission before you build a whole book around it.

2. Export through a proper PDF preset

Exporting with a print-oriented preset (for example a PDF/X preset in Acrobat or a professional layout tool) forces embedding as part of the job and will tell you if a font cannot be embedded, rather than skipping it in silence. This both fixes embeddable fonts that Word may have handled loosely and surfaces the truly restricted ones so you can deal with them.

3. Print-to-PDF as a blunt last resort

If you are stuck with a font you cannot replace, printing the document to a PDF can force the type into the file. Be honest about the trade-off, though: this approach tends to rasterize content, turning crisp vector text into a fixed-resolution image. That can soften the type, inflate file size, and defeat any later text handling. Treat it as a last resort, verify the result on a proof, and prefer options one and two whenever you can. This caveat is worth taking seriously rather than reaching for the quick fix.

Source: Adobe Acrobat font-embedding documentation and current KDP and IngramSpark file specifications, as of July 2026. Related: Formatting a book in Word: the honest limits · KDP previewer errors, explained · All author guides