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 well as a personal archival step. When a book is done, packaging the EPUB alongside a plain-text metadata summary and a readiness report gives you a self-contained snapshot you can store and reopen years later without needing the original software. The ZIP records what the file was and the shape it was in at delivery time.

Because everything runs in your browser, the EPUB stays on your machine. That matters for unpublished manuscripts and pre-release titles under embargo, where uploading a draft to a third-party server is exactly the risk you want to avoid.

You drop a single EPUB onto the tool. It parses the file, reads the embedded metadata, and runs a DRM check before doing anything else. If the file appears DRM-protected, packaging stops and tells you, because it will not bundle a locked file. You then choose which items to include from four toggles: a copy of the EPUB itself, a metadata summary as plain text, a Kindle readiness report, and a delivery README. Click Create delivery ZIP and download the result, named after your book with a -delivery suffix.

The metadata summary is generated from inside the EPUB: title, author, publisher, language, identifier, date, detected EPUB version, chapter count, and whether a cover and table of contents are present. The Kindle readiness report runs pre-flight checks (cover, title, author, language, file size against KDP limits, TOC, identifier, mimetype, and reading order) and marks each PASS, WARN, or FAIL. The README lists the package contents and per-store upload notes.

Two honest limits: the tool packages and reports on the file you give it, it does not convert or edit the EPUB content, 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 will show as not set in the summary.

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.

Finally, the input is one EPUB at a time, and a DRM-protected file will be refused outright. If you need to combine multiple books, edit metadata, or correct content, do that 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 FAIL or WARN 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 official, contractual, or paid delivery, treat the tool's output as a starting checklist and verify manually. Confirm metadata matches your contract or ISBN registration, and run the file through the destination platform's own validator before you consider the delivery final.