How to Write a Character Backstory That Actually Helps You Play

To write a character backstory that helps play, keep it to about five sentences and answer five questions: where your character comes from, what they want, what they fear, who they owe, love or hate, and what secret they keep. Make sure at least one person from that past is still alive and still wants something, and give your Game Master the whole thing, secret included. This guide explains why short beats long, what makes a usable hook, the mistakes to avoid, three templates you can fill in and six short original examples, and ends with how backstories work in Thavernia's character builder.

The short answer: five questions, five sentences#

• 1. Where from? A place and one detail about it: "a salt-mining town where everyone coughs".
• 2. What do they want? Something that can actually happen in the story: find, repay, prove, escape, protect.
• 3. What do they fear? Something the world can test: fire, debt, being forgotten, their own temper.
• 4. Who do they owe, love or hate? A living person with a name and their own agenda.
• 5. What is the secret? One fact the other characters do not know yet, and the Game Master does.

One sentence per question gives you a backstory that fits on an index card and still contains a goal, a weakness, a relationship and a twist. That is more than most three-page histories offer a Game Master, because each sentence points forward into the story instead of backward into the past.

How long should a backstory be?#

Short, almost always. A long backstory spends its energy on things that already happened, which the table cannot play. A short one spends it on loose ends, which the table can. It is also more likely to be read: a Game Master running a group of four will remember four paragraphs, not four short stories.

There is one more reason to stay short: room to grow. A character whose whole life is fixed on paper can only repeat it. A character with blanks can discover a sister, a debt or a past life halfway through the campaign, and those discoveries are often the best moments of play.

The five questions#

1. Where do they come from?

Not just a place name, but one thing that place gave them: a skill, an accent, a habit, a grudge. "From the river city of Askaren" is a label. "From Askaren, where children learn to swim before they walk and nobody trusts a dry-handed stranger" is a character. If your Game Master has a world map, pick a real place on it; if not, offer one detail and let the Game Master fit it in.

2. What do they want?

The most important sentence. A goal turns a character from someone who waits for the plot into someone who drives it. Make it concrete and reachable within the story: "find out who burned the archive" beats "seek knowledge", and "buy back the family boat" beats "become rich". A good goal also has a reason: why now, and why this character?

3. What do they fear?

A fear is a promise to the Game Master: test me here. It can be physical (deep water, fire, enclosed spaces), social (being laughed at, being owed nothing by anyone) or personal (becoming their father, losing control). Pick something that can come up in play without derailing it, and decide roughly how your character reacts when it does.

4. Who do they owe, love or hate?

This is where most backstories fail, and where the best ones win. Name at least one person who is alive, who has their own wants, and who can turn up. A mentor who still sends letters, a rival who now works for the city watch, a creditor who is patient for now. People are the hooks a Game Master uses most, because a person can knock on the door, ask for help or betray you.

5. What is the secret?

One fact the other characters do not know. It does not need to be dark; it needs to matter if it comes out. They are not really a priest, they still have the key, they read the letter, they could have saved someone and did not. Tell the Game Master. A secret only you know is a private thought; a secret the Game Master knows is a scene waiting for its moment.

Hooks the Game Master can use#

A hook is any detail that lets the Game Master pull your past into the present. Some kinds of detail are far easier to use than others. When in doubt, write the version on the right.

Notice that every usable version contains a person or a clock, often both. You do not need many. Two good hooks are plenty for a campaign, and a Game Master would rather have two hooks they can use than ten they cannot.

Common backstory mistakes#

• The novel. Ten pages of childhood that nobody at the table will read. Keep it if you enjoyed writing it, but hand over five sentences.
• Everyone is dead. Parents dead, village burned, mentor killed, killer already slain. There is no one left to bring back, so the past can never enter the story.
• The orphan edgelord, done badly. Tragic past, trusts no one, works alone, will not join the group. The cliché is not the problem; the closed door is. Done well, the orphan has someone still alive, a question still open and a reason to need the others.
• The story is already over. The revenge is done and the treasure found. Leave the big event for play.
• The secret overlord. Secretly a lost heir, a demigod and the best swordsman alive. Power on paper leaves nothing to earn.
• A secret that breaks the group. Secretly working to betray the party ends the game for everyone else. Secrets should complicate loyalty, not cancel it.
• Plot demands. "In session three my father returns as a lich." Offer hooks, not a script; let the Game Master decide when and how.
• Hidden from the Game Master. A brilliant backstory in your notes does nothing. Share it, and say which parts you would like to see in play.

Three fill-in templates#

Each template takes about ten minutes. The first is the default. The second suits characters with a dramatic past. The third is for groups that want their characters tied together before the first session.

I come from ______, where ______.
I want ______, because ______.
I am afraid of ______.
______ is my ______ (mentor / rival / creditor / sister), and right now they ______.
Nobody here knows that ______.

BEFORE: Something happened: ______.
I LEFT: I walked away from it by ______.
STILL OUT THERE: ______ (person or thing) has not forgotten.
IF WE MEET: When I see them again, I will probably ______.
WHAT I REALLY WANT: ______.

To ______ (character): I owe you ______ / you owe me ______.
To ______ (character): We met when ______.
To ______ (character): I do not trust you yet because ______.
Shared: We all know ______ (a person, a place or an event).
GM NOTE: The part of my past I most want to see in play is ______.

Six short example backstories#

All six were written for this guide. Each is five sentences or fewer and is followed by the hooks a Game Master could pick up. Take one, change the names and the place, and it is yours.

Ketra Durmagar, dwarf fighter

Ketra kept the night gate of a mountain hold for twelve years. One winter night she opened it for a voice she knew, her brother's, and raiders came in behind him. The hold survived, but she was stripped of her post and her brother was never found. She wants to find him and learn whether he betrayed the hold or was forced to. She has never told anyone that she still carries the gate key.

• Hooks: a missing brother who may be alive; a hold that wants answers; a key that still opens something.

Tobbin Mosset, halfling rogue

Tobbin was a courier who delivered a sealed letter that started a feud between two noble houses. Both houses now believe he knows what was in it, and both have offered a reward for him. His grandmother, who raised him, still runs the family orchard and refuses to leave. He wants enough money to move her somewhere safe. He did read the letter.

• Hooks: two noble houses hunting him; a grandmother who can be threatened or visited; the contents of the letter.

Maelira Lirenhal, elf cleric

For eighty years Maelira was the healer of a river town, until a fever came that she could not stop. Half the town died, and the survivors stopped coming to her door. One of them, a girl she saved, is now a ship's captain who still writes to her. Maelira is looking for the source of the fever before it reaches another town. On the night it began, her goddess stopped answering her prayers, and she has told no one.

• Hooks: a source of the fever to find; a captain who can offer passage or need help; a silent goddess.

Hroldan Skarvold, northern barbarian

Hroldan was exiled by his uncle after losing a duel he believes was rigged. To survive the winter that followed, he made a bargain with an old woman in the sea caves: shelter, in return for one favour to be named later. His younger sister Hallvi is now heir to the hall, and their uncle rules until she comes of age. Hroldan wants to return before that day and expose the duel. He fears the favour more than he fears his uncle.

• Hooks: a favour that can be called in at any time; a sister in danger; a rigged duel and a witness to it.

Nesrava Tasrik, desert wizard

Nesrava kept the books for a great caravan house and discovered that it sold forged maps to rival caravans, sending them into the dunes to die. She fled with the ledger that proves it, helped by a smuggler she now owes a favour. Her own family runs the house, and her mother is looking for her. She wants the ledger in the hands of someone who will act on it. Some of the forged maps are in her own handwriting.

• Hooks: a ledger everyone wants; a smuggler who will collect; a mother on her trail; her own guilt.

Brannok Velamar, sea folk fighter

Brannok is the only survivor of a ship that went down in calm water. The harbour thinks he caused it, and nobody will hire him. The captain's daughter, Ondra, is the only one who believes his story about a bell ringing under the waves. He wants to find the wreck and prove what happened. He was asleep on watch that night, and he does not know what he missed.

• Hooks: a wreck to find; a bell beneath the sea; an ally who believes him; a truth that may not clear his name.

Bringing the backstory into play#

A backstory is not read aloud at the start of the first session. It leaks into the game a little at a time, and that is what makes it land. A few habits help.

• Show it in small actions. Ketra checks every gate she passes. Tobbin never opens a letter in front of anyone. The table notices long before you explain.
• Reveal one piece per session at most. A secret told in session one is trivia; the same secret in session six is a twist.
• Act on your goal. When there is a quiet moment, ask about your missing brother or the forged maps. The Game Master can only follow a thread you pull.
• Let the Game Master surprise you. You wrote that your mentor vanished. You do not decide where she is. Accept the answer the story gives.
• Update it. After a few sessions, rewrite your five sentences with what you have learned. The backstory becomes a living record instead of a fixed page.

If you play with friends online, share your five sentences with the group before the first session, minus the secret. Knowing that one character fears fire and another owes a guild gives everyone something to play with. For more on setting up a group, see how to play a tabletop RPG online with friends.

Backstories in Thavernia#

Thavernia is a fantasy tabletop RPG run by an AI Game Master. Its character builder splits the story part of a hero into separate fields, which map neatly onto the five questions in this guide:

If you would rather start from something, Generate Random Character fills in every field in your interface language, including a personality, a goal, a flaw and a backstory of two or three sentences, which is about the length this guide recommends. Edit whatever does not fit.

What the Game Master reads matters as much as what you write, so here is exactly how it works. On every turn, the AI Game Master gets a short sheet for each hero: name, class, level, gender and age, the opening of Personality (about 160 characters), Calling, Goal and Flaw (about 120 characters each), and the opening of Backstory, about the first 500 characters, cut at the end of a sentence. Ability scores, hit points and notable gear are on the sheet too. The Backstory comes with an instruction: draw on it now and then for hooks, people and places from the hero's past, never contradict it, and never recite it back. The adventure idea you write when you create an adventure, up to 500 characters, is also in front of the Game Master every turn as the campaign premise.

• Put the important part first. Anything after roughly the first 500 characters of Backstory is cut, so the most important names, hooks and the secret belong in the first few sentences. A five-sentence backstory from this guide fits whole.
• Fill in Goal and Flaw. Both are read on every turn, so a concrete goal and a flaw that causes trouble give the Game Master something to aim at.
• Lead Personality with the core of the character. Only its first sentence or two reaches the Game Master.
• Use the adventure idea for this story's hook. "Ketra, a disgraced gate warden, follows rumours of her missing brother into the lowlands" turns the backstory into the premise of this particular adventure.
• Say it in play. The Game Master reacts to what you write, and it can record lasting facts from the story as campaign memory, so a past you bring up stays known.
• AI suggestions and companions use the same fields. With AI Control set to Assistant, suggestions for your hero's next move draw on Personality, Goal, Flaw and Calling. For a hero who travels as an AI companion, Goal and Flaw shape when it speaks up, and its Backstory is used when you talk with it directly.

To try it, open the free trial: start with a ready-made hero or create your own, and play three turns with no account and no card. A free account adds 20 turns. The D&D character guide covers the rest of the sheet, and what an AI Game Master actually does explains how narration and dice are split.