A flashback works in web fiction when it earns the interruption it costs, which means the scene from the past has to change how the reader understands the present rather than merely filling in history they were content not to have. The serial format raises the stakes on this, because a reader meets the story in fragments across days on a phone with a free back button, so a cut to the past that arrives before they care, or that runs longer than a scene, is a cut some of them will not return from. Trigger the flashback off a concrete present-moment cue, orient the reader in the first line so they know when they are before any pronoun lands, hold it to a single scene rather than a chapter of backstory, and cut back into forward motion the moment the past has done its work.
The flashback is one of the oldest tools in storytelling and one of the easiest to misuse, and in a web serial the misuse shows up faster and more visibly than it does in a printed novel, because the reader is meeting your story in daily fragments and can leave on any one of them. This is a guide to using the tool well: what a flashback actually is and how it differs from the braided dual-timeline structure it is often confused with, when a scene from the past earns the interruption it costs, how to drop into it and climb back out without losing a reader who is holding your story on a phone, and how to keep a flashback from quietly contradicting the canon you have been building for hundreds of chapters. Everything below can be, and has been, successfully contradicted by writers better than me, so take it as the set of patterns I keep returning to rather than a rulebook, and read it against the wider frame in my complete guide to writing web fiction, which is the hub this piece hangs off.
What is a flashback, and how is it different from a dual timeline?
A flashback is a bounded scene set earlier than the story's present that the narrative drops into and then returns from, handing the reader a piece of the past at the moment it will land hardest. The key word is bounded, because a flashback is a tactical interruption rather than a structure, and the present stays the spine of the story throughout. Homer built the Odyssey around the oldest famous version of this move, opening with Odysseus already years into his exile and then letting him narrate, at the Phaeacian court, the earlier adventures that stranded him, so that the reader learns the origin of the trouble after they are already invested in its outcome. That is the whole engine of a flashback: it lets you deliver cause after effect, so the past arrives as an answer to a question the present has already made the reader ask.
This is worth separating cleanly from the dual timeline, because the two get confused constantly and they are not the same craft problem. A flashback is a detour; a dual timeline is a second road. When a past thread runs co-equal with the present one across the length of the story, alternating with it all the way through so that the two build toward a convergence, you are no longer writing flashbacks, you are braiding two timelines, and I treat that as its own structure in writing multiple timelines in a web serial. Brandon Sanderson's The Way of Kings, published in 2010, sits at that structural far end, giving a whole book's worth of a character's past its own recurring slot rather than dropping in for a single scene. My feeling is that most web fiction authors reaching for a flashback actually want the surgical version, the Casablanca version, where the film cuts once to the Paris the two leads shared and then returns, changed, to the present, and the detour is over inside a scene. If you find your past scenes adding up into a parallel narrative, stop and decide deliberately whether you meant to build a braid, because drifting into one by accident is how a serial ends up with two half-told stories instead of one whole one.
When does a flashback earn its interruption?
A flashback earns its place when the reader is already asking the question it answers, so the scene from the past lands as a payoff rather than a detour that stalls the present. The test I keep coming back to is subtraction: if you can delete the flashback and lose nothing but some history the reader was content not to have, then it was never a flashback the story needed, it was backstory you promoted into a scene it did not warrant. Running a web fiction platform, I see the failure mode constantly in the retention data, an author who, right around the chapter where the present momentum should be compounding, cuts away to a fully staged childhood scene explaining a wound nobody in the present has pressed on yet, and the reader who came for the forward story is asked to care about a second one before the first has finished earning them. The curve sags at exactly those chapters, and it does not always recover.
The serial format is what makes this expensive in a way it is not on the page. A reader working through Cradle or He Who Fights with Monsters in a paperback has both hands committed and a chapter of backstory costs them ten minutes they have already decided to spend; a reader following the same story as a web serial is on a phone, between other things, with a free back button and a thousand competing tabs, and a present that stops moving is a reason to close the tab. I think this is why so much of the best progression fantasy stays stubbornly forward-facing, revealing the past in single lines folded into present action rather than in staged flashback scenes, because the genre's readers are unusually impatient with any chapter that does not advance the thing they are actually here for. The flashback that earns its slot is the one you have set the reader up to want, so that when the cut comes they lean in rather than skim, and the way you know you have earned it is that the present has planted the question first.
How do you drop into the past without losing a phone reader?
Signpost the jump on a clean break and orient the reader in the very first line, naming when and where they now are before any "he" or "she" arrives, because a serial reader returning after days away cannot recover context you have not put on the page. The seam is where flashbacks go wrong most often, and the fix is mechanical. Trigger the cut off a concrete present cue, a smell, an object, a line of dialogue, so the reader feels a reason for the memory rather than an authorial lever, and then step across the boundary with a light touch of past-perfect before settling into plain simple past so the scene reads as a scene rather than a summary. Compare a blurred opening, He remembered how it had all started, back when things were different and he was younger, which orients nobody and signals only that a slow patch is coming, with a placed one, Ten years earlier, in the flooded market at Ashwick, the boy who would become the Emperor was picking a stranger's pocket, which tells the reader the time, the place, and the person in a single sentence and lets them drop in without groping for footing.
The tense discipline matters more in a serial than anywhere else because the reader has less working memory of your story loaded when they arrive. Use past-perfect ("had") only to cross the threshold, a sentence or two, then let it go, since a whole flashback written in unbroken past-perfect reads as distant and reported and keeps the reader at arm's length from the very scene you interrupted the story to show them. If the flashback is long enough to span a scene break of its own, give the reader a small recurring signal that they are still in the past, a consistent location or a dateline, the same courtesy you would extend in any braided structure, so that a reader who closes the tab mid-flashback and returns tomorrow can place themselves in a sentence. The goal at every seam is that the reader never pays a comprehension tax, because a comprehension tax at a chapter break in a serial is very often where they decide they are done.
How do you keep a flashback short and get back to the present?
Hold a flashback to a single scene and cut back to the present the instant the past has paid its debt, because every paragraph you linger is a paragraph the forward story is standing still. The discipline is knowing what the flashback owes and paying exactly that. If the reader needed to understand why the protagonist cannot enter a temple, the flashback delivers the one scene that planted the fear and then it is over; it does not also tour the character's schooling, their first love, and the political situation of the province, however tempting the staged past is once you are standing in it. Emily Brontë's Wuthering Heights, published in 1847, sits at the ambitious end of retrospective storytelling, nesting almost the entire novel inside Nelly Dean's recollection, and it works as a designed frame rather than an interruption; that is a deliberate architecture, not the model for dropping a memory into chapter forty of an ongoing serial, and confusing the two is how a single flashback swells into a detour the present never recovers from.
The return is the half writers most often fumble, and it is the half that decides whether the flashback felt worth it. Cut back to the present on a beat that the flashback has changed, so the reader arrives somewhere new rather than merely resuming where they left, and let the present scene visibly carry the weight of what they now know. My feeling is that a flashback should end on the smallest possible hinge, a single present-tense image or line that would have read as ordinary a page ago and now reads as loaded, because that contrast is the entire return on the interruption you charged the reader. The web-native serial The Wandering Inn by pirateaba uses interludes and glimpses of the past this way across its enormous length, dipping back when a character's history sharpens the present stakes and then handing the reader forward again, and the dips earn their place precisely because they are dips and not a second book running underneath the first.
How do you keep a flashback consistent with your own canon?
Keep every flashback consistent with what the present has already established, because the fastest way a flashback breaks a long serial is by contradicting a fact the reader has been carrying for two hundred chapters. This is a bookkeeping problem before it is a craft one, and it gets worse the longer the story runs, since a scene you write in month eighteen has to agree with a detail you invented in month three about who was present, what a character already knew, which object existed yet, and how old everyone was. Readers of long web serials are formidable at catching this, and a flashback that quietly ages a character wrong or gives them knowledge they should not have had yet does more damage than a slow chapter, because it makes the reader stop trusting the ground under the whole story.
This is the part of flashback craft where the tooling actually earns its keep, and it is why I built the world builder and wiki in IlorisNovel to hold canon as a living reference rather than a document you forget to update. A connected wiki lets you check, before you write the market scene from ten years ago, exactly what the present has already committed to about that market and those people, and a timeline view keeps the order of events straight so a flashback slots into a chronology you can see rather than one you are holding in your head. When a flashback grows past a single scene and starts recurring with real weight, that is the moment to ask whether you have crossed from a tactical interruption into a full braided structure, and to plan it as one on the timeline rather than discovering it chapter by chapter; the boundary between the two is exactly the boundary I drew at the top of this piece, and staying on the right side of it is most of what keeps a flashback from becoming a story the present has to compete with. A flashback, kept bounded and kept honest, is one of the most efficient tools you have for making a reader feel the past pressing on the present, and the whole art of it is spending the interruption where it buys the most and then getting out.
Common questions about writing flashbacks
What is a flashback in a story?
A flashback is a bounded scene set earlier than the story's present that the narrative drops into and then returns from, delivering a piece of the past at the moment it will land hardest. It is a tactical interruption rather than a structure, so the present remains the spine of the story and the flashback is a controlled detour off it. The oldest famous example is Homer's Odyssey, where Odysseus, already years into his troubles, sits at a foreign court and narrates the earlier adventures that stranded him, so the reader learns the cause after they already care about the effect.
When should you use a flashback in a web serial?
Use a flashback only when the reader is already asking the question it answers, so the past scene arrives as a payoff rather than a detour that stalls the present. The test is subtraction: if you can cut the flashback and lose nothing but background the reader was content not to have, it has not earned its interruption and belongs in a line of ordinary narration instead. In a serial, where readers arrive in fragments across days and momentum is fragile, an unearned flashback costs more retention than the same scene would in a printed novel read in one sitting.
How do you start and end a flashback without confusing readers?
Start on a clean break, trigger the jump off a concrete present cue, and orient the reader in the first line by naming when and where they now are before any pronoun arrives. Use a light past-perfect to step across the seam and then settle into simple past so the scene reads as a scene rather than a report. End it the instant the past has paid its debt, cutting back to the present on a beat that has been changed by what the reader just learned, so the return feels like an arrival somewhere new rather than a resumption of where they left.
Are flashbacks bad for pacing?
Flashbacks are not bad for pacing in themselves, but they are expensive, because every paragraph spent in the past is a paragraph the present story is standing still. The cost is higher in a web serial than in a novel, since a reader on a phone with a free back button feels a stalled present as a reason to leave. Kept to a single scene that answers a live question and then hands the reader back to forward motion, a flashback pays for its interruption; stretched into a chapter of backstory nobody asked for, it does not.
What is the difference between a flashback and a dual timeline?
A flashback is a bounded insertion, a single scene you drop into and climb back out of while the present stays the spine, whereas a dual timeline is a structure where a past thread runs co-equal with the present one across the whole story and the two alternate all the way through. The difference is scale and weight: one is a detour, the other is a second road. If your past scenes are adding up into a full parallel narrative, you are no longer writing flashbacks and should plan the braid deliberately, which is the separate craft problem I cover in the multiple-timelines guide.
by Jacob Tam · September 29, 2026
I run IlorisNovel, a platform for web fiction writers. If this kind of craft writing is your thing, the rest of the blog lives here.