How to write flashbacks that work
· The StoryProp team
A flashback asks the reader to stop caring about what is happening and start caring about what already happened. That is a real cost, and most flashbacks never pay it back. The reader was leaning forward; now they are being asked to lean back. Whether they follow you depends almost entirely on whether the present scene made them hungry for the past, or whether you simply decided it was time they knew. This is a craft question with a small number of moving parts: when you cut, where you cut, how you signal the cut, and what the past scene is actually doing while the reader is inside it. Get those four right and flashbacks stop feeling like interruptions. Get them wrong and you have written a very polite lecture with quotation marks in it.
The reader has to want the past before you give it
The most reliable rule I know is this: a flashback works when the present scene has generated a question the past can answer, and fails when the writer has generated a question the reader has not yet thought to ask.
Consider a scene where Mara is standing in her mother's kitchen holding a chipped cup, and Daniel asks whether she wants to keep anything from the house. She says no. Then she does not put the cup down. She carries it into three more rooms while they argue about the furniture.
Now the reader wants the past. They are not being told the cup matters; they have watched it matter. A flashback here is not an interruption — it is the release of a pressure the present scene built. If instead the book had opened with Mara as a child at that same table, the cup would have been a fact the reader was asked to file away. Facts filed away are forgotten. Questions held open are not.
So the practical test before you write the cut is to name what the present scene has made unbearable. If you cannot do it in a sentence, you are not ready to leave; the past is not owed a hearing just because it exists. There is a second version of this test that catches subtler failures. Ask what the reader would guess if you gave them nothing at all. If their guess is roughly right, the flashback is redundant — you are confirming rather than revealing. Redundant flashbacks are the ones readers learn to skim, and readers who skim your flashbacks will skim the one that counts.
Placement: never cut during momentum
The past can be interesting and still be badly placed. A flashback dropped into a scene that is accelerating does not enrich the acceleration; it kills it, and the scene rarely comes back at the same speed. Momentum lives in unresolved physical or interpersonal pressure: someone is about to arrive, an argument is two lines from breaking, a decision is being made this minute. Cutting away from any of those is a promise that the detour is worth more than the thing the reader was watching. It almost never is.
The safe placements are after a beat has landed and before the next one starts. A character has just been told something and has not yet responded. A door has closed. A phone call ended. In those gaps the story is already still, and the past can occupy the stillness without displacing anything.
There is a related failure worth naming: the flashback that arrives before the reader has anything to lose. Openings are especially vulnerable, because the writer knows the backstory well and the reader knows nobody yet. If your first chapter keeps reaching backward, the problem is usually the opening rather than the flashback, and it is worth rereading how to write a first chapter with that specifically in mind.
The backstory dump versus pressurized revelation
A backstory dump is not defined by length. It is defined by pressure. A dump is past material delivered with no one in the scene wanting anything. Nobody is resisting, nobody is choosing, nothing is at stake inside the memory itself — it is information wearing the costume of a scene.
Pressurized revelation is the opposite. The past scene has its own want, its own obstacle, its own cost. Mara at nineteen is not remembering the kitchen; she is in the kitchen, trying to leave without an argument, and failing. When the flashback ends, something has happened that did not exist before it started.
You can diagnose this quickly. Summarize the flashback in a sentence beginning with a verb the character performs. If the only verbs available are learned, felt, remembered, or realized, you have a dump. If the verb is refused, lied, took, or stayed, you have a scene. The other tell is length without change: a dump can run half a page and still be a dump, while a real flashback can run four pages and never feel long, because the reader is tracking an outcome. Readers do not resent duration. They resent stasis.
Tense and transition mechanics
The mechanics are unglamorous and they are most of the job. If your present narration is past tense, the standard move into a flashback is past perfect for the first sentence or two — had walked, had said — and then a quiet slide into simple past for the body of the scene. Holding past perfect for pages is grammatically defensible and rhythmically exhausting; the had construction blunts every verb it touches. Coming out, reverse the handshake: one or two past perfect verbs near the end, then a concrete present-time anchor. An object, a sound, a body position. Mara is holding the cup again, the argument about the furniture is still going, and Daniel has repeated the question.
Avoid announcing the transition. She thought back to that summer and She remembered the day are stage directions that tell the reader a flashback is starting, which is the one thing good prose can accomplish without help. A sensory bridge does it better: the same smell, the same object, the same phrase spoken by someone new. The reader crosses without being escorted.
Present-tense narration changes the toolkit but not the principle. Many writers put flashbacks into simple past against a present-tense frame, which reads cleanly and needs no scaffolding at all. What matters is that the shift is consistent — a reader who learns your convention once will follow it forever, and a reader who has to relearn it each time stops trusting the ground. One more mechanical rule: keep flashbacks out of nested layers. A memory inside a memory is a structure the reader has to hold rather than experience, and if the second layer is essential it usually wants to be its own scene somewhere else in the book.
The alternatives you should try first
Most flashbacks are solvable without a flashback, and the substitutes are frequently stronger because they keep the present scene alive while the past does its work. Implication is the cheapest and often the best of them. A character who will not go into a particular room has a history with it, and the reader builds that history themselves — usually more vividly than you would have written it. What the reader constructs, the reader believes.
Artifact is the next tier: an object, a document, a photograph, a scar. The past arrives as a physical fact in present time, which means it can be handled, argued over, hidden, or destroyed. Nothing stops. The chipped cup does more work in Mara's hands than a whole scene of the day it chipped.
Dialogue is the third, and the trick is that the telling has to cost the teller something. When a character explains their past freely, it is exposition; when they are dragged into it, contradicted mid-account, or caught leaving a piece out, it is drama. Two people remembering the same afternoon differently is a flashback and a conflict at once.
Reserve the dramatized flashback for the material none of these can carry — the moment whose specific texture is the point, where the reader needs to have been there rather than to have heard about it. In most manuscripts that is one scene, occasionally two. When you finally cut back, the reader should feel you spent something you had been saving.
The design question underneath all of this — what a character's history actually is, how much of it exists, which parts the story needs at all — is a separate job, and mostly one you do before drafting. Settle it first. Then the four decisions above — when you cut, where you cut, how you signal it, and what the past scene is doing while the reader is inside it — are what put the chosen part on the page.
Flashbacks are where a long manuscript quietly contradicts itself: the age in chapter two, the season in chapter nine, the version of an argument a character already told someone else. With StoryProp, details you have confirmed get written down as records the agent reads before it drafts, so a mismatch surfaces as a question instead of settling into the past tense.