For epub new page, use a semantic page-break operation at the chapter boundary instead of pushing the next heading down with blank lines. Empty paragraphs change with font size and reader layout. A supported break carries editorial intent into the EPUB workflow. The fresh test covers three synthetic chapters, two correctly placed New Page markers, the resulting EPUB resources, and one Kindle Previewer 3 Tablet display. It does not claim identical pagination in every reading system.
Decide whether the boundary really needs a page break
A new chapter is a strong candidate. A major change of narrator or the start of an appendix may be another. A brief pause inside a scene usually needs spacing rather than a forced new page. Write the reason for the break before inserting anything.
This distinction prevents a manuscript from accumulating dozens of breaks that interrupt reading. It also tells a reviewer what to expect: the next chapter should begin separately, while the preceding sentence and heading order should remain unchanged.
Blank lines are not a reliable substitute. On a small screen they can create an almost empty page; with a different font size the next heading may still share the page. The layout result belongs to the reader, while the semantic boundary belongs to the source.
Insert one supported marker and inspect its context
The controlled experiment used three synthetic chapters. Rune inserted one New Page marker immediately before the Chapter Two H1 on line 5 and another immediately before the Chapter Three H1 on line 9. The source contained exactly two 《《｜Page Break｜》》 markers after insertion, while the Chapter One H1 remained on line 1.
Do not apply the operation repeatedly without checking the neighborhood. Search for an existing break, remove accidental empty paragraphs, and confirm that the marker sits between the final paragraph of one chapter and the heading of the next. A duplicate break can become an unwanted blank page.
The scope is Rune-supported input, not a claim that all CommonMark processors interpret the same notation. If the manuscript will be sent through another converter, test that converter independently or keep a source variant appropriate to it.
After saving, reopen the source. Read the last paragraph before the boundary and the first paragraph after it. A correct marker in the wrong location is still an editorial error.
Read the three-chapter package and one reader result
The generated EPUB contained three chapter resources: p001.xhtml, p002.xhtml, and p003.xhtml. Each contained the expected Chapter One, Chapter Two, or Chapter Three H1. This export did not preserve the source operation as a CSS break-before, CSS page-break-before, epub:type="pagebreak", or mbp:pagebreak token; all four token counts were zero.
For this Rune export, the two source markers therefore map to a split from one source file into three chapter XHTML resources. That mapping is stronger and more precise than saying that a literal marker or CSS declaration survives in the final package.
The fresh EPUB was also opened in Kindle Previewer 3 using Tablet mode. The all-pages overview showed Chapter One, Chapter Two, and Chapter Three on separate page thumbnails. Selecting Chapter Two moved to location 5/10, where its heading and body began at the top of a separate page. No extra blank page was observed between the three chapters.
This is an observed result for one synthetic horizontal EPUB and one Previewer mode. Reflowable pagination can still change with screen dimensions, fonts, margins, writing direction, and reader software. Record another result for each distribution reader instead of converting this one observation into a universal guarantee.
Recover from the two common mistakes
The first mistake is replacing a semantic break with a stack of empty lines. Remove the spacing, restore one meaningful boundary, and export a new file. Compare the same two chapter headings rather than reviewing the entire book without a target.
The second mistake is inserting the operation twice. Return to the source copy, search around the chapter heading, and leave a single boundary. Avoid editing generated XHTML first, because the next export could discard that correction.
When chapter order is wrong, fix source selection or order rather than page-break markup. When a navigation destination is missing, inspect the packaged reference. Each symptom has a narrower rollback point.
Keep the approved manuscript separate from the test copy. Record the source hash, inserted boundary, export hash, and package inspection. This makes a later correction reproducible.
Close the structural check and schedule visual review
Keep a boundary register for the full manuscript. It should name the preceding chapter, the following chapter, the editorial reason for separation, and whether a source operation is present. The number of breaks need not equal the number of chapters: the opening chapter has no preceding transition, and short subsections may be intended to continue on the same page.
If the book later changes from horizontal to vertical writing, do not inherit this result without another fixture. Writing direction and page progression can affect reader behavior. Repeat a small three-chapter export under the new direction, inspect the structure, and then perform the visual review in that context.
The structural decision for this semantic page-breaking test is complete when the source contains the two intended break operations, the surrounding text is intact, and three chapter XHTML resources contain the three expected H1 headings. The fresh three-chapter test meets those conditions.
Visual evidence now exists for Kindle Previewer 3 Tablet mode at its saved default condition, including Chapter Two at location 5/10. Production approval still needs the actual distribution readers and at least a default and larger font size. Inspect the final lines of each preceding chapter, the following heading, and any intervening blank page. Record each reader separately.
Rune Studio is suitable when an editor wants to add a supported page boundary and examine the resulting EPUB structure in one Mac workflow. Fine-grained device-specific pagination still requires reader testing. Begin with two transitions in a three-chapter copy, then require two source markers, three expected XHTML headings, and an explicitly named reader observation before repeating the operation across the book.