If KDP just rejected your paperback with a vague “file does not meet our specifications” message, there’s about an 80 percent chance the problem is embedded fonts. Same for IngramSpark.
It’s the most common reason indie author PDFs get bounced. It’s also the most frustrating, because the error messages never tell you which font failed or which page broke. You just get a wall of “fix it and re-upload.”
This guide explains what embedded fonts actually are, why KDP and IngramSpark care so much, and how to fix the problem in under 5 minutes — even if you’re not technical.
What “Embedded Fonts” Actually Means
When you write your book in Word, Google Docs, or Affinity Publisher, you’re using fonts that live on your computer. Times New Roman, Garamond, Calibri — whatever you picked.
When you export your manuscript to a PDF, the fonts can either be:
- Embedded: A copy of the font file is included inside the PDF itself. Anyone, on any computer, sees the book exactly how you designed it.
- Referenced (not embedded): The PDF just says “use the Garamond font” without including the file. If the printer’s computer doesn’t have Garamond installed, the printer substitutes a different font — often badly — and your book looks like a disaster.
KDP and IngramSpark refuse to print books with non-embedded fonts, because they can’t guarantee your book will look right. Their fix is simple: they reject the file.
Why This Happens Even When You Did Nothing Wrong
Three usual culprits:
1. The font’s license forbids embedding
This is the sneakiest one. Some commercial fonts (especially fancy display fonts from font marketplaces) are licensed for screen use only. The font file itself contains a flag that says “do not embed in PDFs.” Your software respects the flag and silently leaves the font out.
You won’t see a warning. The PDF looks fine on your screen. KDP just rejects it.
2. The font isn’t installed properly
You used a font that you downloaded once, dragged to your desktop, and somehow it shows up in Word’s font menu — but the system font installer never properly registered it. When you export, the PDF can’t find a fully licensed copy and skips the embed step.
3. Your export settings are wrong
Even when the font is properly installed and licensed, you can still produce a non-embedded PDF if you use the wrong export setting. Word’s default “Standard” PDF export sometimes drops embeds for “common” fonts (like Times New Roman) because it assumes every system has them. KDP doesn’t care about that assumption.
How to Check If Your Fonts Are Embedded
The fastest way: open your PDF in Adobe Acrobat Reader (free).
- Click File > Properties > Fonts
- Look at the list
- Every font should say “Embedded” or “Embedded Subset” after its name
If even one font is missing that label, KDP will reject the file.
If you don’t have Acrobat, BookReady’s free PDF checker does this automatically and tells you exactly which fonts are missing the embed flag, on which pages.
How to Fix Embedded Font Problems
Different software, different fixes. Here are the three most common.
Microsoft Word
- Click File > Options > Save
- Check the box that says “Embed fonts in the file”
- Uncheck “Embed only the characters used in the document”
- Uncheck “Do not embed common system fonts”
- Save the document
- Re-export as PDF using File > Save As > PDF > Options
- Check “ISO 19005-1 compliant (PDF/A)” — this forces embedding
If the offending font still won’t embed, the font itself blocks it. Replace it with a free open-source equivalent (see list below).
Google Docs
Google Docs has limited control over font embedding. Your safest bet:
- Stick to Google’s built-in fonts (they all embed correctly)
- Use File > Download > PDF Document
- If you absolutely need a custom font, format the book in Word or Affinity instead
Affinity Publisher (recommended for serious indie authors)
- Click File > Export > PDF
- Choose the preset “PDF (for print)”
- Under “More” > “Compatibility,” select PDF/X-1a:2003
- Make sure “Embed fonts” is checked
- Export
Affinity is the gold standard here. It embeds fonts correctly almost every time, and the PDF/X-1a preset is what professional print shops expect.
Safe Fonts That Always Embed
If you’re stuck with a problem font, swap it for one of these. They’re all free and license-clean for commercial book printing:
Body text (serif):
- Cardo — closest to Garamond, free
- EB Garamond — high quality, free
- Crimson Text — modern serif
- Source Serif Pro — Adobe’s free option
Headings (sans-serif):
- Lato
- Open Sans
- Source Sans Pro
Display / chapter titles:
- Cinzel — elegant capitals
- Cormorant Garamond — dramatic serif
- IM Fell English — vintage
You can find all of these on Google Fonts. Download the OTF or TTF, install it system-wide, restart Word or Affinity, and re-export.
Mistakes That Make This Worse
- Re-using the same broken PDF for multiple platforms. If KDP rejected it, IngramSpark will too.
- Editing the PDF in Acrobat to “add fonts.” This doesn’t work. You have to fix the source file and re-export.
- Using “Print to PDF” on Windows. This produces files that are missing critical metadata. Always use a real export function.
- Ignoring the warning. If your software says “font cannot be embedded” during export, don’t skip past it. Fix it before you upload.
Catching This Before KDP Rejects You
The whole reason we built BookReady’s free PDF scanner is that “wait 72 hours, get rejected, fix, wait 72 hours again” cycle. Embedded fonts is the #1 issue we catch. The scanner checks every font on every page and tells you exactly which ones aren’t embedded — in plain English, with the page numbers.
Run your file through the scanner before you upload to KDP or IngramSpark. If it passes, your file passes their checks. If it fails, you’ll know in 10 seconds instead of 72 hours.
Final Thoughts
Embedded fonts are the single biggest invisible problem in indie publishing. A book that looks perfect on your screen can be unprintable, and KDP won’t tell you why. The fix is almost always the same: switch to a clean font, re-export with the right settings, and verify before you upload.
Once you do it right once, you can use the same template for every book after that. Five minutes of setup saves you days of rejection cycles.
You’ve got this.
FAQs
Q: Why didn’t my publishing software warn me about non-embedded fonts?
A: Most consumer-grade software (Word, Google Docs) silently skips embeds for licensing reasons. Only professional layout tools (Affinity, InDesign) reliably warn you.
Q: Can I fix embedded fonts in an existing PDF without re-exporting?
A: Not reliably. Tools that claim to “patch” PDF fonts often corrupt the file in other ways. Always fix the source document and re-export.
Q: What’s the difference between “Embedded” and “Embedded Subset”?
A: “Embedded” means the entire font file is included. “Embedded Subset” means only the characters actually used in the book are included. Both work for KDP and IngramSpark. Subset is usually preferred because it produces smaller files.
Q: My PDF passes KDP but IngramSpark rejects it. Why?
A: IngramSpark is stricter. They require PDF/X-1a:2003 compliance, which forces full font embedding and CMYK color. KDP is more forgiving. Always export with the stricter standard so your file works on both platforms.
Q: Do I need to embed fonts for ebooks too?
A: No. EPUB and MOBI files use system fonts on the reader’s device. Font embedding only matters for print PDFs.