Publisher Delivery ZIP

Publisher Delivery ZIP exists for the moment a book is finished and needs to leave your hands cleanly. Instead of emailing a loose EPUB and hoping the recipient can reconstruct the title, author, and submission details, you hand over one organized archive that explains itself. It fits self-publishing authors preparing a KDP, Apple Books, or Kobo submission, freelancers returning a completed file to a client or editor, and small presses passing a manuscript to an aggregator.

It also works as a personal archive: the EPUB, its cover, a metadata summary and a readiness report in one snapshot you can reopen years later.

Everything runs in your browser, so unpublished and embargoed manuscripts stay on your machine.

You drop a single EPUB onto the tool, then choose which items to include from five toggles: a copy of the EPUB itself, the cover image from inside the book, a metadata summary as plain text, a Kindle readiness report, and a delivery README. Click Create delivery ZIP; the tool parses the file, runs a DRM check before doing anything else, and gives you the result named after your book with a -delivery suffix. A DRM-protected file stops the process, because the tool will not bundle a locked file.

The metadata summary is generated from inside the EPUB: title, author, publisher, language, identifier, date, EPUB version, the number of pages in the reading order, and whether a cover and table of contents are present. The Kindle readiness report is the same report the Kindle EPUB Checker produces: KDP's published rules for the cover inside the book, the EPUB structure checks with every problem listed, the title, language and author, and notes on the separate store cover and KDP's delivery cost, with KDP's source pages listed. The README lists the package contents and general delivery notes.

Two limits: the tool packages and reports on the file you give it; it does not convert or edit the EPUB, fix metadata, or remove DRM. The cover and metadata come from what is already inside the EPUB rather than from separate uploads, so anything missing there shows as not set in the summary, and a book with no marked cover gets no cover file.

The most common mistake is treating the Kindle readiness report as an official validation. It is an unofficial pre-check, and the report says so. Amazon KDP and other distributors run their own validation and may raise issues this tool does not catch, so a clean report is reassurance, not a guarantee of acceptance.

A second pitfall is assuming gaps get filled. If your EPUB lacks a cover, a language tag, or an identifier, the package will faithfully report those as missing rather than supplying them. Fix them in the source EPUB first using a metadata or cover tool, then re-package. Re-running this tool on an unchanged file simply produces the same warnings.

Combining books, editing metadata or fixing content happens upstream; this step is the final wrapper, not the workshop.

Open the downloaded ZIP and confirm the files you expected are present and correctly named after your book. Read the metadata summary and check the title, author, publisher, language, and identifier against what you intend to publish, since these flow straight from the EPUB and a blank field here usually means a blank field in the file. Then scan the Kindle readiness report for any failed or warning lines and decide whether each needs fixing before submission.

Most importantly, open the EPUB itself in a real reader. Test it in Kindle Previewer, Apple Books, or Calibre to confirm the cover, table of contents, and reading order behave as expected, because a passing report does not replace seeing the book render.

For contracted delivery, confirm the metadata matches your contract or ISBN registration.