To track characters across a long web serial, keep a searchable character reference outside your own memory rather than trusting yourself to recall a cast that will grow into the dozens or hundreds. Record each character's fixed traits the moment they appear, name and eye color and speech pattern and defining wound, so an early detail cannot quietly change three hundred chapters later. Track the harder, invisible layer too, meaning who knows what, who has met whom, and where every relationship stands right now, because that state changes constantly and is where serials most often contradict themselves. A wiki you can search, an @mention that ties a name in your draft to its entry, and a timeline that pins when things happened turn continuity from a feat of memory into a lookup, which is the only thing that scales.
Why tracking characters is harder in web fiction than in a novel
Tracking characters across a web serial is a fundamentally different job from tracking them in a novel, because a serial publishes in order, in public, and over a span of years that no human memory was built to hold. When you write a standalone book, your entire cast lives in your head at once during a compressed drafting window, and whatever you forget you fix in revision before a single reader sees it. A web serial removes both of those safety nets. The cast is introduced a few names at a time over hundreds of chapters, so you are never holding the whole ensemble in working memory, and the early chapters went live long ago, which means a contradiction you notice in chapter three hundred cannot be quietly patched in chapter three. Running a web fiction platform, I see this play out constantly, and the authors who struggle are almost never the ones with too little imagination. They are the ones who trusted themselves to remember a cast that outgrew what any writer can remember.
The scale of the problem is easy to underestimate until you are inside it. The Wandering Inn by pirateaba, which began serializing in 2016 and is one of the longest web serials ever written, carries hundreds of named characters, and the reader community maintains an enormous wiki precisely because keeping that cast straight is beyond casual recall. Even outside web fiction the pattern holds, because readers have catalogued small continuity slips in works as carefully edited as George R.R. Martin's A Song of Ice and Fire, where an eye color or a minor detail drifts between volumes. Robert Jordan built The Wheel of Time around a cast so large that continuity eventually became a dedicated job, with his longtime assistant maintaining the notes that kept thousands of named characters coherent across fourteen books. If a traditionally published series with a professional editorial apparatus slips, the lone author updating a serial from memory at a chapter a week is working without a net, which is why the skill worth building early is not remembering harder but recording better.
What actually slips: names, descriptions, and the details readers catalogue
The first layer of character tracking is the set of fixed traits that must never change, and the discipline is to write each one down the moment it appears on the page rather than the moment you notice it has drifted. These are the small, checkable facts: the exact spelling of a name, a character's age and eye color and height, a scar or a limp, a verbal tic or a way of speaking that marks their dialogue. None of these are supposed to evolve, which is exactly why their drift is so damaging when it happens, because a reader who has watched a character for two hundred chapters knows their brown eyes were brown, and when they turn green in a later arc the mistake reads as carelessness even if everything else about the writing is sharp. My feeling is that this layer is the easy half of the job, in the sense that it is mechanical and fully solvable, and the only reason authors get it wrong is that they rely on memory for facts that memory was never going to hold across years of drafting.
Speech is the trait most often overlooked here, and it deserves its own note, because a large cast that all sounds the same is its own kind of continuity failure. A character established early as terse and profane should not, four hundred chapters later, deliver a flowery three-paragraph monologue unless the story has earned that change on the page, and the way you protect against that is by recording how each significant character talks alongside how they look. This is the tracking side of a craft problem I have written about from the writing side in how to write a smart character, where the whole illusion depends on a consistent, distinctive intelligence that the reader can recognize from the dialogue alone. Consistency of voice is what makes a large cast feel like different people rather than one author wearing many hats, and you cannot sustain it across a serial's length on instinct. You sustain it by having somewhere to check who this person is before you write their next line.
Track the invisible layer: who knows what, and who has met whom
The harder and more important layer of character tracking is the moving state, meaning the web of relationships, knowledge, and history that changes constantly as the story runs, and this is where long serials contradict themselves most often. Fixed traits are static and easy to look up once recorded, but relationships evolve by design, which is the entire point of a long-running cast, and that evolution is exactly what makes it hard to keep straight. The single most common error I see is a knowledge slip: a character reacts to information they were never told, or fails to recognize a secret they learned sixty chapters ago, because the author remembered that the reader knows a thing and forgot that this particular character does not. Tracking who knows what, per character, is unglamorous and it is the difference between a plot that feels tight and one that quietly leaks tension every time someone conveniently knows or forgets the right fact.
Alongside knowledge sits the relationship state itself, and I think the useful mental model is to treat every significant pairing as a value that has a current setting rather than a fixed label. Two characters are not simply allies or enemies; they are allies as of the last scene between them, after a specific thing passed between them, with each holding a specific belief about the other that may or may not be true. Mother of Learning by the author known as nobody103 is admired partly because its time-loop structure forces this bookkeeping into the open, since the protagonist accumulates knowledge across loops while most of the cast resets, and the story only works because the author tracked precisely who remembered what in every iteration. You do not need a time loop to face the same problem in slower motion. Every long serial is a machine for changing what characters know and how they feel, and the author who records those changes as they happen is the one whose cast still behaves consistently three hundred chapters in.
Build a living character reference, not a better memory
The reliable solution to all of this is to keep a living character reference outside your own head, tied as closely as possible to the actual writing, so that consulting it costs you seconds rather than a scroll back through half a million words. A character bible is not a pretentious luxury for web fiction, it is basic infrastructure, and as I argued in the broader case for world-building that survives a long serial, the reference should grow alongside the story rather than precede it. That means you are not inventing your whole cast up front, which no one can do well anyway, but recording each character the moment the book commits them to the page: their fixed traits, their relationships as of now, what they currently know, and where they were last seen. The bible becomes a record of what the story has actually established, which is the only version that stays accurate, and the act of updating it as you draft is what keeps the record honest.
This is the specific problem the wiki in IlorisNovel is built to carry, and it is worth being concrete about why the tie to the draft matters so much. A reference in a separate document is better than nothing, but it decays, because the friction of leaving your chapter to go update a file is exactly the friction that makes authors skip the update. The idea behind the world builder is that your characters live as searchable entities in a wiki, an @mention lets you link a name in your chapter straight to its entry so you never lose the thread of who is who, and a timeline pins when each event happened so the sequence stays coherent even across a serial written out of order. The AI world builder can take a rough premise and rough out that cast structure for you to edit rather than starting from a blank page, which helps most in the sprawling, relationship-heavy stories where the tracking burden is heaviest. The point is not the feature list, it is the principle that at web fiction scale, remembering your own cast has to become a lookup, and the same infrastructure that holds your magic system, which I covered in how to build a magic system for web fiction, is what holds your characters too.
A workable system for keeping your cast straight
A practical order of operations for most serial authors is to create a character's entry the moment they get a name, record their fixed traits and their starting relationships immediately, and then update that entry every time a scene changes what they know or where they stand. The first move costs almost nothing and pays off for years, because the alternative is reconstructing a character's history from the text long after you have forgotten writing it. The second move, the ongoing update, is the one that requires discipline, and the trick is to fold it into your drafting rather than treating it as separate admin: when a scene reveals a secret to a character, note it before you move to the next chapter; when two characters' relationship shifts, record the new state while the scene is fresh. The authors I talk to who have serialized successfully for years almost all describe some version of this habit, and the ones who abandoned it are the ones who ended up retconning in public.
The mindset that ties this together is that a cast, like a world, is not something you finish and then furnish a story into, it is something you grow in public alongside the story, under constraints a novelist writing in private never faces. That sounds like a burden, and some days it is, but it also produces the specific reward of the form: a cast that visibly deepens chapter by chapter, that pays off relationships seeded hundreds of chapters earlier, that feels lived-in because the author actually kept track of the life it accumulated. If you want to feel out how a cast and its connections hold together before you commit a serial's worth of continuity to them, you can open the editor and world builder with no account, which is the lowest-friction way to see whether the tracking system you are imagining actually earns its keep once the cast starts to grow.
Common questions about tracking characters in a long serial
How do you keep track of characters in a long novel or serial?
You keep a written character reference and update it as you draft, because no author reliably remembers a large cast across hundreds of chapters and years of writing. Record each character's fixed traits, their relationships, and what they currently know, then consult it whenever a name reappears rather than trusting memory. In web fiction this matters more than in a finished novel, because chapters go live before the story is done and you cannot quietly correct an earlier contradiction after readers have already seen it.
What information should you track for each character?
Track the fixed traits that must never drift, such as name spelling, physical description, age, and speech pattern, alongside the moving state that changes constantly, such as relationships, injuries, secrets they hold, and who they have met. The fixed traits prevent the small slips readers catalogue, like an eye color that changes between arcs. The moving state prevents the larger ones, like a character reacting to news they were never told or greeting a stranger they supposedly met forty chapters ago.
Do web fiction authors need a story bible for characters?
Most authors serializing for any real length benefit from one, because the cast of a long web serial routinely grows into the dozens or hundreds and human memory does not keep pace. A character bible does not need to be written before the story, though. The most useful ones grow alongside the serial, recording each character's traits and relationships as they appear on the page, so the reference is a record of what the book has actually established rather than a plan you may never follow.
How do you avoid continuity errors with a large cast?
You make consistency a lookup instead of an act of memory. Every time a character appears, check their entry before you write them, confirm their description and their current relationships and what they last knew, and add anything new the scene establishes. Errors creep in when an author writes from memory two hundred chapters after a detail was set. A searchable reference tied to your draft, ideally one that links each name to its record, catches the drift before readers do.
How do you track relationships between characters?
Track relationships as a changing state, not a fixed fact, because the whole point of a long serial is that relationships evolve. For each significant pair, note where they stand now, what the last major thing that passed between them was, and what each currently believes about the other. This is harder than tracking physical traits because it updates constantly, and it is where serials most often slip, so a reference that shows a character's connections at a glance is worth more than one that only lists their hair color.
by Jacob Tam · July 16, 2026
I run IlorisNovel, a platform for writers of web fiction. If you want to see what keeping a cast straight here feels like, you can try the editor and world builder with no account.