Use this checklist before every final print upload. Lock your print settings, check the pages most likely to cause trouble, fix problems in your source file, then upload one fresh PDF.
Start with a locked print setup
Set trim size, paper type, and bleed choice before you inspect warnings in Previewer.
If any of those settings change, treat the PDF as a new file and rerun the checklist from the start.
Many "mystery" warnings happen because the file was checked against different print settings than the ones used to make it.
Make a short list of pages most likely to cause trouble
Before you scroll through the whole book, list the pages that usually trigger warnings: chapter openings, pages before or after scene breaks, TOC pages, full-bleed pages, and image-heavy pages.
Keep simple notes with the page number, the exact warning text, and what you think caused it.
A short list keeps you from fixing the same page twice and saves a lot of random scrolling.
Check three things in order: layout, navigation, then image and font quality
Next, check navigation: front matter order, chapter order, and every TOC link.
Last, check image and font quality: full-page images, bleed edges, italics, ornaments, and anything else that looks visually fragile.
Going in this order makes it easier to fix the real problem instead of chasing symptoms.
Fix the source file, not the PDF
Sort each warning into one of four buckets: structure, layout, navigation, or image/font quality.
Fix the manuscript or layout settings in the source file, then export a fresh PDF and rerun Previewer.
Avoid editing the final PDF as your normal method. Those fixes are easy to lose on the next export.
Separate true bleed warnings from generic image or margin issues
Not every flagged image page is a bleed problem. Previewer can flag margin, gutter, trim-safe, and true bleed problems that look similar at first glance.
Use the exact warning text to decide what kind of issue you have. True bleed warnings usually mean your page size or upload settings do not match edge-to-edge artwork. Margin warnings usually mean important content is too close to the edge.
If your book uses image-heavy full-bleed spreads, Previewer should be the final check after you fix the layout in the source file.
Use the exact warning text and save a few screenshots
When Previewer flags a page, copy the warning text exactly. Similar warnings can look almost the same, so exact wording matters.
Save a screenshot of the warning panel with the page number visible. Only save before-and-after page images when the problem is clearly visible on the page.
Keep those screenshots in the same folder as your latest PDF so they are easy to find later.
What to do when Previewer flags margins or gutter
Start with the exact pages Previewer flagged. Check whether text, ornaments, or images are actually too close to the outer edge or the inside gutter.
Compare the same page in your PDF viewer and in Previewer. If both show the same problem, fix spacing or page setup in the source file. If the warning text and the page image do not clearly match, trust the warning text first and capture your own screenshots.
For image-heavy pages, do not change bleed settings until you know whether the warning is really about bleed, margins, or gutter.
Upload one latest PDF only after the warnings are clear
Give each export a clear file name so you do not upload the wrong PDF by accident.
Open Previewer on the newest file only and confirm that the warning count went down and the flagged pages look better.
Keep one final PDF and the screenshots you want to save before you upload to KDP.
The Senswriter way (faster)
If you use Senswriter, the easiest loop is simple: finish edits, export a fresh print-ready PDF, run KDP Previewer, fix the project, then export again.
That keeps your manuscript, print PDF, EPUB, and DOCX handoff in sync instead of creating one-off PDF fixes.
Senswriter does not replace KDP Previewer. It helps you get to a cleaner file faster, then Previewer is still your final check before upload.
Numbers and Reference Tables
KDP Previewer Triage Matrix
Warning class
Fast diagnosis
Source-first fix
Verification step
Margins and trim
Text is too close to the page edge or safe area, often on chapter-open pages.
Fix margins and spacing in the source file; remove manual line-break hacks.
Recheck the flagged pages and a few nearby pages in Previewer.
Pagination drift
Blank pages appear or chapter starts move after edits.
Remove hidden page or section breaks and keep chapter-start rules consistent.
Compare the chapter-start order against your notes.
TOC/navigation
TOC links jump to the wrong heading or to a duplicate heading.
Clean up heading levels and remove duplicate chapter titles.
Click every TOC entry from top to bottom.
Bleed/image
Full-page art shows white slivers or bleed mismatch warnings.
Match page size to trim plus bleed and extend edge art in the source file.
Inspect all full-bleed pages at full-page zoom.
Font consistency
Italic or body-text changes appear on a few pages only.
Unify source paragraph styles and re-export with the final type settings.
Spot-check chapter titles, italics, and ornament pages.
Common KDP warning strings (representative examples)
Previewer wording can vary a little by version. Use the exact text in your own warning panel as the real source of truth; these are representative examples only.
Warning text in Previewer
Usually means
First source-first fix
"Text is outside the margins and may be cut off when printed."
Paragraph spacing, indents, or manual line breaks are pushing text beyond safe print areas.
Normalize paragraph styles and margins in the source file, then re-export.
"Text is close to the edge of the page and may be cut off when printed."
Text blocks sit too close to the trim edge, often on chapter-open pages.
Increase safe spacing and remove manual alignment hacks.
"Images or text are intended to bleed off the page, but bleed is not enabled."
Artwork reaches the page edge but upload settings or page size are still set to no-bleed.
Match the bleed setting and PDF page dimensions to the actual design.
"Images do not appear to be high enough resolution for printing."
The source image is too low resolution for print at its current size.
Replace it with a higher-resolution image and re-export.
"Some content may be clipped in the gutter."
The inside margin is too small for the current page count or trim size.
Recheck the gutter or inside margin and rerun chapter-open checks.
Publish Checklist
Lock trim size, bleed, and paper settings before opening Previewer.
Write down those print settings once so you do not mix them up later.
Make a short list of high-risk pages: chapter opens, scene transitions, TOC pages, and image-heavy pages.
Run pass 1 for margins, trim, gutter, and chapter-start position.
Run pass 2 for front matter order and TOC accuracy.
Run pass 3 for bleed edges, image quality, and font consistency.
Check page numbers and headers/footers for the section behavior you want.
Flag any unexpected blank pages near chapter boundaries.
Classify image warnings by exact text before calling them bleed issues.
Save screenshots of warnings before fixing them.
Classify each issue as structure, layout, navigation, or image/font quality.
Fix the source manuscript and source layout settings, not the final PDF.
Export again and rerun Previewer on the newest PDF only.
Confirm the warning count goes down and the problem does not come back on nearby pages.
Keep one final clean PDF and your screenshots before upload.
Warning-to-Fix Map
Warning pattern: text outside margin guides
Fix: Normalize source paragraph spacing and indent settings, then re-export from the source manuscript.
Verify: Previewer no longer flags margin overflow on the same and adjacent pages.
Warning pattern: text close to trim edge
Fix: Increase source inside and outside margins and remove manual line breaks that force edge crowding.
Verify: Chapter-open and heading-dense pages clear trim-safe checks.
Warning pattern: unexpected blank page before chapter
Fix: Remove hidden page breaks or duplicate section boundaries and keep chapter-start rules consistent.
Verify: Only intentional blank pages remain between chapters.
Warning pattern: chapter start shifted after edits
Fix: Lock print setup, remove older confusing file versions, and export from the latest source only.
Verify: Chapter-start order matches your notes across the full manuscript.
Warning pattern: TOC link target mismatch
Fix: Normalize heading hierarchy and remove duplicate anchor-producing headings in the source file.
Verify: Every TOC link lands on the intended chapter heading.
Warning pattern: TOC labels out of order
Fix: Reorder source chapter headings and regenerate the TOC from the corrected structure.
Verify: TOC labels and reading order both match the manuscript order.
Warning pattern: image may be cut off near trim
Fix: Match bleed settings to the design and keep important visual content inside safe print zones.
Verify: Full-page image pages render without cut-off risk markers.
Warning pattern: low-resolution image alert
Fix: Replace low-resolution source images and regenerate the export from the same manuscript revision.
Verify: The image-quality warning clears for the affected pages.
Warning pattern: ornament or divider overlaps text
Fix: Adjust source spacing around ornaments or separators; do not move decorative elements in the final PDF.
Verify: Ornament pages keep consistent spacing before and after breaks.
Warning pattern: header or footer overlap
Fix: Refine source header and footer spacing and check section-level header linkage settings.
Verify: Odd and even pages with headers show no overlap or clipping.
Warning pattern: page numbers appear in front matter unexpectedly
Fix: Update front-matter pagination and section-start settings in the source file.
Verify: Title, copyright, and TOC pages follow the numbering rules you intended.
Warning pattern: font substitution in Previewer
Fix: Unify source type styles and generate a fresh export from the latest manuscript state.
Verify: Italics, punctuation, and chapter titles stay consistent across spot checks.
Warning pattern: issue appears fixed but warning remains
Fix: Confirm Previewer is reading the newest file and remove stale similarly named PDFs.
Verify: The renamed latest file shows the warning count you expect.
Verification Checklist
Screenshots that actually help
Capture the Previewer warning panel with page number and warning text visible.
Capture your own flagged page at full-page zoom only if the visual defect is actually visible on that page.
After a fix, rerun Previewer on the newest file and capture the updated warning panel if the warning count changed.
Simple final check before upload
Keep screenshots in the same folder as the PDF you plan to upload.
Give screenshot files clear names so you can tell what each one shows later.
If Previewer finishes clean, save one last screenshot of the clean warning panel before upload.
The Senswriter way (faster)
Use the same workflow in one workspace: draft, export, run checks, fix the source, and upload one clean final file.
Write and reorganize chapters/scenes without switching between multiple tools.
Generate print-ready PDF, EPUB, and DOCX from the same manuscript source.
Re-export quickly after fixes so KDP and EPUB checks stay repeatable.
Use optional BYOK AI assist only if you want drafting support.
Why run a warning-to-fix checklist if the PDF looks mostly fine?
Small problems often hide in chapter transitions or TOC jumps. A repeatable checklist helps you catch them before publish day.
Should I clear warnings by patching the final PDF?
No. Fixing the source file and re-exporting keeps your manuscript and final upload in sync for future revisions.
When do I rerun Previewer?
Rerun it after any meaningful manuscript edit or any change to trim size, bleed, paper, or margins.
What should I inspect first if time is limited?
Start with chapter-open pages, page-before-chapter transitions, TOC jumps, and full-bleed image pages.
Does every flagged image page mean I have a bleed problem?
No. Some flagged image pages are really margin or trim-safe-zone problems. Use the exact warning text to separate true bleed-setting mismatches from generic cut-off risk near the page edge.
Can I ship with warning-level findings if pages look fine?
Treat structural or navigation warnings as blockers. Only minor advisory warnings should move forward, and only if you understand exactly why they are safe.
Why write down page numbers and warnings during Previewer checks?
Simple notes keep you from fixing the same page twice, help you remember what changed, and make late edits much less confusing.