A KDP upload pack should bundle the final interior PDF, EPUB, cover assets, listing data, checklist.md, and manifest.json so every deliverable is named, versioned, and auditable.
GUIDES · AMAZON KDP
Export a KDP Upload Pack and Manifest
A KDP upload pack should bundle the final interior PDF, EPUB, cover assets, listing data, checklist.md, and manifest.json so every deliverable is named, versioned, and auditable. 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
A KDP upload pack should bundle the final interior PDF, EPUB, cover assets, listing data, checklist.md, and manifest.json so every deliverable is named, versioned, and auditable. The decision should be made from the final book specifications rather than a generic web template.
The intended reader or decision context is specific: freeze the manuscript, page count, cover geometry, metadata, rights notes, and edition identifiers. That scope keeps the project aligned with the book readers will actually receive.
Inputs to settle first
Before production, freeze the manuscript, page count, cover geometry, metadata, rights notes, and edition identifiers. 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 Export a KDP Upload Pack and Manifest workflow
The operational approach is to export all formats from one approved project and use the manifest as the pack inventory. 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: collecting files from downloads and email invites stale versions and missing upload steps. Correct the source decision rather than patching only the final file.
For the final check, open each deliverable, compare checksums or dates, and walk through checklist.md before upload. KDP Previewer and the current Amazon help pages remain the authority for the submission surface.
How BookWizard supports this workflow
BookWizard connects Export a KDP Upload Pack and Manifest 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