The Scrivener + Vellum Pipeline: From Draft to Published Book

You finished your novel. You revised it in Scrivener, scene by scene, watching the word count climb and the Binder fill with color-coded chapters and carefully written synopses. The manuscript is good. You're proud of it. Now you need to turn it into a book.

Not a manuscript. A book. The kind of thing a reader downloads on their Kindle and never thinks about the formatting because the formatting doesn't give them a reason to. Clean chapter headings. Proper scene breaks. Professional typography. An ebook that looks like it came from a publishing house and a paperback that doesn't scream "I formatted this in Word at 2 a.m."

If you're an indie author who writes in Scrivener and formats in Vellum, you already know these are two of the best tools available for their respective jobs. Scrivener is where you draft, organize, and revise. Vellum is where the manuscript becomes a book. The problem is the space between them. The handoff from Scrivener to Vellum is where things go sideways if you don't know what to expect, and most of the advice available online amounts to "compile to .docx and import into Vellum" without addressing the dozen things that can go wrong along the way.

This article covers the full pipeline, from finished Scrivener draft to published book on retailer shelves, with particular attention to the handoff points where authors lose time. If you've done this before and it went smoothly on the first try, you're either lucky or better at Compile than most of us. If you've done it before and spent an afternoon re-compiling because your scene breaks turned into ornamental flourishes or your chapter headings vanished, this is for you.

The Full Pipeline at a Glance

Before diving into specifics, here's the whole workflow so you can see where each piece fits. You write and revise in Scrivener. At some point you send the manuscript to an editor, which usually means compiling to a Word document. The editor sends it back with changes. You incorporate those changes, either back in Scrivener or directly in the Word file. Then you compile from Scrivener (or import the edited Word file) into Vellum for formatting. Vellum produces your ebook files and print-ready PDFs. You upload those files to retailers and hit publish.

Each of those steps is straightforward in isolation. The complexity lives in the transitions. Scrivener to Word for your editor. Edited Word back to Scrivener (or not). Scrivener to Vellum. Vellum to retailers. Every transition involves decisions about what to keep, what to strip, and what to rebuild. Understanding those decisions is what separates a thirty-minute production process from a three-hour one.

Preparing Your Scrivener Project for the Handoff

The quality of your Vellum import depends almost entirely on the quality of your Compile output, and the quality of your Compile output depends on how your Scrivener project is organized. This isn't about making your Binder pretty. It's about making it machine-readable.

Vellum needs to know where your chapters begin. That means your Binder should have a clear, consistent structure: chapter folders containing scene documents. If you've been working with a flat list of documents and no folder hierarchy, Compile can still produce chapter breaks, but you'll need to be more deliberate about your Section Types and Section Layouts. The cleaner your Binder structure, the fewer decisions you need to make at Compile time.

Scene breaks matter more than most authors realize at this stage. Within Scrivener, separate scene documents in the Binder are implicitly separate scenes. When Compile stitches them together into a single chapter, it needs to place a separator between them. If you're compiling for Vellum, that separator should be a single line containing three hash marks (###), three asterisks (***), or simply an empty line. Vellum interprets these as scene breaks and converts them to ornamental breaks or whitespace in the final book.

Here's where authors run into their first common problem: extra blank lines between paragraphs. If you've been hitting Enter twice between paragraphs while drafting, Scrivener may pass those blank lines through to the compiled output. Vellum interprets any empty line as a scene break. If your compiled .docx has blank lines between every paragraph, Vellum will insert ornamental breaks throughout your entire chapter. The fix is in Scrivener before you compile: use Edit, then Text Tidying, then Remove Empty Lines Between Paragraphs. This strips the extra whitespace from your manuscript while preserving the intentional scene breaks between separate Binder documents.

Front matter and back matter are another decision point. Vellum handles front and back matter extremely well and will generate a title page automatically from the metadata you enter. For most novels, the simplest approach is to let Vellum handle the title page, copyright page, and dedication rather than trying to compile those elements from Scrivener. If you do want to include a custom dedication or epigraph from Scrivener, Literature & Latte's Vellum Export format supports this, but it requires creating specific paragraph styles in Scrivener (Dedication, Epigraph, Attribution) that Vellum recognizes on import. Unless you have a specific reason to manage front matter in Scrivener, let Vellum do it.

If you're setting up your Binder structure from scratch, our guide to structuring your novel in Scrivener covers the organizational decisions that affect everything downstream, including Compile.

Compile Settings That Matter for Vellum

Scrivener 3 ships with a built-in Compile format called "Vellum Export." Use it. This isn't a suggestion born of laziness. Literature & Latte and Vellum's developers (the two Brads at 180g, both former Pixar engineers) coordinated on this format specifically to make the handoff as clean as possible. The Vellum Export format configures Section Layouts, separators, and formatting options to produce a .docx that Vellum can parse correctly.

To use it: go to File, then Compile. In the Compile sheet, choose "Vellum Export" from the format list on the left. If you don't see it, update Scrivener to the latest version of Scrivener 3, as this format was added in version 3.0.3. Set your output to Microsoft Word (.docx). Assign your Section Types to the appropriate Section Layouts. For most novels with a standard chapter-folder-containing-scenes structure, the defaults will work. Click Compile.

The Section Types and Section Layouts system is where Scrivener's Compile earns its reputation for complexity. The short version: Section Types describe what each item in your Binder is (a chapter heading, a scene, a front matter page). Section Layouts describe how those items should appear in the compiled output (with a title on a new page, with a scene separator, with no special formatting). The Vellum Export format comes with Section Layouts designed for chapters and scenes. Your job is to make sure each folder and document in your Binder is assigned the correct Section Type so Compile knows which Layout to apply.

For most novels, the assignment is simple. Chapter folders get a Section Type that maps to a "New Page" layout with a title. Scene documents get a Section Type that maps to a "Scene" layout with a separator between them. If you have front matter documents, assign them a Section Type that maps to "New Page" as well. If Scrivener's default assignment (based on Binder structure) matches your needs, you may not need to change anything. Compile it, open the .docx in Word or any word processor, and verify: each chapter should start on a new page, chapter titles should be present, and scene breaks should be marked with a separator character.

One thing the Vellum Export format handles that many authors don't realize: it preserves Scrivener's built-in styles. If you've used the Block Quote, Verse, or Attribution styles in Scrivener, the Vellum Export format passes those through in a way that Vellum can detect and format appropriately. Bold and italics carry over reliably. Centered text carries over. What does not carry over is any complex custom formatting that doesn't map to standard Word styles. If you've been using custom fonts or unusual paragraph spacing in Scrivener's editor, Compile may strip or override those, which is actually what you want. Vellum controls the final look of your book. Your job in Scrivener is to deliver clean, semantically correct text, not a visually finished product.

What Happens When Vellum Opens Your File

Open Vellum. Choose File, then Import Word File, and select the .docx you compiled from Scrivener. What happens next takes about three seconds and determines whether you spend five minutes or fifty minutes in Vellum.

Vellum analyzes the document, looking for chapter boundaries. It detects chapters primarily through Heading 1 styles applied to chapter titles, which the Vellum Export Compile format applies automatically. It also recognizes certain text patterns: a line that says "Chapter One" or "Chapter 1" or even a bold, centered line followed by a page break will usually register as a chapter boundary. Each detected chapter becomes a separate element in Vellum's Navigator (its version of a table of contents on the left side of the screen).

Scene breaks within chapters are detected based on separator characters or empty lines. If your Compile inserted ### between scenes, Vellum converts those into scene breaks. If your Compile inserted blank lines, Vellum interprets those as scene breaks too. The distinction between a scene break (whitespace) and an ornamental break (a decorative symbol) is a styling decision you make later in Vellum.

Immediately after import, check three things. First, count the chapters in Vellum's Navigator and compare to your Scrivener project. If the numbers don't match, Vellum either split a chapter it shouldn't have (usually because of a stray heading style or extra blank lines) or merged chapters that should be separate (usually because a chapter title wasn't detected). Both are fixable in Vellum: you can merge elements by selecting them and using Chapter, then Merge Selected Chapters, or split an element by placing your cursor where the break should be and using Chapter, then Split Chapter at Cursor.

Second, open a few chapters and check scene breaks. Make sure the breaks appear where you intended and that there aren't extras between every paragraph. If you see ornamental breaks everywhere, the blank-lines issue from your Scrivener source is the likely culprit. You can fix it in Vellum by deleting the extra breaks, but it's faster to fix the source, recompile, and reimport.

Third, spot-check formatting. Italics should be intact. Bold should be intact. Block quotes and verse, if you used Scrivener's built-in styles, should be recognized. If something looks off, it's almost always traceable to the Compile output rather than to Vellum's import.

Vellum 4.1, released in March 2026, includes improvements to chapter detection on import and expanded support for supplemental Word styles. If you're running an older version, updating may solve import problems you've been working around.

Formatting in Vellum

Once your manuscript is imported cleanly, the formatting phase in Vellum is genuinely enjoyable, and that's not something you hear authors say about many production steps.

Vellum works on a template system. You choose a Style from a library of professionally designed options. The Style controls everything: chapter heading appearance, body text typography, drop caps, ornamental breaks, paragraph spacing, and more. You can preview how your book will look on a Kindle, an iPad, an iPhone, and in print, all from within Vellum. The preview is live. Change a Style and the entire book updates instantly.

The single most important piece of advice for authors new to Vellum is this: trust the defaults. Vellum's Styles were designed by people who understand typography and book design. The temptation to customize everything is strong, especially if you're used to controlling every aspect of your manuscript in Scrivener. Resist it. Choose a Style that fits your genre (there are options that lean toward literary fiction, romance, thriller, fantasy, nonfiction, and more), verify it looks good in the preview, and move on. The beauty of Vellum is that it makes decisions you'd otherwise need a designer to make, and it makes them well.

Where Vellum gives you meaningful choices: chapter heading presentation (you can display "Chapter One," "Chapter 1," or just "1," with or without a custom title), ornamental break style (the symbols or whitespace between scenes), drop caps at the start of each chapter, and font selection for ebook and print. With Vellum 4.0's expanded heading controls, you can now fine-tune spacing, alignment, and scale for headings without overriding the entire Style.

What Vellum doesn't do: it doesn't give you pixel-level control over layout. You can't write custom CSS. You can't adjust individual page margins. You can't create layouts that rival what a professional designer would build in InDesign. For the vast majority of novels, this doesn't matter. Vellum's output is indistinguishable from traditionally published books, and multiple indie authors have said exactly that. Where Vellum's constraints become limiting is in complex nonfiction with extensive tables, callout boxes, or multiple heading levels. For novels, those constraints rarely apply.

Output and Distribution

When your book looks right in Vellum's preview, you generate your output files. Click Generate in the upper right corner. Vellum produces ebook files (EPUB for most retailers, plus a Kindle-specific format for Amazon) and print-ready PDFs if you have Vellum Press.

For ebooks, Vellum generates separate files optimized for each retailer: Amazon Kindle, Apple Books, Kobo, Google Play, Barnes & Noble, and a generic EPUB. Each file includes retailer-specific formatting and store links in your back matter, so the "Buy my next book" link points to the right store depending on where the reader bought this one. This is one of Vellum's most practical features and one that saves authors significant time compared to manually building separate editions.

For print, Vellum generates a PDF at the trim size you've selected. Common trim sizes for fiction include 5" x 8", 5.25" x 8", and 5.5" x 8.5". Vellum handles margins, gutters, headers, footers, page numbers, and orphan/widow control automatically. Print setup is also where you choose your body font and verify that the page count works for your distribution channel's requirements.

From Vellum's output, you upload directly to retailers. Amazon KDP accepts the Kindle file for ebook and the PDF for paperback. Apple Books has a direct integration with Vellum, so you can publish to Apple without leaving the app. For Kobo, Google Play, and Barnes & Noble, you upload the appropriate EPUB or use an aggregator. For wide print distribution through IngramSpark, you upload the print PDF and your cover file (which Vellum doesn't create, so you'll need a separately designed cover formatted to IngramSpark's specifications).

The pipeline from "Generate" in Vellum to "live on retailers" can happen in the same afternoon. For authors who've refined their settings, the Vellum-to-published step is the fastest part of the entire process.

Where Editing Fits In

The pipeline described above assumes a finished, edited manuscript. In practice, editing is where the pipeline gets complicated, because it introduces an additional round trip.

The standard flow is: draft in Scrivener, compile to Word for your editor, incorporate edits, then compile for Vellum. If you want the full breakdown of the Scrivener-to-Word-to-Scrivener roundtrip for working with editors, our detailed guide covers every method and their trade-offs. The short version is that getting an edited Word document back into Scrivener with your Binder structure intact is one of the most persistent frustrations in the Scrivener ecosystem, and authors handle it in different ways.

Some authors return to Scrivener after editing. They manually transfer edits back into their Scrivener project, chapter by chapter, preserving their Binder organization, synopses, and metadata. Then they compile from Scrivener for Vellum. This approach maintains Scrivener as the canonical version of the manuscript but costs time, especially after heavy editing.

Other authors skip the return to Scrivener entirely. Once the edited Word file is final, they import it directly into Vellum. This is faster and avoids the roundtrip problem, but it means the Scrivener project is now outdated. The canonical version of the manuscript lives in Vellum, and any future revisions happen there or in the Word file. For authors who treat the editing phase as the end of the writing process and the Vellum phase as pure production, this is a reasonable trade-off.

Neither approach is wrong. The choice depends on whether you want Scrivener to remain the source of truth for your manuscript or whether you're comfortable letting the manuscript's home migrate downstream as it moves through production.

A Bridge for Authors Coming From Word

There's a third scenario that deserves attention: the author whose manuscript lives in Word or Google Docs and who wants to enter the Scrivener-to-Vellum pipeline for the first time.

Maybe you drafted in Word because that's what you were comfortable with. Maybe your editor returned a Word file and you decided not to wrestle it back into Scrivener. Maybe you've heard that Vellum imports work more cleanly from well-structured Scrivener projects than from raw Word documents, and you'd like to take advantage of that.

You can import a Word document directly into Vellum, and for many manuscripts this works fine. Vellum is remarkably good at detecting chapter boundaries from heading styles. But if your Word document doesn't use consistent heading styles, if your chapters are separated by manual page breaks rather than styled headings, or if your manuscript has accumulated formatting artifacts from months of editing, the import may produce chapters that are split incorrectly, scene breaks that are missed, or formatting that needs cleanup.

This is where BinderCraft fits into the pipeline. You upload your .docx manuscript, and within about seven minutes, BinderCraft produces a structured Scrivener 3 project with your chapters organized in the Binder, along with a story bible built from your actual text: character profiles, chapter synopses, beat sheet, relationship arcs, and more. From that organized Scrivener project, you can Compile using the Vellum Export format and get a clean import on the first try, because the Binder structure maps directly to the chapter breaks Vellum expects. Your manuscript is processed in memory and deleted immediately. BinderCraft never stores, reads, or trains on your work.

The same applies for authors who skipped the return-to-Scrivener step after editing. If your edited manuscript is a Word file and you want to bring it back into Scrivener before compiling for Vellum, uploading it to BinderCraft gives you a fresh project built from the current state of the manuscript, with updated synopses and story bible material reflecting the edits your editor made. Then you Compile from that clean project and import into Vellum.

It costs $9.99 per manuscript, no subscription. If you drafted in Word and you're wondering whether the switch to Scrivener is worth it for this pipeline, our comparison covers the real trade-offs.

Try BinderCraft at bindercraft.net

A Note for Windows Users

Everything in this article assumes you're on a Mac, because Vellum requires macOS. There's no Windows version and the developers have been clear that building one isn't on their roadmap.

If you're on Windows and you want a similar pipeline, Atticus is the most direct alternative. It's a cross-platform tool (browser-based, works on any operating system) that handles both writing and formatting, priced at $147 for a one-time lifetime license that includes ebook and print. Atticus produces professional output, and its formatting quality has improved steadily since its 2021 launch. It's not identical to Vellum. Vellum's output is still slightly more polished for fiction, and its interface is faster and more stable as a native Mac app. But for Windows users, Atticus is a genuine option rather than a compromise, and it imports from Scrivener's compiled .docx output the same way Vellum does.

Draft2Digital also offers free built-in formatting tools, and Reedsy's Book Editor is another free option, though neither gives you the level of control over design that Vellum or Atticus provides. For authors who want maximum design quality on Windows, Atticus is currently the answer.

Making It Repeatable

If you publish multiple books a year, the Scrivener-to-Vellum pipeline needs to work reliably every time without re-learning the settings. Here's how to make it a process rather than an adventure.

In Scrivener, save your Compile format. Once you've configured the Vellum Export format with your preferred Section Type assignments and any customizations, that format persists across all your Scrivener projects. Open a new novel, assign the same Section Types, and Compile produces identical output. If you've customized the format (which you shouldn't need to for most novels using the built-in Vellum Export), save your customized version with a descriptive name so it appears in the format list for every project.

In Vellum, save your Style configuration. Once you've chosen a Style and customized it (heading presentation, ornamental breaks, fonts, drop caps), save it as a custom Style. For your next book, create a new Vellum project, import the manuscript, and apply your saved Style. The entire book formats itself in seconds. Some authors maintain one saved Style for a series and a different one for a standalone, keeping the look consistent within a series while allowing variety between projects.

Build a pre-flight checklist for the handoff. Before compiling, run Edit, Text Tidying, Remove Empty Lines Between Paragraphs. Verify your Section Type assignments. Check that front matter is set up correctly (or excluded, if you're handling it in Vellum). After importing into Vellum, check chapter count, spot-check scene breaks, and verify formatting. After generating output, preview the ebook on at least two simulated devices and page through the print PDF looking for widows, orphans, and chapter-opening pages that look sparse.

For authors who've done this a few times, the entire Compile-to-Vellum-to-published process takes under an hour. The first time takes longer because you're making decisions. Every subsequent time, you're executing a process you've already designed.

The Pipeline Is the Product

The Scrivener-to-Vellum pipeline isn't the only way to self-publish, but it's one of the most efficient for authors who care about quality and want to own their production workflow. Scrivener gives you organizational power that no other writing tool matches. Vellum gives you formatting quality that no other production tool matches for the same level of effort. The gap between them — the Compile-to-import handoff — is real but manageable once you understand what each tool expects.

The tools are excellent. The documentation for each tool individually is excellent. What's been missing is guidance for the space between them — the decisions you make when the manuscript leaves one tool and enters another. If this article shortens the time between your finished draft and your published book, it's done its job.

Your readers are waiting. Your book is ready. The pipeline is there to carry it from your Scrivener Binder to their Kindle. Make the handoff clean, and let Vellum make it beautiful.