Bringing a Scrivener project out
Take a snapshot, compile to a plain manuscript, and leave the research folder where it is. What comes next is not technical: a structural read, a revision, a proofread, a cover. Scrivener has done its job — it is a writing environment, and it never claimed to be an editor.
Coming out of the binder
Two minutes of preparation prevents the only real risk in this process.
- Snapshot every document you're moving. Ten seconds, and it removes all downside.
- Compile to plain manuscript DOCX — double-spaced, 12pt, chapters on new pages. Do not customise.
- Leave the research folder in Scrivener. It is not part of the manuscript.
- Note any labels or status flags you rely on; they do not travel.
- Check footnotes in the compiled file. This is the most common thing to verify.
- Structural review before anything else.
- Revise — in Scrivener if you prefer, it is still your writing environment.
- Copy-edit and proofread, in that order.
- Typeset in a formatting tool, not in Compile, unless you already know Compile well.
- Order a printed proof and read it on paper.
A separate free preview: A free outside view of your own pages
A separate editorial preview of one extract; it does not read the whole book or do the specialist job this page describes. Send up to 5,000 words. You get back what the draft appears to be doing to somebody who wasn't there when you wrote it, the strongest thing in it named, the exact place a reader starts to drift, and three revision priorities in order.
A separate editorial preview of one extract; it does not read the whole book or do the specialist job this page describes. An AI-assisted read of your own pages. Not a human edit, not a line edit, and not a scored report.
Snapshot first
Before you export anything, snapshot the documents you are moving. It takes ten seconds and it means the round trip has no downside whatsoever — the binder version is preserved exactly, whatever happens elsewhere.
This is standard practice for anyone who moves manuscripts around, and it removes the only genuine risk in the process.
Compile plain, not pretty
Editors, beta readers and editorial tools all want plain: double-spaced, 12-point, indented paragraphs, chapters starting on new pages.
Scrivener's default manuscript preset does exactly this. Do not tune it. Elaborate Compile presets are for finished output, and you are not at finished output — you are at the beginning of the editorial half.
If you want a beautifully typeset book at the end, that is a job for Vellum (a one-off macOS purchase, around $250 when this was written in 2026) or Atticus ($147, cross-platform), both of which take a clean DOCX and do it in minutes.
What Scrivener has already done for you
More than you may realise. A manuscript held as separate documents in a binder is already structured — chapter boundaries are explicit rather than inferred, and the order is data rather than a guess.
That makes the handoff cleaner than it is from a single long Word file, and it is why the.scriv round trip preserves more than a DOCX does.
It is also why the reverse outline is easy for you: your binder is one already. Read the document titles in order and you have the shape of the book on one screen.
About Your Book Pro
Your Book Pro is a book-writing platform built in Britain. Start with an idea, notes, half a draft, a podcast, or a finished manuscript, and use our purpose-built AI tools for planning, feedback, editing, proofreading, cover designs, and to create print-ready files. Writing is totally free: you can type, upload or speak your book as much as you like, and use only the editing tools you need with Plus, or go unlimited with Pro.
Produce world-class drafts at the fraction of the cost of hiring a human editorial team.
Every account starts with 1,000 welcome credits, and a plain export of your own words is free.
The Scrivener round trip is the flagship:.scriv in,.scriv out. Document structure and order come through intact, and the manuscript goes back into the binder as documents rather than one wall of text. Import diagnostics show what was found before anything is processed.
Then the editorial passes: Detailed Editorial Feedback for the whole-book review, covered by your free welcome credits; the Editing Suite for line, copy and proof in order; Beta Reader in between.
And a plain export of your own words is free forever, on every plan — because an editorial platform that could not give a Scrivener user their project back would be asking them to abandon years of work.
Upload a manuscript written anywhere
Run a whole-book review
Email me my free review linkQuestions people ask
- What should I compile for an editor?
- Plain manuscript DOCX: double-spaced, 12pt, indented paragraphs, chapters on new pages. Scrivener's default preset does it — do not customise it.
- Will I lose my research?
- Only if you delete it. Research stays in Scrivener, which is where it is most useful. It is not part of the manuscript.
- Can I keep working in Scrivener?
- Yes, and most people should. Bring the manuscript across for the editorial passes and take it back to the binder afterwards.
- Should I typeset in Compile?
- Only if you already know Compile well. Vellum and Atticus exist because Compile is hard, and that is not a controversial statement in this industry.