A fantasy story bible is a single source of truth for everything your series must keep straight: characters, places, factions, items, your magic rules, and a master timeline. Track each as its own entry with the fields below, then check every new book against it. The hard part is keeping it true to your prose as you revise.
A standalone novel can live in your head. A fantasy series cannot. By the third book you have a cast of forty, a map that has been redrawn by two wars, a magic system with rules you set up in chapter eight of Book 1, and a timeline that has to survive flashbacks, prophecies, and a generation skip. The story bible is the place those facts live so they stay the same facts across every book.
The goal is not to write an encyclopedia of your world for its own sake. It is to record exactly the things a reader will hold you to: the spelling of a name, who owns a castle, what a magic costs, when a battle happened relative to a birth. A good bible tracks what is checkable, the facts a later scene can quietly contradict, not the atmosphere you can keep in your head.
A series bible is not a worldbuilding wish list. It is the set of facts your next book has to not break.
Here is the template. Every fantasy series bible should track these seven categories. Treat each row as a record type, and give every entity in your world its own entry under the right one. The right-hand column is what to capture for each, the fields that make the entry useful for catching contradictions later.
| Category | What to track for each entry |
|---|---|
| Characters | Full name, aliases and nicknames, titles, species or race, physical traits (eye and hair color, scars, height), personality and voice, relationships, and the arc, where they start and where they end. The fields readers catch breaks in are name spelling, eye color, and age. |
| Places | Name, type (city, keep, realm, forest), geography and what it borders, who rules or owns it, and its state over time, founded, burned, rebuilt, renamed. A castle that changes hands between books is a place whose ownership field has to keep up. |
| Factions | Name, allegiances and rivalries, internal hierarchy and ranks, goals, and membership. Track who is loyal to whom, because alliances shift, and a character sworn to one house in Book 1 cannot quietly serve its enemy in Book 4 without a reason on the page. |
| Items | Name, what it does, provenance (where it came from, who forged or found it), and its current holder, the chain of custody. A named sword cannot be in two characters' hands at once, or lost in Book 2 and drawn in Book 3 with no recovery. |
| Magic & World Rules | Each mechanic, what it does, its cost (what it takes out of the user), and its hard limits (range, materials, conditions). Plus the establishing passage, the chapter where the rule became canon. This is the layer that keeps your magic from cheating later. |
| Timeline | Events in chronological order, dates or eras, character ages at each point, and what happened before what. The spine that flashbacks, prophecies, and "twenty years ago" chapters all have to line up against. |
| Languages & Naming | Naming conventions per culture or region, invented language fragments, honorifics, and how titles map to names. The layer that keeps a Dornish name from reading like an Elvish one, and a sworn brother from being addressed wrong. |
If you only ever fill in the first six, you have a working bible. Languages and naming is the one most authors skip and most readers notice, the moment a character from one culture is suddenly given a name that belongs to another, the world thins.
The categories above tell you what to track. These three fields, added to every entry regardless of type, are what turn a static reference into something that catches breaks. They are the difference between a bible you read and a bible that protects you.
That last field is the one that separates a contradiction from a payoff. Things in a series are supposed to change. People age, alliances break, the magic deepens. The bible's job is not to freeze your world, it is to tell a deliberate change apart from a slip, so you catch the slip and keep the change.
You can build everything above in a spreadsheet or a Notion database, and for Book 1 it will work beautifully. The problem is not the template. The problem is what happens to it across a series under deadline.
A hand-kept bible records what you meant. The manuscript records what you actually wrote. Every revision threatens to move those two apart. You change a character's eye color in a Book 2 rewrite to match a cover, but the bible still says the old color. You rename a city in copyedits and update three chapters but not the entry. You give a faction a new leader in a late draft and forget the bible entirely. None of these is laziness, it is that updating a separate document is a second job, and it is always the first job to get cut when the chapter is due.
By Book 3 the bible and the books have quietly diverged, and the bible is now the less reliable of the two, because you trust it without rereading the prose behind it. The contradiction it was supposed to catch sails through, because the bible no longer matches the manuscript it claims to describe. A reference that is out of date is worse than no reference, it gives you false confidence.
The fix is not more discipline. It is to stop maintaining the bible by hand and instead extract the same structure from the prose, so the source of truth is always the manuscript itself.
The template above is exactly the structure StoryHelm builds automatically. It is called your Canon, characters, places, factions, items, events, and the rules of your world, each entry pinned to the passage it came from. The difference is where the facts come from: instead of you typing them into a separate document, StoryHelm reads them out of the books you wrote.
Two ways in, depending on where you are. If you already have a draft, Manuscript Import reads the finished books and extracts the entities into the template structure for you to review. If your worldbuilding lives in messy notes, Braindump reads those unstructured notes and pulls them into the same categories, characters, places, factions, items, events, so you start from organized entries instead of a blank table. Either way, nothing is invented, every entry traces to text you wrote.
Because the Canon is read from the prose, it cannot drift the way a hand-kept document does. When you revise a chapter, the facts re-extract from the new text. And because the same engine reads your whole series at once, the Coherence Guardian and World Rules agents check each new book against the established entries, the eye color set in Book 1, the magic cost set in chapter eight, the castle's owner, and flag the scene where a later book breaks one. Across a series, this is the Series Atlas: one Canon shared by every book.
StoryHelm is a one-stop workspace: write your series in the built-in Scene Editor, or import finished books from anywhere, and a multi-agent system of 41 specialized agents powered by Claude reads the whole series at once. From your prose it builds the exact bible this template describes, your Canon, with every character, place, faction, item, magic rule, and timeline event pinned to the passage it came from. As you keep writing, the Coherence Guardian and World Rules agents check each new book against those entries and flag the scene that breaks one. StoryHelm reads, organizes, and analyzes; it never drafts or rewrites a word of your story. You write the story; StoryHelm makes sure it holds together.
At minimum: characters (names, aliases, titles, traits, arc), places (geography, ownership, changes), factions (allegiances, hierarchy), items (provenance, who holds them), magic and world rules (each mechanic, its cost and limits), and a master timeline. Naming conventions and languages help too.
A hand-kept template works for a book or two, then drifts from the manuscript as you revise. The fix is to extract the same structure from the prose so it stays current. StoryHelm builds this exact bible (your Canon) automatically and keeps it in sync.
Yes. Braindump reads unstructured worldbuilding notes and extracts them into the template structure (characters, places, factions, items, events) for you to review. Nothing is invented.
It extracts facts that already exist in your prose into structured entries; it does not invent backstory or generate prose. You write the story; StoryHelm organizes and checks it.
Fill the template once or skip it entirely: import your books and StoryHelm extracts the same structure from your prose and keeps it current as you write.
Request a founding seat