Check font preparation in the source document and inspect the actual exported interior using tools that report its fonts. Then review representative pages for missing characters, substitutions, and layout changes. KDP requires embedded fonts in the interior workflow, but a font report alone does not establish that every passage renders correctly or remains readable.
Identify every kind of text in the interior
Begin with a list of where text appears: body paragraphs, headings, captions, tables, footnotes, and any lettering included in imported graphics. These elements may have been created through different workflows. A font choice applied to the main document does not necessarily describe text imported from another file or placed in a separate design object.
Choose representative pages for the review. Include the title page, a dense body page, a table, and a page with unusual characters if the book contains them. The purpose is to cover different text treatments rather than inspect only the first chapter. Record the source and exported filenames so findings remain attached to the file that will actually be submitted.
Review the preparation and export settings
KDP's paperback submission guidance instructs authors to embed fonts in the native file before submission. Review the current requirements and the supported export controls in the software used for the manuscript. Do not assume that a setting remembered from another application has the same name or effect in the present workflow.
If the project passes through several tools, identify which step creates the submission file. A document can be prepared in one application and converted elsewhere. Record that route so a font issue can be investigated at the appropriate stage. The author needs evidence about the resulting file, not only confidence that the original document displayed correctly on the computer where it was written.
Inspect the exported file rather than relying on appearance alone
Use an appropriate PDF inspection or preflight feature to review the fonts reported in the exported interior. Follow that tool's current documentation when interpreting its results. Keep the report or relevant evidence with the export. If it identifies an unexpected font or a problem, trace the affected text back to the source before accepting the file.
A familiar appearance is useful but incomplete evidence. The computer used for editing may have resources available that another part of the workflow does not. Conversely, a report that appears satisfactory does not prove that a particular character or style was the one the author intended. Treat file inspection and visual review as complementary checks with different purposes.
Read the text that is most likely to reveal a problem
Inspect passages with italics, bold text, small capitals, accented names, symbols, and other treatments used in the book. Compare them with the accepted source. Look for missing marks, unexpected spacing, altered emphasis, or characters that no longer represent the intended text. A changed character in a name or instruction can matter even when the overall paragraph still looks neat.
Pay attention to tables and captions as well as running prose. Their smaller spaces can make a substitution or spacing change more disruptive. Check whether the meaning remains clear and whether lines still fit their intended areas. Avoid treating a font issue as cosmetic when it changes an instruction, removes emphasis used to distinguish options, or makes a label ambiguous.
Correct the source and review the layout consequences
When a problem requires a font or style change, make that correction in the editable project and export again. Keep the old result available for comparison, but clearly identify the replacement submission candidate. Do not leave the only fix in an isolated file that the next normal export will overwrite.
Recheck line endings, page breaks, and related references after the correction. A change in text layout can move a heading or alter the length of a table. Even when the font problem is resolved, the resulting pagination may need attention. If the final page count changes, review the other production files that depend on it so the release remains a matched package.
Keep font evidence within the wider release review
Attach the final inspection record to the exact exported file and note any unresolved findings. Repeat the relevant check if that file changes. A report from an earlier export should remain historical evidence, not become an automatic approval for a later file. This simple distinction prevents an apparently complete checklist from referring to the wrong interior.
Use the available preview and proof review to inspect the book as a whole. Font embedding addresses one aspect of file preparation; readability, hierarchy, page composition, and accurate content still require judgment. The author should be able to explain both what was technically checked and what was visually reviewed. That combination supports a more reliable submission than either a clean report or a quick glance alone.
Frequently asked questions
Clear answers for this publishing decision.
Does a correct-looking PDF prove its font preparation is complete?
No. Inspect the file with a suitable reporting tool and review the source workflow. Appearance and technical evidence answer different questions and should be considered together.
Should I inspect only the body-text font?
Review all relevant text treatments, including headings, tables, captions, and imported elements. The main document style may not describe every piece of text in the interior.
What needs another check after changing a font?
Export again, inspect the font result, and review layout changes such as line endings and pagination. Revisit dependent production files when the final page count changes.
What must I check, disclose, and verify myself when AI helped produce the book?
Review facts, rights, and source material yourself, record which parts were AI-assisted or AI-generated so you can answer Amazon’s disclosure question accurately, and treat every automated check as a starting point rather than a verdict.
See what the compliance checks cover