KDP 'Fonts Not Embedded' — The Fix
KDP prints from your PDF, so every font must be physically embedded inside the file — if it isn't, KDP substitutes a default that breaks your layout, or rejects the file outright. If you got a vague 'file does not meet our specifications' rejection, unembedded fonts are the most likely cause. Here's how to confirm it and fix it.
Nothing is stored. Free — no account. Your PDF is inspected in memory only.
Rather not fight the PDF?
Upload your Word manuscript and PaperbackKit typesets a correct KDP interior from scratch — embedded fonts, right trim, real chapters — plus an accessible EPUB.
Drop your .docx here or click to choose
Word manuscripts up to 15MB · your file is deleted after processing
Upload first → see your typeset pages → pay $19 → the files download themselves. Nothing to copy or paste.
Don't have your manuscript handy? — no upload, no signup.
Frequently asked questions
How do I check if my fonts are embedded?
In Adobe Acrobat/Reader open the PDF, go to File → Properties → Fonts. Every font should say 'Embedded' or 'Embedded Subset'. Any font showing neither is not embedded and must be fixed in the source before re-exporting.
How do I embed the fonts?
Re-export the PDF with font embedding turned on. In Word: Save As → Tools → Save Options → 'Embed fonts in the file'. In InDesign/most tools, use a PDF/X preset which embeds fonts automatically. Google Fonts are all licensed for embedding and commercial print.
Why does KDP require this?
KDP's printers can't access the fonts installed on your computer — the font data has to travel inside the PDF itself. This is also the number-one cause of the generic 'does not meet specifications' rejection.
Can PaperbackKit produce a correctly embedded PDF?
Yes — PaperbackKit typesets your manuscript into a print-ready 6×9 PDF with all fonts embedded, so this class of rejection doesn't happen. It also preflights an existing interior PDF and tells you exactly which fonts are missing.