KDP ‘Unsupported Fonts’ Error? Reddit’s Real Fixes

You did everything right. You picked a clean, standard font, you exported a PDF, you hit upload — and KDP threw back the dreaded “We found fonts that are not embedded” (a.k.a. the Unsupported Fonts) error. Worse, the file that KDP happily accepted last week suddenly gets rejected today with no changes you can see. This exact problem sends a steady stream of frustrated authors to r/KDP, and a recent thread from a poet fighting a stubborn Lucida Sans Unicode error captured the whole ordeal perfectly. Let’s unpack what the error actually means and walk through the fixes that real authors used to clear it.

What the “Unsupported Fonts” Error Actually Means

KDP’s print pipeline needs a fully self-contained file. Every font used anywhere in your interior has to be embedded inside the PDF, so Amazon’s printer reproduces your pages exactly without reaching for a font it doesn’t have. When KDP says a font is “unsupported” or “not embedded,” it is almost never complaining about your choice of typeface. It is telling you that some font in the file is referenced but not packaged inside the PDF.

The reason this feels maddening is that the offending font is usually one you never deliberately used. It hides in a single space after a chapter title, in a page header, in a footnote marker, in a stray paragraph mark, or in a character your visible font doesn’t contain (an em dash, a curly quote, an accented letter) that quietly falls back to a system font like Lucida Sans Unicode. Your eyes see Times New Roman everywhere; the PDF sees one rogue character in a font that never got embedded.

Here is the thread that captures it, posted this week in r/KDP:

Notice the tell: it worked a few days ago and now it doesn’t. That points away from your typeface (which didn’t change) and toward the export settings or a tiny piece of leftover formatting — exactly the two things we’ll fix below.

Fix #1: Embed Standard Fonts on Export (Start Here)

Ninety percent of the time this clears it. The default PDF export often skips embedding “standard” fonts because it assumes every device already has them — but Amazon’s printer wants them baked in anyway.

In LibreOffice Writer: File > Export As > Export as PDF. On the General tab, tick “Embed standard fonts.” Export, then re-upload. That one checkbox resolves a large share of these errors on its own.

In Microsoft Word: File > Options > Save > tick “Embed fonts in the file” and untick “Do not embed common system fonts.” Then use File > Save As > PDF (not “Print to PDF,” which can strip embedding). If you have Acrobat, its PDF export gives the most reliable embedding of all.

In Google Docs: Docs can’t control embedding, so its exported PDFs are the most common source of this error. Download as .docx, open it in LibreOffice or Word, and export from there with embedding on. (For a full walkthrough of preparing files properly, see our guide on how to format a book for publishing as a PDF.)

Fix #2: Hunt the Invisible Leftover Font

If embedding alone doesn’t do it, a fragment of the old font is still in the file. One r/KDP author described the classic version of this: the font wasn’t used in any actual word, but a space or line break after a chapter title was still formatted in the old typeface. A quick find-and-replace on formatting cleared it.

But here’s the trap the poet in the thread hit: find-and-replace reported “nothing found,” because the leftover isn’t a real character you can search for — it’s a fallback triggered by an invisible glyph. That’s the situation we answered directly in the thread:

The key move people miss is that headers, footers, and page styles live outside the main text flow, so “Select All” in the body never touches them. Click into each one and set the font explicitly. While you’re there, retype any fancy punctuation (em dashes, curly quotes) in your chosen font, since those are the characters most likely to fall back to Lucida.

Fix #3: Change the PDF Type on Export

If the file is clean and embedding is on but KDP still balks, change the flavor of PDF you produce. Amazon’s tooling historically likes PDF/X-1a, but LibreOffice can’t create that format. One author in the thread found the workaround that finally cleared their error:

To do this in LibreOffice: File > Export As > Export as PDF > on the General tab, under “Archive (PDF/A),” choose PDF/A-2b. PDF/A formats are designed for long-term archiving, which means they force every font to embed — exactly what KDP wants. It’s a slightly heavier file, but it reliably passes the font check.

Why Poetry, Special Characters, and Copied Text Trigger It Most

It’s no accident that the thread above came from someone formatting a poetry collection. Poetry, recipe books, workbooks, and anything with unusual spacing or symbols are the most frequent victims of this error, because they lean on characters and layout tricks that quietly summon extra fonts. An en dash used as a stanza break, a decorative bullet, a mathematical symbol, a smart quote, an ellipsis character, a non-breaking space — each can render in a fallback font even when the surrounding words are perfectly set in your chosen typeface.

The other big source is copied-and-pasted text. When you paste from a browser, an email, a Google Doc, or an older manuscript, the pasted run often carries its original font and styling invisibly, even if it looks identical on screen. That inherited formatting is exactly the kind of thing “Select All → set font” catches but a casual glance never will. A reliable habit before any KDP upload: paste everything as unformatted text into your template, re-apply your styles, and only then export. It feels tedious, but it removes the single most common way a rogue font sneaks into an otherwise clean file.

If you’ve genuinely worked through embedding, cleaned the whole document including headers and footers, exported as PDF/A-2b, and the error still fires, that’s the point to open a KDP support ticket. Attach the file, quote the exact error text, and ask them to identify which font on which page is flagged — they can see the specific offender, which turns an afternoon of guessing into a two-minute fix.

A Quick Order of Operations

When the error hits, work through it in this order so you don’t change five things at once and lose track of what worked: (1) re-export with “Embed standard fonts” on; (2) if it persists, select all — including headers, footers and page styles — and force your font, then retype special punctuation; (3) still stuck, export as PDF/A-2b; (4) as a last resort, copy your text into a fresh document built from KDP’s template and rebuild the styling from scratch, which strips out whatever invisible formatting was hiding. For the broader set of interior issues that trip authors up, our roundup of common formatting mistakes and the full guide to formatting a book for KDP are worth a read before your next upload.

How to Avoid the Font Error Entirely

Every fix above is treating a symptom of the same root cause: hand-exporting a PDF from a word processor gives you a dozen ways to accidentally leave a font un-embedded. You can dodge the whole category of problem by producing your interior with a workflow built for publishing output rather than general documents. Dedicated formatting tools embed fonts by default and export to Amazon’s specs, so “unsupported fonts” simply never comes up.

Full disclosure, I’m the founder of Automateed, so take this with a grain of salt: one reason we built our AI ebook creator to hand you a print-ready, fonts-embedded file is that watching authors lose an afternoon to a stray Lucida glyph is genuinely painful. But this isn’t a pitch for one tool — Vellum, Atticus, and even a carefully-set-up Word template will all embed fonts correctly if you configure them once. The point is that the export step is where these errors are born, so let something handle it deterministically instead of ticking boxes by hand each time. If you’re weighing an AI ebook generator versus doing it manually, reliable, KDP-ready output is the feature that actually saves you these support tickets. And if you want to understand what Amazon is doing with your file under the hood, our explainer on what format a Kindle uses fills in the rest.

Frequently Asked Questions

Sources: real author discussion in r/KDP — “Lucida Sans Unicode Font Error”, including the community’s PDF/A-2b workaround and our own reply on hunting invisible fallback fonts.