Scrivener Sync: The Roundtrip Problem, Solved

If you read our article on the Scrivener-to-Word-to-Scrivener roundtrip, you already know the problem. You compile your Scrivener project to a .docx for your editor. Your editor spends weeks marking it up with Track Changes. You review and accept the changes, resolve the comments, and save a clean Word file. Then you stare at it, because now you have two versions of your novel. The one in Scrivener, with all your synopses and labels and color-coded scenes and carefully organized Binder, is outdated. The one in Word has the text you need, but it's a flat document with no structure, no metadata, and no way to get back where it came from.

That article walked through the workarounds. The dual-monitor method, where you manually transfer every edit from the Word doc into Scrivener, scene by scene. Copy and paste, chapter by chapter, losing italics along the way. Import and Split, which creates new Binder items and orphans all your metadata from the originals. The embedded links method, which works but requires careful setup and a cooperative editor who doesn't accidentally delete the hidden link markers. And the most common solution of all: abandoning Scrivener for the rest of the project and staying in Word.

We've heard from a lot of authors since publishing that piece. The frustration hasn't changed. It hasn't gotten better. And Scrivener hasn't solved it either.

The Problem Hasn't Gone Away

As recently as August 2025, authors on the Literature & Latte forums were still asking the same question in the same way. One writer working with a copy editor described the exact scenario: she wanted to incorporate the final edited Word version back into Scrivener while maintaining her project's formatting and structure. When she tried copying from Word and using "Paste and Match Style," she got font changes and formatting inconsistencies. When she asked for a better approach, the most upvoted response was essentially: learn the embedded links technique, or accept that at some point Scrivener is a drafting tool and the further refinement of your manuscript just happens somewhere else.

That response isn't wrong. It's realistic. But it's also a concession, and it's the same concession authors have been making for over a decade. The roundtrip between Scrivener and Word is a one-way door by design. Scrivener can flatten your project into Word beautifully. Word cannot unflatten itself back into Scrivener. Not without losing everything that made the Scrivener project worth building in the first place.

Scrivener 3.5 on Mac (updated for macOS Tahoe) and 3.1.6 on Windows (released September 2025) brought refinements and bug fixes, but no new roundtrip or sync capabilities. Import and Split still works the way it always has: it creates new Binder items from headings, giving you text divided into chapters but none of the organizational layer you built around that text. Your synopses, labels, status markers, document notes, compile settings, snapshots, and research folders all stay behind in the old project, orphaned from the updated text.

Literature & Latte has mentioned they're working on an upcoming writing app alongside their current Scrivener maintenance. Whether that app addresses the roundtrip problem remains to be seen. For now, the gap is the same gap it's always been.

What Changed

When we wrote that roundtrip article, the best we could offer was a workaround that sidestepped the roundtrip entirely. Upload your edited .docx to BinderCraft and get a brand new Scrivener project built from the edited manuscript. That approach works. It gives you a fresh project with structure and a story bible generated from your current text. But it means leaving your original project behind, with all the organizational work you put into it.

For some authors, that trade-off made sense. For others, it didn't. If you spent months building your Scrivener project, customizing your labels, writing detailed synopses for every index card, configuring your compile settings, adding document notes to scenes, collecting research materials in the Binder, you don't want a new project. You want your project, with the edited text in it.

That's what Scrivener Sync does.

How It Works

You upload two files. Your edited manuscript (DOCX, EPUB, or TXT, whatever came back from your editor) and your existing Scrivener project (zipped as a .scriv folder). BinderCraft matches each chapter in the edited manuscript to the corresponding document in your Scrivener project and updates the text in place. Your project comes back with the edited content merged in and everything else untouched.

That last part is the important part, so it's worth being specific about what "everything else" means.

Your Binder structure stays exactly as it was. Act folders, chapter documents, scene splits, all in the same hierarchy you built. Your synopses stay on every index card. If you wrote a three-sentence summary of Chapter 12 describing how Elena confronts David about the letter, that summary is still there when you open the synced project. Your labels stay assigned. If you color-coded scenes by POV character, those colors haven't moved. Your status markers stay set. If you marked Chapter 7 as "Revised" and Chapter 14 as "Needs Work," that's how they'll read when you open the project. Your document notes in the Inspector, your compile settings, your snapshots, your research folders, your character sheets, any custom metadata you added, all of it survives.

The only thing that changes is the text of chapters where the edited manuscript differs from your existing project. If a chapter's text hasn't changed, it isn't touched at all.

The result is what the roundtrip was always supposed to feel like. You get back the same project you sent out, just with the edits folded in. As if you'd sat down and carefully typed every change into Scrivener yourself, scene by scene, except it took thirty seconds instead of an entire weekend.

Two Tiers, Because Not Every Edit Is the Same

Scrivener Sync comes in two versions, and the right one depends on what kind of editing your manuscript just went through.

Basic Sync costs $4.99 and takes about thirty seconds. It updates the chapter text in your project and preserves everything else. This is the right choice for copy edits and proofreading passes, where the changes are at the word and sentence level. Your editor fixed your comma splices, caught your misspellings, standardized your dash usage, and cleaned up your dialogue tags. The story itself didn't change. The structure didn't change. Your existing synopses and notes are still accurate. You just need the corrected text back in Scrivener so you can keep working there.

Full Sync costs $14.99 and takes about seven minutes. It does everything Basic Sync does, updating your chapter text in place and preserving your metadata. But it also re-analyzes the edited manuscript and regenerates the story bible content in your project. Character profiles are refreshed to reflect any changes your editor helped you make. Chapter synopses are updated to match the revised text. The beat sheet is remapped. Relationship arcs, conflict analysis, worldbuilding notes, and thematic documentation are all regenerated from the current version of the manuscript.

Full Sync makes sense after a developmental edit or a heavy line edit, where the changes go deeper than grammar. If your editor helped you restructure your second act, deepen a character arc, cut a subplot, or shift the balance between two POV characters, the story bible from before the edit is partially outdated. Full Sync gives you an updated analytical layer alongside the updated text, so you can move into the next round of revision with reference material that actually matches what's on the page now.

The distinction matters because novels don't go through one round of editing. They go through several.

The Editing Rounds Nobody Warns You About

If you've been through the professional editing process, you know that the roundtrip problem isn't a one-time event. It's a recurring one.

A novel that goes through a full editing cycle typically encounters two to four separate rounds of professional editing, each producing a new DOCX that needs to get back into Scrivener. A developmental edit addresses big-picture issues: structure, pacing, character arcs, plot logic. After you incorporate the developmental editor's feedback and do your own revision pass, the manuscript goes to a line editor, who works at the sentence and paragraph level, tightening prose, smoothing transitions, sharpening dialogue. After the line edit, it goes to a copy editor for grammar, consistency, and adherence to style. Finally, after formatting, it goes to a proofreader for a last polish.

Each round means compiling from Scrivener. Sending a .docx to the editor. Getting it back. And somehow getting the edited text back into your Scrivener project. Each round, you face the same question: spend hours on the manual roundtrip, or give up and stay in Word?

This is the compounding pain that makes authors abandon Scrivener during the editing phase. It's not that any single roundtrip is unbearable. It's that doing it three or four times, for the same novel, over the course of months, eventually breaks your willingness to bother. One author on KBoards captured this perfectly: once the manuscript goes out to the copy editor, it's out of Scrivener for good. Multiple writers echoed the sentiment. At some point, fighting the roundtrip stops being worth the effort, and the organizational work you invested in your Scrivener project just gets left behind.

With Sync, each round is the same: upload the edited .docx alongside your .scriv project, get the updated project back. After your developmental edit, you might run a Full Sync to get an updated story bible reflecting the structural changes. After your copy edit, a Basic Sync brings the corrected text back in thirty seconds. After your proofread, another Basic Sync. Your Scrivener project stays current through the entire editing process instead of being abandoned after the first round.

What It Doesn't Do (And When You Might Need Something Else)

Scrivener Sync works by matching chapters in your edited manuscript to documents in your existing Scrivener project. For the vast majority of editing workflows, where chapters keep their general identity even as the text inside them changes, this matching works reliably. Your editor can rename chapters, add or remove text within them, fix errors, restructure paragraphs, rewrite entire passages, and the sync will find the right chapter in your project and update it.

There are situations where the match gets harder. If your developmental editor recommended merging two chapters into one, or splitting a long chapter into three shorter ones, the relationship between the edited manuscript and your original project gets complicated. The system handles many of these cases, but if your manuscript went through a fundamental structural overhaul, where chapters were extensively combined, split, and reordered, a fresh conversion to a new Scrivener project might be the cleaner path. You'd lose the metadata from your original project, but you'd get a project that accurately reflects the restructured manuscript, with a new story bible built from the revised text.

The honest answer is that most editing rounds don't restructure the chapter layout. Developmental editors might suggest moving a scene or cutting a chapter, but the basic chapter-by-chapter correspondence between the Word file and the Scrivener project usually holds. Copy edits and proofreading rounds never change the structure. For the editing workflows that most novelists go through, Sync handles the job.

If you're not sure whether your situation calls for Sync or a fresh conversion, the sync page shows you a preview of the chapter matching before you pay. You can see which chapters in your manuscript matched to which documents in your project, and decide from there whether the match looks right.

The Math That Makes This Obvious

A professional copy edit for a full-length novel costs somewhere between $1,500 and $3,000, depending on the editor's experience and the manuscript's condition. A developmental edit runs $2,000 to $5,000 or more. Even a proofread costs several hundred dollars. Authors invest real money in professional editing, and the return on that investment is a better manuscript.

The value of that investment is trapped in a Word document until you can get it back into your working environment. Spending a weekend manually transferring edits, or worse, abandoning your Scrivener project entirely because the transfer is too painful, is a real cost on top of the editing bill. Not in dollars, but in time, frustration, and the organizational work you lose.

$4.99 for a Basic Sync, thirty seconds, and your edited text is back in your project with everything preserved. For a copy edit or proofread round, where the changes are at the word level and your existing metadata is still accurate, that's the entire solution.

$14.99 for a Full Sync after a developmental edit, when you want your story bible updated to reflect the structural changes your editor helped you make, is still less than the cost of a single hour with that editor.

We're not going to pretend this is a difficult decision. If the roundtrip problem has ever cost you an afternoon, the price of Sync pays for itself the first time you use it.

Your manuscript is processed in memory and deleted immediately. BinderCraft never stores, reads, or trains on your work.

Get your edited manuscript back into Scrivener. Try Sync at $4.99.

Getting Started

Scrivener Sync is available now at bindercraft.net/sync. You upload your edited manuscript and your zipped .scriv project, choose Basic or Full Sync, and download your updated project when it's ready. No subscription. No account required.

If you don't have an existing Scrivener project and you're looking to get your manuscript into Scrivener for the first time, with structure and a story bible, that's what our conversion service does. If you already have a Scrivener project and you need your edited manuscript merged back into it, that's what Sync does.

The roundtrip between Scrivener and Word has been a pain point for as long as both tools have existed. We can't change how Scrivener works, and we can't make Word understand Binder structure. But we can take the two files that result from the editing process, the .docx your editor returned and the .scriv project you've been building for months, and bring them back together.

Your synopses. Your labels. Your notes. Your compile settings. Your research. All of it, exactly where you left it, with the edited text in place.

Get back to revising. The roundtrip is over.