Getting Started

How to Write a D&D Backstory (One Page, Three Hooks)

A good D&D backstory fits on one page and contains three things a DM can use: an unresolved thread (someone or something from your past that can show up), a reason you adventure with strangers, and one relationship that still matters to you. That's the whole formula. The forty-page tragedy is a beloved hobby tradition and a gift to absolutely no one, including its author, whose DM read the first paragraph and skimmed the rest. We say this with love and from experience on both sides of the screen.

Write hooks, not history

Here's the reframe that fixes most backstories: a backstory isn't a biography, it's a menu of future scenes. Your DM reads it hunting for things to bring onstage. Every element that can walk through a tavern door (a rival, a debt, a mentor, an unsolved theft) is usable; every element that's fully resolved (the war ended, the village burned, everyone's dead) is scenery.

So the working checklist:

Add a flaw with teeth if your system doesn't force one (Dragonbane does, and it's right to), and a one-sentence personality hook other players can grab.

The one-page ceiling (and the one-sentence floor)

One page maximum, and genuinely: bullet points beat prose, because your DM will reference it mid-session, not curl up with it. If you love writing lore, wonderful; write it after session three, when the campaign has told you which parts of your past matter. Backstory written in play's direction always beats backstory written into the void.

The floor is one sentence, and it's a legitimate choice: "a dockworker who lies about being cursed" gives a table more to work with than three unread pages. Some of the best characters we've watched started as one sentence and grew their history retroactively, in front of witnesses.

Calibrate the tragedy

The dead-parents opening is a genre cliché because it works; it's also the most over-fished pond in tabletop. If you go tragic, leave something alive to lose, since a character with nothing left to lose gives the DM nothing to threaten. And match the table's tone (that's what session zero established): the grimdark orphan at the heist-comedy table is a mismatch no backstory quality fixes.

Last practical move: hand the page to your DM and steal from your party. The best backstory feature ever invented is a pre-existing connection to another PC, which is why half the modern systems build the question in. One shared paragraph with another player outperforms ten solo pages.

Frequently asked questions

How long should a D&D backstory be?

One page or less, bullets welcome; one sentence is a legitimate minimum. DMs use backstories as scene menus mid-campaign, and a page of hooks outperforms a novella every time.

What should a D&D backstory include?

An unresolved thread the DM can bring onstage, a reason your character adventures with a group, one living relationship worth risking something for, and a flaw or personality hook other players can interact with.

Should my character have a tragic backstory?

Tragedy works when something survivable remains: a person, a hope, a home. Total devastation reads dramatic and plays flat, because the DM has nothing left to threaten. Calibrate to your table's tone, set at session zero.

Do I write the backstory before or after making the character?

Sketch a sentence before (concept first), write the page after the sheet exists, and expand only after a few sessions reveal what the campaign cares about. Backstory grows best in play's soil.

What if my DM never uses my backstory?

Hand them a shorter version with the three hooks bolded, and say which one excites you; most unused backstories are unread ones, and length is usually why. If they still don't bite, weave it in yourself; your character can talk about home unprompted.