Tabletop NPC Headcanons: Five Lines, and Why One of Them Should Contradict the Character

This page is about the version of a headcanon that has a job: the one you read out loud in the four seconds before an NPC answers a question. It is not about the ten-page backstory. Most tables never hear the ten-page backstory, and the parts of it that do surface arrive as improvisation anyway.

Why most NPCs collapse

An NPC usually fails at the table for one of two reasons, and they are opposites. The first is that the NPC is a function — a shopkeeper who sells rope and has no other quality, so the players treat the interaction as a menu. The second is that the NPC is a document: a paragraph of history the Dungeon Master wrote on Sunday and cannot recall on Thursday. Both failures have the same cause. The lines were written at the wrong level of detail for the number of times the NPC will actually appear.

Headcanon lines fix the first problem because they are small and behavioural. They also cause the second problem if you write too many of them. The number matters more than the quality.

The five-line order, and why the order matters

Build the NPC from the outside in, in this sequence:

• Quirks — something the players can observe without asking a question. A habit, an object, a way of speaking. This is the line you get to use in the first fifteen seconds, so write it first.
• Secrets — one thing the NPC is not saying. It does not need to be a plot hook. A secret can be small and private, and it is usually better when it is.
• Relationships — one connection to somebody or something already in the campaign, including another NPC the party has already met.
• Personality — how the NPC behaves under mild pressure. Not a list of adjectives; one sentence about a decision they would make.
• Backstory — last, and often never. A one-shot NPC does not need a past. A recurring NPC earns one, and by then you will know which questions the players keep asking, so the backstory you write will be the one that gets used.

The off-spec line

Pick exactly one line and make it disagree with the NPC's function. A guard captain who is afraid of the dark. A healer who does not believe in the treatment they are giving. A fence who never lies about prices. The contradiction is not a joke and it is not a twist — it is the detail that tells your players this is a person with an interior, and it costs one line to write.

Keep it to one. Two contradictions read as a gimmick, and three read as comedy, which is a different character than the one you wanted.

A contradiction is also the cheapest way to make an NPC memorable without making them important, which is what you actually want for the seventh guard the party stops on the road.

What to leave blank

Blank space is a feature, not an unfinished note. Every line you did not write is one you can invent when a player asks a question you did not plan for, and an answer invented in the moment will always fit the scene better than one written before the scene existed. Five lines and a name is a complete NPC. Twelve lines is a character sheet you will not read.

The exception is consistency. If an NPC returns in a later session, the lines you already used are now canon, and they must not change. Write down the five lines you actually spoke, not the five you planned — the spoken version is the one the players remember, and contradicting it is the one mistake a table will notice immediately.

A worked example

An innkeeper the party meets once. Five lines, written in the order above:

• Quirk — wipes the same clean spot on the bar when she is deciding whether to lie.
• Secret — the room the party was given has been paid for already, by someone who did not leave a name.
• Relationship — the town's guard sergeant eats here on the same night every week and always pays in exact change.
• Personality — she gives a straight answer to a direct question and a long story to an indirect one.
• Off-spec — she is scrupulously honest about money in a trade where nobody is.

No backstory line. Nothing about her childhood, her family, or the war. If the party returns next session and asks, the answer will be better invented at the table, and it will be consistent with the five lines above because those five lines are the only canon there is.

Which categories to use, by how often the NPC appears

• Appears once, in one scene — Quirk and one more. Two lines.
• Appears in two or three scenes — Quirks, Secrets, Relationships. Three lines, and make the secret touch something the party already did.
• Recurring, or has a name the players use — all five, in order, and only then start considering backstory.

Getting the raw lines

The Headcanon Generator on this site draws from handwritten lines in these five categories and six tones, and it is built for exactly this use: generate a set, keep the two or three lines your table can see, and throw the rest away. Turning the category filters on and off is the fastest way to make a set that fits how often the NPC will appear. Nothing you type is uploaded, so a name from your own campaign notes never leaves the tab.

If you want the version of this workflow for characters the players will read about rather than meet, that is a different page: headcanons for a recurring NPC need the same five lines plus consistency, and headcanons for a player character need the off-spec line aimed inward instead of outward.