What is a story bible?

6 min read · Updated October 23, 2026

A story bible is the reference file for everything that's true in your story: who your characters are, what they look like, where they live, what they know and when they learned it, how the magic or technology works, and what happened in what order. It's the place you check instead of rereading three hundred pages to find out whether your hero's eyes were green or grey.

It isn't a draft, an outline or a pitch. It's a record of canon: the facts the reader has already been told, or will be told, that the rest of the story has to agree with. Writers keep one so that chapter forty doesn't contradict chapter four, and so that book three doesn't contradict book one.

You can keep a story bible in a notebook, a word processor, a spreadsheet or a dedicated app. The format matters much less than the habit of writing facts down as they become true.

Where does the idea of a story bible come from?

The term comes from television. A long-running show has many writers, directors and departments working on episodes out of order, sometimes years apart. A show bible (also called a series bible) gives them all the same reference: the premise, the regular characters and their histories, the sets, the rules of the world, and what has already happened on screen. A new writer joining in season four reads the bible so they don't give a character a sister who was established as an only child.

Publishing has its own version. When a copyeditor works on a manuscript, they usually build a style sheet: a list of how names are spelled, which words are capitalized or hyphenated, and the story facts they need to check, such as ages, dates and eye colors. For a series, the style sheet from book one often travels to the copyeditor of book two.

Novelists borrowed both ideas. A novel's story bible is closer to the show bible in scope (characters, world, history) but often includes the style-sheet details too (spellings, invented words). For a closer look at how the terms differ, see story bible vs. series bible vs. style sheet.

What goes in a story bible?

Most story bibles cover the same core categories:

• Characters. Names, aliases and titles, physical details, ages and birth dates, family, relationships, voice, and how each one changes over the story.
• Places. What they look like, where they are relative to each other, how long it takes to travel between them, who lives or rules there.
• Groups. Families, houses, guilds, governments, religions, companies, and who belongs to which.
• Objects. Weapons, heirlooms, vehicles, anything with a name or a history.
• Rules and lore. How the magic, technology or society works, and what it costs.
• Timeline. What happened when, in the story's own calendar, including backstory that never appears on the page.
• Style details. Spellings of invented names and words, and any naming conventions.

The full checklist goes through each category and why it matters. If you'd rather start from a blank form, there's a copyable story bible template.

A good entry is short and specific. Here's what one might look like for a character in the sample series The Ashen Crown:

The chapter numbers matter. When you later find a line in book two that calls Kael's eyes grey, you can see at once which detail came first and where to look.

Who needs a story bible?

Anyone whose story is too big to hold in their head. In practice, that tends to mean:

• Series writers. The longer the series, the more you need it. By book four you're writing against details you set down years ago, and readers remember them better than you do.
• Fantasy and science fiction writers. Invented places, calendars, languages and magic systems multiply the number of facts you have to keep straight.
• Writers of big casts. Family sagas, ensemble thrillers, mysteries with a long list of suspects.
• Writers with long timelines. Anything that spans years or generations, or jumps between time periods, needs ages and dates that add up.
• Co-authors and teams. If two people write in the same world, a shared bible is how you agree on what's true.

A short standalone with five characters over one weekend may not need much. Even then, a single page with names, ages and a few physical details can save you a search through the manuscript.

What a story bible isn't

It helps to know what to leave out, because a bible that tries to be everything stops getting used.

It isn't an outline. An outline is about what will happen. A bible is about what is true. You can keep plans in your bible if you mark them clearly as ideas, but the main job of the bible is to record canon.

It isn't a worldbuilding encyclopedia. Some writers spend months documenting a world before they write a word. That can be fun, but a bible is most useful when it tracks what the story actually uses. If a detail never touches the page, it can live in a separate notes file. The worldbuilding bible guide covers how to keep the two apart.

It isn't a summary of each chapter. Chapter summaries are useful, but they're a different tool. A bible is organized by subject (this character, this place, this rule) so you can look things up.

It isn't finished. A bible grows as you write and changes when you revise. Facts can also change inside the story: a character's title, allegiance or hair color can be true for a while and then stop being true. A good bible records when each fact holds, not just the latest version.

How do you keep a story bible up to date?

The common failure is a bible that's thorough for the first ten chapters and then abandoned. A few habits help:

1. Write facts down when you invent them, not at the end of the draft. A one-line note is enough.
2. Note the chapter. Every fact should say where it was established. That's what lets you settle contradictions.
3. Note the in-story date when it matters. "Mara becomes Lady of Thornwatch on 4 Ashmoon 412" is more useful than "Mara becomes Lady of Thornwatch."
4. Do a short pass after each chapter or session. Five minutes of updating beats a week of reconstruction later.
5. Check new chapters against it. The point of the bible is to catch continuity errors before readers do.

What if the book is already written?

You can build a story bible after the fact, and many writers do, usually right before a sequel or a major revision. The approach is different: you're extracting facts from a finished text rather than recording them as you go. See building a story bible for a finished book for a reading-pass method and how AI can speed it up.

Where to start

If you're starting today, don't try to fill every category. Open a document, make a heading for each main character, and write down the details you've already committed to on the page, with the chapter for each. Add places and a rough timeline next. The bible will tell you what else it needs as you go.