Every working television writer knows what a series bible is. Most novelists writing series don't, and find out the hard way somewhere around the middle of book two when they realize their protagonist's mother has died twice in two different ways. This is a guide to building one properly — what it actually is, what goes in it, and how to keep it useful across the years a series actually takes.
What a series bible is (and isn't)
A series bible is the canonical reference document for your story world. It's where the true facts live: names, dates, descriptions, rules, relationships, motivations. When your draft says one thing and the bible says another, the bible is right (or the bible needs updating — but you decide that deliberately, not by accident).
What it isn't:
It isn't your draft. Drafts contain prose that may or may not survive revisions. Bibles contain canonical truth that survives across drafts and books.
It isn't your outline. Outlines plan what will happen. Bibles record what is — about the world, the characters, and what has already happened in published or finalized material.
It isn't a worldbuilding wiki for its own sake. A series bible serves a working project. Pages exist because you need them to keep the story consistent. Pages that don't earn their place get pruned.
It isn't optional after book one. The moment you've written a second book in the same world, you have a continuity surface that needs maintenance. You either build a bible deliberately or you build one by accident in the form of contradictions in your published work.
Who needs one
Anyone writing a series — novels, novellas, comics, TV, games, tabletop campaigns that span multiple arcs. Anyone writing a single novel above about 80,000 words. Anyone writing in a shared world with other authors. Anyone building a setting they intend to reuse.
You can write a standalone short story without one. Past that, the question stops being "do I need a series bible" and becomes "how formal should mine be."
What goes in a series bible
The exact contents depend on your project, but a working series bible typically has six sections.
Characters. Every named character gets an entry. Major characters get pages: physical description, voice and speech patterns, backstory, current state, relationships, secrets, motivations, and — importantly — what they know and don't know. Minor characters get a paragraph: who they are, where they appear, anything specific that has to stay consistent (an accent, a tic, a relationship to another character).
Places. Every named location gets an entry. Geography, climate, culture, political situation, who lives there, what's happened there. For locations that feature heavily, sub-pages for specific buildings, districts, or features.
Timeline. Every dated event that matters. Births, deaths, battles, founding of institutions, key moments in characters' lives, the events of each book. This is the spine that holds the whole bible together. Without it, you have a pile of facts. With it, you have a history.
Lore and rules. The way the world works. Magic system rules. Political structures. Religions and their tenets. Technology levels. Economic realities. The constraints that make your world feel solid and that your plots have to respect.
Languages and naming. Naming conventions for each culture, common words and phrases, any constructed language elements. This sounds optional and isn't — naming drift is one of the most common sources of continuity errors in long series.
Story-level continuity notes. Anything that's true about what's happened in the published books that future books need to respect. Who knows what. Who's met whom. Which secrets are out. Which relationships are public. This is what television writers' rooms spend most of their time on, and it's the section novelists are most likely to forget.
How to build one (without losing months)
The trap with series bibles is treating them as a project. They aren't a project. They're an artifact you build alongside your actual writing.
Start small, before you draft book one. A character page for each major character, a location page for each major place, a one-page document with your magic system rules and political setup. That's it. Resist the urge to build out the whole world before writing. You'll find the world by writing it; the bible grows to match.
Add as you write, not in batches. When you introduce a named character in chapter three, you create their entry immediately. Not after you finish the chapter, not after you finish the book. The moment the name appears in your draft, the entry exists. This is the single most important habit. Skipping it is how bibles fall behind and become useless.
Capture canonical facts as they happen. When you write a scene where a character reveals their backstory, that backstory goes in the bible right away. When you establish a rule of your magic system in dialogue, the rule goes in the bible. The bible isn't where you plan things — it's where you record what you've actually committed to in the prose.
Audit between books. Before drafting book two, read book one with the bible open. Every named entity, every date, every rule. Where the bible matches the book, great. Where it doesn't, the book is canon (it's published or finalized) and you update the bible to match. Where the book itself contradicts itself — congratulations, you've found your first list of errata for the second edition.
Reference, don't remember, while drafting. This is the working principle of the bible. While drafting, every time you mention something from earlier — a character, a place, a rule, a past event — you open the bible and check. This feels excessive at first. It becomes second nature. It saves you a copy-edit pass that would otherwise find 200 contradictions.
How to maintain one (the hard part)
Building a series bible is easy. Maintaining it across a multi-year project is where most writers fail. Three principles help.
Lower the friction. Anything that requires more than 10 seconds of effort won't get done consistently. If updating your bible means switching applications, finding the right file, navigating folders, and remembering formatting conventions, you'll stop doing it. The bible needs to be one click from your draft, with a structure simple enough that you don't have to think about where things go.
Make the system catch errors for you. Human discipline is finite. Across three books and five years, you will forget things. The bible's tooling should surface contradictions — between entries, between bible and draft, between canon and outline — rather than waiting for you to find them. If you're relying on memory to catch errors, you're going to ship errors.
Treat the bible as a living document. It changes. Characters develop. The world deepens. Facts that seemed settled in book one turn out to need refinement in book two. That's fine. What matters is that the bible reflects the current canonical state, and that changes are deliberate. When you update an entry, the change should propagate to everything that referenced it.
The tools question
You can build a series bible in a Word document. Many writers have. It works for short series with simple worlds and disciplined writers.
You can build one in Notion or Obsidian. Many writers do. We've written elsewhere about where Notion falls apart for worldbuilding and the trade-offs of Obsidian for fiction writers. The short version: both work, both require significant setup and discipline, and both have specific gaps when used for series-scale fiction.
The case for a purpose-built tool gets stronger the longer your series is and the more complex your world. The series bible problem is fundamentally about connected information — characters linked to places, events linked to timelines, rules linked to scenes that depend on them — and tools built around static documents fight you when you try to use them that way.
This is what Inkwarden is built for. Lore, characters, places, and timelines stay connected automatically. Canon and outline share a timeline so you catch contradictions early. The book editor is in the same workspace as your bible, so referencing is one click and your draft and your canon never drift apart. You can talk to your characters in their own voice when you're not sure how they'd react. The series bible isn't a separate project — it's the workspace your series lives in.
Join the Inkwarden waitlist if you're building a series that needs to stay honest across years of work.
The bottom line
A series bible isn't a luxury for ambitious projects. It's the working memory of any series, whether you build it deliberately or not. The question is whether yours is a deliberate, maintained, useful working document — or a pile of half-remembered facts you're trying to keep straight in your head while drafting.
Build the bible early. Update it constantly. Audit it between books. Use tools that catch contradictions rather than waiting for you to find them. Future-you, three books deep and trying to remember whether the Ash War was 412 or 410, will be grateful.