How we publish Kindle books end to end, from manuscript to live listing

Publishing a Kindle book end to end means turning a manuscript into a valid ebook file, a print interior and covers sized to the page count, plus a listing whose title nobody else is using, then getting each format through Amazon KDP review. We built this pipeline for Ruthless Vow by Elle Voronova, live on Amazon since 20 October 2026 and shown on our Published page. Here is how it works and what we changed after launch.

What does publishing a Kindle book end to end involve?

Publishing a Kindle book end to end covers five stages: editing the manuscript, building the ebook file, building print interiors and covers, writing the listing, and submitting each format for KDP review. Each stage has an output and a check. A skipped check came back to us as a rejection or a fix to a live book.

The book is published by its author under a pen name. We build what KDP asks for: the formatted file, the cover and the listing.

How do you turn a manuscript into a Kindle file?

We turn a manuscript into a Kindle file with a build script. Chapters live as separate text files, and one command compiles them into a single manuscript, an EPUB for Kindle and a PDF for proofreading. Because the build is scripted, any edit produces a fresh, consistent file instead of a manual export that drifts from the last one.

Before the build, the manuscript went through two cold-read passes, each reading the book the way a first-time reader would, and together they fixed 56 flow issues. Scripted builds also make late edits cheap, the same reason we generate our blog from files, as described in why we built a content engine in Python.

Every EPUB is checked with EPUBCheck before upload. One problem it does not catch showed up in KDP itself: the dashboard reported that the Start Reading location was not set. The EPUB's nav document had no body-matter landmark, so Kindle did not know where chapter one begins. A small shared script now adds that landmark in every build.

How do you make print editions and covers that pass review?

Print editions need an interior PDF at the chosen trim size and a cover whose full width depends on the page count, because the spine grows with every page. We read the cover dimensions for each book from KDP's cover calculator, build paperback and hardcover covers from the same artwork, and keep all front-cover art inside the safe area.

Our interior is 6 by 9 inches on cream paper, and the same interior PDF serves the paperback and the hardcover. The dimensions come from KDP's cover calculator rather than a template, since a few pages more or less changes the spine.

The hardcover still came back rejected the first time. Front-cover art crossed the safe line near the edge and the spine. We changed the cover generator to box the front art inside the safe area, rebuilt every hardcover cover, resubmitted, and the hardcover went live. Each format has its own review, so a passed paperback says nothing about the hardcover.

Why check a book title before you choose it?

A book title should be checked for exact matches on Amazon before it is chosen, because a shared title buries a new book in search. That is why every title and subtitle is now checked against the store before anything else is built.

The check is simple and evidence-based.

1. Search the exact phrase in the Kindle store and record every match.
2. Scan for stock genre words that make a title read like a copy of the bestsellers around it.
3. Keep the subtitle unique too, and put genre tropes in the keyword slots and categories instead.
4. Show the evidence with the proposed title, so a person decides on data, the pattern in human-in-the-loop automation.

For a book already live with a shared title, pair the author name and the full title in every ad and link. That is what readers need to type to find it.

What goes into a KDP listing?

A KDP listing is the title, subtitle, description, seven keyword slots, categories, price, rights settings and content questions, including whether AI was used. We write the listing in a file that lives next to the book, so the text uploaded to KDP is the same text that was reviewed, and a mistake can be found and fixed fast.

That file paid off once already. On one upload, the descriptions of two different books were swapped. Because each listing lived in its own file, the fix was a paste and a republish, not a rewrite from memory. KDP's content guidelines set what a listing may say, and we answer the AI question truthfully.

Two more lessons from the dashboard. We hit a weekly limit on new title submissions, so launches are planned around it. And a listing is never finished at upload: we open the live product page and check it.

If you are deciding whether a book belongs in your go-to-market, start with Amazon KDP for founders. We run the pipeline with the habits described in running a company on AI agents: written rules, scripted checks, and a person who approves every submission.

Frequently asked questions

One pipeline, every format

A book that sells starts as a file that builds the same way every time, a cover that fits its page count and a title nobody else owns. The writing is the hard part, and the pipeline should never be. Nactore is a technology and growth company, one partner that builds, ships, ranks and grows, measured on your growth.

Have a manuscript waiting? Book a free 30-minute call and we will tell you what it needs to be ready for Amazon.