There’s a precise moment when you realize you have a problem.
For me, it was chapter nineteen. A minor character was referencing an event I’d invented eight months earlier, and I couldn’t remember the exact date. I went looking. In a text file, then a notebook, then another notebook, then the notes app on my phone. I found it in three different places. With three different dates.
That was the day I understood what a story bible really is, and above all why almost nobody actually keeps one.
What is a story bible?
A story bible is the reference document for your world. It gathers everything you’ve invented: the characters, the places, the history, the rules, the chronology. It’s your single source of truth, the one you turn to when you can’t remember whether your heroine has green eyes or gray, or exactly what year the war broke out.
The concept doesn’t come from the novel. It comes from television.
When several screenwriters write the episodes of a single series, they need a shared document that guarantees the whole thing stays consistent. In France, the SACD even gave it an official definition, adopted in 1998: the bible is the original, foundational reference document of a series, which sets out and describes the elements needed for different authors to write the episodes of a television work.
Novelists made it their own, and they were right to. Because a lone author facing a four-hundred-page manuscript is in exactly the same situation as a team of screenwriters: they have to stay consistent over a long stretch of time, with a fallible memory.
You’re not writing as a team. But you’re writing over several months, sometimes several years. And the you of chapter thirty-two no longer holds the same memories as the you of chapter three.
Why keep one
Three reasons, in order of how much they really matter.
Consistency. It’s the obvious one, but it’s also the most painful. An inconsistency in a novel doesn’t kill the book, but it breaks something more precious: the reader’s trust. The moment they think “wait, that’s not what it said before” is the moment they step out of your world. You’ve just lost the immersion it took you three hundred pages to build.
Time. Hunting for a piece of information in your own notes is one of the most time-devouring and demoralizing activities in all of writing. A well-kept bible turns ten minutes of digging into ten seconds of looking it up. Multiply that by the number of times it happens.
Creativity. This is the reason people forget. A bible isn’t just a defensive tool against mistakes. A well-built world generates ideas. When you know how your kingdom’s economy works, the conflicts appear on their own. When you know your characters’ pasts, their reactions become obvious. The bible doesn’t just tidy your ideas away: it manufactures new ones.
What a story bible contains
Here are the main sections. Treat them as a menu, not an obligation.
The world
- Geography, maps, climates
- History and major eras
- Cultures, religions, myths
- The magic or technology system, with its rules and its limits
- Politics, economy, social hierarchies
- Languages, expressions, vocabulary
- Calendar and the measure of time
The characters
- Identity, appearance, age
- Psychology, motivations, fears
- Way of speaking (the one everyone forgets and that makes all the difference)
- Biography and past
- Relationships with the other characters
- Character arc: where it starts, where it ends
The places
- Description, atmosphere
- Hierarchy: a room is inside an apartment, which is inside a building, which is inside a neighborhood, which is inside a city
- What happened there
The structure
- Chronology of events
- What each character knows, and when they learn it
- The narrative threads in play
A word of warning, which may be the single most important piece of advice in this article: only fill in what serves your story.
If your novel takes place entirely inside a single manor, you don’t need the monetary system of the neighboring kingdom. A bible isn’t an exam to pass. It’s a working tool.
The method: where to start
This is the part most articles skip. They hand you the list of sections, then leave you staring at the blank page. But the real question isn’t what to fill in, it’s in what order.
There are two major approaches, and a third that’s the one almost everyone actually practices.
Top-down
You start from the general. A founding idea, a “what if…” question, a law that governs your world. Then you work your way down: the continents, the nations, the cities, the streets, the people.
This is the architect’s approach. It produces consistent, solid worlds. It has one formidable flaw: you can spend your whole life at it without ever writing a line of the novel.
Bottom-up
You start from a detail. A scene, an image, a character who won’t leave you alone. Then you work your way up: where does he come from, what world could have produced that scene, what rules make it possible.
George R.R. Martin began A Game of Thrones with a scene: men finding wolf pups in the snow. The genealogies, the houses, the centuries of history came afterward.
This is the gardener’s approach. It produces living, embodied worlds. It has a flaw too: without someone taking it in hand, it produces inconsistencies by the bucketload.
In practice: both
The truth is that almost nobody does one or the other. You lay down enough of a foundation to get going, you write, and the world grows richer as you write. A scene raises a question, the answer enriches the bible, the bible opens up a new scene.
It’s that back-and-forth that builds a universe. Not a perfect plan drawn up before the first line.
The iceberg theory
One question remains: how deep to dig?
Hemingway answered it in 1932, in Death in the Afternoon. He wrote that the dignity of movement of an iceberg is due to only one-eighth of it being above water.
Applied to your world: the reader will only ever see one-eighth of what you’ve invented. The other seven-eighths aren’t wasted. They’re what gives weight to the visible eighth. It’s because you know how years are counted in your world that a simple date, dropped into a line of dialogue, will ring true.
But the image carries its own trap too, and Brandon Sanderson pinned it down well: the iceberg has to actually be there, under the water. An eighth floating on its own, with nothing beneath it, fools no one. And conversely, seven-eighths submerged that never once break the surface are no use either.
Build deep. Show little. But show.
Three examples worth a whole method
Tolkien, or the world in service of the language. People think Tolkien invented languages for his world. It’s the other way around. He invented a world for his languages. He said so himself: the stories were made to provide a world for the languages. The Silmarillion is, literally, the story bible of Middle-earth, published as is.
Herbert, or the world as a system. Frank Herbert didn’t just invent a desert planet. He wrote an entire appendix devoted to the ecology of Dune, where we learn that terraforming Arrakis would take between three hundred and five hundred years. That figure isn’t decorative: it structures the whole plot, because it gives the Fremen a patience measured in centuries. A believable world isn’t an accumulation of details. It’s a system whose consequences you’re willing to live with.
Television, or the bible as discipline. Series work because someone wrote the document that lets others write. The bible for The Wire was the pitch David Simon presented to HBO in September 2000, with the characters, the world, and the arc of an entire season. Nothing magical: rigor put down on paper.
The mistakes that kill a story bible
The info-dump. You’ve invented three thousand years of history, and you want to tell all of it. Don’t. The reader wants a story, not an encyclopedia. Context should surface, not pour out.
Worldbuilder’s disease. Six months designing a monetary system, three calendars, and twelve dynasties. And still not a first line. It’s procrastination disguised as serious work, and it’s all the more insidious because it feels like progress. Set yourself a limit, then write.
Magic without limits. If magic can do anything, nothing is at stake anymore. The reader knows a solution will turn up. Magic that has a cost, rules, impossibilities—that’s magic that creates tension instead of dissolving it.
Realism instead of plausibility. Your world doesn’t need to be realistic. It needs to be consistent with its own rules. That’s a very different thing, and a more demanding one.
And the worst of all: the stale bible. This one deserves that we stop and look at it.
The real problem: keeping your bible alive
Nobody fails at starting a story bible. You fail at keeping it.
Here’s how it always goes. You create your sheets with enthusiasm. You fill them in. You’re proud. Then you sit down to write, and writing does what it always does: it changes things. A minor character grows in importance. A rule of magic evolves. A date shifts because it suited the scene better.
You tell yourself you’ll update the bible later.
You don’t. Nobody does. Not out of laziness, but because the natural motion of writing is to push forward, not to double back to maintain a side document.
And twenty chapters later, you’ve got the worst of both worlds: a bible that exists, that you trust, and that’s wrong.
It’s the problem that neither Word, nor Notion, nor a binder full of sheets solves. They give you a place to store information. They can’t know that your text has changed.
A word about the tool I ended up building
You’re on the Grimoire blog, so you can probably guess what’s coming. Let me just say it plainly: this problem is exactly the one that led me to code my own writing software. (The full story is behind the scenes, if you’re curious.) Take what follows for what it is: the way I solved the problem for myself.
The starting idea was simple: what if the story bible didn’t live next to the manuscript, but with it?
In practical terms, in Le Grimoire your manuscript is organized in the Codex (parts, chapters, scenes). Alongside it, you have your character sheets (identity, psychology, way of speaking, biography) and your location sheets, which handle the real hierarchy: a room belongs to an apartment, which belongs to a building, which belongs to a neighborhood.
The timeline holds the dated events, and the fictional calendars let you build your own measure of time: your months, your seasons, your festivals, a ten-day week if your world calls for it. Once activated, that calendar becomes the reference for the whole application.
The Constellation displays your characters and their relationships in 3D: each character is a star, each link a line of light. At a glance you see the camps, the loners, the knots of tension.
And above all, there’s scene analysis. You write your chapter. The AI reads it, and extracts what it contains: the characters present, the places, the relationships that have just shifted, the events to place on the timeline. It offers to create or update the corresponding sheets. Nothing is created without your approval.
That’s the point that matters: the bible fills itself from the text, not the other way around. It can’t go stale, because it’s fed by what you actually write.
A principle I set for myself on day one, and won’t compromise on: the AI in Le Grimoire assists, it never writes in your place. It’s a world secretary, not a ghostwriter. It files, it links, it flags what’s off. Your prose stays yours, entirely.
Le Grimoire runs locally on your machine, with a lifetime license or a subscription, whichever suits you. If the idea speaks to you, the trial is free and no strings attached.
To close
A story bible isn’t a masterpiece to contemplate. It’s a workbench.
Start small, with what your story needs today. Dig deep where the story takes you, and leave the rest under the water. Write, and let the world grow with the text.
And above all, find a way to keep it alive. Because a bible that lies is worse than no bible at all.
Me, it took eight months and a whole piece of software to get there. I hope you’ll manage faster.