Keeping continuity in a long web serial means making sure nothing in chapter three hundred contradicts what chapter thirty already established, and the only version of that discipline that survives hundreds of chapters is the version you do not hold in your head. You build a written record of the facts as you set them, the rules of your world, the order events happened in, and the setups still waiting to pay off, then you consult that record before each chapter instead of trusting memory. Character consistency is a related but separate discipline; this is about the world and the plot, the layer where a forgotten rule or a shuffled timeline quietly turns into the kind of plot hole readers do not forgive.
What does continuity mean in a long web serial?
Continuity is the promise that your story never contradicts itself, that a fact set early stays true unless the narrative deliberately changes it on the page and tells the reader why. In a short story that promise is easy to keep because you can hold the whole thing in your head at once. In a web serial that runs for years and hundreds of chapters, it stops being a memory task and becomes an accounting task, and the authors who serialize successfully treat it that way. There are really two layers to it, and it helps to separate them, because both sit under the broader craft of world-building for web fiction. One is character continuity, keeping your cast's traits and relationships and knowledge straight, which is its own problem and which I have written about separately in tracking characters across a long serial. The other, the one this article is about, is world and plot continuity: the rules of your magic, the geography of your map, the chronology of your events, and the promises your foreshadowing has quietly made. Works at the scale of Worm, Wildbow's roughly 1.7 million word serial from 2011 to 2013, or The Wandering Inn, which has passed ten million words as of this writing and is among the longest works of fiction in English, do not keep that straight by talent alone. They keep it straight with a system.
Why does continuity break down in web fiction specifically?
Continuity breaks down in web fiction because you publish before the story is finished, so you cannot quietly fix an earlier chapter once readers have already read it. A novelist writing for print revises the entire manuscript before anyone sees a word, which means a contradiction introduced in the first draft gets caught and smoothed over in the fourth, invisibly. The web serialist has no such luxury. Chapter forty went live months ago, hundreds of people have read it, and if chapter two hundred contradicts it, the fix is not a silent edit but a visible reckoning. Add to that the sheer span of the form. A serial written across two or three years is written by an author who has themselves changed, forgotten their own earlier decisions, and often adopted the discovery-writing habit of building the world as they go rather than planning it first. That habit is not a flaw, and I have argued elsewhere that worldbuilding should usually come after the story, not before. But it does mean the canon is being invented one chapter at a time, and unless something records each new fact as it lands, the author is building on a foundation they can no longer fully see.
How do you keep continuity across hundreds of chapters?
You keep continuity by turning it into a lookup instead of a memory test, which means building a canon reference as you write and consulting it before you write. The reference has three working parts, and none of them needs to exist before you start; they grow with the serial. The first is a rules ledger, a plain record of the constraints your world runs on, so that when your magic costs stamina, or your power tiers cap what a character can survive, or a journey between two cities takes four days on foot, those facts are written down the moment the story commits to them. The second is a timeline, because chronology is where memory fails soonest and where a serial written months apart will place two events in an order that cannot both be true. The third is the geography and the inventory, the map and the list of who currently holds what artifact, which sounds trivial until a sword you destroyed in one arc reappears in another. On IlorisNovel this is what the wiki and the timeline are for; the wiki holds the rules and lore you can search, the timeline pins events in order, and because entries link back into your draft, checking a fact is a click rather than a scroll through your own back catalogue. The tool is not the point, though. The habit is: before you write a chapter that leans on an established rule, you look the rule up rather than reconstruct it, the same way you would consult your own magic system's constraints instead of re-deriving them from feel.
Which continuity errors do readers actually catch?
Readers catch four kinds of world-and-plot continuity error more reliably than any other, and knowing which they are tells you where to spend your attention. The first is a broken rule of magic or power, and this one stings most because it feels like cheating; when a system that has cost something for two hundred chapters suddenly costs nothing to save the hero, the reader feels the author reaching in. This is the spirit behind Brandon Sanderson's widely cited First Law, that an author's ability to solve conflict with magic is proportional to how well the reader understands that magic, and a rules ledger is simply how you keep your own understanding fixed so the reader's can be too. The second is scrambled chronology, which is why a time-loop serial like Mother of Learning demands almost inhuman continuity discipline, since every reset has to stay consistent with every prior one. The third is impossible geography, the journey that took a week last time and an afternoon this time, and a long cultivation-style progression like Will Wight's Cradle only holds together because its power scaling and its distances stay internally lawful across a dozen books. The fourth, and the one authors forget most, is the abandoned setup: the gun on the mantel, in Chekhov's old formulation, that the story loads and then never fires. My feeling is that this last one hurts a serial more than the small factual slips do, because readers forgive a mistake far more easily than they forgive a promise the story made and quietly dropped.
Should you plan continuity up front or track it as you go?
Track it as you go, and build the record from what the chapters have actually established rather than from a plan you may never follow. I think the instinct to write an enormous canon bible before chapter one is usually a form of productive procrastination, and for a discovery writer it produces a document the finished story keeps contradicting anyway. The reference that earns its keep is the one that grows a step behind the draft, recording each rule and event the moment the page makes it true, so it is a log of your real canon rather than a forecast of an imagined one. This is not an argument against records; it is an argument about their direction. Even the largest planned series lean on exactly this kind of maintained log. Robert Jordan's Wheel of Time was tracked with detailed continuity notes, and when Jordan died in 2007 the record was complete enough that Sanderson could finish the series from it. Running a web fiction platform, the continuity complaints I see in author threads almost never come from writers who kept a growing reference and lost the thread; they come from writers who trusted memory across a two-year gap and got caught. Readers have catalogued small slips even in A Song of Ice and Fire, which tells you the standard is not perfection. The standard is a story that obeys its own rules often enough, and visibly enough, that when it does bend one it clearly meant to.
Common questions about continuity in a long web serial
What is a continuity error in a web serial?
A continuity error is any place where a later chapter contradicts something an earlier chapter already established, such as a rule of magic that suddenly works differently, a journey that takes days in one arc and hours in another, or a character reacting to news they were never told. In a finished novel these get caught in revision. In a web serial they go live before the story is done, and readers who have followed for a year notice the moment the world stops obeying its own facts.
How do you avoid plot holes in a long web serial?
You avoid plot holes by writing down the facts and rules of your world as you establish them and checking that record before you write anything that depends on it. Most plot holes are not failures of imagination, they are failures of memory: an author sets a limit in chapter forty and forgets it by chapter two hundred. A searchable reference to your own canon, updated every time a chapter establishes something, turns consistency from a feat of recall into a quick lookup.
Do web fiction writers need a timeline?
Most authors serializing past a few dozen chapters benefit from one, because chronology is the layer memory fails at first. A timeline records when events happened relative to each other, how long journeys and training and recoveries actually take, and which characters were present for what. Without it, a serial written over years will eventually place two events in an order that cannot both be true, and readers who binge the back catalogue in a weekend will catch what the author, writing months apart, did not.
How do professional long-series authors keep continuity?
They keep written records and, past a certain scale, delegate them. Robert Jordan's Wheel of Time was maintained with detailed continuity notes, and when Jordan died in 2007 Brandon Sanderson finished the series by working from those records rather than from memory. The lesson for a solo web fiction author is that even the people who do this professionally do not trust their heads. The record is the tool; the size of your cast and your word count just decide how much you need it.
Is it too late to fix continuity if I have already published?
It is usually not too late, because most continuity slips can be resolved forward rather than by editing the past. If a rule drifted, you can have the story acknowledge the exception in an upcoming chapter and give it an in-world reason, which readers accept far more readily than a silent retcon. Start the canon record now from the chapters already live, so the contradiction you just found is the last one that reaches readers instead of the first of many.
by Jacob Tam · August 6, 2026
I run IlorisNovel, a platform for web fiction writers. The wiki and timeline that keep a long serial consistent are built into the editor, and you can try it with no account.