This guide helps you avoid font-related KDP rejects: choose one supported typeface, export once, verify embedding in the PDF, and rerun checks after any type change.
For reliable KDP uploads, keep one primary body typeface and avoid mixing fonts manually across chapters.
Pick your final typeface early in proofreading. Late typeface swaps can move line wraps and chapter pagination right before launch.
Open the export in a PDF viewer and inspect document font details. Look for embedded or embedded-subset entries for the book font.
Then run KDP Previewer and scan chapter starts, italics, and ornamental lines for unexpected substitutions.
If KDP reports a font issue, first confirm you uploaded the newest export and not an older local file.
Fix font issues in source manuscript settings (Word, Google Docs, or Senswriter), then re-export and recheck. Avoid patching font data in a PDF editor.
Copy the warning text exactly from Previewer and log it with the affected page number. Similar wording can point to different root causes.
Use the warning text plus page number to verify you fixed the right issue after each re-export.
Keep one screenshot of the warning state and one screenshot after the fix for each font-related blocker.
| Tool | Where to check | Pass signal |
|---|---|---|
| Adobe Acrobat Reader | File > Properties > Fonts | Primary fonts show Embedded or Embedded Subset. |
| macOS Preview | Tools > Show Inspector > Fonts | Book font appears consistently across inspected pages. |
| Command line (pdffonts) | Run pdffonts your-file.pdf | Expected fonts listed without missing/blank entries. |
Previewer wording can vary slightly by version. Use exact message text plus page number in your release log.
| Warning text in Previewer | Usually means | First source-first fix |
|---|---|---|
| "Embedded font missing for some text on this page." | Part of the chapter is using an unembedded or fallback font. | Normalize styles to one font family in source and re-export. |
| "Some characters may not display correctly." | Selected font lacks glyph support for required characters. | Swap to a font with full glyph coverage for used symbols/accents. |
| "Text may be rendered with a substitute font." | Reader is substituting fonts due to embedding or licensing issue. | Re-export with fully embedded font and remove mixed direct formatting. |
| "Image-based text may appear blurry in print." | Text was flattened into images or rasterized artwork. | Use live text with embedded fonts instead of image text blocks. |
| "Decorative glyphs may not print as expected." | Ornamental symbols come from unsupported or partial glyph sets. | Replace with supported symbols and verify at full-page zoom. |
Fix: Return to source manuscript, confirm the intended font is applied consistently, then regenerate export.
Verify: Reopen PDF font properties and confirm Embedded/Embedded Subset appears for the expected font.
Fix: Remove mixed local overrides and reapply one body-text style in source manuscript.
Verify: Spot-check multiple chapters and italics for consistent typography.
Fix: Switch to a font with full glyph support for required characters, then re-export.
Verify: Check known accent/special-character pages in Previewer and final PDF.
Fix: Ensure italic style comes from the same font family, not a fallback replacement.
Verify: Inspect italic-heavy passages in at least three chapters.
Fix: Recheck heading styles in source and normalize spacing/line-height before re-export.
Verify: Compare chapter-open pages before and after the fix.
Fix: Confirm you uploaded the newest file version and remove stale local duplicates.
Verify: Rename release file and rerun Previewer with the newly named PDF.
Fix: Inspect copied text in that section for direct formatting overrides and normalize style.
Verify: Recheck the exact affected pages in Previewer.
Fix: Replace decorative glyphs with simpler separators or supported symbols in source.
Verify: Inspect ornament pages at full zoom for consistent rendering.
Use the same workflow in one workspace: draft, export, run checks, fix source, and publish one clean release-candidate file.
It means only used glyphs are embedded, which is normal for many print workflows and usually acceptable for KDP ingestion.
Font metrics change line length and page flow. After any font change, run a fresh full pass in Previewer before publishing.
No. Check multiple chapter starts and scene breaks first, then upload only after a full clean preview pass.