Story Bible: What It Is and How to Build One

A story bible is your book's record of what's true: characters, world, timeline, rules. Here's a lean way to build one that stays useful.

A story bible is the single reference document where you keep everything that's true about your story: your characters, your world, your timeline, your rules. It exists so you never have to scroll back through sixty chapters to check an eye color or remember whether the sword was lost before or after the siege. The best story bible is not a pre-writing encyclopedia; it's a living record of what your book has actually established.

• A story bible records canon (what is true in your story), while an outline plans what happens next.
• You need one the moment your book is long enough that you can't hold it all in your head, and series and serials need one early.
• Start small: premise, cast, world rules, timeline. Add entries as the draft makes them real.
• The bible only works if you keep it current, so choose a format you will actually update.
• For long or serialized fiction, track who knows which secret and when, not just who looks like what.

What is a story bible?

The term comes from television, where writers' rooms keep a shared document so every writer treats the show's world the same way. Novelists borrowed it. For a book, a story bible is your private continuity tool: a place where a fact lives once and every chapter can lean on it.

It helps to separate three things people often blur together. An outline is a plan: the turns you intend to write. A story bible is a record: what is established and true. A series bible is a story bible stretched across several books, so that book four doesn't contradict book one.

One more distinction matters, because many search results mix it up. A pitch bible is a short, polished document (often 5 to 15 pages, according to the screenwriting site Scriptfella) built to sell a TV show to executives. What novelists need is the opposite: a messy, detailed, internal working document. If you're writing prose, ignore the pitch-deck advice.

What goes in a story bible

Most good bibles share the same handful of sections. Use these as headings and fill them only as far as your story needs.

Overview. Premise, a one-line logline, genre, tone, point of view and tense, and the kind of reader you're writing for. This is the part you reread when you lose the plot of your own plot.

Characters. One entry per person: name and nicknames, age or birthday, what they look like, how they talk, what they want versus what they need, their history, and how they relate to everyone else. A relationship list is more useful than it sounds.

World and settings. Geography, key locations, history, how society is organized, and the hard rules of anything unusual, such as a magic system or technology. Write down the limits. Rules without limits don't constrain your plot, so they can't help you.

Timeline. What happened when, including backstory, plus where each character is and how old they are at each stage of the book.

Plot and threads. Your acts or arcs, your subplots, what you've foreshadowed, and which mysteries are still open. A thread you planted and forgot is the classic reason readers write angry comments.

Style rules. Vocabulary your narrator uses or avoids, how profanity works, anything that can never be broken.

How to build one without losing weeks

The most common advice online is to fill out a fifty-question character questionnaire for every person before you write a word. Resist it. Over-planning is a trap: you burn your energy on a world you haven't tested, then lose motivation when the draft starts changing things. One craft writer at Well-Storied describes cutting more than 20,000 words of subplots that wandered because there was no clear record of what each character wanted.

A lighter path:

1. Write a one-page seed. Premise, main cast with a line each, the central rule of your world, and the ending you're aiming for.
2. Draft, then record. When a chapter establishes a fact (a scar, a debt, a law of magic), put it in the bible that day.
3. Treat the bible as canon, not wishlist. If it says something the page doesn't, one of them has to change. Decide which, and update the loser.
4. Prune. Delete what you no longer believe. Bible bloat is real; an out-of-date entry is worse than none, because you'll trust it.

Story bible for a long series or web serial

Standard guides assume a standalone novel or a trilogy. If you're writing a serial that runs to hundreds of chapters, the bible has extra jobs. Track power progression and item inventories so a hero doesn't lose a skill by accident. Track subplots that stretch across 100 or more chapters. And most important, keep a who-knows-what ledger: the reader may know a secret that a character doesn't, or the reverse, and your dialogue has to respect that chapter by chapter.

This is where a static document starts to strain. You change an early chapter, and fifty later facts quietly go stale.

Where to keep it

Any of these can work: a paper binder, a Google Doc, Notion, Scrivener, a plotting app such as Plottr, or a plain folder of Markdown files you can open in Obsidian. Plottr, for instance, starts at $15 a month or $199 for a lifetime license, according to Reedsy's review of it. The right tool is the one you'll open every day. A fancy setup you avoid is worth less than a text file you update.

Whatever you choose, make it searchable and keep older versions, so you can see what you believed three months ago.

How Novelmint handles the story bible

On Novelmint, the story bible is part of the writing workspace rather than a separate file you have to babysit. You keep notes on characters, places and world rules in one story bible that every chapter is written from, and every bible document keeps its history so you can look back at an earlier version and restore it. For a series, the cast, places and bible are shared across every book.

You don't have to type it all yourself. Describe a character, a place or a world rule, or attach an image, and Minty, the built-in AI editor, drafts an entry, checks it against what you already have, and saves it when you approve. If you have an existing bible, you can paste it into the chat or import a .txt, .md, .docx or .pdf file, and you can bring in a finished manuscript and have the cast, threads and bible worked out from it.

The part that tackles bible bloat is continuity. Ask Minty for a check and you get a list of contradictions in character facts, world rules, objects, chronology and plot logic, each tied to the beats that disagree. The Continuity check agent can read your whole book against your bible and suggest a fix for each problem, in the background while you do something else. Each chapter is also written knowing what is true at that moment in your series: who is alive, who knows which secret, how each pair of characters stands.

If you'd rather work from your own AI assistant, Novelmint connects to Claude, ChatGPT, Cursor and other AI apps over MCP, so they work from the same plan, characters and notes. Here's how that connection works. To see how the whole planning-to-publishing path fits together, start with planning a book with Minty.

FAQ

What is a story bible in writing?

It's a reference document that records everything established about your story: characters, setting, rules, timeline and plot threads. Its job is consistency, so details stay the same from the first chapter to the last.

Do I need a story bible for a single novel?

Not always. A short, tightly plotted standalone can live in your head and an outline. You need a bible once the book is long, has a large cast, includes invented rules, or turns into a series.

What's the difference between a story bible and an outline?

An outline looks forward: it plans what will happen. A story bible looks at what is already true. Many writers keep both, and the bible is the one you update as the draft establishes new facts.

What should I put in a story bible first?

Start with a one-page seed: your premise, a line on each main character, the core rule of your world, and your intended ending. Add everything else when the draft makes it real.

How long should a story bible be?

As long as it's useful and no longer. A bible you can't keep current is a liability. Prune entries that no longer match the draft.

Can AI help me build a story bible?

It can draft entries from your descriptions, import notes you already have, and flag contradictions. The decisions stay yours, and on Novelmint, nothing is saved until you approve it.

Ready to put your bible to work? Start a book on Novelmint and let your notes and your chapters stay in step.