Guides · Workflow
Using Loreon alongside Scrivener.
By Daniel Bentes · Published 28 July 2026
The short answer: yes, you can keep Scrivener. Compile to Word, plain text or MultiMarkdown and import it; Loreon reads prose against a structured record, which Scrivener does not claim to do. The cost is a manual, one-way-at-a-time handoff — no plugin, no sync, no merge — and everything that is not prose stays behind: corkboard, labels, snapshots, research on one side, story bible and findings on the other.
The right question
Not "should I switch".
Most writers arriving here are not shopping for a new drafting environment. They have a Scrivener project they like, a manuscript inside it, and a specific problem Scrivener does not claim to solve. "Should I replace Scrivener" is the wrong question and a losing pitch; "can I keep Scrivener and still check continuity" is the real one.
The answer is yes, with a manual handoff and one real cost. Both are described below.
What each one is for
Organisation versus checking.
| Scrivener | Loreon | |
|---|---|---|
| The job | Organising and drafting a long manuscript — "typewriter, ring-binder, scrapbook" in their own words. | Keeping a long manuscript true to itself. |
| Structure | Scrivenings mode, corkboard, outliner, Collections, split-screen editing across up to four documents, snapshots with comparison. | Chapters and scenes, with far less structural tooling. |
| Research beside the draft | Import images, PDFs, movies, sound files and web pages into the project itself. | Text only. Nothing like this. |
| Reading prose against a record | Not offered — it is not what the software is for. | A structured story bible and checks that read the prose against it, per scene or across the whole book. |
| Across several books | Projects are per-book; canon lives in your head and your notes. | One canon across volumes, with a cross-volume coherence check. |
| AI | None. Deliberately — nothing on their site advertises an AI feature, and for many writers that is precisely the appeal. | Agents that draft and check, all of them opt-in and on request. |
| Output | Word, RTF, OpenOffice, PDF, Final Draft, plain text, EPUB, Kindle, MultiMarkdown and Pandoc for LaTeX. | Markdown, plain text and PDF. No EPUB, no DOCX. |
| Where it runs | macOS, Windows and iOS, licensed separately. Works offline. | Browser only. No offline mode. |
Scrivener details verified 28 July 2026 against literatureandlatte.com.
The handoff
How a manuscript actually moves.
The formats line up, and that is the whole mechanism — there is no integration, no plugin and no sync.
Scrivener → Loreon
Compile to Word, plain text or
MultiMarkdown. Loreon imports .docx,
.md and .txt up to 10 MiB and splits the text into
chapters and scenes you can edit. A .docx is converted to text in your
browser before anything is uploaded.
Loreon → Scrivener
Export Markdown or plain text and import it back. Scrivener imports Word and plain text among others.
What does not travel
Almost everything that is not prose. Your corkboard, labels, statuses, keywords, Collections, snapshots and research files stay in Scrivener. Your Loreon story bible, canon links and findings stay in Loreon. Compile settings do not survive either direction.
This is a manual, one-way-at-a-time handoff, not a round trip you can run repeatedly. There is no merge: moving a manuscript back after editing it in the other tool means replacing, not reconciling. In practice the workable pattern is to draft where you prefer and move a copy across at revision time — not to keep both in step.
Format compatibility above is taken from each vendor's own documentation on 28 July 2026. We have not performed the round trip end to end ourselves — Scrivener is a licensed desktop application — so treat the mechanism as verified and the friction as unmeasured.
The questions that follow
Ownership, formatting, revision.
- Who owns what I upload? You do, and your content is not used to train models — see privacy & ownership. Nothing about importing a manuscript changes its ownership.
- Can I do my formatting in Loreon? No. Scrivener's Compile is far more capable than anything we offer, and if your book ends in an EPUB you need Scrivener or a dedicated formatting tool regardless.
- What does the revision loop look like? Import the compiled draft, build or derive canon, run validation, work the findings, then apply the fixes wherever you keep the master copy. Findings cite chapter and paragraph, which is what makes applying them elsewhere practical.
- Do I have to stop using Scrivener? No — and if the drafting environment is working, changing it to solve a continuity problem is solving the wrong thing.
The bottom line
Keep the one that is working.
Scrivener is excellent at organising and drafting a long manuscript and has been for years. It does not read your prose against a record of what is true, because that is not what it is for. If that is the gap, you can fill it without giving up the environment you already like — at the cost of a manual handoff and a copy that has to stay authoritative in one place at a time.
For the head-to-head, see Loreon vs Scrivener. For where each kind of tool fits, see choosing software by workflow. For what we do not do at all, the limitations page.
Loreon · The Writing Studio
Or let the software read it.
Everything above works with a spreadsheet and patience. Loreon does the same reading against a structured story bible and hands you the findings, with the passages cited.