Multiple timelines work in a web serial when the second time period exists to pay off or complicate the first, so that a scene set in the past changes how the reader understands the present rather than merely decorating it. The serial format makes this harder than it is in a printed novel, because a reader meets the two strands in fragments across days on a phone, and a cut to a timeline they half-remember is a cut they may not return from. Braid the strands on clean chapter breaks, label which era each chapter belongs to in its first line, keep both timelines actively moving toward a point where they meet or collide, and track what every strand knows and when so the two never quietly contradict each other.
A braided timeline is one of the most satisfying structures a long story can use, and also one of the easiest to break, and in a web serial the breaking happens faster and more visibly than it does anywhere else. This is a guide to writing multiple timelines in a serial without paying for the ambition in lost readers: what the structure actually is and how it differs from time travel, when a second timeline earns its place instead of becoming padding, how to move between eras so a reader on a phone is never lost, how to keep two strands from contradicting each other across months of updates, and how to pace both so neither becomes the boring one you skim to get back to the good one. 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 treat the wider frame in my complete guide to writing web fiction as the hub this piece hangs off.
What does it mean to write multiple timelines in a web serial?
Writing multiple timelines means telling one story across two or more distinct time periods that the reader follows in alternation, rather than along a single chronological line. The key word is structure, because this is a decision about how you arrange the telling, not a thing that happens inside the plot. That distinction matters, and it is where a lot of new authors get tangled, because a dual timeline is not the same as time travel or a regression story where a character physically moves between eras. In a braided narrative the characters stay put in their own time; it is the reader who is asked to hold two clocks at once. Brandon Sanderson's The Way of Kings, published in 2010, is the clean textbook case, running a present-day war alongside a sequence of flashbacks that slowly explain how a broken man ended up where the present thread finds him, and the flashbacks are not decoration, they are the delayed answer the present has been asking.
The reason the structure is so powerful is that it lets you control the order in which the reader learns things independently of the order in which they happened, and that control is the whole game. Iain M. Banks built Use of Weapons, published in 1990, out of two timelines running in opposite directions, one moving forward and one moving backward, converging on a single revelation that reframes everything, and the novel is famous precisely because the structure and the meaning are the same thing. My feeling is that this is the test worth applying before you commit: if the two timelines are just two stories happening to share a book, you have parallel plots, not a braid, and the reader will feel the difference as a lack of pull. A true multiple-timeline story uses the gap between eras as a source of tension, so that the reader is always slightly ahead of one thread and slightly behind the other.
When do multiple timelines actually earn their place?
A second timeline earns its place only when the past thread changes how the reader understands the present one, so the two strands are causally bound rather than merely adjacent. The test I keep coming back to is subtraction: if you could delete the second timeline and lose nothing but some atmosphere and some backstory, then it was never a timeline, it was flashback material you have inflated into a structure it does not need. Running a web fiction platform, I see this failure often, an author who opens a promising present-day serial and then, around the point where the momentum should build, starts alternating in a fully separate past timeline that turns out to explain things nobody was yet asking about, and the retention curve sags at exactly the chapters where the reader is being asked to care about a second story before the first one has finished earning them.
The braids that work are the ones where the earlier thread is quietly loaded and the later thread eventually sets it off. David Mitchell's Cloud Atlas, published in 2004, nests six narratives across different eras and gets away with an enormous span because each layer presses on the next, so the reading experience is cumulative rather than episodic. In web fiction the same principle holds at smaller scale: the past timeline should be answering a question the present timeline keeps raising, or it should be a fuse burning toward the moment the two meet. This is also where a second timeline overlaps with the craft of a second viewpoint, since both are ways of showing the reader something the main thread cannot, and if you are weighing the two, my piece on writing multiple POV in a web serial is the sibling to this one, because a great many dual-timeline serials also carry a dual POV, one per era, and the two decisions get made together.
How do you switch between timelines without losing a phone reader?
You switch only on a clean chapter break, never inside a scene, and you orient the reader in the very first line by signaling the era before any ambiguous pronoun can strand them. The serial format is the whole reason this rule is stricter here than in print. A novel's dual timeline is read in long sittings, where the reader holds both strands in warm memory and a switch registers instantly; a serial is read in fragments across days, so a reader coming back after a gap meets your timeline jump cold, and if the opening sentence does not immediately tell them which clock they are on, they spend the first paragraph confused, and confusion at a free chapter break is how you lose people. The fix is cheap. Give each timeline a fixed, recognizable anchor, a dateline in the chapter heading, a location that belongs to only one era, a point-of-view character who never appears in the other thread, so that the reader places themselves in a sentence rather than a page.
Consistency of the signal matters more than cleverness of it. My advice, then, is to pick one method of marking the timelines and use it every single time, because the reader learns the code fast and then stops noticing it, which is exactly what you want. Nobody103's Mother of Learning, one of the most-read web serials of the last decade and completed in 2020, is instructive here even though it is a time loop rather than a two-era braid, because it trains the reader to track which iteration of the same month they are in by anchoring every reset to fixed, repeated beats, and the reader comes to read those repetitions as coordinates. Whatever your anchor, the goal is that a returning reader never has to work to know where in time they are standing, so that all the work they do is on the story instead.
How do you keep parallel timelines from quietly contradicting each other?
You keep a running record of what each timeline knows and when, because the most common way a dual-timeline serial breaks is by letting one strand reveal something the other strand should already reflect. This is a bookkeeping problem before it is a craft problem, and it is brutal precisely because of the serial's length and cadence. When you write a braided story across months of updates, the fact you established in a past-timeline chapter in March and the present-timeline chapter that contradicts it in July are too far apart to hold in your head at once, and readers who binge the archive in one weekend will catch the seam you missed. My feeling is that authors underestimate this until the first time a comment thread gleefully documents an inconsistency, and by then it is load-bearing and expensive to fix. The deeper mechanics of this, the discipline of tracking who knows what across a long run, are the whole subject of my piece on keeping continuity in a long web serial, and everything there applies double when you are running two clocks.
This is the point where the right tools stop being a luxury. On IlorisNovel I built the wiki and timeline tools partly for exactly this load, so that an author running two eras can keep a living entry for each character that records what they knew in the past thread versus the present one, use @mention to surface those facts inside the editor while drafting, and lay both strands out on a shared timeline so the ordering never drifts. You do not need my tools specifically to solve this, a spreadsheet and stubbornness will do, but you do need something outside your own memory, and the fastest way to feel why is to draft a braided chapter with the reference open beside it. If you want to see what that feels like without making an account, you can try the editor and write a two-timeline scene against a live wiki in about a minute. The tool is not the point; the habit of writing against an external record is, because a braided serial that violates its own history reads as carelessness even when the prose is good.
How do you pace two timelines so both stay urgent?
You pace a braided serial by giving each timeline its own live tension, so the reader never treats one strand as the price of admission for the other. The classic failure of the structure is the boring-timeline problem, where the present thread crackles and the past thread is a slow, dutiful trudge toward information the reader has already guessed, so that every cut to the past reads as a delay rather than a development. The correction is to make sure each timeline has its own engine, its own question the reader wants answered and its own forward motion, so that a cut from one to the other trades tension for tension instead of trading tension for homework. The interweave should feel like a relay, where the strand you leave is left on a small hook and the strand you rejoin is already moving, which is the same cliffhanger discipline a single-timeline serial lives on, only doubled.
The best braids also point at a convergence and let the reader feel it approaching, because a dual timeline without a destination eventually reads as two shows sharing a channel. Whether the strands literally meet, as in Use of Weapons, or the past thread simply catches up to the moment the present thread began, the reader needs to sense that the gap between the clocks is closing, because that closing gap is the structural version of a countdown. My advice, then, is to know before you start where and roughly when the timelines resolve into each other, even if you are otherwise a discovery writer, because the convergence is the promise the whole structure is making, and a promise the reader can feel tightening is what turns a clever arrangement into a story they cannot stop reading. Get that right and the multiple-timeline serial does something a straight chronology never can, letting a revelation you planted in the past detonate in a present the reader thought they understood.
Common questions about writing multiple timelines in a web serial
What does it mean to write multiple timelines in a web serial?
Writing multiple timelines means telling a story across two or more distinct time periods that the reader follows in alternation, such as a present-day thread braided with a past one, rather than a single chronological line. It is a structural choice, not a plot device, so it is different from time travel, where characters move between eras inside the story. Brandon Sanderson's The Way of Kings, published in 2010, is a clean model, interleaving a present campaign with flashbacks that slowly explain how the protagonist arrived there.
When should a web serial use more than one timeline?
A web serial should use a second timeline only when the past thread changes how the reader understands the present one, so that the two strands are causally linked rather than merely running side by side. If you could cut the second timeline and lose nothing but background, it has not earned its place and should become ordinary backstory instead. The strongest dual-timeline structures build toward a moment where the earlier thread reveals or detonates something the later thread has been sitting on the whole time.
How do you switch between timelines without confusing readers?
Switch only on a clean chapter break, never mid-scene, and orient the reader in the first line by naming the era or the timeline's anchor character before any pronoun arrives. A serial reader returns after days away, so an unlabeled jump between time periods is far more disorienting here than in a book read in one sitting. A consistent signal, a dateline, a recurring location, or a fixed point-of-view per timeline, lets a returning reader place themselves in a sentence rather than a page.
How do you keep two timelines from contradicting each other?
You track what every timeline knows and when, because the fastest way a dual-timeline serial breaks is by having the past thread reveal something the present thread should already reflect, or the reverse. Across hundreds of chapters written over months, the details that must stay consistent, who knew what, which object existed when, sit too far apart to hold in your head. A living reference of facts per era, plus a timeline view that keeps the two strands ordered, is what stops a long braided serial from quietly violating its own history.
Is a dual timeline harder to write in a web serial than in a novel?
Yes, mostly because of how the serial is read rather than how it is written. A novel's dual timeline is consumed in long sittings where the reader holds both strands in active memory, while a serial is read in fragments across days against a free back button, so every cut to the less urgent timeline risks a reader who does not return. The fix is to keep both strands genuinely urgent and to make each timeline switch instantly legible, so the reader is never paying a comprehension tax at a chapter break.
by Jacob Tam · August 15, 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.