Ebook Export and Publishing: Move from edited project to the right deliverable for each channel

A file that looks perfect inside your editor can break in delivery if the channel expects different structure or constraints. Start by mapping the buyer’s path: Are they reading in a store app that reflows text, downloading to a dedicated e-reader, printing a copy, or importing into an editing pipeline? That determines whether you should lead with PDF (fixed pagination) or EPUB (semantic, reflowable). DOCX should be treated as the editable handoff for collaborators and for anyone who will re-edit or typeset again; it is rarely the right “reader” format.

If you’re unsure, use this rule of thumb for your own project: if the manuscript relies on precise placement (tables, artwork with captions tightly aligned, a designed workbook grid, or a consistent “page” numbering experience), export PDF as the primary deliverable. If the book is mostly narrative text where the reader benefits from scaling and theme controls, export EPUB first. Then generate secondary formats from the same finished project so your cover and metadata stay consistent across channels.

In practice, the most common “mystery” publishing errors are not missing files—they’re mismatched presentation. Before you upload or publish, confirm that the cover image embedded in the exported file matches the latest cover version used in your project. Also verify that the title shown in the listing, the file name you downloaded, and the author name in the exported document all point to the same manuscript identity.

When you validate, do it like a buyer would: open the EPUB on a device/app where font sizing changes, go to the table of contents entry, and confirm it lands on the expected chapter. For PDF, scroll through to the early pages where readers notice inconsistencies first (title/copyright/first chapter headings) and confirm navigation links work. For DOCX, confirm headings and page breaks preserve the logical structure a later editor expects, especially if you plan to hand it off for additional revision.

To avoid wasting a day redoing uploads, do a fast QA pass immediately after downloading each export. For PDF: check (1) the first page title layout, (2) any chapter start formatting, (3) that the table of contents entry count matches the project chapters, and (4) that images are not stretched or blurred. For EPUB: open in at least one real reader app (not just a file preview) and perform a font-size sweep: smallest, medium, and largest. Confirm that headings remain readable and that images/figures don’t overlap text. For DOCX: verify that heading styles are preserved (so the next editor can update contents cleanly) and that lists don’t flatten into paragraphs.

Finally, re-check after any content change. Automateed regenerates exports from the current project state, so your verification is meaningful only if you test the newest download after edits. If you keep a “latest” folder on your computer, name files with the date or project revision to prevent sending an earlier build by mistake.