Outgrown the binder?Keep it. Add a memory.

What Scrivener does well

Scrivener is a writing app from Literature & Latte, available for Mac, Windows and iOS. Its binder lets you break a manuscript into scenes and chapters, move them around freely, and keep research (notes, images, PDFs) inside the same project. The corkboard shows each piece as an index card, and Compile turns the whole thing into a formatted manuscript or ebook.

Those ideas are why so many novelists use it, and why plenty never need anything else. If your book lives on one computer, you write alone, and you like arranging cards by hand, Scrivener is a mature and deep tool that has been refined for many years. This page is for the writer whose project has grown past what the binder can remember on their behalf.

Where a long series strains the binder

The binder holds documents; it doesn’t know what is in them. A character sheet you wrote during book one says what you believed then. By book three the scar has moved to the other hand, the brother has picked up a second name, and the inn changed owners in a chapter you’ve half forgotten. Keeping the research folder true is a job, and it’s the job most writers quietly stop doing somewhere around chapter twenty.

Authrot builds the bible from the text instead. When a chapter is read, it finds the characters, places, items, factions and lore the chapter mentions and records each reference: named, referred to, relied on, or shaping the scene without a mention. Facts that change are kept over time, and the ones that must never change can be anchored, so a later line that breaks one is flagged beside it.

• Near-duplicate entries caught and merged, with the references in your prose moved too
• Rename a character across the whole text, with a preview and undo
• Characters who have been offstage too long flagged as due back
• Search by close spelling, for the name you only half remember

Moving a Scrivener project over

A .scriv project can’t be opened directly: it is a folder of Scrivener’s own files, and Authrot doesn’t read that format. The route that works is the one Scrivener is built for. Compile the manuscript to a Word file (.docx) or Rich Text (.rtf), then drop that file into the import dialog. Files are read in your browser, never parsed on a server.

Lines such as “Chapter 7” or “Prologue” start new chapters, and a heading that recurs at the same level does the same, so most compiled drafts split cleanly. Before anything is saved you see every proposed section with its word count, can join or split them, and can check the reading order. For research, export or copy your character and world documents out as Word, RTF or plain text, and send them to the story bible in the same dialog.

One thing to check before you compile: make sure each chapter starts with a heading or a “Chapter” line in the compiled file, since that is what the importer splits on. If your binder holds one document per scene, that line is what turns twenty scenes back into one chapter. Anything that still lands in the wrong place can be joined or split in the dialog afterwards.

• Compile to .docx or .rtf; the .scriv folder itself is not read
• Say whether the files are your manuscript, your notes, or both
• Character sheets and world notes can become bible entries
• Files in folders named Characters, World or Notes go where those names suggest

What a web studio changes

Authrot is a web app. It installs to your desktop or home screen, works on a phone with the same editor, and keeps going offline: edits stay in the tab and sync when you reconnect, with a review of what changed. There’s no project file to carry between machines, and the laptop, the desktop and the phone all open the same book.

It is also shared by design. Invite a co-author or an editor by email, pick one of six roles for them, and you’ll see each other’s cursors in the same chapter. Each person can work on their own branch if they prefer, and every version is kept, so nothing anyone does is final until you decide it is.

History also replaces the habit of taking a snapshot before a risky edit. Every version of every document is kept without you asking, any version can be previewed and compared with the one before it, and a single change to the plan or the bible can be undone on its own. Ctrl or ⌘ with S still saves a named moment, for the times you want to mark one.

An outline that checks the draft

Scrivener gives your outline a place to live. Authrot reads the draft against it. Each chapter can carry a plan (what happens, the moments to land as a checklist, its scenes) and sits under the arc it serves. A drift check tells you when a chapter strays from its arc, from your writing rules, or from its anchors.

Promises are tracked too. The setups a chapter plants are recorded against the words that planted them, and the story map groups them by when they pay off. On a three-book series that is the difference between remembering the locked door from book one yourself and hearing about it from a reader.

If you wrote synopses on your index cards, they have a home here too: each chapter keeps a summary beside its plan, picture and alternates on one details page. Paste them in as you go, or let the chapter reading tell you what the chapter actually does and compare it with what you meant it to do.

When to stay with Scrivener

If you write on one machine for long stretches, work alone, and value Compile’s fine control over a manuscript’s layout, Scrivener may well suit you better. Authrot’s PDF export is a 6×9 book in your chapter heading styles, not a full typesetting tool. Writers who think best on a corkboard of index cards may miss that view too.

Some writers use both: plan and draft where the bible keeps up, then export to Word and finish the layout in whichever tool they like. Export goes to Word, Markdown, EPUB, PDF or plain text, one file or one per book, and you can download all your data whenever you want, so trying the studio doesn’t lock anything in.