A story bible is the single reference document that holds everything true about your book: characters, places, rules, timeline and open plot threads. Screenwriters have used them for decades. Novelists mostly kept them in their heads — until books got long enough that memory stopped being enough.
An AI story bible is the same thing, except the AI reads it while writing. That difference is what keeps chapter 30 consistent with chapter 3.
What goes in a story bible
A useful story bible is specific enough to catch contradictions. Vague notes catch nothing.
- Characters: full name and spelling, age, physical details that recur, occupation, speech patterns, relationships, what they want, what they fear, and how they change.
- Locations: geography, distances, how long travel takes, what a place looks and smells like.
- World rules: how magic, technology, politics or the legal system work — and what they cannot do. The limits matter more than the powers.
- Timeline: when each event happens relative to the others, plus ages and seasons.
- Open threads: every question you raised and where you plan to answer it.
- Voice and tone: POV, tense, register, and what the narrator would never say.
The last two are the ones writers skip and then regret.
Why it matters more with AI than without
Without a story bible, a human writer forgets a detail and fixes it in revision. An AI does something worse: it invents a replacement and writes 2,000 confident words on top of it.
This is the "AI amnesia" problem. General chatbots have a limited context window; once your manuscript exceeds it, earlier chapters fall out of view and the model fills the gap with plausible fiction. Names drift. A character's dead brother reappears. The magic system quietly gains a new rule because the scene needed one.
A story bible the AI actually consults turns that around: instead of guessing, it looks up.
Manual bible vs AI-generated bible
There are three approaches on the market, and the difference is who does the work.
| Approach | Who maintains it | Strength | Cost to you |
|---|---|---|---|
| Manual document (Notion, Word) | You | Total control | You must update it forever, and the AI never reads it |
| Codex-style database (e.g. NovelCrafter) | You build it, AI queries it | Precise, highly configurable | Real ongoing effort |
| Automatic (e.g. YourNovel.app) | Generated as you write | Nothing to maintain | Less granular control |
The honest trade-off: a hand-built codex is more precise, because you decide exactly what the AI sees. An automatic bible is more likely to actually exist, because most people who plan to maintain a database by hand… don't, past chapter 10.
Note also that having a bible is not the same as having memory. Sudowrite offers story-bible features but does not maintain persistent memory across sessions, so context is re-established each time you sit down. YourNovel.app pairs its automatic Story Bible with Holistic Memory, which keeps the whole manuscript in play while drafting.
✍️ Ready to write the book this article is about?
YourNovel.app writes it with you — a complete, KDP-ready manuscript, with an AI that remembers your entire book. Free to start, no credit card.
How to build one that actually works
- Start before chapter 1, but keep it small. Protagonist, antagonist, setting, the central question. Half a page.
- Add entries as they appear, not in advance. Inventing 40 characters up front produces a document you never read.
- Record the specific, not the poetic. "Green eyes, chipped left incisor, says 'right then' when nervous" is usable. "Mysterious and haunted" is not.
- Write down the limits. What magic cannot do, how long the journey actually takes.
- Update the moment you contradict yourself. The bible is only true if it is current.
- Log open threads with a target chapter. This alone prevents most abandoned subplots.
Common mistakes
- Building it and never opening it. A bible you don't consult is a diary.
- Only recording appearance. Voice and motivation cause more continuity errors than eye colour.
- Letting it drift from the manuscript. If they disagree, the bible is wrong — fix it.
- Making it so elaborate it becomes procrastination. Worldbuilding can be a very satisfying way to avoid writing.
Frequently asked questions
What is a story bible? A reference document holding everything consistent about your book — characters, places, world rules, timeline and open plot threads — so you and your tools can check facts instead of guessing.
What is an AI story bible? The same document, in a form the AI reads while it writes. Instead of inventing forgotten details, the model consults the entry.
Do I need one for a short book? Under about 30,000 words you can usually hold it in your head. Beyond that, and especially across a series, a bible stops being optional.
Is a story bible the same as an outline? No. An outline is what *happens*, in order. A bible is what is *true*, regardless of order. You want both.
Can AI create the story bible for me? Yes. Some tools generate and update it automatically as you write, which removes the maintenance problem that makes most manual bibles fail.
A bible that writes itself
The best story bible is the one that still exists at chapter 40.
YourNovel.app builds and updates yours automatically as you write, and its Holistic Memory keeps the entire manuscript coherent — so the AI drafting chapter 30 still knows what happened in chapter 3. Start free, no credit card, first chapter included.