One source manuscript can support both Kindle and paperback, but the ebook must reflow while the print edition needs fixed trim-aware pagination.
GUIDES · AMAZON KDP
Ebook and Paperback from One Manuscript
One source manuscript can support both Kindle and paperback, but the ebook must reflow while the print edition needs fixed trim-aware pagination. This page explains the decision, production steps, risks, and final review required for a KDP-ready edition.

Product proof
See it in BookWizard
The direct KDP answer
One source manuscript can support both Kindle and paperback, but the ebook must reflow while the print edition needs fixed trim-aware pagination. The decision should be made from the final book specifications rather than a generic web template.
The intended reader or decision context is specific: separate semantic structure from print-only styling and mark headings, images, breaks, and front matter consistently. That scope keeps the project aligned with the book readers will actually receive.
Inputs to settle first
Before production, separate semantic structure from print-only styling and mark headings, images, breaks, and front matter consistently. Record these choices in the project brief so drafting, design, and metadata use the same assumptions.
This is especially important for KDP because a late edition change can affect pagination, cover dimensions, identifiers, listing fields, or distribution choices.
A practical Ebook and Paperback from One Manuscript workflow
The operational approach is to edit one canonical manuscript, then produce and inspect separate EPUB and interior PDF outputs. Work from one approved source instead of editing disconnected exports.
Use explicit approval points for structure, manuscript, visual assets, edition settings, and metadata. That keeps speed from turning into version confusion.
Mistakes and final checks
A key risk is this: reusing page numbers, headers, fixed spacing, or print references in EPUB creates a poor Kindle experience. Correct the source decision rather than patching only the final file.
For the final check, test the EPUB in a Kindle previewer and the PDF in KDP Previewer. KDP Previewer and the current Amazon help pages remain the authority for the submission surface.
How BookWizard supports this workflow
BookWizard connects Ebook and Paperback from One Manuscript to the rest of KDP production: Autobook supports structured drafting, the print editor handles trim-aware pages, Cover Studio builds the wrap, and Export Studio packages PDF, EPUB, manifest.json, and checklist.md. Publish Studio prepares listing fields, while the Chrome extension uses preview-before-apply so you remain in control. Studio is $20/mo with 1M AI tokens, and a typical ~50-page pack can take about 45 minutes. BookWizard does not auto-publish and does not promise royalties.
FAQ
Common questions
Last reviewed: 2026-07-29