How to make a worldbuilding bible

5 min read · Updated October 23, 2026

A worldbuilding bible is the part of your story bible that covers the world itself: places, peoples, history, and the rules of magic or technology. Its job is not to hold everything you could invent. Its job is to make sure the world behaves the same way on page 400 as it did on page 4.

Fantasy and science fiction readers notice rule-breaking more than they notice almost anything else. A character who dies is a loss. A magic system that suddenly costs nothing is a broken promise. Writing the rules down is how you keep them.

Start with what's on the page

The most useful world bible begins with what the manuscript already says, not with a blank template. Go through your draft and list:

• Every named place, and what the text says about it.
• Every named group: nations, houses, guilds, religions, orders.
• Every named object that matters to the plot.
• Every rule the text states or implies about how the world works.
• Every reference to the past.

That list is your bible's core. You can add background later, but canon comes first. If your notes say one thing and the published book says another, the book wins.

Places

For each place, record the details readers will notice if they change:

• Where it is, relative to other places: "three days' ride south of Thornwatch."
• What it looks like, in the words you used.
• Who controls it, and since when.
• What happened there that the story refers to.
• Its status over time. Thornwatch in The Ashen Crown is a cliffside castle at the start of chapter one and a burned ruin by the end of it. Both are true, at different times.

Nest places when it helps: a tavern is in a district, which is in a city, which is in a kingdom. That way, when a kingdom changes hands, you know which places it affects.

Cultures, factions and peoples

Groups are where worldbuilding gets deep fast. Keep entries practical:

• Name, and what outsiders call them. The Order of the Flame might be "the burners" in a tavern.
• Who leads, who belongs, who they serve or oppose. House Thorne is led by Lord Aldric, sworn to guard the Ashen Crown.
• Customs that appear on the page: greetings, oaths, funerals, food, dress, taboos.
• Language notes: naming patterns, common words, how they swear.
• What they believe, if it drives what characters do.

Relationships between groups change over a series. Record alliances and rivalries with the time they began and ended.

Magic and technology rules

This is the section to write most carefully. Rules are promises to the reader, and most of a magic system's tension comes from its limits.

For each system, record:

• What it can do.
• What it can't do. These limits are often more important.
• What it costs. In The Ashen Crown, Emberfire is "heat drawn from grief," and every use burns away a memory. That cost is why Kael doesn't remember his mother's face.
• Who can use it, and how they learn.
• Exceptions you've already written, and why they're allowed.

Then check every scene that uses the system against those rules. A knight who calls Emberfire twenty times in a battle and remembers everything has broken the rule, unless the book explains it.

Science fiction works the same way. Travel times between systems, communication delays, power sources, what an AI can and can't do: write the numbers down once and use them everywhere.

History

Readers rarely need your full history, but your characters live in its consequences. Record:

• Eras and how years are counted. The Ashen Crown counts years After Sundering (AS), so the burning of Thornwatch is in 412 AS.
• Major events with dates: wars, founding of cities, falls of dynasties.
• What each culture believes happened, if versions differ. In-world disagreement is fine. Accidental disagreement is not.
• Anything a character remembers, so the memory stays consistent.

If your world has its own calendar, record its months, their lengths and its eras. See keeping a story timeline for how calendars affect ages and travel.

Maps

You don't need a beautiful map. You need one that answers "which way" and "how far."

• Sketch it early, even if it's boxes and arrows.
• Note distances in travel time, by each kind of travel the story uses.
• Mark which places are on which side of rivers, mountains and borders.
• Keep it consistent with the text. If chapter two says Varrow is south of Thornwatch, the map shouldn't put it east.

Items and artifacts

Important objects need their own entries. Record what they look like, what they do, who owns them over time, and where they are now. The Ashen Crown is "a crown of fused cinders that chooses its bearer." If book three describes it as gold, that's a problem. If someone carries it to Varrow, it shouldn't later turn up in Thornwatch without someone bringing it back.

How much worldbuilding is too much?

There's a well-known trap: building a world instead of writing a book. A few tests help.

• Does a scene use it? If not, it can wait.
• Does a rule constrain the plot? If yes, it belongs in the bible now.
• Would a reader notice if it changed? If yes, record it.
• Are you avoiding a hard scene? Worldbuilding is a comfortable place to hide.

A practical split: keep a canon section for what's on the page or locked in, and a notes or draft section for ideas you haven't used. When an idea makes it into a chapter, move it to canon and note the chapter.

Keep the world and the characters connected

A world bible kept separately from your character notes tends to drift. Link them. Kael Varn is a member of the Order of the Flame and serves House Thorne. Thornwatch is House Thorne's seat. When you look up any one of them, you should be able to find the others.

The same goes for the timeline. Events happen in places, involve characters and change factions. One connected bible is easier to keep right than three separate documents. For the character side, see the character bible guide. For a ready-made structure, see the story bible template.

A short checklist

Before you start a new book in the world, check:

• Every place the book uses has a location and a travel time to its neighbors.
• Every magic or technology rule has its costs and limits written down.
• Every faction's current leader and allegiances are up to date.
• Every important item's current owner and location is known.
• The calendar and current date are clear.

That's enough. A world bible that covers these, and stays current, does more for your series than a hundred pages of history nobody reads.