Looking for a Scrivener alternative?

First: you may not need to switch

Scrivener lets you draft a long project in small pieces, keep research beside the manuscript, and view the same project as a binder, a corkboard or an outline. It works offline with your own project files, takes snapshots before big edits, and compiles to Word, PDF, EPUB and other formats, including scriptwriting formats. It is sold as a licence rather than a subscription: as listed in October 2026, $59.99 per desktop platform, $95.98 for a Mac and Windows bundle, and $23.99 for iOS.

If it already works for you, those strengths are hard to replace, and a newer tool's polish won't make up for a workflow you've spent years learning. Many writers who once found Scrivener complicated get on well by keeping the binder simple, leaning on search, and learning features only as they need them.

Why writers look elsewhere

The reasons are usually specific, and worth naming, because each one points towards a different kind of alternative.

• Working across devices. Desktop licences are per platform, and syncing with the iOS app goes through Dropbox. Writers who move between a work laptop, a home computer and a tablet sometimes prefer a tool that opens in a browser.
• The learning curve. Scrivener is deep. Some writers find that compile, metadata and project organisation pull attention away from writing; others value exactly that control.
• Wanting connected story records. Scrivener's character sheets, metadata, collections and links can track a great deal, maintained by hand. Some writers want records that link to the passages where facts appear, or help finding possible contradictions.
• Gathering reader feedback. Sharing a draft with beta readers usually means exporting a file. Some tools offer reader links with comments in the text.
• A different feel. Some writers simply want a newer interface, or one built only around fiction.

What to check before you leave

• Your compile needs. If you rely on a carefully tuned compile for print, ebook or submission formats, find out how a new tool produces each one, or plan to keep Scrivener for that final step.
• Local files. Scrivener projects live on your own computer. Browser-based tools usually store your manuscript on their servers. Decide whether that suits you, and read where and how it is stored.
• What you've already paid for. A Scrivener licence doesn't expire. A subscription adds a recurring cost, so it should pay for something you'll use again and again.
• Research material. Scrivener can keep PDFs, images, web pages and other references inside the project. Check what a new tool can hold, and decide where the rest will live.
• Scripts. If you write screenplays as well as novels, check the new tool's script support; many novel-focused tools have none.
• Writing without a connection. If you write on trains or anywhere without reliable internet, test the new tool with the network switched off.

Alternatives by what you need

Import support varies. Novelium advertises importing Scrivener project files, and Lore & Lilac imports a zipped .scriv project; many other tools take a DOCX compiled from Scrivener. Whatever a tool claims, import one real draft and read it through before relying on it.

A safe way to migrate

There's no rush. The safest migration moves one draft at a time and leaves the original untouched.

1. Reach a natural stopping point. The end of a draft or a revision pass is far easier to move than a book in mid-change.
2. Keep the whole project. Make a copy of the complete .scriv project, or a zipped backup from Scrivener itself, and store it somewhere separate. Don't delete it after you move.
3. Compile a DOCX for each draft you want to keep. One file per draft, named with the draft and the date. Check that chapter and scene titles are included in the compile.
4. Bring your notes separately. Character sheets and research don't always travel with the manuscript. Export or copy what you need.
5. Import one draft and read the result. Use the zipped project if the new tool accepts it, or the DOCX. Look for italics, scene breaks, chapter order, and anything unusual such as footnotes or images.
6. Write in the new tool for two weeks before moving anything else. If it doesn't suit you, nothing has been lost.
7. Keep the archive. Years from now, the .scriv project is still your record of how the book was built.

Using both

Switching doesn't have to be all or nothing. Common combinations:

• Draft in Scrivener, revise elsewhere. Compile a DOCX of the finished draft and import it into a tool built for revision, story records or reader feedback.
• Plan elsewhere, draft in Scrivener. Keep the outline and lore in a planner or worldbuilding tool, and the manuscript in Scrivener.
• Write elsewhere, compile in Scrivener. Bring a finished DOCX back into Scrivener if its compile is what you trust for final formats.

Whichever combination you choose, keep one tool as the master copy of the manuscript at any moment, and move text in one direction at a time. Two live copies of a novel will eventually disagree.

Where Lore & Lilac fits

Lore & Lilac suits Scrivener writers who want to work across devices and keep story records tied to the manuscript. It runs in the browser, in desktop apps for Windows, macOS and Linux, and as an installable app on phones and tablets, and books you've opened on a device open there offline. Its story bible cites the passage behind each detail, and the revision desk and retcon rehearsal help you see which passages a change will touch. It never writes prose, and AI features stay off for each book until you allow them.

It imports a zipped .scriv project — the Draft in binder order, with synopses, and research text as notes — and shows a fidelity report before anything is saved; PDFs, images, snapshots, labels and compile settings stay in Scrivener. Moving from Scrivener walks through it. It stores manuscripts on our servers rather than as local files, and opens offline only for books you've already opened on that device; its desktop app can also keep restorable backups of each book on your computer. It has no screenplay formatting or tracked changes, and doesn't match Scrivener's compile options; its print-ready PDF goes through your browser's print dialog. Read the full comparison.