EPUB page order is established by more than numbered filenames. The editor chapter list, OPF spine, and navigation sequence must agree after any reorder.
When working on EPUB page order, consider a six-chapter handbook moving a supplement directly after chapter three. The task is complete only when editor chapter order and placement of unlisted appendices can both be confirmed after the saved output is reopened. An export message by itself does not answer the search question.
Decide what success means for this book
For this example—a six-chapter handbook moving a supplement directly after chapter three—the first decision is whether editor chapter order has a known starting value. The final decision is whether placement of unlisted appendices survives export and reopening. Keeping those two moments separate prevents a temporary editor display from becoming the handoff criterion.
Preserve the received manuscript, edit a working duplicate, and write the EPUB separately. With EPUB page order as the goal, those three files keep the source, intentional edits, and packaged book distinct.
The direction is one-way: preserved source, editable duplicate, separately written EPUB, then a reopened EPUB. The method does not recreate the manuscript from the EPUB or treat the package as an editing source.
Build a representative test case
Build the example around a six-chapter handbook moving a supplement directly after chapter three. Keep the part that could genuinely fail. If the risk concerns OPF itemref sequence, include the exact chapter, character, path, or label that creates that risk. Removing it for a cleaner demo would produce an easy pass with no value for the real book.
Scrutinize four independent facts
- Editor chapter order: while you record the starting order, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from OPF itemref sequence.
- OPF itemref sequence: while you move one chapter at a time, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from nav.xhtml entry order.
- Nav.xhtml entry order: while you review table-of-contents inclusion, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from placement of unlisted appendices.
- Placement of unlisted appendices: while you export under a new versioned filename, write down the expected state and what the book actually shows. Treat this as its own decision; do not infer it from editor chapter order.
Complete the operation in order
- Record the starting order. Before moving on, confirm editor chapter order; if it differs from the expected state, correct that step rather than compensating later.
- Move one chapter at a time. Before moving on, confirm OPF itemref sequence; if it differs from the expected state, correct that step rather than compensating later.
- Review table-of-contents inclusion. Before moving on, confirm nav.xhtml entry order; if it differs from the expected state, correct that step rather than compensating later.
- Export under a new versioned filename. Before moving on, confirm placement of unlisted appendices; if it differs from the expected state, correct that step rather than compensating later.
- Compare spine, navigation, and chapter openings. Before moving on, confirm editor chapter order; if it differs from the expected state, correct that step rather than compensating later.
Walk the example from source to handoff
During step 1, record the starting order. In the case of a six-chapter handbook moving a supplement directly after chapter three, scrutinize editor chapter order before changing anything else. This prevents renaming files without changing reading order. If the observation is unknown, repeat that step with the working duplicate instead of editing the master manuscript.
During step 2, move one chapter at a time. In the case of a six-chapter handbook moving a supplement directly after chapter three, scrutinize OPF itemref sequence before changing anything else. This prevents reviewing an older EPUB after reordering. If the observation is unknown, repeat that step with the working duplicate instead of editing the master manuscript.
During step 3, review table-of-contents inclusion. In the case of a six-chapter handbook moving a supplement directly after chapter three, scrutinize nav.xhtml entry order before changing anything else. This prevents removing an unlisted chapter from the spine. If the observation is unknown, repeat that step with the working duplicate instead of editing the master manuscript.
During step 4, export under a new versioned filename. In the case of a six-chapter handbook moving a supplement directly after chapter three, scrutinize placement of unlisted appendices before changing anything else. This prevents renaming files without changing reading order. If the observation is unknown, repeat that step with the working duplicate instead of editing the master manuscript.
During step 5, compare spine, navigation, and chapter openings. In the case of a six-chapter handbook moving a supplement directly after chapter three, scrutinize editor chapter order before changing anything else. This prevents reviewing an older EPUB after reordering. If the observation is unknown, repeat that step with the working duplicate instead of editing the master manuscript.
What the example showed
The trial produced this observation: The test book exported 5 chapters with writingMode=horizontal and version 1.1. Inspection returned spine=9, images=1, missing=0, nav=true, NCX=true, and valid=true.
That value belongs to the files and settings used for this example. It supports the documented sequence; it does not turn EPUB page order into a promise for every manuscript, reading system, or retailer.
The untested boundary is equally important: valid=true is a local package reading, not retailer acceptance or identical rendering in every reader. Outside this scope: The check is local EPUB package inspection, not retailer acceptance or identical rendering in every device. Add retailer preview, device testing, accessibility review, or rights clearance when the book requires those decisions.
The W3C EPUB 3.3 specification defines the EPUB navigation document as a required publication component.
Recover from the three likely mistakes
- Renaming files without changing reading order: go back to “record the starting order,” then re-examine editor chapter order. Change only the responsible input so the next comparison remains meaningful.
- Reviewing an older EPUB after reordering: go back to “move one chapter at a time,” then re-examine OPF itemref sequence. Change only the responsible input so the next comparison remains meaningful.
- Removing an unlisted chapter from the spine: go back to “review table-of-contents inclusion,” then re-examine nav.xhtml entry order. Change only the responsible input so the next comparison remains meaningful.
Decide whether Rune Studio fits
Rune Studio is a candidate when an editor wants manuscript work and EPUB preparation in one Mac application for a project involving a six-chapter handbook moving a supplement directly after chapter three. Product documentation describes available functions; the observation above documents only this example.
See the product on the Rune Studio website. Keep the adoption boundary explicit: the check is local EPUB package inspection, not retailer acceptance or identical rendering in every device.
Take the next step
Start with this action: record the starting order. Then follow the remaining steps until placement of unlisted appendices can be reproduced from the reopened publication. That is the practical finish line when working on EPUB page order.