KDP Previewer Checklist

Run this checklist before every final print upload. The high-confidence loop is: lock print settings, inspect high-risk pages, classify warnings, fix source content, re-export, then verify one release-candidate file.

Start with a locked print setup

Set trim size, paper type, and bleed choice before you inspect warnings in Previewer.

If any of those values change, treat your file as a new release candidate and rerun the full checklist.

Many "mystery" warnings are not mystery at all. They come from checking a PDF against a different print setup than the one used to generate it.

Create a page-risk map before a full pass

List the highest-risk page types first: chapter-open pages, pages before/after scene breaks, full-bleed pages, image-heavy pages, and TOC destinations.

Keep a short release log with page number, warning class, root cause hypothesis, and fix owner.

A 10-minute risk map often removes hours of random scrolling and duplicate fixes.

Run three passes in order: layout, navigation, then asset quality

Pass 1 (layout): inspect margins, trim-safe zones, headers/footers, chapter starts, and unexpected blank pages.

Pass 2 (navigation): verify front matter order, chapter sequence, and every TOC jump target.

Pass 3 (assets): inspect full-page images, bleed edges, and typography consistency (especially italics and ornament-heavy pages).

When checks are sequenced, you avoid fixing downstream symptoms before upstream structural issues.

Map each warning to a source fix, not a PDF patch

Treat each warning as one of four classes: structure, layout, navigation, or asset quality.

Fix the source manuscript or source layout settings, then generate a fresh PDF and rerun Previewer.

Do not patch the final PDF as a normal workflow. Those edits are fragile and often vanish on the next export.

Search by exact warning text and capture screenshot evidence

When Previewer flags a page, copy the warning text exactly and search it in your release notes. Warning labels often look similar, so exact wording prevents false fixes.

Capture three screenshots for each blocker: warning panel with page number, flagged page at full-page zoom, and post-fix rerun showing the warning cleared.

Keep screenshots in the same release-candidate folder as the final PDF so the entire fix history stays auditable.

Finalize one release candidate only after warnings clear

Use versioned naming such as `book-title-print-rc04.pdf` to prevent stale-file mistakes.

Reopen Previewer on the newest file only and confirm warning count plus page-specific defect checks.

Archive one final candidate with screenshots for margin, TOC, and image-sensitive pages before upload.

Numbers and Reference Tables

KDP Previewer Triage Matrix

Warning class Fast diagnosis Source-first fix Verification step
Margins and trim Text appears near trim or outside safe zones on chapter-open pages. Normalize source margins and spacing; remove manual line-break hacks. Recheck flagged pages and neighboring spreads in Previewer.
Pagination drift Unexpected blank pages or chapter starts shift after edits. Remove hidden page/section breaks and lock chapter-start policy. Compare chapter-start sequence against release log.
TOC/navigation TOC links jump to wrong heading or duplicate anchor. Clean heading hierarchy 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+bleed and extend edge art in source. Inspect all full-bleed pages at full-page zoom.
Font consistency Italic/body font substitution or clipping appears on select pages. Unify source paragraph styles and re-export with final type settings. Spot-check chapter titles, italics, and ornament pages.

Common KDP warning strings (verbatim examples)

Previewer wording can vary slightly by version, but these exact phrases are common in print checks.

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 trim-safe zones. Normalize paragraph styles and margins in source, 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 trim edges, usually on chapter-open pages. Increase safe-margin spacing and remove manual alignment hacks.
"Images or text are intended to bleed off the page, but bleed is not enabled." Artwork reaches page edge but upload settings or page size are configured as no-bleed. Match bleed setting and PDF page dimensions to the interior design intent.
"Images do not appear to be high enough resolution for printing." Source image DPI is too low for print at placed size. Replace asset with high-resolution source and re-export.
"Some content may be clipped in the gutter." Inside margin is too small for page count or trim size. Recheck gutter/inside margins and rerun chapter-open checks.

Publish Checklist

  1. Lock trim size, bleed, and paper settings before opening Previewer.
  2. Record print setup values in release notes.
  3. Build a risk map: chapter opens, scene transitions, TOC destinations, image-heavy pages.
  4. Run pass 1 for margins/trim and chapter-start positioning.
  5. Run pass 2 for front matter order and TOC destination accuracy.
  6. Run pass 3 for bleed edges, image quality, and font consistency.
  7. Check page numbers and headers/footers for intended section behavior.
  8. Flag any unexpected blank pages near chapter boundaries.
  9. Capture screenshots of each warning before fixing.
  10. Classify each issue as structure, layout, navigation, or asset quality.
  11. Fix source manuscript content and source layout settings only.
  12. Re-export and rerun Previewer on the newest file version.
  13. Confirm warning count decreases and no regression appears on previously clean pages.
  14. Archive one final release-candidate PDF with verification screenshots.

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/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 normalize chapter-start policy.

Verify: Only intentional parity blanks remain between chapters.

Warning pattern: chapter start shifted after edits

Fix: Lock print setup, remove stale file variants, and export from the latest source only.

Verify: Chapter-start sequence matches release log across full manuscript.

Warning pattern: TOC link target mismatch

Fix: Normalize heading hierarchy and remove duplicate anchor-producing headings in source.

Verify: Every TOC link lands on the intended chapter heading.

Warning pattern: TOC labels out of order

Fix: Reorder source chapter headings and regenerate TOC from the corrected structure.

Verify: TOC labels and reading sequence both match manuscript order.

Warning pattern: image may be cut off near trim

Fix: Match bleed setting to design intent and keep key visual content within trim-safe 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 export from the same manuscript revision.

Verify: Image quality warning clears for the affected pages.

Warning pattern: ornament or divider overlaps text

Fix: Adjust source spacing around ornaments or separators; avoid moving decorative elements in final PDF.

Verify: Ornament pages keep consistent spacing before and after breaks.

Warning pattern: header or footer overlap

Fix: Refine source header/footer spacing and check section-level header linkage settings.

Verify: Odd/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 source.

Verify: Title/copyright/TOC pages follow intentional numbering rules.

Warning pattern: font substitution in Previewer

Fix: Unify source type styles and regenerate a fresh export from the latest manuscript state.

Verify: Italics, punctuation, and chapter titles remain 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 candidates.

Verify: Renamed latest file shows expected warning-count reduction.

Proof Checks

Screenshot packet for warning-to-fix proof

  • Capture Previewer warning panel with page number and warning text visible.
  • Capture flagged page at full-page zoom with trim and margin guides visible.
  • Capture the same page after fix and rerun, with warning panel count reduced.

Release-candidate evidence checklist

  • Store screenshots in the same folder as the release-candidate PDF version.
  • Reference screenshot filenames in your release log next to each warning row.
  • Keep one final clean-panel screenshot before upload to document sign-off.

The Senswriter way (faster)

Use the same workflow in one workspace: draft, export, run checks, fix source, and publish one clean release-candidate file.

Open the Senswriter Workspace and see export examples.

Frequently Asked Questions

Why run a warning-to-fix checklist if the PDF looks mostly fine?

Small defects often hide in chapter transitions or TOC jumps. A repeatable checklist catches those before publish day.

Should I clear warnings by patching the final PDF?

No. Fixing source content and re-exporting keeps your manuscript and release file aligned for future revisions.

When do I rerun Previewer?

Rerun it after any meaningful manuscript edit or any print setup change, especially during release week.

What should I inspect first if time is limited?

Prioritize chapter-open pages, page-before-chapter transitions, TOC jumps, and full-bleed image pages.

Can I ship with warning-level findings if pages look fine?

Treat structural or navigation warnings as blockers. Only non-impact advisory warnings should proceed, and only with explicit release notes.

Why keep a release log for Previewer checks?

A release log prevents repeated work, proves fixes by page number, and helps you avoid regressions during late edits.

Sources and Claim Checks