Scrivener vs Novelcrafter vs Storystruct: a writer’s honest comparison.

If you’re writing a novel in 2026, you have more options than ever — and more noise than ever, too. Scrivener is the long-standing default. Novelcrafter is the new wave. Storystruct is the quiet one. They’re built for different brains, and picking the wrong one can mean a year of friction you didn’t need.

This is an honest, side-by-side comparison. We make Storystruct, so we’re obviously biased — but we’ve used the other two, and we’ll tell you when to pick them instead.

Scrivener: the studio for self-publishers

Scrivener is the reason most novelists ever heard of a “writing app.” It’s been around since the late 2000s, it runs on Windows and macOS, and it has a genuinely enormous feature set: an outliner, a corkboard with virtual index cards, a split-screen editor, metadata on every scene, project-wide search, snapshots, customisable compile, and a long, slow learning curve.

The thing Scrivener does that almost no competitor has caught up with is compile. The compiler is the part of Scrivener that turns your binder of scenes into a finished .docx, .epub, .mobi, or PDF with a real table of contents, page numbers, headers, and per-section formatting. For self-publishers, this alone can justify the licence. For novelists sending to agents, the .docx output is clean and predictable.

What Scrivener is not is a modern web app. It’s local-only, single-user, and tied to a desktop OS. There’s no collaborative review built in; you email a .docx to your beta readers and import their edits back. There’s no in-app feedback parser. The UI is functional but hasn’t been redesigned in a decade, and the iOS companion app is a separate purchase.

Where Scrivener wins

• The compile pipeline. Typeset, paginated output to .epub, .mobi, or PDF, with the kind of granular control indie authors actually use.
• The corkboard and outliner. Drag index cards around. Reorder by structure, not by rewriting.
• Local-first. Your project is a folder on your disk. No cloud lock-in.
• The ecosystem. Twenty years of templates, tutorials, and community knowledge.

Where Scrivener shows its age

• No native beta-reader feedback view. You still ship a Word document and import a Word document back.
• No story structure tooling beyond scenes and metadata — no first-class plot beats, no threads, no character graph.
• Single-device, single-OS. The iOS app is a separate purchase and a second-class citizen.
• UI from a different era. A power user’s dream, a casual user’s wall.

Novelcrafter: the fiction-aware worldbuilding graph

Novelcrafter is a newer entrant that caught on fast, and for one good reason: it’s the only mainstream novel writing app that builds a real, queryable graph of your fictional world for you. You write or paste your prose (or your worldbuilding notes), and Novelcrafter uses a clever algorithm to extract every character, place, faction, and object that appears. The result is a Codex that lets you ask questions like “when did Halvor last speak to Sera?” or “which chapters mention the salt crown?” without a marathon of scanning through your entire story.

For serial fiction writers with sprawling casts, this is genuinely useful. Novelcrafter also offers AI assistance, and credit where it’s due: their privacy policy is clear that they don’t train on your work and don’t log the prose you send to a model. The catch is structural, not sinister. Novelcrafter uses a bring-your-own-key model — you connect your own account with an AI provider (OpenAI, Anthropic, Google, OpenRouter), and your prose is sent to that provider. From that point on, the provider’s data terms govern your words, not Novelcrafter’s. So “Novelcrafter won’t train on you” is true, and easy to mistake for “nothing will.” If you route to a consumer-tier endpoint or a free OpenRouter model, the answer can be very different. Read the provider’s terms — not just Novelcrafter’s — before you send a manuscript you intend to publish.

Where Novelcrafter wins

• The Codex. A real queryable graph of your cast and world, in a category that mostly gives you folders.
• Fast chapter-level search. Ask “which chapters mention X” and get an answer.
• Modern UI. Clean, web-based, fast.

Where to be careful

• The AI exposure depends on a provider you choose. Novelcrafter doesn’t train on you or log your prompts, but once your prose reaches the model you connected, that provider’s terms apply. Pick a no-training API tier — or a local model — if pre-publication confidentiality matters to you.
• You have to read two policies, not one. Novelcrafter’s is short and clear. The provider’s is the one that actually decides what happens to your words. Most readers only check the first.

Storystruct: the quiet, structure-first workspace

Storystruct is built for a specific kind of writer: the one whose desk is a mirror image of their creative mind. You have half-finished index cards, a folder called cast_final_v3_USE_THIS_ONE, a Notion page with character arcs, a separate Google Doc for the plot, an email thread with a beta reader who is very patient, and a deep suspicion that you have set up a thread about a missing key in chapter 3 and never paid it off. Storystruct is for you.

It is one app, in the browser, with five rails: Plot, Cast, Threads, Manuscript, and the chapter’s Feedback view. Each rail is a calm, scannable surface. The Plot rail lays out your acts and beats in a single scrollable view; you mark beats as rising, midpoint, climax, or resolution, and you can pin a beat to a scene when you’re ready to write it. The Cast rail holds your characters, their goals, motivations, conflicts, and the relationships between them. The Threads rail tracks the promises you’ve made the reader: promises, progress and payoffs, tagged and classified, linked to the scenes where they appear. The Manuscript rail is your chapters and scenes, in the order you want them, with as many chapter versions you need to get it right. The in-app chapter feedback is, in our biased opinion, the killer feature.

The flagship: feedback parsing, done properly

Beta-reader feedback is the part of novel writing that everyone agrees is important and no tool gets right. You email a chapter. Your reader edits it in Word, with track changes and comments. They send it back. You have, on average, seven of these documents open at any one time, and the comments are anchored to text that no longer exists because you’ve already rewritten the chapter twice.

Storystruct fixes this. You upload the .docx (with track changes and Word comments) or a .md file against the chapter. We parse it, run a bespoke diff algorithm against a snapshot of the chapter’s prose, and show you the result. Insertions, deletions, and style changes, with the reviewer’s comments anchored to the exact words they refer to. The diff is stored as a review, so the same feedback can be read again, in the same place, long after you’ve rewritten the chapter underneath it. Nothing leaves your account.

This is the part of Storystruct that’s hardest to find anywhere else. Scrivener doesn’t have it. Novelcrafter only has feedback by an AI-chatbot — not a real tool that parses beta-reader feedback. We built it because the other two left us with a folder of Notes I keep meaning to read.

The other half of the flagship: real story structure

Storystruct is the only one of the three that treats plot, characters, and threads as first-class objects you can lay out before you write a sentence. Beats have types. Threads have states (open / paid off / abandoned). Characters have arcs. Each one of those live in their own scrollable views, and when you’re ready to write a beat, you bind it to a scene and our system starts indexing it to make it searchable. No corkboard metaphor from 2007. No drag-and-drop graph that takes a week to learn. Just structure.

What we don’t have, and why that’s the point

• No AI. None. We do not call a third-party model, don’t embed a smart-suggest engine, don’t analyse your prose for “tone.” This is the cleanest privacy answer there is: with no AI feature, there’s no provider, no key, and no second policy to read. The whole question of “will my prose get trained on” never arises, because your writing never leaves the app for anyone’s inference cluster.
• No analytics. We don’t need to know what browser you use, what operating system you’re on, what country you live in or what you had for breakfast. All we need to do is build an amazing app for writers, which is, in fact, what we are ourselves.
• No partners snooping around in your manuscript. The only sub-processors are our EU hosting (we have our own bare metal) and our own SMTP. See the privacy policy for the full picture. It is short by design.

Where Storystruct wins

• First-class story structure. Acts, beats, threads, arcs, characters, and world entries are objects, not notes in a folder.
• Beta-reader feedback parsing. Upload a .docx with track changes and comments, or a .md file. Get back a review you can read next to your prose, anchored to the words it refers to, forever.
• Typeset export — .docx for now, more coming soon. Per-chapter or per-manuscript.
• EU-hosted, privacy-respecting. Data lives in the Netherlands. No advertising. No analytics scripts. No AI provider in the loop at all.
• Free while in early access. €0, no credit card, no timer. The novels you start now stay with you, whatever we charge later.

The limits we will soon overcome

• No built-in .epub/.mobi export. We export a typeset .docx, which is the format agents and most self-publishers actually want. If you need a direct .epub, run our .docx through Calibre or your publishing tool of choice.
• No desktop app yet. Browser-first, mobile-friendly. The text editor is a real editor, not a typewriter view.
• Early access. The product is shaped by the writers using it. Feature requests get read.

Feature comparison at a glance

• Plot, acts, beats, threads, character arcs: Storystruct has them as first-class objects. Scrivener has scenes and metadata. Novelcrafter has its extracted Codex.
• Beta-reader feedback parsing: Storystruct parses .docx with track changes and .md feedback, anchors comments, and replays reviews after rewrites. Scrivener has no native feedback view. Novelcrafter’s feedback is AI-driven.
• Export: Scrivener’s compile is the category leader, with direct typeset .epub, .mobi, and PDF. Storystruct and Novelcrafter both export .docx and Markdown; for .epub you’d run that through a tool like Calibre.
• AI assistance: Novelcrafter’s headline feature (bring-your-own-key, so the provider is yours to choose). Storystruct has none by design. Scrivener has none.
• Privacy / data sovereignty: Storystruct stores in the EU, has no AI provider in the loop, and no sub-processors beyond hosting and email. Scrivener is local-first, so your data never leaves your machine. Novelcrafter doesn’t train on you or log prompts and names all its sub-processors — but with bring-your-own-key, your prose reaches whatever AI provider you connect, under that provider’s terms.
• Price: Storystruct is free while in early access (€0, no card). Scrivener is a one-time license. Novelcrafter is a subscription.

Which one should you actually pick?

There is no single right answer. There is a right answer for you.

Pick Scrivener if you want one tool that takes a novel from first draft to a publishable .epub, .mobi, or print PDF without you ever leaving the app, and you’re happy to learn a deep, old-school interface in exchange. It is the studio for self-publishers.

Pick Novelcrafter if your obsession is a queryable graph of your fictional world and you want AI assistance on your own terms — ideally routed to a no-training API tier or a local model if your manuscript is pre-publication. It is the best-in-class worldbuilding tool.

Pick Storystruct if you want a quiet, structure-first workspace that takes your plot, characters, threads, manuscript, and beta-reader feedback seriously, that has no AI and so never sends your prose anywhere, and that lets you start writing tonight for free. The flagship is the feedback parser. The other flagship is the structure. The price is zero, while it lasts.

Frequently asked questions

Is Storystruct really free?

Yes. Storystruct is in early access and everything is free while we shape it. No credit card, no cap, no timer. When paid plans arrive, the stories you write now stay with you — we will never take a novel away from a writer who started here. See pricing.

Will feature X be implemented?

Send us an email at hello@storystruct.com. Chances are if the feature you’re suggesting is genuinely useful for writers such as us, it’s already on the roadmap. But send the email anyway.

What if I’ve already started a novel in Scrivener or Novelcrafter?

You can keep your existing tool. Storystruct is not a hostile migration. If you decide to move, you can import your manuscript and your chapter structure, lay out your plot and characters fresh, and start using the feedback parser from your next chapter onwards. We’d rather you use the right tool than the tool that pays us.

Open a story, lay out some beats, and feel the workspace. No setup, no template wizard, no credit card. If your mind is as messy as ours, you’ll be at home in five minutes.