Backstory: how much past you actually need
Every character has a past, but not every past deserves to land on the page. Backstory is useful to the extent that it explains something about the present: why a character overreacts to an apparently small detail, why they avoid certain situations, why they want what they want. The trouble starts when the writer knows a character's past better than the reader needs to, and tries to transfer all of that knowledge onto the page.
Backstory is a tool, not a debt to pay off
Many manuscripts treat the protagonist's past as information owed to the reader: sooner or later it has to be told, and chapter two or three seems like the right spot. The result is often a block — an extended flashback or a summary — that stalls the story to give context the reader, at that point, has no reason to want yet.
Backstory works better as a tool on hand, used when it explains something happening now, not as a debt the author feels bound to pay off in full and early.
The right question: why does the reader need to know now
Before writing a scene of the past, it's worth asking what changes in the reader's understanding by knowing it at that point in the book. If the answer is "nothing specific, but it's interesting anyway," it probably isn't the moment yet — or it isn't needed at all.
Backstory that works arrives once the reader has already asked themselves a question: why doesn't she trust anyone? Why can't he ask for help? At that point the information answers a curiosity already lit, instead of creating one the reader didn't have.
Dosing instead of pouring
The most reliable technique isn't the big explanatory flashback, but dosing: a detail here, a reaction there, a line that hints without explaining. The reader assembles the picture piece by piece, and that's a more engaging experience than receiving it all at once.
A line like "he never touched his phone on Sunday evenings, hadn't for years" says more, in less space, than a paragraph explaining why. The question that stays open — why Sunday, specifically? — keeps the reader hooked more than an immediate answer would.
Trauma as a cause, not a total explanation
When the backstory includes a painful event — a loss, an abandonment, an act of violence — the risk is letting it become the only key to reading the character, as though that event explained every choice they make for the rest of the book. Real people are messier than that: they react differently depending on the day, contradict their own history, sometimes heal in ways that have nothing to do with the original event.
A painful backstory works better as one cause among others, not as a total explanation that reduces the character to "the one that thing happened to."
The flashback: when it's the right form
Sometimes the past needs to be shown in a scene, not just hinted at. In those cases the flashback is the right tool, but with two conditions: it needs the same tension and the same craft as a present-day scene — not a summary in a different key — and it needs to be anchored to a specific reason in the present that justifies it there, not elsewhere.
A flashback disconnected from the story's rhythm, inserted because "the reader needed to know," feels like an interruption even when the content is interesting.
How much backstory you really need: the next-scene test
A practical test for whether a piece of the past is necessary: ask whether, without it, the next scene would still work. If the character's behaviour stays understandable even without that explanation — mysterious, perhaps, but not incoherent — the backstory is an optional enrichment, to be dosed sparingly. If without that piece of the past the reader would lose the thread of why the character acts that way, then it's necessary, and you need to find the most economical way to give it.
Keeping characters' pasts within reach
Even when a character's past never lands on the page in full, you still need it to write consistently — to know what that character would avoid saying, which topics make them uncomfortable, what would make them overreact. In NovLore, each character's sheet in the dashboard keeps this material separate from the text: you can note down the full backstory for yourself, and decide scene by scene how much of it to let surface, without that knowledge having to translate into pages of explanation.
Frequently asked questions
Do I need to know a character's whole past before I write?
It isn't necessary, and for many writers it's counterproductive: it risks becoming time spent away from the actual story. It's enough to know what makes their reactions consistent in the scenes you're writing; you can discover the rest along the way, when it's genuinely needed.
How early in the book can I reveal the protagonist's main backstory?
Not too early. If the reader gets the explanation before they've asked themselves the question, the information carries no emotional weight yet. It's better to let curiosity build for a few chapters before satisfying it, even partially.
Does a flashback always interrupt the pace?
Not necessarily, but it's a real risk. A short flashback, written with the same tension as a present-day scene and placed where the reader genuinely wants to know what happened, can work well. The trouble starts when it's long, flat, or arrives before the reader feels the need for it.