Story Bible Template for a Fantasy Series
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.
Not writing fantasy? Get the genre-neutral Series Bible Template.
What a fantasy bible has to track
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.
The template: seven entity categories
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 fields that catch contradictions
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.
The exact book and chapter where the fact became canon, eye color, magic cost, who owns the keep. Without it you cannot prove which version is the original when a later scene disagrees.
Each scene the entity shows up in, so drift is visible across books, not just within one. A cost that creeps or a name that shifts only shows up when you can line up every use.
Changes you meant, a character ages, a castle is rebuilt, a power grows because it was earned on the page. Marked as canon so a later check reads it as a tracked event, not a contradiction.
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.
Why a hand-kept bible goes stale by Book 3
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.
Build the same structure from your prose
Most of the template above is the structure StoryHelm builds automatically for each book you analyze. It is called your Canon, characters, places, factions, items, events, and the rules of your world. Each character, place, faction, item and rule shows up to three sentences from your book that mention it by name, though not the line that set each detail. 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 each finished book and adds the entities to its Canon right away, where you can confirm or edit them. If your worldbuilding lives in messy notes, Story Elements scans those notes for names, quotes the sentence each came from, and lets you file each one as a character, place, faction, item or world rule, so you start from named entries instead of a blank table. Those entries save the name only and sit in your Story Bible for reference; the continuity checks use what a read of your manuscript records. Either way, nothing is invented, every entry traces to text you wrote.
Because the Canon is read from the prose, it does not wait on you to update it: when you revise a chapter, re-running the analysis re-extracts the facts from the new text. Each book is read on its own. In a Full read, the Coherence Guardian checks that book against itself and can flag a scene that breaks a magic rule the same book set up. Across a series, the Series Atlas lists every book's Canon together, and a separate cross-book check compares the physical description each book records for a character whose name matches, flagging a change such as gray eyes turning brown and showing what each book records. When both books hold enough of that character's dialogue, it also flags a noticeable change in how the character speaks. Where two fully read books give the same event a different year, month, season or length, it flags that too. It runs only when you start one from your series' Checks page, not when a read finishes: you choose at least two books with a completed read and see the credit cost before you confirm. Adding or removing a book can leave a reminder on your series overview, but the check does not run until you confirm it. It does not compare places, owners, or the magic rules StoryHelm extracts, so the castle's owner and a magic cost set in Book 1 are still yours to check in later books.
StoryHelm is a one-stop workspace: write your series in the built-in Scene Editor, or import finished books as Word, PDF, EPUB or text files, and an analysis powered by Claude reads one book at a time. From your prose it builds most of the bible this template describes, your Canon: every character, place, faction, item, magic rule, and timeline event it finds, most of them shown beside a few sentences from your book that name them. In a Full read, the Coherence Guardian checks each book against itself. A separate cross-book check, which you start from your series' Checks page, flags a character, matched by name, whose recorded appearance changes from one book to the next, or whose way of speaking shifts when both books hold enough of their dialogue. It also flags the same event given a different year, month, season or length in two fully read books. StoryHelm reads, organizes, and analyzes; it never drafts or rewrites a word of your manuscript. You write the story; StoryHelm makes sure it holds together.
Fantasy story bible FAQ
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 most of this bible (your Canon) from each book's read and keeps it in sync when you re-run.
Yes. Story Elements scans your worldbuilding notes for names and suggests each one with the sentence it came from. You file it as a character, place, faction, item or world rule, or skip it. A new entry saves the name only, and nothing is added until you approve it.
It extracts facts that already exist in your prose into structured entries; it does not invent backstory or write your prose. You write the story; StoryHelm organizes and checks it.
Keep reading
Let your fantasy bible build itself
Fill the template once or skip it entirely: import your books and StoryHelm extracts most of that structure from your prose and keeps it current when you re-run the analysis.
Get the free Self-Audit