How to Write a D&D Backstory: A 5-Step Method With Examples

Backstories tend to land in two ditches: a shrug (“soldier, wandered off”) or a thesis you’re emotionally attached to but nobody can remember. The sweet spot is smaller than you think: a toolkit your DM can steal from, a compass for you in scenes, and a believable reason you’re here with these people.

You’re not auditioning for a spin-off. You’re giving the campaign something to pull on.

This guide gives you five building blocks, a fill-in template, a worked example and a list of pitfalls. If you haven’t picked your class and background yet, start with how to build your first D&D character.

Chibi adventurer writing a backstory with memory bubbles

Step 1: A reason the road called, now

Why leave the old life now, and not five years ago? Exile, grief, curiosity, debt, a mistake. Make it specific enough to picture.

The second version is a scene your DM can echo later: the brothers, the fire, the question nobody has answered.

Step 2: One relationship with teeth

A mentor, sibling, captain, creditor or rival: one person you’d actually answer a letter from. You don’t owe a family tree; you owe a face the story can bring back.

Good relationships have tension built in. A mentor who’s proud of you is nice. A mentor who’s proud of you but secretly sold you out to pay a debt is a campaign arc.

Step 3: A secret or a wound

Not always grim. Maybe shame, a hidden skill, a belief that will chafe the party, a kindness your character is embarrassed by. This is the stuff roleplay bites.

Decide whether your secret is known to you (the player) but hidden from the party, or a mystery even to you that the DM can fill in. Tell your DM which.

Step 4: A goal that fits this campaign

Not a twenty-year prophecy. A now goal: pay someone back, find someone, clear a name, earn a place to rest. The DM can aim hooks at it, and you always have a direction when the party asks “what next?”

Check the campaign pitch first. A goal of “sail the open sea” in a campaign set in one underground city will sit unused.

The most overlooked step. Give your character a reason to say “we” instead of “I”: a shared employer, a debt to another character, a common enemy, or just a sense that this group is the first that ever trusted them. Coordinate with one other player if you can. Two characters who already know each other give the first session an instant scene.


Use your background as the frame

Your D&D background already answers “what did I do before this?” Build on it instead of contradicting it:

BackgroundBuilt-in question to answer
AcolyteWhich temple, and why did you leave it or get sent out?
CriminalWho did you work with, and who do you still owe?
Folk HeroWhat did you do that made people notice you, and who resents it?
NobleWhat does your family expect from you, and what are you avoiding?
SageWhat question are you trying to answer, and who else wants that answer?
SoldierWhich unit, which war, and what happened that still bothers you?

The 2014 Player’s Handbook also gives each background tables for personality traits, ideals, bonds and flaws. Rolling or picking one of each is a great way to get unstuck.


The fill-in template

Try this paragraph scaffold, then stop:

[Name] grew up [short origin]. Until [inciting event], life looked like [routine]. After that, [how adventuring happened]. Now they chase [current goal] while carrying [complication]. The person who still pulls their sleeve is [relationship]. They don’t know [open question].

The last sentence matters most. It’s the door you’re leaving open for your DM.


Worked example: from shrug to hooks

Before: “Tamsin is a half-elf rogue. Her parents died, so she grew up on the streets and became a thief. She’s very good at it and doesn’t trust anyone.”

Nothing here is wrong, but there’s nothing for the DM to use. The parents are gone, the streets are generic, and “trusts no one” fights the party game.

After:

Tamsin grew up in the dockside wards of a river city, picking pockets for a fence called Old Marrow, who fed her and never asked about her parents. Three months ago, a job went wrong: Tamsin lifted a sealed letter from a merchant, and the next morning the merchant was found dead. Marrow vanished the same night. Now Tamsin wants to find Marrow and learn who the letter was meant for, while keeping the guard from connecting her to the murder. She still has the letter. She hasn’t been able to read the cipher.

What the DM now has:

That’s about 100 words, and it could carry a whole campaign arc.


What usually hurts more than it helps

World-shaking chosen-one arcs are hard to share the spotlight with, and hard to integrate without making every plot about you.

Lone-wolf isolation reads cool on paper and fights the party game in practice. You can be guarded; still choose to travel with these people for a reason.

Over-explained timelines leave no air. Gaps are invitations for you and the DM to discover who you become.

Fully resolved pasts offer little friction. If the villain who burned your village is already dead, there’s nothing left to chase. A sore spot that still twinges creates play.

Dead family as the whole hook. Very common, rarely useful on its own. If you go this route, leave something unresolved: who did it, what they took, who survived.

Secrets that only make sense if the DM rewrites the world. “My father is the god of thunder” needs a conversation, not a surprise.


Talk to your DM before you fall in love with a draft

Your backstory meets their world first. Ask:

Offer threads, not locks: “My parent owed the Merchants’ Guild” hands them faces and pressure without scripting outcomes. If you’re in a session zero, that’s the perfect place to compare notes with the other players too.


Backstory checklist

Before you hand it in, check:


Make the past visible in play

Drop it into dialogue without explaining the whole story: “This village quiet reminds her of home before the river rose.”

Choose against efficiency sometimes when values clash. That’s interesting tension, not bad play.

Flag connections when something at the table brushes your history, so the DM can weave it in.

Let it grow. Session twenty you shouldn’t be identical to session one. Backstory is soil, not a cage. For turning all this into in-character choices, see how to roleplay your D&D character.


A line to hold while you write

Give your DM two doors to open, not a mansion to tour.

If you can name those doors out loud, you’re ready for session one.

Frequently asked questions

How long should a D&D backstory be?

One to three paragraphs is enough for most campaigns, roughly 150 to 400 words. Your DM needs a few clear hooks, not a full life story, and a short backstory leaves room for the campaign to fill in.

What should a D&D backstory include?

A reason your character became an adventurer now, at least one important person still in their life, a secret or unresolved problem, a goal they can pursue in this campaign, and some reason to travel with the rest of the party.

Should I give my character a tragic backstory?

You can, but tragedy alone isn't a hook. Make sure something from the past is still unresolved, such as a culprit still at large or a debt still owed, so the DM has something to bring back into the story.

Do I need to write a backstory before session one?

A short one helps your DM tie you into the opening, but many players start with just a few sentences and expand after a few sessions once they know the character better.

Can my backstory change during the campaign?

Yes. Leaving gaps lets you and your DM discover details during play. Just check with your DM before adding something big, like a secret sibling who rules a kingdom.

Useful at the table

As an Amazon Associate we earn from qualifying purchases, at no extra cost to you. More about this.

← All articles

Free: Class Quick Reference

All 12 Player's Handbook classes on one printable page each: levels 1 to 5, subclasses, a standard array and the mistakes new players make. Leave your email and the 12-page PDF is yours, plus the occasional new guide.