What is a story bible and why do web fiction writers need one?

Long-form web fiction lives or dies on canon consistency. Readers who binge 200,000 words in two weeks remember details the writer wrote 18 months ago. The story bible is the only practical defense.

What goes in a story bible? A functional story bible has six sections. Characters (one entry per named character with description, motivation, and current location). World rules (the laws of magic, technology, or social structure that the story has committed to). Magic or power system (specifically the constraints; what cannot be done is more important than what can). Locations (with relative geography). Timeline (events with chapter references). Open threads (plot threads introduced and not yet resolved).

Is a story bible the same as brainstorming notes? No, and this is the most common mistake: treating the bible as a writing aid instead of a tracking aid. The bible is not where you brainstorm. It is where you record what you committed to once a chapter is published. Brainstorm in a separate document.

When should you update it? Update the bible the same day you publish, never in batches. Writers who batch updates miss a lot of canon details by the time they get around to it. The discipline of "write chapter, publish chapter, update bible, close laptop" is what makes the bible reliable at chapter 80.

How does a story bible work for LitRPG and progression fantasy? Note when each fact changed, not just what is true now: "Silver rank from chapter 9" is far more useful than "Silver rank". Stats, ranks, and titles are exactly where readers catch slips. See the LitRPG writing guide for how to structure a system that stays consistent.

What tool should you keep it in? Searchability matters more than structure. Use a tool that lets you search across all entries in one keystroke (Notion, Obsidian, Scrivener, or a dedicated tool such as PlotWrite's Story brain, which builds its pages from the chapters you have already written and lets you approve every fact). A beautiful nested folder structure that requires three clicks to find a character's eye color will not be opened during the rush of a chapter draft.

How often should you audit it? At 100,000 words, audit the bible against the published chapters. Reread the bible top to bottom and check three to five canon details against the actual text. Errors at this stage are cheap to fix. Errors at 400,000 words require chapter rewrites or awkward retcons that readers notice. For a fuller habit list, read how to avoid canon mistakes in long serials.