To embed fonts in your book PDF means to include the font data inside the file itself, so KDP’s printing system reads your chosen typefaces exactly as you designed them. If any font in your interior or cover PDF is not embedded, KDP may reject the file outright or substitute a different font, shifting line breaks, page counts, and the overall look of your book. You can verify embedding in the free Adobe Acrobat Reader by opening File > Properties > Fonts.
- What Does It Mean to Embed Fonts in a PDF?
- How Do You Check Whether Fonts Are Embedded in Your PDF?
- What Is the Difference Between “Embedded” and “Embedded Subset”?
- Why Do Some Fonts Refuse to Embed?
- How Do You Fix Unembedded Fonts in Word, InDesign, and Other Tools?
- What Can You Do When KDP Rejects a Font You Haven’t Actually Used?
- When Should You Outline Fonts Instead of Embedding Them?
- Frequently Asked Questions
What Does It Mean to Embed Fonts in a PDF?
Embedding a font means storing a copy of the font’s character data directly inside your PDF file. When KDP’s print system opens your uploaded PDF, it does not look for fonts installed on its own servers; it reads the font data packaged within the file. If that data is missing, the system either rejects the upload or substitutes a default font, which almost always changes line lengths, paragraph breaks, and page counts.
KDP’s paperback font requirements state that authors should embed all fonts in interior and cover files prior to submission. The requirement applies to every font in the document: body text, headings, page numbers, chapter titles, and any decorative or display type. You need to embed even fonts that seem standard (like Times New Roman or Arial), because KDP’s production environment does not assume any fonts are pre-installed.
Think of it this way: your PDF is a self-contained package that travels to a print facility. If the package does not include everything the printer needs, something will go wrong. Font embedding is the step that makes the package complete.
How Do You Check Whether Fonts Are Embedded in Your PDF?
You can check font embedding status using the free Adobe Acrobat Reader; you do not need the paid Acrobat Pro for this step. Open your PDF in Acrobat Reader, then go to File > Properties (on Mac, this is under the Acrobat Reader menu or via Cmd+D). Click the Fonts tab. This displays every font used in the document along with its embedding status.
Each font in the list will show one of three statuses:
- Embedded: the PDF includes the entire font file. This is the ideal status.
- Embedded Subset: the PDF includes only the characters the document actually uses. This is usually acceptable (more on this below).
- No label after the font name: the PDF refers to the font by name but does not contain the font file. This is the problem. Any font without an “Embedded” or “Embedded Subset” tag will cause issues at upload.
Go through the entire list. If even one font shows no embedding status, you need to export your file again with that font embedded. A common trap: authors check only the body font and miss an unembedded font used in a single header, a footnote, or a page number style.
What Is the Difference Between “Embedded” and “Embedded Subset”?
A fully embedded font includes every character in the typeface’s character set, whether your document uses them or not. An embedded subset includes only the specific characters that appear in your document. For a 200-page novel using Garamond, a subset might include 80 or 90 glyphs out of the font’s full 600-plus character set.
KDP’s help documentation states that it recommends fonts be “fully embedded, rather than embedding as subsets.” In practice, KDP accepts both “Embedded” and “Embedded Subset” files without rejection. The recommendation for full embedding is precautionary: if you later need to make minor text edits in Acrobat and a character you need is not in the subset, the edit will fail silently or produce a visible substitution.
For most self-published authors, embedded subsets are fine. The file size difference can be significant; subsetting a font-heavy document with 15 different typefaces might save 10 to 20 MB compared to full embedding. If you are producing a final, print-ready PDF that you do not plan to edit further in Acrobat, subsetting is a practical choice. If you want maximum safety and do not mind slightly larger files, choose full embedding in your export settings.
Why Do Some Fonts Refuse to Embed?
The most common reason a font refuses to embed is a licensing restriction set by the font’s creator. Every font file contains a metadata field called the “embedding permission” flag. And software like Word, InDesign, and Affinity Publisher reads this flag before it lets a PDF include the font. If the flag says “no embedding” or “print and preview only,” your design software will either skip the font during export or display a warning.
Fonts downloaded from free font websites are frequent offenders. Many carry the label “free for personal use,” which typically means you can use them on screen but cannot embed them in a commercial PDF. The distinction matters: using a font to design something on your computer is one thing; packaging that font’s data inside a file you distribute (or send to a printer) is another. Some paid fonts also restrict embedding unless you purchase an extended license.
If you encounter a font that will not embed, replace it with one whose license allows embedding. Google Fonts are an excellent fallback: every font in the library is open source, and Google’s FAQ says you can use any of them in a book you sell, in print or as an ebook. Alternatives like EB Garamond, Libre Baskerville, Lora, and Source Serif 4 are typographically strong replacements for common book fonts.
How Do You Fix Unembedded Fonts in Word, InDesign, and Other Tools?
The fix depends on which application you used to create your book interior. Here are the steps for the most common tools self-published authors use.
Microsoft Word
Word can embed fonts at two stages: in the document itself and during PDF export. For document-level embedding, go to File > Options > Save, then check “Embed fonts in the file” under “Preserve fidelity when sharing this document”. Uncheck “Embed only the characters used in the document” to get full embedding rather than a subset. Also uncheck “Do not embed common system fonts” so that Word includes standard fonts like Times New Roman.
When exporting to PDF, go to File > Save As (or Export), choose PDF, and click Options. Check “ISO 19005-1 compliant (PDF/A)” to force font embedding in the output. PDF/A is a stricter archival format that requires all fonts to be embedded; KDP accepts PDF/A files without issue. After export, verify in Acrobat Reader that all fonts show “Embedded” or “Embedded Subset”.
Adobe InDesign
InDesign embeds fonts automatically when you export to PDF, provided the font’s license permits it. For book interiors, export using the PDF/X-1a:2001 preset (File > Adobe PDF Presets > PDF/X-1a:2001). This preset embeds font subsets by default, converts all colors to CMYK, and flattens transparency: exactly what KDP’s print workflow expects.
To ensure full embedding rather than subsetting, open the export dialog, go to the Advanced panel, and set “Subset fonts when percent of characters used is less than” to 0%. This forces InDesign to embed the complete font regardless of how many characters your document uses. If InDesign displays a warning icon next to a font during export, that font has a licensing restriction. Check it via Type > Find Font, select the problem font, and click More Info to see the restriction details.
Affinity Publisher
When exporting to PDF, choose the PDF/X-1a preset. Affinity Publisher embeds all fonts by default when using this preset. If licensing stops a font from embedding, Affinity will display a warning during export. Replace the restricted font before proceeding.
LibreOffice Writer
Go to File > Export as PDF. In the General tab, check “Embed all fonts” (available in LibreOffice 7.0 and later). For older versions, you can also check “Archive (PDF/A-1a)” which forces font embedding. LibreOffice handles most open-source fonts well, but some system fonts may not embed if they carry restrictive licenses.
Formatting tools (Vellum, Atticus, Kindle Create)
Dedicated book formatting tools like Vellum, Atticus, and Kindle Create embed fonts automatically during export. If you are using one of these tools and your fonts are from the tool’s built-in library, the tool handles embedding for you. If you have imported a custom font, the same licensing rules apply: the font must permit embedding, or the export will either skip it or produce a warning.
What Can You Do When KDP Rejects a Font You Haven’t Actually Used?
Since early 2026, authors on the KDP Community forum have been reporting that KDP’s Print Previewer (the preview KDP shows after you upload your interior file) rejects their paperback interior with an error like this:
Unsupported fonts are used in your file. Please create a new interior file with “LucidaSansUnicode” replaced.
In every report we have read, the error names a font from the Lucida family, a set of fonts that comes installed on many Windows and Mac computers. And the authors who reported it were sure they had not used it in their book. Several authors found that changing the book’s main font, even to one KDP suggests, did not clear the error, because a font can hide in places an author would not think to look.
KDP’s Paperback Fonts page lists those hiding places: a space or punctuation mark, a line break, a header or footer you are not using, or a style you never applied to any text. It also lists four fixes. If you use Word, one of them needs a warning. KDP’s first fix is to outline the fonts (turn every letter into a shape, so that no font is left in the file), but this is not what Word’s Outline option, under Text Effects, is intended for. It draws a line around each letter and leaves the font in the file. The next section covers true outlining.
Finding the Font in Your Manuscript
Forum members have cleared KDP’s unsupported-fonts error with these checks:
- Make a note of the exact font name in the error. It is a clue to where the font came from. In the reports we have read that name the program, LucidaGrande errors came from books made in Apple Pages on a Mac, and LucidaSansUnicode errors from Word on Windows and from OpenOffice.
- Search for the font. Word’s Find and Replace dialog can look for formatting as well as text. Open it (on Windows, click the drop-down arrow next to Find on the Home tab and choose Advanced Find; on a Mac, choose Edit > Find > Advanced Find and Replace) and expand it (click More on Windows, or the arrow button on a Mac), leave the Find what box empty with the cursor in it, then choose Format, then Font, and pick the font named in the error. Unlike selecting all the text, this also finds empty lines set in that font. One author found four blank lines in LucidaSans this way, changed them, and the book went through.
- Check page numbers, headers, footers, and bullets. Another author traced the font to the page numbers in her footer. Removing them and inserting them again is worth trying. A third found it in the bullet characters of a list.
- In Pages, reapply your font inside the footnotes as well. A regular forum contributor who uses Pages advises selecting all the text and reapplying your font, then doing the same inside the footnotes, because footnote numbers are one of the places the font turns up. This works if you have used a single font throughout the book. If you’ve used different fonts in the design, you’ll need to select each run of text in the same font individually.
Checking the PDF Before You Upload Again
Before you upload a corrected file, open the new PDF in Acrobat Reader and look at its font list, using the check earlier in this post. If the list still shows the font KDP rejected, it is still in the file.
If the Error Will Not Clear
When an unsupported-fonts error survives every check, the forum’s regulars disagree about what to do next. Some keep searching the manuscript for the font. Others convert all the text in the finished PDF to outlines, which removes every font at once but leaves a larger file that you can no longer edit. One author uploaded her Word file instead of the PDF and reports that it went through (KDP accepts Word files only for books without bleed, meaning no images or color running to the edge of the page). Others, however, prefer to keep the PDF, because it holds the layout you have already checked. KDP’s help page does not say which fonts it rejects, so the error message is the only place that tells you which font to remove.
When Should You Outline Fonts Instead of Embedding Them?
Outlining (also called “converting to outlines” or “converting to curves”) transforms each letter from editable font data into a vector shape. The resulting PDF no longer contains any font data at all; every character is a graphic. This eliminates embedding issues entirely, because there is no font left to embed or refuse embedding.
However, treat outlining as a last resort for book interiors, not the default workflow. Outlined text is no longer searchable or selectable, which hurts accessibility and makes the PDF harder to work with after export. The typographic quality can also degrade slightly, because outlined glyphs lose the hinting instructions that fonts use to render cleanly at small sizes. For a 300-page novel set in 11-point type, this degradation may be visible.
Outlining is appropriate in two narrow scenarios: when a single decorative font on a cover or title page refuses to embed and you cannot find an acceptable replacement, or when a print service specifically requests outlined files (KDP does not). The exception is a font KDP has rejected that you cannot find and remove; there, outlining the whole interior is one of the fixes KDP’s own help page lists (see What Can You Do When KDP Rejects a Font You Haven’t Actually Used?). Otherwise, for body text in a book interior, embed rather than outline. If a body font will not embed, replace it with one that will; the font selection process is a better investment of time than converting an entire manuscript to outlines.
Frequently Asked Questions
Do I need Adobe Acrobat Pro to check font embedding, or does the free Reader work?
The free Adobe Acrobat Reader is sufficient. Open your PDF, go to File > Properties, and click the Fonts tab. Every font in the document will be listed with its embedding status. You do not need a paid subscription to view this information.
Will KDP reject my file if fonts are embedded as subsets instead of fully embedded?
No. KDP accepts both “Embedded” and “Embedded Subset” fonts. KDP’s documentation recommends full embedding as a best practice, but subset embedding does not trigger a rejection. The only status that causes problems is a font with no embedding at all.
What happens if I upload a PDF with an unembedded font to KDP?
KDP’s file review will flag the issue. In some cases the upload is rejected outright with an error message referencing fonts. In other cases KDP substitutes a default font, which changes line breaks and page counts, producing a printed book that looks noticeably different from your intended design.
Are Google Fonts safe to use in a print book PDF?
Yes. Every font in the Google Fonts library is open source, and Google’s FAQ says you can use any of them in a book you sell, in print or as an ebook, at no cost.
Does the font embedding requirement apply to cover files as well as interior files?
Yes. KDP requires all fonts to be embedded in both interior and cover PDFs. Cover files often use display or decorative fonts that are more likely to have licensing restrictions, so check the cover PDF separately after export.