AI for Worldbuilding and Series Bibles: Documented Features and a Method That Outlasts Any Tool

Novelcrafter, Sudowrite and Claude each document a way to store world details where an AI can read them: a Codex, a Story Bible, and Projects. Whether any of them keeps a long series consistent is not something we can claim, so the safest method is to keep the canon in files you own and let the tool read copies.

NarratedIndie drafts its pages using Claude, one of the tools discussed here. See our AI use policy.

How each tool stores a series bible

The tools differ most on two questions: how a fact is shared across books, and whether a fact can stay hidden from the AI until the right point in the story. This table reports each vendor's documentation as read on 2026-11-08. It says what is offered, not how well it works.

• Sudowrite. The Story Bible docs describe it as gathering "the core elements of your story in one place" as a source of truth for the AI, and the Series Support docs say a change to a Character or Worldbuilding card is reflected across every book in the folder. That cuts both ways: an edit made for book three also changes what book one sees. The same page warns against moving a removed project back into its series, because near-duplicate cards can return. The Story Bible page adds that Scene and Draft generation "will only look at explicitly mentioned" Characters and Worldbuilding elements. Characters, Outline and Worldbuilding export as .csv per the export docs. Read the Sudowrite review for limits.
• Novelcrafter. Its help docs describe the Codex as a tool to "track characters, locations, and worldbuilding details", and the Series Codex shares entries over every book in a series. Progressions exist so that a scar or a new job does not reach the AI too early. Codex Tracking sets when an entry is sent to the AI, with "include when detected" as the default. Matching ignores capitals unless you change that, which matters for a character called Will. The software is priced separately from the AI, which uses your own key on Hobbyist and above, and its pricing page marks Universes as planned; see the Novelcrafter review.
• Claude Projects. Projects are workspaces with their own chat histories and knowledge bases. You upload documents and set instructions. Free users get five, and expanded knowledge handling is on paid plans. The page also describes a beta new version that is rolling out in stages. See Claude for novelists.
• Dedicated planners. Plottr's home page describes a series bible where one project holds all books, characters, places and notes, and Campfire's free plan lists limits of 25,000 manuscript words, 10 characters, 20 timeline events, 2 maps and 5 locations (both as read on 2026-11-08). See best outlining software.

For how the three structures differ on billing and training, see Sudowrite vs Novelcrafter vs Claude.

A series bible template you can copy

The template is a single spreadsheet with one fact per row, which any tool can read a filtered copy of. These rows are invented, for a fantasy series that does not exist.

What each column does:

• ID lets you cite a fact in a margin note, a change log or a question to a tool.
• Type lets you filter. Useful types are rules, characters, places, timeline, objects, factions and language.
• Status separates canon from what is still open, so an unresolved idea never gets treated as settled.
• Established gives you a book and chapter to check. A line you can check beats a paragraph you cannot.
• Changes at records a deliberate change. In the invented siege row, the contradiction is the plot, and without this column it looks like an error.
• Who knows catches the most common leak in a mystery or an epic, where a character acts on what only the reader knows.
• Reveal from is the column no tool can work out for you. It says when a fact may safely appear, and it decides what goes into the copy you hand to an AI.

Add two small sheets. A change log records the ID, the old value, the new value, the date and why. An open questions sheet holds what is undecided, so it stays out of the canon.

Moving the template into a tool

Export a filtered copy for the book you are working on, and leave the master alone. These mappings are our suggestions, built on the features documented above.

Two import details are useful for a spreadsheet master. Sudowrite's Worldbuilding docs say a .csv upload skips AI entirely, treating each row as an element, each column as a trait and the first row as headers, and that importing Worldbuilding does not use credits. Pasted or uploaded text goes through AI instead, with a limit of 60,000 words and 30 elements at a time.

Keep the copy small. Novelcrafter's description guidelines advise starting with the smallest Codex that does the job, keeping spoilers out of entries, and moving physical descriptions to notes unless you want the AI to mention them, because it tends to latch on to vivid details. That is one vendor's advice about its own tool, and we have not measured it.

A method for a series bible

The method works whatever tool you pick.

1. Keep one master file you own. A plain document or spreadsheet, not a vendor workspace.
2. One fact per line, with a book and chapter. For example "Mara's left hand is scarred (book 1, ch 4)". Lines you can check beat paragraphs you cannot.
3. Separate canon from drafts. Mark what is settled and what is still open.
4. Add a changes log. When you change a fact, record what, when and why.
5. Paste or sync a trimmed copy into the tool and update it when the master changes.
6. Check AI output against the master. Treat every contradiction as the tool's error until you confirm it.
7. Export regularly. Use the formats in the docs above so the bible survives a cancelled plan. Sudowrite's docs list no export for Braindump, Genre, Style, Synopsis or Scenes, so copy those by hand.

A canon check you can run yourself

We have not run this, and the planned test on this site has not happened. It gives you your own evidence before you commit a series to a tool, and it costs one short session.

1. Choose ten facts from your bible, including two that change over time and two marked secret.
2. Load the trimmed copy into the tool, with one secret left out.
3. Ask ten plain questions, such as "how long did the siege of Harrowgate last, and according to whom?"
4. Mark each answer right, wrong or invented. Treat an answer about the omitted secret as invented.
5. Repeat after adding a further chapter or two of text, to see whether the answers hold.

Use a small fictional sample if you are not ready to upload your manuscript, and read the vendor's training statement first.

Who should and should not do this

Use a tool-held bible if you want the AI to draw on your world while you draft. Keep it lightweight if you write alone and remember your canon, and leave AI out entirely if you do not want AI-generated prose. A short standalone novel rarely needs the full template; a few rows per major character and rule will do. KDP's page covers text, images and translations an AI tool creates for a book you publish; it does not mention worldbuilding notes you keep outside the book. If AI-written bible text ends up in the manuscript, the AI-generated definition applies, as the KDP disclosure guide explains. If a Story Bible workflow appeals, you can look at Sudowrite.

More tools and guides are in the AI drafting tools hub.

Last verified 2026-11-08. Rules and prices change: check the linked primary page before you rely on this.