How to Make an EPUB in Six Steps: A Two-Chapter Starter Project

A two-chapter sample passes through six checks into one verified EPUB

The deciding move behind the search “how to make an EPUB” is not another feature: close each step with an inspected result rather than a filled form. The controlled case is a minimal cover-free EPUB with title page, two body chapters, and navigation. A pass must demonstrate this outcome: complete a two-chapter sample with visible evidence at every one of six steps. The excluded range is stated separately: cover production and KDP submission are excluded.

Decision: Close each step with an inspected result rather than a filled form

Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove work identity, package structure, or the stages between them.

The article-specific evidence card has these fields: work identity, volume settings, source selection, chapter order, metadata, package structure. Do not count the following excluded range as evidence: cover production and KDP submission are excluded.

The acceptance case for this search

Use a minimal cover-free EPUB with title page, two body chapters, and navigation. The decisive fields are work identity, volume settings, source selection, chapter order, metadata, package structure; keep the three stop conditions visible throughout the run.

This case addresses the failure behind the search: facing empty setup fields without knowing whether source or metadata comes first. 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.

Do the work without changing the baseline

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.

The result card

Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.

Do not hide these blockers

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.

When to shortlist Rune Studio

Current product documentation covers capabilities relevant when you need to preserve manuscript order and metadata, generate EPUB 3, and inspect the resulting structure. That scope can justify a trial, but it does not show that a minimal cover-free EPUB with title page, two body chapters, and navigation passed this article's acceptance card.

Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you close each step with an inspected result rather than a filled form. Use another tool or destination check for the excluded range stated here: cover production and KDP submission are excluded.

Start with the smallest revealing case

For the search phrase “how to make an EPUB,” the conclusion is to close each step with an inspected result rather than a filled form. The result is accepted only when the record establishes this outcome: complete a two-chapter sample with visible evidence at every one of six steps.

Begin here: prepare two short chapters and an empty six-row checklist. If work identity remains blank, 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.