The shortest useful answer to the search phrase “KDP novel manuscript to EPUB” is this: declare whether chapters, scene breaks, navigation choices, and colophon data belong to source or settings. The controlled case is a three-chapter novel with six scene breaks, dialogue, navigation choices, and colophon data. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for chapter heading, scene break, navigation inclusion, colophon, revision reflection. The excluded range is stated separately: KDP upload, Japanese vertical layout, and cover design.
Decision: Declare whether chapters, scene breaks, navigation choices, and colophon data belong to source or settings
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove chapter heading, revision reflection, or the stages between them.
The article-specific evidence card has these fields: chapter heading, scene break, navigation inclusion, colophon, revision reflection. Do not count the following excluded range as evidence: KDP upload, Japanese vertical layout, and cover design.
One case, one authority, one result
Use a three-chapter novel containing six scene breaks, dialogue, navigation choices, and colophon data. Keep chapter and scene markers in the manuscript, keep colophon data in settings, inspect chapter movement after generation, then change one dialogue line in source and regenerate. A scene break promoted to navigation, duplicated colophon text, or package-only revision fails the workflow.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to declare whether chapters, scene breaks, navigation choices, and colophon data belong to source or settings. Name the source, working copy, and delivered or reopened result so that another editor can locate each one without relying on a filename such as final.
The path to the inspected result
Use the following product-independent sequence on the named sample. It is an acceptance method, not a claim that Rune Studio has already completed this particular case.
- 1. Add stable chapter and scene markers. Attach the observed chapter heading evidence to this step.
- 2. Record which chapters enter navigation. Attach the observed scene break evidence to this step.
- 3. Keep colophon data in settings. Attach the observed navigation inclusion evidence to this step.
- 4. Generate and test chapter movement. Attach the observed colophon evidence to this step.
- 5. Change one dialogue line in source and rebuild. Attach the observed revision reflection evidence to this step.
How to mark the run
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Chapter heading — expected state: written before the run; hold the row if scene breaks become navigation entries.
- Scene break — expected state: written before the run; hold the row if colophon data is duplicated in body text.
- Navigation inclusion — expected state: written before the run; hold the row if the revision exists only inside the EPUB.
- Colophon — expected state: written before the run; hold the row if scene breaks become navigation entries.
- Revision reflection — expected state: written before the run; hold the row if colophon data is duplicated in body text.
Three failures that invalidate the run
A second pass is meaningful only when its source and changed condition remain identifiable. Keep the earlier result and append the retest instead of replacing the failed row.
- 1. Scene breaks become navigation entries; preserve the failed artifact.
- 2. Colophon data is duplicated in body text; change only the responsible condition.
- 3. The revision exists only inside the EPUB; return to the named source.
When to shortlist Rune Studio
Current product documentation covers capabilities relevant when you need to manage manuscript direction, navigation, cover, and colophon as separate publishing decisions. That scope can justify a trial, but it does not show that a three-chapter novel with six scene breaks, dialogue, navigation choices, and colophon data passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you declare whether chapters, scene breaks, navigation choices, and colophon data belong to source or settings. Use another tool or destination check for the excluded range stated here: KDP upload, Japanese vertical layout, and cover design.
First task
For the search phrase “KDP novel manuscript to EPUB,” the conclusion is to declare whether chapters, scene breaks, navigation choices, and colophon data belong to source or settings. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for chapter heading, scene break, navigation inclusion, colophon, revision reflection.
Begin here: label chapter, scene, navigation, and colophon ownership. If scene breaks become navigation entries, stop at that row and return to its source. Check the Rune Studio product page for the current Mac feature scope before applying the same acceptance card to a product trial.
