A worldbuilding bible records the rules and facts of an invented setting so they stay consistent: how the magic works, who rules what, how far it is between two places, what year it is.
Like "story bible", the term is practitioner jargon with no authoritative definition anywhere I could source. So this page describes a working method rather than a standard, and says so.
The distinction that makes one useful: record what the book has committed to, not everything you have imagined.
Two Different Documents
Worth separating, because conflating them is what turns this into a time sink.
Invention is generating the world: histories, languages, cosmology, the shape of the money. It is creative work, it is often the reason people write fantasy, and it has no natural end.
Reference is recording what the manuscript has already established so you do not contradict it. It is bookkeeping, it is finite, and it is what this document is.
A worldbuilding bible that contains four centuries of history none of which appears in the novel is an invention document. That is fine, but it will not stop you giving a character the wrong eye colour in chapter nine, and stopping that is the job.
The practical filter: if the book has stated it, record it. If the book has not, you are still inventing.
What Goes In
Rules and their limits. How the system works, and more importantly what it cannot do. Costs, exceptions, who can and cannot use it. Limits are what a reader tests and what a plot exploits, and they are the part most often left vague and then contradicted.
Geography and distance. What is where, how long travel takes, what is north of what. Travel time is a frequent contradiction because it is rarely written down and constantly implied.
Political and social structure. Who holds power, over whom, and how that is enforced. Names and titles with exact spellings.
Chronology. The calendar, what year it is, how long ago the founding war was, how old everyone is now.
Vocabulary. Every invented term with its exact spelling, capitalisation and plural. This is where errors enter most reliably, because a coined word typed from memory forty times will not be typed identically forty times.
Names of everything. People, places, houses, ships, gods. Spelled once, thereafter copied.
What the Editorial Bodies Contribute
The one part of this with real sourcing is the mechanics half, which professional standards call a style sheet. IPEd defines it as a list "developed by an author while writing or an editor during an edit, detailing points of editorial style", and Editors Canada requires copy editors to develop one covering things like "abbreviations; treatment of numbers; vernacular usages".
For an invented world that means recording your own conventions: whether "the Dawnlands" takes a capital D mid-sentence, how you render a term's plural, whether ranks are capitalised. An editor will otherwise decide these for you, and their decision may not match what you had in mind.
Fuller treatment in what to include in a story bible.
Keeping It Honest
Record decisions, not intentions. "Magic costs the user memory" belongs in it once the book says so. Before that it is a plan, and plans change.
Note where each fact was established. Knowing a rule appeared in chapter four means you can check what you actually wrote rather than what you remember writing.
Update it during revision, not only during drafting. Most contradictions are introduced by editing: a cut scene that established a fact, a renamed character, a moved chapter.
Let it stay incomplete. A bible that only covers what the book has committed to will have gaps, and the gaps are where you are still free.
What Deckle Does
The Codex holds this, with entries grouped by type and fields you define yourself. Since no authority specifies what a worldbuilding bible contains, a fixed schema would be inventing a standard; user-defined fields put the schema where it belongs.
Practically, that means you can create a "Magic system" type with fields for cost, limits and who can use it, and a "House" type with fields for seat, sigil and allegiance, rather than forcing everything into a generic notes box.
Three things make it work as reference rather than as another document to maintain:
It lives inside the project, so it cannot drift away from the manuscript or migrate separately.
The Timeline handles chronology, which a flat list handles badly. Events sit in story order regardless of the order they appear in the book.
Search across the manuscript is how you find every place a term appears when you need to check whether the world stayed consistent. See finding and replacing text across your manuscript.
For the consistency problem this exists to solve, see how to catch continuity errors.
Common Mistakes
- Recording what you imagined rather than what you wrote. Only the second is reference.
- Building it before the book. Invention has no end; reference is finite.
- Leaving the rules vague. Limits are what plots exploit and readers test.
- Not writing down travel times. They are constantly implied and rarely recorded.
- Skipping spellings of invented words. They will vary. Reliably.
- Not updating it in revision. That is when most contradictions are introduced.
FAQ
Q: Is there a standard format for a worldbuilding bible? A: No. The term has no authoritative definition in any source I could find.
Q: How much detail should it have? A: Enough to keep the book consistent. Anything beyond that is invention, which is a different activity.
Q: When should I start? A: As soon as the book establishes something you would otherwise have to look up.
Q: Is worldbuilding the same as this? A: No. Worldbuilding invents; this records what the manuscript has committed to.
Q: Do I need one for a contemporary novel? A: Less of one, but the same continuity problem applies to real places, jobs and family relationships.