The short answer: build only what the story can spend
You need enough worldbuilding to run your plot, color your setting, and keep your promises to the reader — and not one shelf more. For a standalone novel, that usually means twenty to thirty bible entries spread across places, culture, rules, history, and language. For a two-to-three-book series, expect forty to fifty entries. For an epic series of four or more books, the honest number lands between sixty and seventy-five, and every entry still needs a scene that justifies it.
The rest of this guide shows how those numbers are set, how the one-tenth convention rations your page time, and how to tell the difference between preparation and procrastination. Read it end to end before you open a new bible document, because the cheapest worldbuilding mistake is the hundred pages of notes you never needed.
How the calculator sizes your scope
The tool takes four inputs and turns them into a bible budget. Genre decides which categories run deep and which stay shallow. Book type decides the overall size of the list. The magic-or-tech switch decides whether the rules shelf gets full treatment or a trimmed one. Manuscript length decides how many words of explicit worldbuilding the pages can carry without drowning the story.
Behind those inputs sits a simple table of starting counts. A standalone begins at eight places, six culture notes, six rules, four history beats, and two language decisions — twenty-six entries before adjustments. A series begins at fourteen places, ten culture notes, ten rules, eight history beats, and four language decisions, totaling forty-six. An epic series begins at twenty-two places, sixteen culture notes, fourteen rules, twelve history beats, and six language decisions, totaling seventy.
Genre then reshapes the table. Fantasy adds two language decisions and two history beats, because invented names and old wars do heavy lifting on that shelf. Science fiction adds three rules entries and two places, because the system and its stations, ships, or settlements carry the premise. Historical fiction adds four history beats and two culture notes while trimming one language decision, because researched accuracy replaces invention. Mystery and thriller trims two places, two rules, and one history beat, because pace punishes sprawl. Contemporary and romance trims two places, two history beats, one culture note, and settles language at a single decision, because the real world donates most of the setting for free.
The system switch trims four rules entries when the story has no magic or invented technology, floored at two. A contemporary romance does not need six system rules, but it still needs two — the unspoken rules of its small world, like who knows whose business on one street.
Manuscript length sets the spending limit. The long-standing iceberg convention holds that roughly one tenth of what you invent reaches the page, while nine tenths stays in notes. A 90,000-word manuscript therefore carries about 9,000 words of explicit worldbuilding: descriptions, explanations, rituals, travel, arguments about how things work. Everything else lives in the bible as backup you may never quote.
Each bible entry is budgeted at roughly 300 words of notes — a name, a function, two or three details, and an off-page note. Multiply entries by 300 to get the bible's weight, then divide by manuscript length. When that share passes eighteen percent, the tool raises an overbuilding flag, because preparation heavier than that ratio usually means notes are substituting for drafting.
Worked numbers: the default standalone fantasy
Take the defaults: fantasy, standalone, system switched on, 90,000 words. The base standalone list is twenty-six entries. Fantasy adds two language decisions and two history beats, bringing the total to thirty. Thirty entries at 300 words of notes each is 9,000 words of bible. One tenth of 90,000 is 9,000 words of on-page worldbuilding. The bible share is ten percent — comfortably under the eighteen-percent flag, so the verdict reads balanced.
Now change one input: flip the book type to epic series and keep everything else. The base jumps to seventy entries, fantasy adds four more, and the total lands at seventy-four. Seventy-four entries at 300 words each is 22,200 words of notes against the same 90,000-word manuscript — a bible share near twenty-five percent. The flag fires, and the advice is concrete: trim the deepest categories first and park sequel-payoff ideas in a separate book-two file.
Change a different input instead: keep the standalone fantasy but shrink the manuscript to 50,000 words with the epic-series type still selected. The tool returns its strongest signal, because an epic plan on a short manuscript cannot stage what it promises. Seventy-plus entries across a short book means each invention gets a paragraph rather than a plotline, and readers feel the thinness everywhere.
The five shelves of the bible
Think of the bible as five shelves, each with its own job. The calculator fills each shelf to a depth label — Light, Standard, Deep, or Encyclopedic — and the labels tell you where your hours should go.
Places: where scenes can only happen
Places are the locations that host action. A place earns its entry when a scene could happen nowhere else: the negotiation that only works in the glass courthouse, the chase that only works across the night market's rooftops. Generic taverns and corridors do not need entries. Distinctive stages with rules, owners, dangers, and hours do.
A standalone needs surprisingly few. Eight well-chosen places beat twenty thin ones, because each location must be introduced, navigated, and remembered by the reader. Series multiply the count because each book needs fresh stages plus returning ones that visibly change. If a place hosts no scene, strike it from the bible and spend the entry elsewhere.
For each place, record its function in one line, its owner or controller, what it costs to enter or use, what danger it holds, and what stays undescribed. The last field matters most. Readers do not need the sewer map; they need the smell, the toll, and the reason your character is down there at midnight.
Culture: how people live when nobody is watching
Culture covers values, work, food, clothing, greetings, funerals, holidays, and the thousand small frictions of daily life. New writers either skip it entirely or write forty pages of it. Both choices hurt. A story without culture feels like chess pieces moving on blank squares. A story drowned in culture reads like a textbook with dialogue breaks.
The working method is habits plus costs. Give each group one visible habit and one price they pay for it. Harbor folk who never waste fresh water will notice a visitor pouring it out — that single detail implies hydrology, scarcity, trade, and virtue without a single lecture. Six such notes outperform sixty pages of invented anthropology, because each one arrives attached to a judgment, a conflict, or a kindness.
Culture shows best through disagreement. Let two characters from different streets argue about the right way to mourn, tip, marry, or apologize. The reader absorbs both cultures in one scene and never feels taught. Any culture note that cannot reach a scene through a habit, a cost, or an argument belongs in the book-two file.
Rules of the system: powers and devices with prices
Every speculative story runs on a system — magic, invented technology, or both — and every system needs costs, limits, and edge cases. A power without a price is a plot hole waiting for its moment. A device without a limit solves whatever the writer finds inconvenient. Readers forgive invented physics. They do not forgive cheating.
Each rules entry should state what the power or device does, what it costs, what it cannot do, and one edge case the plot will test. Healing that shortens the healer's own life creates choices. Teleportation that cannot cross running water creates geography. A truth serum that fails on the practiced liar creates the climax. Six to ten such entries carry most standalones. System-driven series need ten or more, plus a page for interactions — what happens when two powers combine, contradict, or cancel.
Stories without an invented system still have rules, just social and physical ones. A locked-room mystery needs the house rules: who holds keys, which doors stick, when the generator dies. A romance needs the small-world rules: who gossips, what reputation costs, which invitations cannot be refused. The calculator floors this shelf at two entries even with the switch off, because no story runs on nothing.
History: old events that still send bills
History earns its place only when the past still charges the present. A war nobody remembers is decoration. A war whose veterans sit on the council, whose debts fund the villain, and whose orphans carry the viewpoint is load-bearing structure. Four such beats carry a standalone. Series need eight or more, because each book can detonate a different buried charge.
Write each history beat as a chain: what happened, who still profits, who still bleeds, and which character discovers the gap between the official story and the truth. The discovery scene is the point. History that no character ever questions is wallpaper, however lovingly painted.
Resist the timeline temptation. A thousand years of dynasties impresses no reader if the plot touches only the last twenty. Build backward from the story's needs: the grievance behind this negotiation, the ruin beneath this city, the law that blocks this wedding. Stop when the chain reaches events nobody alive remembers and nothing buried matters.
Language: names, terms, and flavor
Language is the smallest shelf and the easiest to overfill. Two to four decisions cover most books: how names sound in each culture, which invented terms the reader must learn, and how much flavor — accents, oaths, proverbs — seasons the dialogue. A short, consistent glossary beats a full invented tongue every time, because readers memorize five terms gladly and fifty resentfully.
Test every invented word against the confusion budget. Each new term spends reader attention, and a chapter can afford only a few. If two terms sound alike, merge them. If a term appears once, replace it with plain speech. If a name cannot be pronounced on first sight, respell it. Fantasy earns extra language depth because invented names carry world signal, but even there, discipline wins: distinct first sounds, consistent endings per culture, no apostrophe confetti.
Illustrative example one: a hypothetical standalone fantasy
Consider an illustrative hypothetical writer planning a standalone fantasy at 90,000 words with a guild-magic system. She runs the calculator and receives thirty bible entries: eight places, six culture notes, six rules, six history beats, and four language decisions, with a 9,000-word on-page budget.
She builds in shelf order. First the eight places: the glass courthouse, the night market, the drowned temple, the guildhall stairs, the border ferry, the salt vaults, the widow's kitchen, and the ash field. Each gets a scene it alone can host. The drowned temple holds the midpoint reversal; the salt vaults hold the heist; the widow's kitchen holds the quiet chapter where the protagonist learns the price of the magic.
Next the six culture notes, each a habit plus a cost: harbor folk who tithe catch to the drowned god, guild apprentices who may not refuse a direct question, mourners who burn the dead's shoes. Then the six rules, each with a price and an edge: guild magic burns the caster's memories, works only on worked materials, and fails outright on living flesh — which is why the villain's living armor terrifies everyone.
The six history beats all send present-day bills: the drowning of the temple district funds the guild's monopoly, and the protagonist's grandmother voted for it. Four language decisions keep names pronounceable and terms few: guild ranks, three oaths, coin names, and temple titles. She freezes the bible at roughly 9,000 words of notes, drafts three chapters, and lets only genuine reader confusion earn new entries. Her ending resolves every invented thread, because a standalone that leaves threads dangling reads as a broken promise rather than a sequel hook.
Illustrative example two: a hypothetical epic science-fiction series
Now consider an illustrative hypothetical writer planning an epic science-fiction series, first book 120,000 words, with drive technology, three factions, and a generation ship. The calculator returns seventy-five entries: twenty-four places, sixteen culture notes, seventeen rules, twelve history beats, and six language decisions, with a 12,000-word on-page budget and a bible share near nineteen percent — just over the flag line.
The flag is doing its job. Seventy-five entries is a multi-year construction project, and the writer must ration ruthlessly. He splits the bible physically: a book-one file with thirty-five entries and a series file with forty parked ideas. Book one gets six stations and decks rather than twenty-four, four faction-culture notes rather than sixteen, and eight drive-and-weapon rules rather than seventeen. The generation ship's twelve history beats compress to five that detonate inside book one; the other seven wait, dated and untouched, in the series file.
His on-page budget forces the hardest choices. Twelve thousand words of explicit worldbuilding across 120,000 words means most explanations must arrive as action: the drive's cost appears when the engineer pays it, the faction schism appears when a docking request is refused, the ship's history appears when a sealed deck is opened. Anything he cannot stage in book one stays in the series file, no matter how much he loves it. The epic scope survides only because book one is scoped like a series entry wearing epic clothes.
Edge cases the calculator watches for
Short manuscript with epic ambitions is the classic failure. Writers fall in love with the world and starve the book, producing seventy entries across a novella-length draft where nothing gets room. The tool answers this combination with its firmest verdict for a reason: either the book must grow or the bible must shrink, and hoping readers imagine the missing middle is not a plan.
Long standalone with series creep is the quieter failure. At 150,000 words and above, a standalone starts tempting sequel-sized invention — maps of continents the plot never visits, dynasties that never surface, systems book one never tests. The tool warns here too. Length is not scope. A long book needs deeper scenes, not wider trivia, and anything that pays off only in a sequel belongs in a separate file until the sequel exists.
Speculative genre without a system is the interesting edge. Fantasy or science fiction with the system switch off is not wrong, but it is a deliberate bet that place and culture will carry the marvel. Low-magic fantasies and near-future thrillers win this bet regularly. The calculator flags the combination so the choice stays conscious, then sizes the rules shelf at its floor rather than zero.
Contemporary settings with heavy invention signal a different confusion. If a contemporary romance needs forty bible entries, the writer is usually worldbuilding the wrong thing — inventing street names while the emotional stakes stay vague. The trimmed contemporary counts redirect effort: a handful of places, a few small-world rules, one language decision for naming consistency, and the rest of the energy into people.
Zero or missing manuscript length is not a failure at all; it is a missing input. Without a word count there is no spending limit, so the tool reports the entry list and waits. Enter the target length honestly — the draft you plan, not the saga you dream — and the budget math can do its work.
Failure modes: how worldbuilding usually goes wrong
The most common failure is front-loading: chapters of explanation before any character wants anything. Readers extend new writers about ten pages of trust. Spend it on a person with a problem, not on the grain trade. Every worldbuilding fact should arrive because someone needs it, pays for it, or suffers for lacking it — ideally all three at once.
The second failure is the uncapped magic or device. A system without costs and limits removes tension permanently, because any crisis can be solved by a new application discovered just in time. The fix is mechanical: write the price, write the limit, write the edge case, then force the climax through the narrowest gap. If the protagonist wins by breaking a rule you established, the victory must cost more than following it would have.
The third failure is trivia accumulation — entries with no scene attached. Test each entry with one question: which chapter uses this? If the answer is none, the entry is not preparation; it is a hobby. Hobbies are fine, but they should not delay drafting. Park unclaimed entries in a separate file and draft the chapters. Chapters recruit worldbuilding far more efficiently than worldbuilding recruits chapters.
The fourth failure is inconsistency, and it is the one readers punish most loudly. A wall that cannot be climbed in chapter three and is climbed casually in chapter twenty breaks the contract. The bible exists to prevent exactly this: one canonical entry per fact, updated through a dated changelog during drafting, consulted before every revision. Small bibles stay consistent easily, which is itself an argument for scoping down.
The fifth failure is sequel leakage in standalones. Unresolved invented threads — the sealed vault never opened, the prophecy never addressed, the faction introduced and abandoned — read as errors, not hooks, when no sequel is guaranteed. Resolve every thread the book opens. If a thread cannot resolve inside this manuscript, cut its opening too.
Questions writers ask next
How do I start when the blank bible intimidates me? Start with places, because locations decide which other notes the story can use. List the scenes you already know the book needs, name where each happens, and merge wherever two scenes can share a stage. The place list then dictates culture (who lives there), rules (what the place allows), history (what happened there), and language (what things are called). One shelf pulls the next.
How much map do I actually need? Enough to keep travel honest and no more. Readers check maps for two things: whether the journey time matches the plot tension, and whether the climax geography makes sense. A simple route sketch with distances and travel times covers both. Full cartography with mountain ranges nobody crosses is decoration that risks contradicting your own chapters.
Should I invent a language? Almost certainly not a whole one. Learn from the masters of restraint: a few dozen words, consistent sounds per culture, and grammar that never appears on the page. What readers experience as a language is really naming consistency plus three or four phrases repeated in emotional moments. Everything deeper is linguistics as a hobby, and it should not bill hours to the novel.
How do I handle research for historical settings? Research fills the history and culture shelves, but the same rationing applies. Collect what the plot touches plus one layer of texture around it: the food, clothing, and money of the streets your characters walk, the law that blocks their plans, the recent events their elders argue about. General background reading is welcome; only plot-adjacent research earns bible entries.
When should the bible freeze? One week before drafting begins. Up to that date, invention is free and welcome. After it, every new entry needs a sponsor — a drafted scene that fails without it, or a beta reader's confusion. Log every post-freeze change with a date and a reason, because mid-draft invention is where contradictions breed. The changelog is the difference between a living document and a slow drift into incoherence.
How do beta readers fit into scope control? Ask them worldbuilding-specific questions rather than general impressions: what confused you, where did explanation slow you down, which place or custom felt thin, what rule seemed to bend for the plot. Confusion marks underbuilt spots that need entries. Skimming marks overbuilt spots where explanation should be cut. Readers are the most honest scope instrument you own.
Where the work continues
Sizing the bible is the planning half of the job; writing the book is the other half, and that half needs a drafting space that keeps the plan visible. Co-Writer at /write is the product destination built for exactly this next step, giving you a place to turn the checklist and category depths into chapters with your bible beside the draft. Bring the frozen entry list there, work the build order the calculator recommends, and let each scene claim its entries one chapter at a time.
A closing discipline
Worldbuilding feels like writing, which is why it swallows schedules. The discipline this calculator teaches is a spending discipline: every entry costs future consistency, every explanation costs present pace, and the manuscript pays both bills. Scope the bible to the book, freeze it before drafting, spend the one-tenth budget on facts with costs and consequences, and leave the rest in notes. The world will feel bigger for what you withheld than it ever could from what you displayed.