A D&D backstory template your DM will actually use

By Brenn and Lindsay, the two writers who built Inkling

Your DM does not need your character’s whole life. They need a few sentences, a few people, and a few loose threads they can pull. Here is a one-page template built for exactly that, with a worked example you can copy.

We both came to the table as writers, which means we have both, at some point, handed a DM four pages of backstory and watched their eyes glaze over. It was not their fault. A backstory is not a short story. It is a set of hooks, and the best ones are short, specific and a little unfinished, so the campaign has somewhere to go.

How long should a D&D backstory be?

Shorter than you think. Sly Flourish suggests one to five sentences, with gaps left on purpose for the DM to fill. In an EN World thread about session zero, most players said they bring a handful of bullet points, and the idea of a 75-page backstory got some good-natured teasing. Our rule of thumb: a few sentences to one page. If yours runs longer, that is fine. It just becomes your version, and your DM gets the short one.

What matters more than length is what your DM expects. Some tables love a rich history; others want a name and a reason to be in the tavern. A D&D Beyond forum thread on backstory length keeps coming back to the same point: ask first, leave holes, and offer a short summary alongside anything long. The best time to ask is session zero, and our session zero questionnaire has questions that turn straight into backstory material.

What does a DM actually need from your backstory?

Think like the person running the game. Your DM is prepping situations for four or five PCs at once, so they need material they can pick up and use without rewriting your life story. Five things do most of the work:

• Hooks. Specific, pullable things: a debt, a rival, a promise, a place you can never go back to.
• Living NPCs. Two or three people who are still alive, still nearby, and still want something from you. A dead mentor is a memory. A living one is a scene.
• Open threads. Questions you do not know the answer to. Who really set the fire? Why did the letters stop? These are gifts, because your DM gets to answer them.
• A secret for the DM only. Something the rest of the party does not know yet. It lands harder when it comes out at the table.
• What is fixed and what is flexible. Mark the parts that must stay true and the parts your DM is free to change.

That last one saves a lot of friction. In a D&D Beyond thread from a player whose DM rewrote part of their history, the advice that kept coming up was simple: say which parts matter to you, and talk before the big moment. Your DM is not trying to wreck your character. They just did not know which detail was holding the whole thing up.

The orphan with no ties, and how to fix it

Every table has met this character: parents gone, village burned, no friends, no family, walks alone. We understand the appeal. It feels dramatic, and it keeps your character safe from being used against you. But it leaves your DM with nothing to pull. No one can be kidnapped, no one can show up at the gate with news, no one can ask for help. A D&D Beyond thread on making orphans better arrives at the same fix we use: keep the loss if you love it, then tie it to specific, living people and places.

• The orphanage matron who still writes to you, and whose letters stopped last month.
• The older kid who shared their bread with you and now runs a gang in the city the party is heading to.
• The fire that took the village. You saw who set it, and no one believed you.

Same tragedy, three hooks. Your character is still alone in the world. They are just not alone in the story.

A D&D backstory template you can copy

Fill this in at the short end first: one or two sentences per line. If you get stuck on a line, leave it blank and bring it to session zero as a question for your DM.

BACKSTORY FOR THE DM (one page or less)

Name and one-line pitch:
  (Who they are, in a sentence a stranger would remember.)

Where they come from:
  (One place, one sentence. Something your DM can put on a map.)

The wound:
  (What happened that still stings, and still shapes what they do.)

What they want:
  (What they would say out loud if you asked them.)

What they need:
  (What they are missing, that the campaign might teach them.)

Living NPCs (2 or 3):
  - Name, who they are to me, what they want from me right now
  -
  -

Open threads (2 or 3 questions I don't know the answers to):
  -
  -

Tie to the party:
  (Leave room for one link to another PC. Settle it at session zero.)

Secret (for the DM only):
  -

Fixed (please keep these true):
  -
Flexible (change these as you like):
  -

A quick word on want and need, because those two lines come from novel writing, not the rulebook. The want is the goal your character chases out loud. The need is what they are actually missing, and it usually pulls a little against the want. The gap between the two is where a character arc lives. You do not have to plan how it closes; that happens at the table. We go deeper in character arcs for D&D characters.

A worked example

Here is a backstory we built with the template for a rogue named Maren Quill. The town, the people and the toll company are all invented for this post, so borrow whatever you like.

Name and one-line pitch:
  Maren Quill, a river-barge pilot who can read any current
  and trusts no one who can't.

Where they come from:
  Saltmere, a toll town where the River Vash meets the sea,
  run by whoever holds the lock keys.

The wound:
  Her father's barge sank at the Saltmere lock. The lock-keepers
  called it an accident. Maren was at the tiller.

What they want:
  To buy back her father's barge license and run the river
  under her own flag.

What they need:
  To stop carrying the sinking alone, and let someone else steer.

Living NPCs:
  - Cobb Quill, her younger brother. Still pilots for the Grey Tithe,
    the toll company. Wants her home and done asking questions.
  - Old Hesk, lock-keeper. Owes Maren his life after a flood.
    Knows more about the sinking than he has said.
  - Adaya Crane, head of the Grey Tithe. Once offered Maren a job.
    Maren turned her down in front of the whole wharf.

Open threads:
  - Who opened the lock gates early the night the barge went down?
  - Why did the Grey Tithe buy up her father's debts the week before?

Tie to the party:
  Open. She would happily owe someone passage money.

Secret (for the DM only):
  Maren kept one crate from the wreck. She has never opened it.

Fixed:
  Her father is dead. Cobb is alive and loves her.
Flexible:
  Everything about the Grey Tithe. Whether it was an accident at all.

Count the hooks: a brother caught on the other side, a lock-keeper with a guilty conscience, a powerful woman Maren embarrassed in public, two open questions, and one unopened crate. That is months of material, and it fits on an index card and a half. Notice what is missing, too: no list of every town she passed through, no childhood pets. Those can come up in play if they ever matter.

Notice also that every NPC wants something right now. Cobb wants her home. Hesk wants his secret kept. Adaya Crane wants respect, or revenge. Wants are what let a DM put an NPC in a scene, because a person who wants something will act.

Write the long version for you, and the short one for the DM

If you love writing, you do not have to cut yourself off. The compromise that works at most tables is two versions:

• The “for me” version can be as long as you like: the smell of the river, the fight with Cobb, the night of the sinking told in full. Write it to find your character’s voice. It will help you play them.
• The “for the DM” version is the template above. One page or less, and every line usable.

Offer the long one, but do not require it. Some DMs will read every word; plenty will not, and that is not a verdict on your writing. The long version can keep growing between sessions if you let it, and our 30 journal prompts for between sessions are a good way to keep it going.

How to give your backstory to your DM

A backstory is an offer, not a contract. The best ones read like a list of invitations: here are the people I care about, here are the questions I have, use what fits your world. A few habits help it land:

1. Ask about the world first. Is there a faction, a town or an old war you could tie into? A backstory that fits the DM’s map gets used.
2. Send it before session zero, so your DM has time to fold your NPCs into their prep.
3. Keep the secret private. Send that line to your DM alone. The other players will enjoy finding it out at the table far more.
4. Leave room in the spotlight. Your backstory is one thread in a shared story. A hook that could pull in another PC is worth more than one only you can use.
5. Talk before the big moment. If a reveal is coming that touches a fixed part, a two-line message clears it up.

Then let it go a little. The best part of writing a backstory is watching your DM turn a line you wrote months ago into the scene everyone remembers. If the people in your character’s life start piling up, our guide on how to keep track of NPCs will help keep them straight.

How Inkling fits

We built Inkling as a writing desk, and its character cards line up with this template almost field for field: a one-line pitch, the wound, what they want, what they need, and notes for voice, quirks and relationships, which is where Maren’s brother, the lock-keeper and her rival go. Add a portrait by uploading your own sketch, a piece you commissioned from an artist, or a photo of your painted mini. Your cast stays searchable across every project, and you can export it as a Google Doc of character sheets to send to your DM.

The long “for me” version can live as a story right next to the card. When you want your DM to read it, send a private read-only link: nothing for them to sign up for, and they can leave notes in the margins.

What Inkling is not: it is not a virtual tabletop, it has no dice, and it has no stat blocks, hit points or spell slots. Keep your numbers on your paper sheet or whatever character app your table uses, and keep the story in Inkling.

Inkling is an independent writing app. Dungeons & Dragons and D&D are trademarks of Wizards of the Coast LLC. Inkling is not affiliated with, endorsed by, or sponsored by Wizards of the Coast.