KDP Font Embedding Guide
Quick answer
KDP needs fonts embedded in the uploaded PDF so the print system can reproduce text reliably. If fonts are missing, subset incorrectly, unsupported, or blocked by licensing, KDP may reject the file or substitute text. The safest fix is to replace unsupported fonts, export a fresh PDF with font embedding enabled, and verify the final PDF before upload.
When this matters
This matters when KDP flags unsupported fonts, Lucida fonts, subset fonts, missing embedded fonts, or Word PDF export problems. It is especially common in manuscripts created in Word, Canva, older design apps, or files edited after export.
Common causes
- Word exported the PDF without fully embedding fonts.
- A font license blocks embedding.
- A subset font is missing glyphs added during late edits.
- Lucida or another unsupported font remains in headers, symbols, page numbers, or imported objects.
- A PDF optimizer removed embedded font data.
How to check
Inspect the final PDF font list in Acrobat, Preview alternatives, or command-line tools such as pdffonts if available. Check whether every font is embedded or embedded subset. Search for hidden text areas, headers, footers, and imported graphics that may contain a flagged font.
Tool
Use the pre-upload checklist for the final font and export review.
Related KDP errors
Before uploading again
Use the pre-upload checklist and run the risk scan after exporting a fresh PDF with embedded fonts.