Preparing an EPUB for KDP requires two separate decisions. First, is the local book structurally complete with navigation, cover, colophon, and reading order? Second, does KDP accept and present that exact file correctly? Rune Studio can support the first decision; only an actual KDP upload can answer the second.
Define the local finish line
Use a three-chapter book with three navigation entries, one cover, and one colophon. Check chapter sequence, every navigation destination, cover designation, author and publication details in the end matter, and missing images.
Amazon's KDP supported file types describe the upload doorway. The EPUB 3.3 Recommendation describes the format's package roles. Being an accepted type does not promise that an individual book will pass review.
Assemble the local EPUB in Rune Studio
On Series Information, enter title, author, language, and writing direction. Choose the standalone or numbered volume, select the three manuscript files, and use Chapter Order to retain chapters one through three with all three included in navigation. Metadata holds edition, date, and cover. Review and Export should display the title page, navigation, chapters, colophon, and intended file name before writing to the workspace's EPUB folder.
Open each navigation entry after export. Review the cover and colophon as separate components. Do not infer that a valid container proves a readable device presentation.
In the available local run, a three-chapter EPUB passed its structural check. Nav and NCX contained three chapter destinations, and the reading sequence ran through title, navigation, three chapters, and colophon. A second build was also valid and reproduced the same structure, with publication values present.
What this evidence cannot answer
The local result does not show a KDP upload screen, an acceptance result, a Kindle preview, or storefront series grouping. Those items remain unverified and should not be phrased as successful. Upload the same locally approved artifact, retain any KDP error wording, and inspect cover, chapter jumps, colophon, and uncommon characters in the online preview.
When a change is required, return to the source and wizard, create a new edition, and upload that edition. Avoid editing the submitted container in a way that the local source cannot reproduce.
Decide whether this division of labor fits
Rune Studio is a candidate for Mac authors who want to edit local manuscripts and generate a KDP-ready candidate EPUB 3. It does not replace KDP product setup, pricing, territory selection, review, or storefront management. Those tasks stay on the retailer side.
Begin with a copied three-chapter project, satisfy only the local checks, and then take the unchanged file to KDP. Use Rune Studio's current Mac scope and Amazon's current documentation for their respective responsibilities.
