A year of aggregated, anonymized tracking data reveals patterns in how web fiction readers actually behave. Not what they say they read — what they consistently follow, drop, and return to.
The average reader follows more than they think
The typical Storywatch user tracks 12-15 active stories. When asked, most estimated 5-8. The gap between perceived and actual reading volume is consistent across the user base. Web fiction readers underestimate how many serials they're following because manual tracking (tabs, bookmarks) fragments the count across platforms.
The dropout curve is predictable
Stories are most likely to be dropped between chapters 20 and 40. Before chapter 20, readers are still evaluating. After chapter 40, they're committed. The 20-40 window is where the initial hook has worn off and the story's ability to sustain interest is being tested.
This has implications for authors: chapters 20-40 are the most important for retention. A strong opening gets readers to chapter 20. A strong middle keeps them past 40.
Readers follow across platforms more than platforms admit
The average tracked reader follows stories on two to three platforms. Royal Road + AO3 is the most common combination. SpaceBattles readers almost always also read elsewhere. Platform-loyal readers who only use one site are the minority.
Completion is the rarest shelf
The Dropped and On Hold shelves collectively hold more stories than the Reading shelf. This isn't failure — it's the natural shape of web fiction consumption. Readers try more than they finish. The ratio is roughly 3:1: for every three stories started, one is actively followed to current, and the other two are dropped or paused.
What this means
Readers need tools that account for how they actually read: across platforms, with high churn, following more stories than they can track manually. Platform-native tools handle within-platform tracking. The gap is the cross-platform view. Storywatch fills it.