How to Preview a KDP Book Before Publishing: eBook, Print, and Proof Copies

The KDP previewer is the last line of defence before your book reaches readers. It costs nothing and takes 20-30 minutes to use properly. Skipping or rushing it is the single most common source of avoidable post-publication problems, from formatting errors that generate one-star reviews to broken links that make your book unusable. For the full publishing guide, see our complete beginner’s guide to self-publishing on Amazon KDP.

How to Access the Previewer

KDP has separate preview workflows for digital and print books. For eBooks, the Online Previewer is available from the eBook content setup after upload. KDP also provides the free desktop Kindle Previewer, which authors can use throughout production and which offers more inspection options than the online tool.

For paperbacks and hardcovers, launch Print Previewer from the Book Preview section after uploading the interior and cover. Print Previewer checks for issues you need to fix before submission. A screen preview still cannot reproduce paper, binding, color, and physical trim perfectly, which is why proof copies remain important for print books.

Previewing Your eBook: What to Look For

Test the book as reflowable content rather than as a sequence of fixed pages. Switch among tablet, phone, and e-reader views and vary the font size. Confirm that chapter headings remain attached to the right text, images scale sensibly, lists and tables remain readable, and intentional emphasis does not turn into odd spacing or broken line wraps.

Click every navigation link. Check the visible table of contents and Kindle Interactive TOC where applicable, plus endnotes, footnotes, external links and back matter. Also test dark and alternate reading backgrounds when the production tool supports them, especially if the book uses custom text colors or transparent images.

Previewing Your Print Book: What to Look For

Read Print Previewer page by page, not only the warning summary. Check trim and gutter margins, bleed, page-number sequence, blank pages, running heads, chapter starts, images, tables, and the transition between front matter and the main text. Review the full-wrap cover for spine position, text clearance, barcode area, and any element close to the trim edge.

Then order a physical proof for decisions that depend on the manufactured object. KDP allows up to five proof copies per order for eligible draft titles after Print Previewer approval. Use the proof-copy guide to check binding, paper, density, image reproduction, cover color, and real reading comfort.

The Full Pre-Publication Preview Checklist

• Title and copyright pages are correct.
• Interactive and visible TOC links go to the correct sections.
• Chapter breaks and headings behave across eBook display settings.
• Images are sharp, positioned correctly, and legible on small screens where relevant.
• Lists, tables, footnotes and endnotes remain usable after conversion.
• Print trim, bleed, gutter and outside margins are correct on every page.
• Page numbers and running heads are consistent.
• Cover front, spine and back align with the current page count.
• No placeholder text, comments, hidden marks, or accidental blank pages remain.
• A physical proof has been reviewed when the printed object matters to quality.

Common Issues Found in Preview

Common eBook problems include broken navigation, unexpected heading sizes, text that depends on manual tabs or spaces, images that overwhelm a phone screen, and formatting that only looked correct in Word. Common print problems include gutter encroachment, bleed errors, low-resolution images, content outside the safe area, unexpected blank pages, and a cover spine built for the wrong page count.

Previewer warnings deserve investigation, but absence of a warning is not proof that the book is editorially correct. A technically valid file can still contain a duplicated paragraph, misspelled heading, inconsistent character name, unreadable chart, or a bad page break. Keep technical QA and proofreading as separate passes.

What to Do After Preview

If the preview reveals a problem, fix the editable source and export a new publication file. Do not patch the converted output blindly if that breaks your ability to reproduce the edition later. Keep versioned masters so you can identify exactly which file is live.

Once the file is clean, complete the listing and pricing. Rank Fuel’s Listing Generator can help organize the Amazon copy, while Keyword Research and Category Finder/Category Research support the discovery decisions around it. Before pressing Publish, run the full KDP book production checklist so the technical preview, metadata, pricing, rights, and proofing work meet in one final gate.

What Previewer cannot prove

A preview simulation cannot prove that every physical copy will match your screen color, that the chosen paper feels right, or that the spine is comfortable to read. It also cannot tell you whether the pacing of a chapter feels wrong, a factual claim is unsupported, or an illustration is inappropriate for the intended reader.

Use Previewer to answer technical display questions, a proof copy to answer physical-production questions, and a human editorial/proofreading pass to answer language and content questions. Problems become expensive when one tool is expected to do all three jobs.

A three-layer proofing workflow

Use three layers of checking rather than expecting one preview to catch everything. Layer one is structural: inspect the source and exported file for the correct chapters, navigation, page order, images and final text. Layer two is platform simulation: use Kindle Previewer or Online Previewer for eBooks and Print Previewer for physical editions, deliberately checking the pages and components most likely to break. Layer three is real-world proofing: for print, order a proof copy and inspect the physical object under normal reading conditions.

Each layer catches a different class of error. A simulator can reveal a chapter heading stranded at the bottom of a page or an eBook image that scales badly. A physical proof can reveal a gutter that feels cramped, a gray background that prints muddy, or a spine that is hard to read. An editorial read can catch a wrong date or repeated paragraph that neither previewer recognizes as a technical problem.

Keep a short proof log. Record the issue, page or location, fix, and whether the change affects eBook, print, or both. Re-run the relevant preview after corrections. That discipline is especially valuable when multiple formats are being prepared at once because a fix that improves paperback layout can accidentally damage a reflowable eBook if the same source is reused carelessly.

A final practical check

Before you act on this guidance, check the current KDP screen for the title and marketplace you are working in. Amazon changes labels, eligibility and timing details over time, while the underlying decision remains the same: keep the account accurate, keep the book compliant, and make one deliberate change at a time so you can tell what actually improved the result.

Keep a dated note of the file, metadata and settings used for the live edition. That simple record makes later troubleshooting much faster because you can separate a platform delay from a change you made yourself, and it gives you a clean baseline for the next revision.