A story bible documents one book’s world, characters, and rules. A series bible spans every book at once with one shared canon and cross-book continuity, tracking the timeline, character arcs, and facts across the whole series so a later book never quietly contradicts an earlier one.
A story bible is the reference document for a single book. It is the single source of truth for everything that has to stay consistent inside that one manuscript: who the characters are, what the world’s rules are, and which facts you have already committed to on the page. When you write “her eyes were grey” in chapter two, the story bible is where you record it so chapter nineteen doesn’t turn them green.
The point of a story bible is not paperwork. It is continuity. It catches the small drifts that pull a reader out of the story, the changed spelling of a name, the scar that moves shoulders, the rule of magic that quietly contradicts itself. A good story bible turns “I think I established that somewhere” into “here it is, chapter six.”
For a one-book project, a story bible typically holds:
If you only ever write standalone novels, a story bible per book is all you need. The trouble starts the moment you write a second book in the same world.
A series bible is everything a story bible is, applied across every book at once. Where a story bible answers “is this book internally consistent?”, a series bible answers the harder question: “does this book still agree with every book that came before it?”
That is a genuinely different job. A character introduced in book one ages, changes, and carries a history that book five has to honor. A throwaway detail in book two can become a plot hole in book four. The contradictions that sink a series rarely sit inside a single book; they sit between books, which is exactly where a per-book story bible can’t see.
On top of the per-book canon, a series bible adds three things no single story bible has:
A story bible can tell you a book agrees with itself. Only a series bible can tell you book four still agrees with book one.
Put simply: a series bible contains a story bible for each book, then adds the cross-book layer no single story bible can provide. One is a subset of the other, not a rival to it.
| Your situation | What you need | Why |
|---|---|---|
| A standalone novel | Story bible | All the continuity that matters lives inside one manuscript. |
| A duology or trilogy | Series bible | Book two has to agree with book one. The risk is between books. |
| An ongoing or open-ended series | Series bible | The shared canon, timeline, and arcs grow with every new book. |
| A box set or backlist of related books | Series bible | Old contradictions surface when readers binge the whole set in order. |
The rule of thumb: one book, a story bible is enough. The instant a second book shares the same world, characters, or timeline, you have crossed into series-bible territory, whether or not you have called it that yet. The cost of waiting is that the contradiction you skip past in book two becomes the plot hole a reader emails you about after book four, usually with the chapter number attached.
You don’t maintain either document by hand. Write your manuscripts in StoryHelm’s built-in Scene Editor (or import finished books), and StoryHelm builds both layers from the text itself: Canon as the story bible for each book, and the Series Atlas as the series bible across all of them, with one shared canon, a cross-book timeline, arc tracking, and the Coherence Guardian flagging contradictions between books, severity-ranked by book and chapter. The AI reads and analyzes; it never drafts or rewrites a word of your prose. You write the story; StoryHelm keeps it consistent with itself.
Not quite. It contains a story bible for each book, but it adds three things none of them have alone: cross-book continuity, a series-wide timeline, and long-arc tracking. A bigger document still only sees one book at a time. The series layer is the part that holds every book up against the rest at once.
No. You never convert a story bible into a series bible by hand. The per-book canon you already built stays as it is, and the cross-book layer assembles itself on top of it as you add books. In StoryHelm that per-book layer is your Canon and the series-wide layer is the Series Atlas, but the principle holds with any method: the series view should grow from the books you already have, not require a fresh start.
Bring in book one or the whole shelf. StoryHelm reads every manuscript, builds one shared canon, and flags the contradictions that hide between books, named by book and chapter, before a reader bingeing the box set finds the one you missed in book four. It reads and analyzes; it never drafts or rewrites a word of your prose.
Request a founding seat