Scrivener to EPUB: three ways to get a clean ebook

A clean ebook starts with a clear manuscript structure. Before changing software, check what is actually wrong: missing chapter breaks, inconsistent spacing and duplicated headings usually need different fixes. This guide offers three routes from a Scrivener project to EPUB. You can compile directly, use Calibre for conversion and inspection, or hand a compiled DOCX to Mythwrite for further work and EPUB export. Choose one route for a sample chapter before processing the whole novel.

Keep a backup of the Scrivener project and save each test output with a recognisable name. Include the date and route, such as 'harbour-test-compile'. Use a sample containing a chapter opening, two scenes, italics, a link and any unusual material in your book. A route that handles an ordinary paragraph but loses your letters or scene separators has not yet passed the test.

Prepare the manuscript once

Inspect the order of the sections you intend to publish. Remove scratch material from the intended output and check whether front matter belongs in the file. Give chapter headings a consistent structure. Avoid making a heading look correct by adding repeated spaces or blank paragraphs: those choices make it harder to distinguish content from presentation when you export.

List the elements you expect to survive: italics, emphasis, scene separators, chapter titles, images and links. Add a note about how each should behave. For example, a letter might need a distinct paragraph style but should still be readable when the reader increases the text size. That short checklist gives you something measurable to inspect after every conversion.

Route one: Scrivener Compile

Scrivener can compile a project to an ebook. Literature & Latte's guide begins with File > Compile, then choosing the EPUB ebook option in Compile For and the Ebook format in the sidebar. Wording can vary with the installed version. Start with that built-in format before attempting a custom one, and check the current manual for your platform if the dialogue differs.

Review the included sections and assign appropriate section layouts. Section types describe the role of a piece of the manuscript; layouts determine how those pieces appear in the compiled output. A chapter heading and a scene body need different treatment. If the first test produces a title twice, look for a heading supplied both by the layout and by text already in the manuscript.

Compile the sample and inspect its chapter starts, separators and navigation. If every scene begins a new chapter, revisit the assignment of section layouts before editing the exported file. Save the settings that produce the intended result. This route suits a manuscript that you want to continue maintaining in Scrivener, because you can regenerate output from the same project after corrections.

Route two: Calibre conversion and inspection

Calibre's official manual describes adding a book, choosing Convert and selecting an output format. It supports conversion to EPUB and provides an Edit book tool for further work on EPUB files. This route is useful when you want a separate conversion stage and are willing to inspect its results carefully. Conversion should not be treated as an automatic repair for unclear chapter structure.

Compile a clean Word document from Scrivener, then add the resulting DOCX to Calibre. Open Convert books and select EPUB as the output. Check the title and author metadata before converting. Begin with a small number of deliberate settings changes. If you alter spacing, chapter detection and font treatment simultaneously, it becomes difficult to tell which setting caused a new problem.

Read the output and inspect the contents list. Calibre documents structure detection and table-of-contents controls; consult those sections if headings are missing or ordinary paragraphs become navigation entries. Where possible, correct the source headings and convert again. Use Edit book for a specific problem that you understand, and keep a note of any manual changes so that a later conversion does not silently discard them.

Route three: DOCX into Mythwrite

Mythwrite imports DOCX and provides publish-ready EPUB export on its Collaborator tier. The hand-off starts with Scrivener Compile to Word, not with uploading the native Scrivener project. Keep the original project and compiled document. This route is worth testing if you intend to continue revising in Mythwrite or want drafting and publishing tasks within that workspace.

Compile a representative chapter to DOCX. Check that the document itself contains the expected headings and scene boundaries, then use Mythwrite's import flow to bring it into a project. Review the imported outline and read through the text before making further changes. Compare chapter order, paragraph breaks and emphasis with the source document. Do not assume that a successful upload proves every structural choice survived.

Once the imported structure is correct, use the publishing workflow to choose the book's presentation and export an EPUB. Inspect that file separately from the editor view. If you continue revising in Mythwrite, decide which copy is now your working manuscript and label the older files accordingly. Keeping two active versions without a clear hand-over makes it easy to publish an outdated chapter.

Check the ebook as a reader

Open the EPUB in a reading application and move through it using the contents navigation as well as ordinary page turns. Increase the text size and try a narrow display. Look at the longest heading, a paragraph with italics, the first paragraph after a scene break and any image caption. The goal is readable text across different viewing choices, rather than preserving the exact line endings from your drafting screen.

Follow every link you intend readers to use. Check the title and author, the beginning and end of the book, and the transition from front matter into the first chapter. Make a short correction list with the location and observed problem. Fix a repeated problem at its source when possible. Correcting fifteen chapter openings individually can hide the fact that one shared setting needs attention.

Keep the route reproducible

Record the application version, source filename, export settings and any manual repairs beside the final EPUB. After the last editorial change, regenerate the file and repeat the sample checks. Make sure the output you inspect is the output you intend to upload, rather than an earlier file with a similar name.

Choose direct Compile when it produces the structure you need with manageable settings. Choose Calibre when a separate conversion and inspection stage suits your process. Try Mythwrite when you want to bring the manuscript into its writing and publishing workflow. None of these routes removes the final reading check. A repeatable method and a carefully inspected file matter more than how many programmes the manuscript passed through.