This guide helps you avoid font-related KDP rejects: choose one supported typeface, export a fresh PDF, check that the font is embedded, and rerun Previewer after any type change.
For reliable KDP uploads, pick one main body font and avoid mixing several different body fonts across the book.
Choose your final typeface early in proofreading. Late font swaps can change line wraps and move page breaks right before launch.
Open the PDF in a viewer that shows font details and look for Embedded or Embedded Subset next to the main book font.
Then run KDP Previewer and check chapter starts, italics, and decorative lines for any unexpected font changes.
If KDP reports a font issue, first make sure you uploaded the newest PDF and not an older file from your computer.
Fix font issues in the source manuscript settings (Word, Google Docs, or Senswriter), then export again and rerun Previewer. Do not treat a PDF editor as the normal place to fix fonts.
Copy the warning text exactly from Previewer and note the affected page number. Similar warnings can point to different causes.
Use that warning text plus the page number to make sure you are fixing the right problem after each re-export.
Save a screenshot of the warning panel before the fix, then save another one after the fix if the warning count changes.
That warning is mainly about appearance changes. Look for changed line wraps, different italics, altered ornaments, missing characters, or chapter-open pages whose spacing shifted.
Compare the same page in your original PDF, in KDP Previewer, and in a second PDF viewer. If the only visible difference is unrelated margin crowding, do not treat that by itself as proof of a font-embedding problem.
If you need to keep proof for yourself, save your own before-and-after images for the exact flagged pages instead of relying on generic examples.
| 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 are listed without missing or blank entries. |
Previewer wording can vary slightly by version. Use your own Previewer panel as the source of truth and log the exact message text plus page number from that run.
| Warning text in Previewer | Usually means | First source-first fix |
|---|---|---|
| "Embedded font missing for some text on this page." | Part of the page is using an unembedded or fallback font. | Normalize styles to one font family in the source file and re-export. |
| "Some characters may not display correctly." | The selected font does not include all the characters you used. | Switch to a font with full support for those characters. |
| "Text may be rendered with a substitute font." | Previewer is substituting a font because of embedding or licensing issues. | Re-export with a 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-based text. |
| "Decorative glyphs may not print as expected." | Ornamental symbols come from an unsupported or partial glyph set. | Replace them with supported symbols and check again at full zoom. |
Fix: Return to the source manuscript, confirm the intended font is applied consistently, then export again.
Verify: Reopen PDF font properties and confirm Embedded or Embedded Subset appears for the expected font.
Fix: Remove mixed local overrides and reapply one body-text style in the source file.
Verify: Spot-check several chapters and italics for consistent typography.
Fix: Switch to a font that supports the needed characters, then re-export.
Verify: Check known accent or special-character pages in Previewer and the final PDF.
Fix: Make sure the 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 the source file and normalize spacing or 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 the latest file and rerun Previewer with that newly named PDF.
Fix: Inspect copied text in that section for direct formatting overrides and normalize the style.
Verify: Recheck the exact affected pages in Previewer.
Fix: Replace decorative glyphs with simpler separators or supported symbols in the source file.
Verify: Inspect ornament pages at full zoom for consistent rendering.
Use the same workflow in one workspace: draft, export, run checks, fix the source, and upload one clean final file.
It means only the characters actually used in the book are embedded. That is normal in many print workflows and is usually fine for KDP.
Different fonts take up space differently. After any font change, run a fresh full pass in Previewer before you publish.
No. Check several chapter starts and scene breaks first, then upload only after the whole preview pass is clean.