Chapter titles in web fiction operate differently from chapter titles in finished novels, because readers see the table of contents every time they open the next drop. The craft principle I lean on is simple. Title the chapter after the question it raises, not the answer it gives. That keeps the page-turn intact and the navigation useful at the same time, and it costs you almost nothing once you start watching for it.
Why chapter titles matter more in web fiction than they do in finished books
Chapter titles in web fiction function as navigation, marketing, and reread infrastructure in a way that chapter titles in a hardback do not, because the reader is interacting with the table of contents constantly rather than once at the beginning of a sitting. A reader who buys Mistborn in paperback opens it, reads forty pages, sets it down, and almost never glances at the chapter list again. A reader following the same author on Royal Road, by contrast, sees the chapter list every time they refresh the page, every time they tap the bookmark icon, and every time they come back from a week away and need to find the chapter where the heist crew finally split up. The table of contents is the second-most-trafficked surface in the entire reading experience, after the chapter pages themselves, and the titles in it are doing constant work whether the author has thought about that or not.
That is why a chapter title that quietly gives away the punch of the chapter costs a web fiction author more than the same title would cost a novelist. The novelist is mostly trusting the reader to encounter the title once, in passing, as they flip to the next chapter; the web fiction author is putting the title in front of the reader before every reading session and again in every notification email. If the title says "The ambush," the reader has now been told what is about to happen perhaps half a dozen times before they ever load the chapter. The surprise is dead long before the prose has a chance to deliver it, and the chapter has to work much harder to recover.
The two failure modes are pure numbering and outright spoilers
The two most common chapter-title problems in web fiction are opposite errors, and most authors only worry about one of them at a time. The first is pure numbering. Calling every chapter "Chapter 47" and nothing else is the safest possible choice and also the one that asks the reader to do the most work, because it strips out the reread cues that make a serial pleasant to navigate. A reader who wants to go back to the scene where the protagonist first met the antagonist now has to remember the chapter number, which they almost never do, and they end up scrolling through twenty pages of identical thumbnails trying to find a duel scene by feel. Plain numbering also leaves you with no surface for character voice or thematic resonance at all, which feels like a missed opportunity in a form where every piece of metadata is more visible than the equivalent metadata in print.
The second failure mode is the more common complaint among readers. A title like "The ambush" or "First battle lost" or "The big escape" hands the chapter's payload to the reader before the prose has a chance to land it. Tolkien did this in The Lord of the Rings, calling chapters things like "The Bridge of Khazad-dûm" and "The Breaking of the Fellowship" without much apparent concern that the second title gave the game away, and it is fair to say that he got away with it because the book is read primarily in long uninterrupted sessions where the chapter title is barely noticed. A serial does not have that luxury. The title is going to be stared at, refreshed past, and notification-emailed, and any plot beat it contains is going to be diffused into the reader's attention long before the chapter itself arrives.
Title the question, not the answer
The principle I try to hold to, both in my own drafting and when I'm reading other people's outlines, is that the chapter title should point at the question the chapter is asking rather than the answer it gives. A chapter in which the protagonist is captured can be called The wrong door instead of Captured. A chapter in which a beloved mentor dies can be called by the last sentence the mentor said, or by an image from the scene, or by the name of the room. The reader still feels the weight of the title in retrospect, but they walk in not knowing how the title is going to land, and the prose gets to land it.
The rule is loose enough to leave plenty of room for personality. Cradle uses one- or two-word titles that are usually thematic rather than narrative: "Cycles," "Apprenticeship," "Refiner." Worth the Candle uses titles that read like scene labels written by a mildly sardonic narrator. A Practical Guide to Evil uses titles that play with the reader's expectations and occasionally bait them deliberately. None of those four serials is using the same style, but they share the property that the title functions as a frame rather than as a summary. You walk in oriented but not informed, and the chapter is allowed to surprise you.
When a deliberately spoiler-y title actually works
There is a real counter-argument, and it deserves an honest hearing rather than a dismissal. The argument is that an author cannot really spoil their own book, because the chapter title is itself an authorial choice, and choosing to put a plot beat in the title shifts the reader's focus from "what happens" to "how does it happen." If the chapter is called "Captured" and the reader walks in already knowing the protagonist is going to be captured by the end of it, the reading experience is no longer one of surprise. It is one of dread, of watching the inevitable arrive, of attention given to the texture of how the trap closes rather than to the question of whether it will. That is a real and sometimes wonderful effect, and a writer who is consciously aiming for it should not be talked out of it by a craft rule about questions versus answers.
Dragon Ball Z did this constantly with episode titles like "Frieza Defeated," and the show worked anyway because what the audience came for was the spectacle and the choreography, not the suspense over outcome. Greek tragedy did the same thing structurally millennia earlier, with the audience knowing exactly how Oedipus or Antigone was going to end and still being undone by the inevitability of watching it happen. My feeling about this is that deliberate spoilers are a legitimate craft choice, but they have to be a choice. The problem in web fiction is rarely that an author has decided suspense will beat surprise; the problem is usually that the author wrote a placeholder summary as the chapter title during drafting and forgot to come back and replace it. The fix is not to ban descriptive titles. The fix is to make sure the title is doing the work the author wanted, and to know which work that is.
Three patterns that hold up across a long serial
The first pattern is a line lifted from inside the chapter itself, usually a fragment of dialogue or a piece of internal narration. The chapter where the protagonist finally faces the villain becomes I've been looking forward to this, in italics, with the line repeated somewhere on the page. The chapter where the protagonist breaks down becomes I don't know how to do this anymore. The line gives the reader a hook, a vibe, and a foothold for rereading without giving away the structure of the scene. It is also a useful drafting tool, because if you can't find a sentence in the chapter that wants to be the title, the chapter may not have a single emotional center yet.
The second pattern is an arc-level structural title that signals scope rather than content, like "The Tournament, part three" or "Reign of the Magpie King, chapter seven." This works well for long set pieces and badly for everything else, because once the reader sees "part four," they are now waiting for "part five" rather than reading the chapter in front of them. Shadow Slave and a few other long-running serials have leaned too hard on this pattern and turned thirty consecutive chapters into a numbered queue, which is a navigation gain but a reading-experience loss. Used sparingly, on the two or three big arcs of a book, the arc-title pattern does honest work. Used constantly, it shades back into the same flat-numbering problem we started with.
The third pattern is the POV name, lifted essentially intact from A Song of Ice and Fire, where Martin titles every chapter after the viewpoint character. In a serial with multiple POVs, that is enormous reader service. The reader who only cares about one of the four POV strands can scan the table of contents and read just those chapters; the reader who has been away for a week can use the rhythm of POV names to relocate themselves in the rotation. The pattern is also entirely spoiler-resistant, since the name itself reveals nothing about the chapter's events, and it works well in combination with a colon-and-subtitle structure where the subtitle gestures at the chapter's question.
What this looks like in practice
If your chapter list right now reads like Chapter 47: The Heist Goes Wrong, Chapter 48: Captured, Chapter 49: The Escape, Chapter 50: A New Power, you have written four spoilers in a row and asked the reader to pretend they didn't see them. You can keep the same chapter content and rewrite the titles as something like The wrong door, A small white room, The third sentry, What the lock was for, and the reading experience improves before you have changed a single word of prose. The discipline is the same one good copywriting uses everywhere else. Promise the reader an experience, not an outcome, and let the prose carry them to where the title was always pointing.
Common questions about chapter titles in web fiction
How should I title chapters on Royal Road or other web fiction platforms?
Pick titles that point at the question of the chapter rather than the resolution, because the chapter list on every web fiction platform is also the navigation surface, and readers scan it before they tap in. A line lifted from inside the chapter, a thematic image, or a POV character name will all carry a reader into the chapter without pre-loading them with the outcome. What does not work is a title that gives away the resolution, because that title is the first thing the reader sees and the last thing the chapter is supposed to deliver.
Are numbered chapters worse than named chapters in web fiction?
Pure numbering costs you navigation and reread value, both of which matter more in a serial than in a finished book, because readers are jumping in and out of the table of contents constantly. A reader who wants to return to the duel scene can find A second sword in the rain faster than they can find Chapter 47. My feeling is that flat numbering is the safest choice and also the laziest one, and a writer who cares about the reread experience should at least try to do better.
How do I title a chapter without spoiling what happens?
Title the question the chapter is asking, not the answer it gives. A chapter where the protagonist is captured can be called The wrong door instead of Captured. A chapter where someone dies can be named after the last thing the character said, or after the room, or after an image from the scene. A line of dialogue, a place name, or a POV name will all orient the reader without telling them how the chapter ends.
When does a deliberately spoiler-y chapter title actually work?
When the author has decided the suspense is stronger than the surprise. If the reader already knows the protagonist will be captured by the end of the chapter, the question shifts from "what happens" to "how does it happen," and a title like Captured becomes a feature rather than a bug. The trick is that the choice has to be deliberate, not an accident of summary, and the author has to be sure the dread of watching the inevitable arrive will pay better than the surprise of it landing.
Should chapter titles in progression fantasy be funny or serious?
They should match the tone of the work, which in most progression fantasy means a register a touch drier than the prose itself, since the title is doing meta work rather than scene work. Dungeon Crawler Carl leans comedic in its titles because the book is a comedy. Cradle uses sober one- or two-word titles because the book is earnest. The error to avoid is borrowing the title tone from a different kind of book than you are actually writing, which is what produces the awkward effect of a serious story with breezy summary titles.
I run IlorisNovel, a platform for writers of web fiction who want to keep what they earn. The rest of the craft blog lives here.