How to Build a Character Bible (+ Free Template) | Skrib

Search for a character bible template and you’ll find the same document a hundred times: two hundred questions, most of them about eye colour, favourite food, and what the character would do in a zombie apocalypse.

Writers fill in forty fields, lose interest, and never open it again. The document failed because nothing in it was doing a job.

A working character bible is small and ruthless. Every field in it earns its place by doing one of exactly two things: generating behaviour, or preventing a contradiction. If a field does neither, it’s trivia, and trivia is what makes bibles die around chapter thirty.

This article covers what to record, what to leave out, and a template built on that principle. It sits beneath our character architecture guide, which covers how to design a character in the first place - a bible documents architecture, it doesn’t invent it.

What is a character bible?

A character bible is a maintained reference document that records everything about a cast that a writer needs to stay consistent across a long or collaborative project. It’s a working system rather than a planning exercise: it’s built during drafting, updated as decisions are made, and consulted when memory fails.

That distinguishes it from the one-page design tools writers use before drafting, which exist to pressure-test a single character’s interior logic and are typically discarded once the draft is underway.

Bible, worksheet, or world bible?

Three documents get conflated constantly. They do different jobs at different stages.

The design worksheet is upstream of this document - if you haven’t established a character’s wound, want, need and contradiction, start with the architecture guide rather than filling in fields.

The world bible is a different animal entirely, and for game studios and shared universes it becomes a large piece of infrastructure. That’s covered separately in our game writing material.

When you actually need one

Be honest about this. A character bible is overhead, and overhead is only worth carrying past a certain project size.

You need one when:

• The project runs longer than you can hold in memory - roughly, past 40,000 words or 20 episodes

• More than one person writes in the world

• The work publishes serially, so errors ship before you can catch them

• The cast exceeds five speaking characters with distinct voices

• The project will pause and resume, which is most projects

You don’t need one for a short story, a spec feature with three characters, or anything you’ll finish in a month. For those, the design worksheet is sufficient and a bible is procrastination wearing a lanyard.

The two jobs every field must do

This is the organising principle. Sort every candidate field into one of two buckets, and delete anything that lands in neither.

Generative fields produce behaviour. They answer what would this person do here? The false belief, the contradiction, the thing they do when cornered. You consult these when writing a new scene.

Defensive fields prevent contradictions. They answer what did I already establish? The sister’s name, the limp, the fact that she doesn’t drink. You consult these when checking a draft.

Trivia is neither. Favourite colour generates nothing and contradicts nothing, because it will never appear on the page. Cut it.

A useful audit: for any field, ask which of the two questions it answers. If the answer is “it helps me know them,” that’s the feeling of productivity, not the fact of it.

The five sections of a working character bible

1. Identity and continuity - defensive

The boring section, and the one that saves you. Names, ages, relationships, physical details you’ve committed to on the page, and anything a reader could catch you contradicting.

The rule: record it the moment it appears in the draft, not before. A bible pre-populated with details you haven’t used is a wish list. A bible that logs what you actually wrote is a continuity check.

Include the page or chapter where each detail first appeared. When you contradict yourself in chapter forty - and you will - that reference is what turns a two-hour search into a two-minute fix.

2. Backstory - generative, with discipline

Most bibles drown here. The correction is a hard split between two categories:

Record: the formative event, and the false rule the character drew from it. One line each. This is the generative payload - it’s what tells you how they’ll behave in a scene you haven’t written yet.

Don’t record: a chronological life history. Biography is inert. A character’s third-grade teacher generates nothing unless that teacher installed the rule.

Keep a third, short list: backstory the reader already knows. In serial and collaborative work this is essential, because what’s been disclosed determines what still has surprise value.

That last distinction - what you know versus what the audience knows - is a craft problem in its own right, and Backstory Dumps vs. Earned Reveals covers how to time disclosure.

3. Voice - generative

The section most bibles get wrong by recording the wrong layer.

Writers tend to note vocabulary and verbal tics. Those are the surface, and they’re the first thing to become a tag. What actually keeps a voice consistent is recording the structural habits underneath. Specifically:

• Sentence shape under pressure. Does this character get shorter or longer when stressed? Almost everyone does one reliably.

• Evasion pattern. What do they do with a question they don’t want to answer - deflect, joke, answer a different question, go silent?

• What they never say. More useful than what they do say. A character who never apologises directly, or never uses the word “feel,” is instantly recognisable.

• Register range. How they speak to a superior versus a child versus alone.

• Two or three sample lines you’re confident in, kept as a tuning fork.

Those five items regenerate a voice after a three-month gap. A list of catchphrases won’t.

Voices drift anyway over long projects - that’s a separate and thornier problem, handled in Character Voice Consistency. And keeping five or more voices audibly distinct is its own discipline, covered in Ensemble Casts.

4. Contradiction - generative

The section almost no template includes, and the one that does the most work.

Record the second true thing about the character that sits at an angle to the first - the meticulous investigator with the chaotic apartment, the pacifist who’s alarmingly good at violence. This is what stops a bible from producing predictable characters.

A bible is a consistency device, and consistency taken to its conclusion produces cardboard. The contradiction field is the deliberate counterweight: it reminds you that the character is allowed to violate their own pattern, and specifies where.

Log two things: the contradiction itself, and the conditions under which it surfaces. A contradiction that appears at random reads as inconsistent writing. One that appears under identifiable pressure reads as a person.

5. Relationships and arc position - both

Who they are in relation to each other person, in one line each - and crucially, what each relationship costs them. A relationship with no cost generates nothing.

Then track arc position: what the character believes now, where they are relative to abandoning or entrenching in it. In serial work, update this at the end of each installment. It’s the field most likely to prevent the drift where a character quietly abandons their false belief because a plot beat needed it gone.

If arc types aren’t settled yet, character arcs explained covers the three shapes and how to identify which one a draft is running.

The character bible template

Copy this per character. Aim for one screen. If a character’s entry runs past that, you’re recording biography.

CHARACTER: [name]
Role: [protagonist / antagonist / supporting / ensemble]
Last updated: [date] · Current through: [chapter/episode]

- FOUNDATION (generative) -
Formative event:
False rule (in their voice, unspoken):
What the rule protects them from:
Want (external, observable):
Need (internal, resisted):

- CONTRADICTION (generative) -
Second true thing:
Surfaces when:

- VOICE (generative) -
Sentence shape under pressure:
Evasion pattern:
Never says:
Register range:
Tuning-fork lines:

- RELATIONSHIPS (both) -
[Name] - dynamic in one line - what it costs them:
[Name] - dynamic in one line - what it costs them:

- ARC POSITION (both) -
Arc type: [positive / negative / flat]
Believes now:
Last shift (where, what changed):

- CONTINUITY (defensive) -
Established details [+ first appearance]:
Disclosed to reader so far:
Open questions I've raised and not answered:

Medium-specific additions, only if relevant:

• Screen: casting-adjacent physical notes only where they affect story; scene-number references for continuity

• Stage: physical business and blocking habits, since voice and body carry everything

• Serial: installment number of each disclosure; running list of threads left open

• Games: behavioural boundaries - what this character would never do regardless of player input; branch-relevant states

Keeping it alive past chapter thirty

Every bible dies the same way: it stops matching the draft, so you stop trusting it, so you stop opening it.

Three habits prevent that.

Update at the end of a session, not the start. Two minutes logging what you established while it’s fresh. Retroactive reconstruction never happens.

Log decisions, not intentions. The bible records what’s on the page. Plans belong somewhere else, or the document becomes fiction about your fiction.

Keep it in the same window as the draft. This is the practical one. A bible in a separate app is a bible you consult when you remember to, which is after you’ve made the error.

Where writers get this wrong

Building it before the draft. A bible assembled in advance records guesses. Start it in chapter three, when you know who these people actually are.

Recording everything. Two hundred fields per character across an ensemble is a maintenance burden nobody sustains. One screen, ruthlessly.

Treating it as canon rather than record. If the draft contradicts the bible, the draft usually wins - update the document. Writers who treat the bible as binding start writing to the file instead of the story.

Skipping the contradiction field. A bible with no contradiction logged will, over a long project, sand every character down into their own description.

Keeping the bible next to the page

The consultation problem is mostly a layout problem. A reference document you have to leave the draft to open is one you’ll check after the mistake rather than before it.

Skrib is built around that adjacency. The Board is an infinite canvas that holds documents, sticky notes and uploaded files - a card per character, relationship lines between them, reference images attached - and it sits alongside the Draft rather than in another tab. The Library keeps every project and imported file searchable, which is what makes a continuity check take seconds rather than a scroll through forty chapters.

For serial authors and game writers this is the difference between a bible that survives the project and one that’s accurate through chapter twelve. Everything exports back out to .docx, .md, .fdx or .fountain, so the bible isn’t hostage to the tool it lives in.

Frequently asked questions

What should a character bible include? Five sections: foundation (formative event and false rule), contradiction, voice habits, relationships and arc position, and continuity details. Every field should either generate behaviour or prevent a contradiction - anything that does neither is trivia and should be cut.

How long should a character bible be? About one screen per character. Longer entries almost always mean biography has crept in, and long entries are the main reason bibles stop being maintained.

What’s the difference between a character bible and a series bible? A character bible covers the cast. A series bible is broader - format, world rules, season arcs, tone - and typically includes the character bible inside it. Writers pitching television are usually being asked for the latter.

When should you start a character bible? Around chapter three or episode two, not before. A bible built in advance records guesses about who the characters will turn out to be; one started a little way into the draft records what’s actually on the page.

Do I need a character bible for a standalone novel? Often not. Under roughly 40,000 words with a small cast, a one-page design document per character is enough. Bibles earn their overhead on series, serials, ensembles, and anything more than one person writes.