What Is a Story Bible? (And When You Actually Need One)

Every fantasy writer eventually hears the phrase "story bible." Every series writer hears it too. Every screenwriter working in a writer's room lives inside one. Most working novelists who hear the term assume it's a fancy worldbuilding document and skip building one until book three, when the continuity errors start piling up.

Short version, before the long one. A story bible is the canonical reference document for a long-running fictional project: characters, places, history, magic system, technology, timeline, rules, and any other facts the story has committed to. It exists so the writer (and any collaborators) can answer "what's true in this world?" without re-reading the whole manuscript.

This post explains what's in one, when you need one, when you don't, and how to actually maintain it.

What goes in a story bible

A working story bible has six or seven sections, depending on the project.

1. Characters

The longest section in most bibles. Each named character gets an entry with:

• Full name (and any nicknames, titles, aliases).
• Age at story start; calculated age in each subsequent book if a series.
• Physical description at story start. Height, hair color, eye color, distinguishing features, scars, age markers.
• Family (parents, siblings, children, spouses, exes).
• Occupation, role, faction, or title.
• Voice and speech patterns. "Speaks formally; uses 'shall' instead of 'will'." "Avoids contractions when angry."
• Established backstory facts. Where they were born, key events, when they met the protagonist.
• Established physical history. Wounds, illnesses, surgeries, anything that affects them physically going forward.
• Established secrets (canonical and revealed to whom).

For a series, characters accumulate facts across books. Your story bible's character entries grow.

2. Places

Every named location with:

• Name and any alternate names (in different languages or eras).
• Geographic location (which continent, country, region, neighborhood).
• Brief description.
• Who lives there or what faction controls it.
• Established events that happened there.
• Travel time to other key locations. (Critical; readers will catch travel-time inconsistencies.)

3. Timeline

The most-skipped section, the most useful when it exists. A chronological list of every event in the story's history, with dates relative to the story start (Year 0).

• Year -847: The First Faerie War ended.
• Year -50: The protagonist's grandfather was born.
• Year -22: The protagonist was born.
• Year 0, Day 1: Chapter 1 starts.
• Year 0, Day 4: Chapter 4 (protagonist arrives at the academy).
• Year 0, Day 40: Chapter 17 (midpoint reversal).

The timeline catches things like "the war ended 30 years ago but a character who was 5 at the time is somehow now 40."

4. Worldbuilding rules

Especially important for fantasy and sci-fi. The magic system, the technology, the political structure, the religious system, the economy. Each rule with:

• What the rule is.
• What exceptions exist (canonical exceptions, not just "anything goes").
• What the rule costs. (Magic systems with no cost are notoriously prone to plot holes.)

A magic system entry might look like:

Blood magic requires a personal sacrifice (the caster's own blood) proportional to the spell's scale. Healing a wound: a single drop. Killing a person from distance: a cup. Resurrection: impossible (canonically; nobody knows the cost, but it kills the caster every time someone has tried). Side effects: prolonged use causes anemia and visible aging.

5. Factions and organizations

Political parties, magic schools, military units, criminal organizations, religions, guilds. Each with their structure, leaders, current alliances and rivalries, and history.

6. Linguistic and cultural conventions

How does the world handle names (patronymic? surnames?). What's the calendar? What's the currency? What gestures mean what? Do characters bow, nod, or shake hands when greeting? What are the taboos?

These accumulate. Most writers don't realize they made decisions about these things until book two, when they have to make a consistent choice and can't remember what they did in book one.

7. Continuity tracking (per-book)

Things that happened in the previous book that the next book can't contradict. Wounds. Promises. Relationships. Property ownership. Who knows what.

This section is sometimes called a "loose threads" document or a "carryover" log.

When you need a story bible

Four kinds of writers benefit unambiguously.

Fantasy and science fiction writers building a new world. If your world isn't ours, every fact has to be tracked. There's no shared reality the reader can fall back on. Inconsistencies destroy immersion faster than in any other genre.

Series writers, in any genre. As soon as you're writing a sequel, you're at risk of contradicting book one. By book three, the cumulative facts to track are too many to hold in your head. A bible isn't optional; it's the only way you'll keep the series consistent.

Mystery and thriller writers tracking who knows what. Mysteries live or die on the reader's "what does each character know at this moment" model. A bible's secrets-and-knowledge tracker keeps the mystery fair.

Co-authored or shared-universe projects. As soon as more than one writer is touching the same canon, a bible is the contract.

When you don't need one

Standalone literary fiction. The world is recognizable. The character set is small. The timeline is short. You can hold it in your head.

Short novels under 70,000 words. Probably small enough to keep in working memory.

Memoir or auto-fiction. Your life is the bible.

Fast-draft work-in-progress. Building the bible while drafting the first draft slows you down. Build it during revision, when you know what facts you've committed to.

When to start a story bible

The wrong answer: before drafting.

The right answer: when you're about 30% into your first draft, and you're starting to feel uncertain about whether facts you mentioned in chapter 4 are still true.

Building a bible too early traps you. You haven't yet discovered what the book wants to be; you're already locking in canon. The result is a meticulously-built bible that doesn't fit the story you actually wrote.

Building it too late (mid-revision of book two) is painful; you have to reverse-engineer it from the manuscript. Doable, but tedious.

The sweet spot is "during late first draft" or "during early revision of book one." You know what the book is by then. You haven't committed to a sequel yet.

How to maintain it

Keep it in a single file. A Markdown file, a Notion doc, a Scrivener research folder, an Obsidian vault. Whatever; one place. Multi-file bibles fragment and rot.

Update it as you make canonical decisions, not before. Every time you commit a new fact in the manuscript ("Maren's mother died when Maren was eleven"), open the bible and write it down. Not later. Now.

Date-stamp every entry. When you revisit the bible six months later, you want to know when each fact was added, in case the manuscript has since contradicted it.

Separate canonical from speculative. Some entries are "I'm thinking about this for book three." Mark those as speculative. Canonical entries are things the manuscript has committed to.

Use the bible during writing. Pull it up when you're about to introduce a new scene. Skim relevant entries. Don't draft from memory if the answer is in the bible.

What the story bible doesn't do

It doesn't:

• Plan your plot. The bible records the facts; the outline plans the plot. They're different documents.
• Write your character voices. The bible records linguistic conventions; the prose is still yours.
• Catch every continuity error. You still need beta readers and editing passes; the bible catches the predictable errors.
• Substitute for editing. A bible is a tool; it doesn't replace structural editing.

The story bible as collaborative artifact

In a writer's room (TV writing), the bible is the shared canon. The showrunner writes it; the staff writers reference it constantly. In novel-writing, especially solo, the bible is just for you (and any beta readers, editors, or collaborators).

When you eventually work with a developmental editor, sending them the bible alongside the manuscript helps. The editor can verify the manuscript against the canon and flag drift faster.

When you eventually sell foreign rights or audiobook rights, the bible helps translators and narrators. They can answer questions about pronunciation, dialect, and intent.

When you write a sequel, the bible is the foundation. Book two starts with the bible, not from scratch.

Common story bible mistakes

Over-detailing things that don't appear on page. You don't need the full genealogy of every minor house if the manuscript only references three of them. Build what the story needs; expand when the next book needs more.

Mixing the bible with the outline. The outline is "what happens next." The bible is "what's true." Don't conflate them.

Treating the bible as a dumping ground for unused worldbuilding. Things that didn't make it into the manuscript shouldn't be in the canonical bible. They go in a separate "cut content" or "ideas" file. The canon is what's in the books.

Updating it less often than you commit facts in the manuscript. A stale bible is worse than no bible because you'll trust it. Update it as you draft, not in batches months later.

Building it in a software tool you can't easily export from. Some worldbuilding tools (World Anvil, Scrivener, certain Notion templates) lock your data. If you stop paying or the company shuts down, you lose the bible. Use Markdown, plain text, or anything you can export to a portable format.

Story bible templates that exist

A few public templates worth looking at:

• The Save the Cat character grid. Useful for protagonists and antagonists, less for ensemble.
• The Brandon Sanderson series-bible approach. Tracks magic-system costs and constraints rigorously.
• The Marvel Cinematic Universe writer's bible. Inaccessible publicly, but the leaked references give a sense of scope.
• The standard TV writer's room bible format. Character sheet, world overview, episode index, ongoing arcs, continuity notes.

Pick a template that fits your genre and modify it for your project. There's no perfect format.

Where Inkett fits

Inkett is the writing stack for working novelists. The Planner gives you a node-based view of acts, chapters, characters, settings, and plot threads, which is structurally a bible-shaped surface: characters as nodes, places as nodes, the relationships between them as edges. The Editor catches continuity drift between chapters, the exact failure mode a bible exists to prevent. The Co-Writer drafts in your voice with the linked planner as context, so the manuscript stays consistent with the canon you've built.

Worth pairing with: How to Outline a Novel in 2026, How to Track Continuity in a Novel when it ships, and How to Write a Series when it ships, for the related workflow pieces.

A bible isn't a luxury. For most writers writing in a series or in a fantasy/sci-fi world, it's the difference between a coherent project and a five-book continuity collapse.