Lore bible vs. character bible: which one do you need?

Most writers' first worldbuilding document is about the people. That is natural — the story is about the people — and the document it produces is usually called a character bible. It is a real and useful thing. It is also, for most fantasy, a part of the answer rather than the answer.

What a character bible holds

The facts that belong to a person: appearance, voice, wants, wounds, relationships, and the timeline of what they know. The last one is the most valuable and the most neglected — not "Serin is cautious" but "Serin learns about the siege in chapter nine, and nothing after it until book two". A scene can violate that. A scene cannot really violate "cautious".

A character bible answers the questions a character-driven draft asks: what would she say, what does she already know, what has she already lost.

What a lore bible adds

The facts that belong to no one person. The city and what it costs to cross it. The faction and why it wants what it wants. The rule of magic and its price. The history that explains why the two of them are on opposite sides of a river. The calendar, the distances, the economy — the load-bearing facts of a world, most of which no character entry owns.

A lore bible is the same structure — entries, one subject each, linked — pointed at the whole world rather than its inhabitants.

When a character bible is enough

When the world is a backdrop. A character-driven standalone, set in a few named places, with no magic system and no faction politics: the facts that could go wrong are mostly facts about people, and the people have a document. Build the character bible, keep it honest, and do not build the other one yet.

The test is mechanical: can a scene contradict a fact that no character entry owns? A journey that took three weeks in book one and four days in book three is not owned by any character. If your story has facts like that — distances, durations, prices, rules, histories — they need a home.

When you will outgrow it

Series do, by construction. Book two introduces the second city and the second faction. Book three needs the war that connected them. The facts multiply faster than the characters, and the moment they do, the character bible stops being a container: the world's facts have nowhere to live, so they live in your head, and your head is exactly where they go to drift.

The same thing happens to standalones with a magic system. A magic system is a set of rules, and rules belong to the world, not to the person who uses them. The moment the plot needs an exception, the unrecorded rule is the first thing to bend.

The relationship

They are not rivals. Character entries are a subset of the lore bible — the people are part of the world. The practical move is to start where the story is: the people, if the story is about the people. Then, at the moment the world generates a fact of its own, give that fact an entry. The document grows into a lore bible the way the world grows into a world — one invention at a time, recorded before you close the file.

Related

• What is a lore bible? — the definition and an entry template
• Building a lore bible you will actually use — the four structural habits of the ones that survive
• Lore bible examples from published fantasy — what the big series did at scale

And if the question is whether a specific scene breaks what you have already decided, the lore consistency checker checks it against the facts you list — free, no account.