Scrivener has been the default writing app for novelists, screenwriters, and academics since 2007. It has millions of downloads, a loyal user base, and a reputation as the most serious long-form writing tool on the market. If you have written or attempted a novel in the last fifteen years, someone has probably told you to use Scrivener.
Scyn is not a writing app. It does not have a text editor, a manuscript view, or a compile button. It does one thing: let you map your story's structure as a network of connected events. Whether that matters to you depends on what part of the writing process you are trying to solve.
Left: a writing environment with outlining built in. Right: a dedicated plotting canvas where story events connect through cause and effect.
This is not really a head-to-head comparison. Scrivener and Scyn occupy different parts of the writing workflow. The relevant question is whether Scrivener's built-in outlining tools are enough for your plotting needs, or whether a dedicated plotting tool fills a gap that Scrivener leaves open.
We built Scyn, so factor that into how you read what follows.
What Scrivener actually is
Scrivener is a complete writing environment. You can draft, revise, research, organize, and export an entire manuscript without leaving the app. It was designed around a ring-binder metaphor: your project is a collection of documents (scenes, chapters, notes, research) that you can view and rearrange in different ways.
The core features that matter for plotting:
The Binder. A hierarchical file tree on the left side of the screen. Every piece of your project lives here: chapters, scenes, character notes, research documents. You drag items up and down to reorder them, nest scenes inside chapters, and build your manuscript structure through folders and sub-folders.
The Corkboard. Virtual index cards, each attached to a document in your Binder. You write a synopsis on the card and rearrange cards to restructure your manuscript. Moving a card moves the underlying document. This is Scrivener's most visual planning tool.
The Outliner. A spreadsheet-style view of your manuscript. Each row is a document. Columns show metadata: synopsis, word count, status, labels, keywords, and custom fields you define. You can sort, filter, and scan your entire project at a glance.
Collections. Smart lists that pull together documents matching certain criteria. All scenes from a specific POV character. All chapters marked "needs revision." All flashback scenes. These let you slice your manuscript by metadata rather than by position in the Binder.
These are serious organizing tools. For many writers, they are enough.
Where Scrivener's outlining tools stop
Scrivener's planning tools all share a structural assumption: your story is a hierarchy. Chapters contain scenes. Parts contain chapters. The Binder is a tree. The Corkboard displays one level of that tree at a time. The Outliner is a flat list of that tree's contents.
This means Scrivener is excellent at answering: what comes in what order, and how is the manuscript organized?
It is less equipped to answer: why does this scene exist, and what would break if I removed it?
The Corkboard shows you cards. It does not show you the connections between them. You can see that Scene 7 exists and read its synopsis. You cannot see that Scene 7 depends on a decision made in Scene 3 and sets up the reversal in Scene 15. Those causal links live in your head, or in notes you write to yourself, but they are not part of the structure Scrivener makes visible.
The Outliner shows you metadata about each document. It does not show you the relationships between documents. You can tag a scene with a label and a status and a keyword. You cannot draw a line between two scenes and say "this one causes that one."
For plotters who think about story as a sequence of events, this may never feel like a limitation. You know the order. You know the beats. The Binder holds it all. Done.
For plotters who think about story as a web of cause and effect, where pulling one thread might unravel three others, Scrivener's tools leave the most important structural information invisible.
What Scyn does differently
Scyn approaches story structure as a graph, not a tree.
You place story events as nodes on a canvas. You draw directional edges between them to represent causal relationships. Event A causes Event B. Event B and Event C together set up Event D. The result is a map where you can trace the chain of causation from your inciting incident to your climax and see whether every link in that chain actually holds.
Directional edges between nodes show which events cause or enable others. The isolated node with no connections is a dangling plot thread, made visible by the structure itself.
This is the only thing Scyn does. There is no text editor. No manuscript management. No compile step. No research folder. You are not writing your book in Scyn. You are mapping its structure before (or during, or after) you write it somewhere else.
The trade-off is that Scyn's one feature goes deeper than any writing app's outlining sidebar can. When cause and effect are first-class objects you can see and manipulate, certain structural problems become impossible to miss:
Dangling plot threads. A node with no outgoing connections is a setup that never pays off. A node with no incoming connections is an event that comes from nowhere. Both show up instantly on the canvas.
Fragile plot points. If one node has eight edges flowing through it, your entire story depends on that single event. You can see the bottleneck and decide whether to reinforce it or distribute the load.
Disconnected subplots. A cluster of nodes with no connections to the main storyline is a subplot that has nothing to do with the rest of the book. On a canvas, it literally floats apart.
What Scrivener does that Scyn never will
Scyn does not replace Scrivener. It could not even if it tried. They do different jobs.
Drafting. Scrivener is where you write the actual words. Rich text editing, full-screen composition mode, page view, word count targets, writing history. Scyn has no text editor.
Research management. Scrivener lets you import images, PDFs, web pages, audio files, and any other reference material directly into your project. You can open research documents alongside your manuscript in a split view. Scyn stores story events and the connections between them. Nothing else.
Compile and export. Scrivener turns your manuscript into a finished document: Word, PDF, ePub, Kindle, Final Draft. You can write in your preferred font and format, then compile to submission guidelines or self-publishing specs. Scyn exports to PNG and PDF, which are snapshots of your plot map, not publishable manuscripts.
Metadata and organization. Labels, statuses, keywords, custom fields, Collections, smart search. Scrivener's organizational depth runs deep. You can slice your manuscript a dozen different ways. Scyn has nodes and edges. The organizational model is spatial, not metadata-driven.
Screenwriting. Scrivener includes script formatting for screenplays, stage plays, and comics. Scyn has no genre-specific features.
Offline access. Scrivener is a desktop app. It works on a plane, in a cabin, anywhere without internet. Scyn is a web app. No connection, no Scyn.
Snapshots. Scrivener lets you take a snapshot of any document before revising it, with a compare tool to see what changed. Version control built into the writing process.
What Scyn offers that Scrivener does not
Cause-and-effect visualization. The core difference. In Scyn, the relationships between story events are visible and editable. They are part of the structure, not notes about the structure. In Scrivener, they are implicit. This is not a feature gap. It is a different model of what story structure even means.
Free permanent access. Scyn has a free plan with no expiration. One project, local save, PNG export. No credit card required. Scrivener offers a 30-day free trial, after which you pay $49 for the desktop app (Mac or Windows, sold separately). The iOS app is an additional $19.99.
Browser-first access. Scyn runs in any modern browser. Laptop, tablet, Chromebook, a borrowed computer at a library. Scrivener requires installing a desktop application, and the Mac and Windows versions are separate purchases. The iOS app exists but has a reduced feature set and syncs via Dropbox.
Shareable maps. Scyn lets you generate a public link to your plot map. Send it to a critique partner, a developmental editor, or a writing group. They can explore the structure interactively without creating an account. Scrivener projects are local files. Sharing means exporting a document or sending the project file itself.
Price for ongoing use. Scyn Pro is $49 per year for unlimited projects, cloud sync, and collaboration. Scrivener is a one-time purchase of $49 per platform. If you only use one platform, Scrivener is cheaper in the long run. If you use Mac and Windows, the bundle raises the cost. But the tools do different things, so the price comparison only matters if you are choosing between them for the same job.
The real question: is Scrivener enough for plotting?
For many writers, yes. If your plotting process is:
- List your scenes or chapters in order.
- Write a synopsis for each one.
- Rearrange until the flow feels right.
- Start drafting.
Then Scrivener's Binder, Corkboard, and Outliner handle that workflow elegantly. You do not need another tool. The planning and the writing happen in the same place. That integration matters.
If your plotting process looks more like:
- Identify key events without worrying about order.
- Map how those events cause and depend on each other.
- Look for structural gaps, missing connections, orphaned setups.
- Rearrange based on what the causal structure reveals.
- Then move to a writing app and draft.
Then Scrivener's tools do not show you the information that matters most to you. The Corkboard shows cards but not connections. The Outliner shows metadata but not causation. The Binder shows hierarchy but not dependency.
That second process is what Scyn was built for.
Using them together
Scrivener and Scyn are not competing for the same slot in your workflow. One is a writing environment. The other is a structural visualization tool. Many writers will benefit from using both.
A practical workflow: use Scyn during the brainstorming and structural planning phase. Map your events, draw the causal connections, identify where the structure is strong and where it breaks. Once you have a plot map you trust, move to Scrivener. Build your Binder structure based on what the map revealed. Draft in Scrivener's editor. Use Scrivener's Corkboard and Outliner to manage the manuscript as you write.
If you hit a structural problem mid-draft, the kind where you realize your Act Two subplot never actually connects to the climax, go back to the map. Restructure there, where the connections are visible. Then return to Scrivener and execute the changes.
The tools have different strengths because they answer different questions. Scrivener asks: how is this manuscript organized and how do I get it written? Scyn asks: does this story's structure actually hold together?
The honest summary
Scrivener is the more complete product by almost any measure. It has been refined for nearly twenty years. It handles the full lifecycle of a writing project, from first idea through final export. Its outlining tools are more sophisticated than what most word processors offer, and they are deeply integrated with the drafting process.
Scyn does less. Considerably less. But the one thing it does, making causal structure visible and editable, is something Scrivener was not designed to do. Whether that gap matters depends on how you think about story.
If you have ever stared at Scrivener's Corkboard and wished you could draw lines between the cards to show which scenes depend on which, Scyn exists because of that exact wish.
Scrivener has a 30-day free trial. Scyn's free plan does not expire. Try both and see which questions they help you answer.