What Is a Story Bible? (And How to Build One)
Your beta reader sends back chapter nineteen with one line in the margin: didn't you say he couldn't hear out of that ear?
You go looking. Chapter four, page two — Teodor, your protagonist's uncle, turns his head so his good ear faces the door. Chapter nineteen — he's across a crowded hall, picking a whispered conversation out of the noise. Both scenes are good. Only one of them gets to stay, and fixing it means rereading eleven chapters to find out which other moments quietly depend on him hearing things.
That afternoon is what a story bible exists to prevent.
What Is a Story Bible?
A story bible is a single reference document that records every fact you've established about your novel — characters, places, world rules, the timeline, invented vocabulary — so you can look up what you already decided instead of trying to remember it. It is not a plan and it is not a pitch. It's an encyclopedia for one book, written by the only person who will ever read it.
The Novel Smithy defines it plainly as a document used to keep track of all the worldbuilding and details in your novel. Writers in the Storm reaches for the same image: much like a set of encyclopedias, a story bible is a reference guide for your story. Both framings matter, because they tell you what the document is for: retrieval. You don't write a story bible to think. You write it so that eight months from now, at 11pm, you can answer one narrow question in twenty seconds.
Where the Term Comes From (and Why It Matters)
The story bible is borrowed from television. In screenwriting, a bible is a reference document used by screenwriters for information on characters, settings, and other elements of a television, film or video game project, written to provide consistency on key details, character development, and an accurate continuity or timeline.
TV needs one because a season is written by eight people who have to agree on whether the sheriff has a brother. Novelists assume this doesn't apply to them — one writer, one book, one brain.
It applies. Your collaborators are all versions of yourself, spread across eight months. The you who wrote chapter four in February had a clear picture of Teodor's deafness and never wrote it down, because it was obvious. The you who writes chapter nineteen in September has that picture 60% intact and doesn't know which 40% is missing. A story bible is how February leaves a note for September.
What Actually Goes In One
Five categories cover almost every continuity failure a novel can have. Writers in the Storm notes that the two most common things included in a story bible are the world and the characters, which is right — but the last three are where the ugly errors hide.
Characters. The Novel Smithy's list is a good floor: names, relationships to one another, and key physical features. Add two things it's easy to skip — what each character wants in this book, and how they talk. Voice drift is the continuity error nobody catches until a reader does: your gruff dockhand who spoke in fragments for nine chapters starts producing complete sentences with subordinate clauses in chapter twenty-two.
Places. Not atmosphere — geometry. Which side of the river the customs house is on, how long the walk is, whether the tavern has a back door, because in chapter twenty-eight somebody needs to leave through it.
Rules. Whatever governs your world and can't be broken without the reader noticing: magic costs, who has legal authority over whom, how fast news travels. These are the entries writers most often keep in their heads and most often contradict, because a rule feels like something you'd obviously remember.
Timeline. The sequence of events and the gaps between them. How old everyone is when the book opens, what season chapter one happens in, how many months have passed by the end.
Vocabulary and spellings. Every invented word, place name, rank, and piece of slang, spelled the way you've decided to spell it. The least interesting section, and the one that saves the most copyedit time.
A Story Bible Is a Lookup Table, Not an Essay
Here's where most story bibles die. A writer sits down on a Saturday, opens a blank document, and writes four beautiful pages about the history of the mining colony. It's genuinely good prose. It is also useless, because six months later the question isn't "tell me about the colony," it's "what did I name the arbiter's clerk?" — and the answer is in the middle of paragraph three on page two.
Write entries, not chapters. One fact per line. Ugly, greppable, updated in eight seconds:
Teodor Vaszary — Vesna's uncle, 58. Deaf in left ear (mining blast, 19 yrs ago). Turns head to put right ear toward speaker. Speaks in short declaratives; never uses her full name. Wants: to keep the colony's charter out of arbitration.
That's the whole entry. It takes twelve seconds to read and answers the chapter-nineteen question instantly. Storing each fact as its own record rather than burying it in a long document is the difference between updating a fact and hunting for one.
The other half of the format rule: write it in the order your story invents things, not in the order a wiki would list them. You don't need a complete cast list before chapter one. You need to add Teodor's ear to the bible the same afternoon you invent it, while you still know why it matters.
A Worked Example: Six Weeks of Entries
Priya is 38,000 words into a political fantasy set in a mountain mining colony — Teodor's book, as it happens. She started her bible in week two, not before — one entry per new element, added as she drafted. By the end of March she had 64 entries, most of them three lines long. The whole thing took maybe forty minutes of cumulative typing across six weeks.
In April she hit the scene where Teodor overhears the arbiter in the assembly hall. She wrote about 200 words before something nagged, opened the bible, searched "Teodor," and read the entry: deaf in left ear. Twenty seconds.
The scene still worked — she staged the arbiter on Teodor's right and had him lose the last third of the conversation, which turned a convenient eavesdrop into a better one. He acts on partial information for the next four chapters, and that becomes a plot thread she hadn't planned.
The alternative is the version most of us have actually lived: the contradiction ships, the beta reader catches it in September, and Priya spends a Saturday rereading eleven chapters to find every load-bearing consequence. Forty minutes of typing across six weeks against one lost Saturday and a scene rebuilt from scratch — that's the real trade.
One honest exception: if you're writing an 80,000-word contemporary with four characters and one town, a full story bible is overhead you don't need. A single page of notes will outperform it.
Story Bible vs. Outline vs. Lorebook vs. Series Bible
These four terms get used interchangeably, and they aren't.
An outline is what happens next. A story bible is what's already true. An outline is predictive and gets obsolete the moment you deviate; a bible is a record and only ever grows. If you want the planning side, that's the job of a beat sheet or Save the Cat structure — a different document with a different failure mode.
A lorebook is a story bible formatted for a machine — entries with trigger keywords, so the right facts get injected into an AI's context when the relevant word appears in your scene. Same content, different plumbing. If you're using AI to draft, how you format those entries determines whether they actually fire, and most people's first attempt doesn't.
A series bible is a story bible that survived contact with book two. The difference is discipline: it has to record not just what's true but what the reader already knows and when they learned it. Keeping book three consistent with book one is a harder version of the same problem, and it's the case where skipping the bible is genuinely unrecoverable.
Why the Story Bible Matters More If You're Drafting With AI
Because the model has no memory of your book. It sees only what's in its context window at the moment it generates, and everything outside that window gets confidently invented rather than left blank — which is why AI forgets your story details in a way that looks nothing like human forgetting. A human writer who can't remember the uncle's ear writes around it. A model fills the gap with something plausible and moves on, and the invented detail reads exactly as confident as the real ones.
That makes the bible load-bearing. Every fiction-focused AI tool has converged on some version of it: Sudowrite's Story Bible, per their own documentation, "gathers the core elements of your story in one place so that you and Sudowrite's AI can reference them as you develop your work," organized as Braindump, Genre, Style, Synopsis, Characters, Portraits, Worldbuilding, Outline, and Scenes & Draft. That's a well-designed structure, and the sequencing genuinely helps writers starting cold.
The question worth asking is where those entries live. A story bible is the most concentrated version of your unpublished book that exists: every twist, every character's real motive, the ending. NovelMage runs as a desktop app on Windows and macOS with the Codex stored locally, and you can point it at a local model through Ollama or LM Studio, or bring your own Claude, GPT, or Gemini key — so the bible can stay on your machine even while you're generating against it.
Keeping It Usable at 90,000 Words
A bible that's grown to 300 entries has the same problem as no bible at all, if you can't find anything. Two habits keep it working.
Prune at the end of each draft. Entries for cut characters and abandoned subplots are worse than useless — they're contradictions waiting to be reintroduced when you search for something adjacent.
Mark what's true versus what's revealed. For anything with a reveal, note the chapter where the reader learns it. This is the single most useful field in the whole document during revision, and almost nobody includes it.
Frequently Asked Questions
Should I write my story bible before or during drafting?
During, in almost every case. A bible written before chapter one is really an outline in costume — it records decisions you haven't stress-tested yet, and most of them will change. Start with three or four entries for your leads and your setting, then add each new fact the day you invent it. The Novel Smithy makes the case for building one during the editing phase specifically, as a cheat sheet you consult before making any change — the other high-value moment for it.
What's the difference between a story bible and a character bible?
A character bible is one section of a story bible. Some writers use the terms interchangeably because characters generate the most entries, but a bible with no timeline and no world rules will miss the errors readers complain about loudest — someone knowing a secret before they could have learned it, or two events that can't both fit in the same week.
How long should a story bible be?
However long the facts are, and no longer. A 90,000-word standalone typically lands somewhere around 40 to 80 short entries. Length is a bad target; retrieval speed is the real one. If you can't answer "what color are her eyes" in under thirty seconds, it's too long or badly organized regardless of page count.
Do I need special software for a story bible?
A plain text file or a Notion page holds the facts fine. What they can't do is hand those facts to a model at the moment it's generating — with a separate document you're pasting entries in by hand every session, and the session you forget is the session the contradiction gets written. That's the gap a built-in bible closes: NovelMage's Codex sits beside the manuscript and feeds it automatically, for a $99.99 one-time purchase covering up to 3 devices, with a 7-day free trial and no subscription.
Can I generate a story bible from a finished manuscript?
Partly. AI is good at extracting explicit facts — names, stated ages, places — from a completed draft, which gets you a usable first pass. What it can't reliably extract is intent: which contradictions are errors and which are a character lying. Treat a generated bible as a draft to correct, not a record to trust.
Start With Five Entries
Open a file today and write entries for your protagonist, your antagonist, your primary setting, one world rule, and the month your book opens in. That's ten minutes, and it's the version of a story bible that actually survives — the one you start small and feed as you go, not the one you spend a Saturday perfecting and never open again.
If you'd rather have those entries sitting beside your manuscript and feeding your AI automatically instead of living in a second window you forget to open, NovelMage keeps your Codex and your draft in the same offline desktop app — one purchase, no subscription, and your story bible never leaves your machine.