Converting a scenario script to EPUB does not mean placing every scene code in the reader’s table of contents. Keep SC01 through SC20 as production identifiers, group those scenes into a smaller set of reader-facing chapters, and reserve page breaks for meaningful transitions. That preserves traceable scene order without turning navigation into a list of internal labels.
The example here uses twenty scenes, five chapter headings, and four intended page-break points. It does not attempt to judge the writing or rearrange the story automatically.
Add chapter and break columns to the scene list
Create a small table with four fields: scene code, scene name, chapter, and page-break decision. SC01 through SC04 might belong to Chapter One, followed by SC05 through SC08 in Chapter Two. A production label such as “Station Exterior—Night” can remain useful to the writer while the chapter receives a title meaningful to the reader.
Do not make every screenplay page boundary an EPUB page break. Reflowable books adapt to different screen sizes, so the original paper pagination has little value. Mark only chapter openings, deliberate interludes, or another structural pause the reader should feel.
Put the script and map side by side
Open a two-column layout in Rune Studio. Place the script in the left pane and the scene map, character sheet, or timeline in the right. Files open from the project tree and tabs can be dragged between panes. If the script and map contain the same SC codes in the same order, those codes can also serve as custom markers for linked scrolling.
A checked setup used two panes, two open tabs, 17 pt body text, and 14 pt interface text. That demonstrates a practical editing arrangement. It does not imply automatic scene analysis or collaborative cloud editing.
Collapse twenty scenes into five navigable chapters
Insert a chapter heading before the first scene in each group. Keep scene headings below that level. The table of contents should expose the five chapter destinations, while scene codes remain available in the manuscript for searching and revision.
Work through the map one group at a time. Verify that every scene appears once and that no code moves to another chapter by accident. If story order must change, make that editorial decision in the authoritative script rather than patching the order only during EPUB export.
Use explicit page-break markup at the four chosen transitions. Preview the result and remove breaks that produce an isolated line or an unnecessarily empty screen. The goal is structural pacing, not imitation of screenplay pagination.
Map the script into EPUB reading order
In the EPUB wizard, enter the title, author, language, and writing direction. Choose the script file, inspect the generated chapter sequence, and decide which chapter headings belong in navigation. On the final screen, read the order as a reader would: front matter, Chapter One through Chapter Five, then any closing matter.
In a local rebuild check, a first and second export each contained seven reading-order items and both passed package inspection. One controlled source change produced a different second EPUB while preserving the structure. This supports the rebuild path for the sample; it does not establish retailer acceptance.
Three failures to catch before export
The first is a table of contents crowded with internal scene labels. Solve it by keeping SC codes in the source and exposing chapter titles in navigation. The second is excessive page breaking inherited from a paper script. Solve it by keeping only meaningful section boundaries. The third is correcting order in the generated package while leaving the script unchanged. Solve it in the source and regenerate.
Rune Studio’s role is to keep manuscript, reference files, preview, and EPUB output in one Mac workspace. It does not score scenes or resolve narrative structure for you. Begin with SC01 through SC04, create one chapter heading and one deliberate break, and prove that miniature path before processing all twenty scenes. The current feature set is described on the Rune Studio product page.
Place breaks according to reading, not screenplay pages
A scene code can remain searchable without becoming a navigation destination. Before marking a page break, read the exchange around it. A break in the middle of a reply or continuous action can feel arbitrary in an ebook even when it matched a printed script page. Prefer changes of location, time, viewpoint, or deliberate dramatic pause.
Keep a scene-to-chapter map with the source so later revisions can still trace Chapter Three back to SC09 through SC12. Reader navigation and production traceability can coexist; they do not need the same labels.