Guides · Story bibles
How to create a story bible for a novel.
By Daniel Bentes · Published 16 July 2026
A story bible is a set of structured canon entries — one per character, location, culture, world rule, or historical fact — built so it can be checked against, not a running page of notes nobody rereads. Build it by capturing facts by kind, anchoring each one to the passage that established it, and adding only what the prose actually needs. You can start it from a premise before you've written a page, or grow it out of a draft you already have.
The method
Five moves to a bible worth rereading.
None of this requires software. It requires treating the bible as a reference you'll query under pressure, not a document you write once and hope to remember. The method is the same whether you keep it in a spreadsheet, a folder of text files, or a tool built for it.
- Treat it as a reference, not a wiki. A bible only pays for itself if you — or something reading on your behalf — can query it mid-draft: "how old is she in this chapter," "what does this substance do here," "did the Order ever hold office." A page of running notes forces a reread to find one fact. A reference built for lookup gets you the answer in seconds.
- Capture by kind of fact, not by chapter. Give characters, locations, cultures, the world's rules and systems, and its history and timeline each their own kind of entry — structured the same way every time: a name, a short description, the handful of facts that actually matter, and how it connects to everything else. One structured entry per fact, so the bible stays a set of lookups instead of one long document.
- Start from a premise, or start from a draft. Still planning? Sketch the spine first — the handful of characters, the one rule of magic or trade, the one faction that will carry the plot — and let entries accumulate as you outline. Already have pages written? Work backwards: read the draft and mine it for what it has already established, one fact at a time, instead of inventing canon that quietly contradicts what's already on the page.
- Record where each fact came from. Every entry should cite the passage that put it into canon — the chapter, ideally the line. That citation is what keeps the bible anchored to the book instead of drifting into a parallel document with its own opinions. When a fact needs to change, you can find every passage it touches instead of guessing.
- Keep it lean and living. Add only what the prose needs. A bible padded with lore the book never uses is nearly as useless as no bible at all — it takes just as long to search and rewards you less. Update entries as the manuscript grows rather than saving one big pass for the end; a bible that's a chapter behind the draft is already wrong.
Example · character entry
What a character entry holds.
For example, take Vellhark — a fogbound harbor city from a working two-volume manuscript — and Tarsil, one of its point-of-view characters. His entry isn't a biography. It's the handful of facts the prose keeps needing: his age, an injury that pays off later, and what he knows that nobody else in the room does yet. Structured this way, "how old is Tarsil in chapter nine" and "does he know about the Order yet" are both one glance away, not a reread of chapters one through eight.
- Facts, not paragraphs. A short bio plus a handful of discrete facts — age, an injury, what he knows — each queryable on its own.
- Voice, recorded once. "Speaks in clipped, unfinished sentences" keeps every later scene's dialogue consistent without a reread.
Smuggler turned reluctant customs informant. Speaks in clipped, unfinished sentences; lies by omission, never invention.
A character entry: a short bio, a handful of discrete facts, nothing the prose doesn't need.
Example · substance-and-rule entry
What a rule-bearing entry holds.
Bloodglass is a substance with a status that can change: legal in Vellhark as the story opens, restricted the day the Long Quay Customs House — the office Vessa Ondrin runs — starts seizing it, and traded quietly by the Korrith Order regardless of the order on paper. An entry like this needs the same discipline as a character's: a line or two of description, the facts that actually matter, and citations back to the passages that established each one. When a later chapter has Tarsil selling openly what an earlier one called contraband, the entry is what catches it — not memory.
- Status is a fact too. "Unbanned in Vellhark, restricted in the north" is one line the prose can be checked against.
- Established by, not just described. Cited passages anchor the entry to the manuscript, so a rule can't quietly drift.
A refined volcanic glass, faintly luminous and addictive to handle. Legal in Vellhark as the story opens — barely.
- § vol. I, ch. 7 — "Bloodglass was not banned in Vellhark. Not yet."
- § vol. I, ch. 9 — "two fingers lost to a bloodglass burn"
A rule-bearing entry: status and effect as discrete facts, each anchored to the passage that established it.
Pitfalls
Where story bibles usually fail.
Most bibles don't fail from lack of effort — they fail from shape. The same handful of mistakes show up on almost every project that abandons its bible partway through:
- The wiki nobody rereads. A bible built once and never queried is just a longer document to forget. If nothing — you or a tool — reads it back against the prose, it isn't earning its place.
- Over-detailing lore the book never uses. Three pages on a dynasty's succession law that the plot mentions once is effort spent where the reader will never look. Depth belongs where the story actually goes.
- Letting the bible drift from the manuscript. A revision changes a name, an age, a rule — and the entry doesn't get updated. From then on the bible is actively wrong, which is worse than having no bible.
- One long document instead of structured entries. A single sprawling file with everything in it can't be queried, can't be checked against automatically, and gets harder to search every chapter you add to it.
Next
Once the bible exists.
A bible answers what's already true about your book. Two problems come right after it: keeping new prose in sync with it as you draft — see how to maintain continuity in a novel — and making one bible hold up across more than one book — see how to plan a book series. If you'd rather the cross-linking happen as you type — and the checks run against canon whenever you ask for them — that's what Loreon's structured story bible is built for.
Loreon · The Writing Studio
A bible earns its keep when software reads it too.
Everything above works with a spreadsheet and discipline. Loreon's story bible holds the same structured entries — characters, locations, cultures, and the rules and history of your world — cross-links names to their entries as you type, and records the passage each fact was established by. Generate a starter bible from a premise, or import a manuscript you already have and grow canon out of the text itself. See pricing — the editor and the bible are free; credits meter only the agent work — or open the studio directly at app.loreon.ink.