How to Write a Series Bible That Survives Every Book
To write a series bible, start from the books you have finished, not your plans. Give every character, place, faction, item and event its own entry with the fixed facts readers notice, write each rule of your world with its cost and its limit, keep one timeline in story order, and update it whenever a new book changes the record.
A single book has a memory you can hold in your head. A six-book series does not. The story bible is the discipline that keeps Book 1's eye color, Book 3's broken promise, and Book 5's payoff agreeing with each other, long after you've forgotten you wrote them.
A story bible is the structured, single source of truth for everything your series knows about itself: every character, place, faction, item, and event, plus the rules and relationships that bind them. In StoryHelm each book's record is called its Canon, and across a multi-book series the Series Atlas gathers every book's Canon in one place, with a cross-book check you can run that flags where two books describe the same character's appearance differently, where that character starts to sound different, or where two fully read books give the same event a different year, month, season or length.
How to write a series bible, in six steps
- Start from the finished books. The bible records the series you wrote, not the one you planned; a planning document that never met the manuscripts is where most drift begins.
- One entry per recurring entity. Every character, place, faction, item and event that appears in more than one scene gets its own entry, with its aliases and forms of address.
- Record the fixed facts. Eye color, scars, handedness, ages anchored to a dated scene, a place’s spelling and distances, who holds which rank: the details a reader can check.
- Rules with cost and limit. For every rule of magic or technology, write what it costs and where it stops; a power with no limit is the fastest continuity break.
- One timeline in story order. Date every event on one story clock, flashbacks on their own layer, and sort by story time, not chapter order.
- Update and check each new book. When a draft changes a fact, change the record the same day; before each book ships, read the new book against the record, never against memory.
Free Series Bible Template (PDF)
A ready-to-use, genre-neutral series bible template covering characters, places, factions, items, events, magic/tech rules, and a master timeline. Apart from the series-wide timeline, which StoryHelm's Series Bible export can list and a cross-book check compares only for the same event given a different year, month, season or length in two fully read books, these are the same kinds of entries StoryHelm records for each book. Use it to seed your canon by hand, or as a checklist for what a complete series bible should contain before Book 2.
Download the PDFHow to Build a Character Bible
The deepest section of any series bible, step by step.
ReadStart from the free Series Bible Template, a ten-page PDF. By genre: a story bible template for a fantasy series, series bible software for fantasy authors and for urban fantasy and romantasy. If you keep the record in a spreadsheet today, StoryHelm vs a spreadsheet bible says where that stops working, and the timeline entry defines the clock. For a world that spans books, how to keep track of worldbuilding across books. If you plan in Plottr, StoryHelm vs Plottr says how the two fit together. For worldbuilding workspaces, StoryHelm vs Campfire. For software that builds the record from your books, see series bible software that builds itself.
StoryHelm builds a canon for each book it reads (characters, places, factions, items and events, from your manuscript) and gathers every book’s canon in the Series Atlas. You confirm or correct any entry; a book’s canon updates when a read runs. The Series Bible export (PDF, DOCX or Markdown) lists events from the books you select together.
Why a series needs more than notes
Most authors start a series with the best of intentions: a Scrivener folder, a spreadsheet of names, a notebook with a hand-drawn map. It works fine for Book 1. By Book 3, the notes have drifted out of sync with the manuscripts. A character who died in chapter nine of Book 2 sends a letter in Book 4. A coastal kingdom quietly becomes landlocked. The notebook says one thing; the prose says another; the reader catches both.
The problem is not discipline. A story bible maintained by hand is a copy of the truth, and a copy drifts the moment you stop updating it. The version that matters is the one in your manuscripts, so the bible has to stay tethered to what you actually wrote, not to what you remember writing.
That tether is the whole idea behind a story bible that builds itself. Instead of you transcribing facts into a reference document, the reference document is read back out of the prose: characters, places, and events extracted from the text, organized into Canon, and refreshed each time you run a read. Change a fact in chapter twelve, re-run the analysis, and the bible updates with it, instead of preserving the old version you forgot to correct.
When the bible assembles itself, StoryHelm reads and extracts what already exists in your manuscript into structured Canon. It does not draft characters, invent backstory, or generate prose. You write the series; StoryHelm shows you where it drifts.
Read the cluster
Six pieces: what a story bible is, how it differs from a series bible, a template you can fill in by hand, the two ways StoryHelm helps you build one, from raw notes or from a finished manuscript, and how to try a what-if without touching your main working draft.
What Is a Story Bible? (And Why Yours Should Build Itself)
The classic story bible is a binder you maintain by hand, and abandon by Book 3. We break down the four jobs a story bible actually has to do (remember, organize, cross-reference, and catch contradictions) and why a hand-kept binder fails at the last one. Then we show the modern alternative: a Canon that is extracted from your prose and refreshed each time you run a read, so it doesn't depend on you updating it by hand.
Read articleStory Bible vs Series Bible
The two terms get used interchangeably, but the distinction matters once you have more than one book. A story bible governs the canon of a single work. A series bible governs the canon shared across every book: the rules, timelines, and entities that must stay consistent from Book 1 to the finale. This piece draws the line clearly, with examples of facts that live in each.
Read articleFrom Notes to Story Bible (Story Elements)
You already have the raw material: a paragraph naming the three rival houses, a line that says iron breaks the binding spell, a list of who holds the harbor in which year. Story Elements scans those unstructured notes for names and suggests each one, quoting the sentence it came from. You file each one, by name, as a character, place, faction, item, or world rule in your Story Bible, attach it as a note to an entry you already have, or set it aside. No prose is generated, and nothing is added until you approve it.
Read articleStory Branching: Try a What-If Without Touching Your Manuscript
Write a second version of a scene next to the one you have, compare the two scene by scene, and keep the one that works. Story Branches leaves your main working draft untouched until you choose, and you write every word of the alternative yourself.
Read articleHow to Turn a Manuscript Into a Story Bible: Automatically
Upload a finished book and StoryHelm reads the book, extracts its characters, places, and key events, and assembles a structured Canon you can browse, correct, and set beside the next book's in the Series Atlas. The book becomes its own reference document.
Extraction is grounded in the text. Each entry in your Canon shows up to three sentences from that book that mention it by name, so you can see where it appears. When a cross-book check you run finds two books recording the appearance of a character with the same name differently, StoryHelm names both books and sets what each one records side by side. It does not quote the passages or decide which is right; you find the lines and make the call.
Later book records: “physical description: gray eyes, dark hair”
Story bible vs series bible: what lives where
| Fact about your world | Story bible (one book) | Series bible (all books) |
|---|---|---|
| A character's eye color, scar, and speech tics | Yes: stable within the book | Yes: must match across every book |
| A one-scene innkeeper who never returns | Yes | Optional: only if reused later |
| The rules of your magic / technology system | Often implicit | Yes: readers notice when the rules bend |
| The master chronology of dated events | Local timeline | Yes: one timeline spanning all books |
| A promise planted in Book 1, paid off in Book 5 | No: out of scope | Yes: the payoff has to survive the whole series |
| Faction allegiances that shift between books | Snapshot | Yes: recorded book by book |
In StoryHelm, a per-book story bible is your Canon for that project; the Series Atlas gathers every book's Canon in one place and, when you run its cross-book check, flags where two books record a character's appearance differently, where that character starts to sound different, or where two fully read books give the same event a different year, month, season or length.
What a series-grade story bible contains
The five entities
- Characters: traits, arcs, relationships
- Places: geography, ownership, state changes
- Factions: allegiances, hierarchies
- Items: provenance, who holds them when
- Events: what happened, in what order
What links them together
- A master timeline across all books
- World rules (magic, tech, society)
- Relationships between entities
- Aliases & name variants, recorded
- Setups & their payoffs, threaded
What keeps it accurate
- Entries tied to the lines that name them
- Refreshed on every read
- Contradictions surfaced, not buried
- Gathered across books, owned by you
- Editable: your edits never overwritten
Write in StoryHelm's editor or import your finished books, and it reads them one book at a time, then gathers the results across the series. Two systems do the work.
The structured single source of truth for one book (characters, places, factions, items, events), extracted from your manuscript each time you run a read, each entry shown with up to three sentences that name it.
Every book's Canon gathered in one place, with a cross-book check that flags where two books record a character's appearance or marks differently, where a character with enough dialogue in each book starts to sound different, or where two fully read books give the same event a different year, month, season or length. It runs only when you start one from your series' Checks page and confirm the credit cost, not when a book's read finishes. Adding or removing a book can leave a reminder suggesting a check.
Built on 61 analysis passes across 7 workflows, powered by Claude. You write the story; StoryHelm makes sure it holds together.
Look up a term while you read
Every concept in this guide has a plain-language entry in our glossary, the Continuity Encyclopedia. Definitions, examples, and how each one shows up in StoryHelm.
Turn your finished books into a bible you can check for drift.
Bring in book one or all six. StoryHelm reads the prose, extracts every character, place, and key event into a Canon that updates after each analysis run, and, when you run a cross-book check, names the two books where a character's recorded appearance stops agreeing, or where two fully read books give the same event a different year, month, season or length. That is the slip a reader leaves a one-star review over, found before your box set ships, not after.
Get the free Self-Audit