What Is a Story Bible? (And How to Make One for a Novel)

The term comes from television. A writers' room needs a shared reference so that the person writing episode nine doesn't contradict the person who wrote episode two — what the characters know, where the town is, which brother is dead. That document is the show's bible.

Novelists inherited the idea, and inherited some confusion with it. A show bible is written before production, partly to sell the show. A novelist's story bible is written during the draft, for exactly one reader: the novelist, eight months from now, who cannot remember whether the inn was called the Fox or the Falcon.

Understanding that difference tells you what to put in it.

What a story bible is

A story bible is the single place where you record the facts of your fiction so that they stay the same on page 300 as they were on page 30.

It is not worldbuilding for its own sake. It is not a pitch document. It is not the novel. It is a lookup table with a memory, and its only test is whether it prevents contradictions and answers questions faster than searching the manuscript.

What goes in it

Characters

Not the full psychological profile — that's a character profile, which is a different document with a different job. In the bible you want the checkable facts: full name and its spellings, age at the story's start, family, occupation, distinguishing physical details, and the chapter of first appearance.

Plus the one thing writers always forget: what this character knows, and when they learned it. Most continuity errors in novels are not about eye colour. They are about a character reacting to information they haven't been told yet.

Places

Names, geography, and the relationships between them: how long does it take to get from the farm to the city, and by what means? Distances become plot holes faster than any other category, because travel time is the one thing readers unconsciously audit.

Lore and rules

If your world has magic, technology, politics, or religion that departs from ours, write down the constraints, not the flavour. "Magic is powered by memory" is flavour. "A spell costs the caster a specific memory, permanently, and they cannot choose which" is a rule — and rules generate plot, because they can be violated at a price.

Timeline

The spine. Every dated event, in order, including the ones that happen before the novel opens. Most of the timeline never reaches the page. Build it anyway: a contradiction in the backstory is a contradiction the reader will find.

Threads

Open questions and unfired guns. What did you promise the reader in chapter two that you have not yet paid off? This is the section that turns a story bible from a continuity tool into a structural one.

What does not go in it

• Anything you haven't decided. A bible full of speculation is a bible you stop trusting.
• Prose. If you find yourself writing scenes in the bible, write the scene in the novel.
• Everything. A bible that records every detail is a second novel you must also keep consistent. Record what recurs.

When to write it

The two failure modes are symmetrical and both fatal.

Write the whole bible first and you will spend six months building a world, feel enormously productive, and have no book. Worldbuilding is the most pleasant way to avoid writing that has ever been invented.

Write no bible at all and you will reach chapter thirty carrying two hundred facts in your head, at which point you will start avoiding scenes with the minor characters, because you can't remember what you said about them.

Build it as a byproduct of drafting. When you invent a fact on the page, record it. The bible grows at exactly the rate the novel does, and never contains a fact you haven't earned.

The maintenance problem

Every writer who has kept a story bible knows how it fails. It is a separate document. Updating it is friction. You skip it once, during a good writing day, because you are not going to break the flow to record that the innkeeper's name is Béla. Then you skip it again. Three months later the bible describes a novel adjacent to the one you are writing, and you stop opening it.

The document did not fail. The sync failed.

This is the design problem behind Narrale's Story Bible: it lives beside the manuscript rather than in another tab, and the AI reads what you actually wrote and proposes the entries — extracting characters, places and lore from your chapters, and flagging when chapter 22 contradicts chapter 3. You correct it rather than compile it.

A story bible should be the thing that remembers, so that you can be the thing that writes.

Related: How to write a character profile · Continuity errors and plot holes