Skip to content

Book Wiki

Every character, location, and plotline — kept where your story actually lives

Writer Studio's Book Wiki is manual-first: you create every card, and each one stays connected to the scenes where it appears. The AI can suggest an entry — it never confirms one for you.

Download Writer Studio — free

Story bible software usually means a separate app or a pile of spreadsheets you keep syncing with your draft by hand. Writer Studio's Book Wiki keeps your characters, locations, and plotlines in one place instead — connected directly to the manuscript, not floating beside it. Every card is yours: you create and edit it, and nothing enters the wiki until you say so.

Is the Book Wiki really story bible software?

Yes, in the sense that matters: it's a structured record of your story's people, places, and threads, built to be read while you write. Every entry — character, location, or plotline — shares one spine: name, aliases, summary, description, tags, and notes. On top of that shared spine, each kind adds what it needs. A character gets a role. A location gets an optional type. A plotline gets a status. That consistency is deliberate — you learn one card once, and it works the same way everywhere in the wiki, including for any custom kind you add later.

Entry kindAdds to the shared spineLinked to scenes by
CharacterRoleAppearance (present or POV)
LocationType (optional)Appearance (setting)
PlotlineStatus — Introduced / Developed / Paused / ResolvedOrdered membership
Custom type (Faction, Magic system…)Your own text, choice, and list fieldsAppearance, if you turn it on

How do you keep track of characters without losing continuity?

By marking exactly where each one shows up, and trusting only what you've confirmed. Characters and locations use appearances — a link you set from an open scene, marking a character present or as the point of view, or a location as the setting. Open that character's card and its "Appears in" list shows every confirmed scene, so you can answer "where does this character appear?" without hunting through the manuscript. This is deliberately separate from a mention: when the editor recognizes a name you've typed, it highlights it as a candidate, but that highlight only becomes an appearance once you click to confirm it. A character can be named in passing without being marked as present — the wiki only trusts what you've said is true, which is what makes it a dependable series continuity tracker as a book grows.

Plotlines work differently, because a thread isn't something that "appears" — a scene belongs to it. You add scenes to a plotline in order, and its card shows the thread moving scene by scene as your structure changes.

Can you build your own kinds of entries?

Yes — Entry Types let you go past the three built-ins. If your story needs a faction, a magic system, an artifact, or anything else, you define a custom type with its own icon, color, and fields (text, choice, or list), and its entries get the same card, search, Trash, and AI handling as Character or Location. You can also extend a built-in type with your own field — a character's theme song, a location's founding date — without touching anything already written. Fields you don't use can be hidden rather than deleted, and hiding never loses the value underneath.

Does the AI write your Book Wiki for you?

No — it can only suggest. After reading a scene, the AI assistant might propose a new character card or fill in a field, but every suggestion lands marked "suggested" and sits apart from your confirmed entries until you act on it. Confirm it and it becomes a normal card you own; reject it and it's gone. The AI never edits a confirmed card, adds an appearance, or writes into your wiki silently — the Book Wiki stays the author's record, and the AI only ever offers.

Wiki cards live as files inside your project, right alongside your manuscript structure, so they travel with it and land in your backups. Delete one and it goes to Trash, not gone for good. And getting back to a character in the manuscript takes a click either way — the card's "Appears in" list jumps to every confirmed scene, while full-text search separately turns up every textual mention of a name or alias.

Download Writer Studio and start building your Book Wiki as you write — it's free.

Frequently asked questions

Does the Book Wiki track character relationships or story arcs?
Not as a relationship map or a Weiland-style arc tool. Each character card has a role, an optional deeper profile in the Egri tradition (physiology, sociology, psychology), and confirmed appearances across your scenes — a structured record you write, not a diagram the app builds for you.
What's the difference between a mention and an appearance?
A mention is the editor recognizing a name in your prose — a candidate, nothing more. An appearance is a link you confirm between an entity and a scene. Only confirmed appearances show up on a card's 'Appears in' list, so you always know what's real.
Can I create my own kinds of wiki entries?
Yes. Beyond the built-in Character, Location, and Plotline cards, you can define custom Entry Types — a faction, a magic system, an artifact — with your own text, choice, and list fields, and let AI suggest values only for the fields you mark AI-fillable.
Does the AI ever add or change something in my Book Wiki on its own?
No. The AI can suggest a new card or field, but every suggestion is marked 'suggested' and sits apart from your confirmed entries until you accept or reject it. It never edits a confirmed card silently.
Download Writer Studio — free