How to Write a Web Novel: A Beginner's Guide to Serialised Fiction

This guide is for someone who has never written a serial and wants to start one that survives its first hundred chapters. It covers choosing what to write, planning an arc, the chapter as a unit, the first chapter, posting, and the habits that keep a serial alive. Our web serial guide goes deeper on structure and retention once you are running; this is the on-ramp.

Understand the market you are writing into

Web novels are read on platforms: English sites where most fiction is free and popular series can earn through reader support and paid tiers, and the large Korean, Chinese and Japanese platforms where readers pay per chapter and the industry is a professional one. The conventions differ by platform, but a few things are true nearly everywhere.

Readers browse by genre and by tag. Nobody finds a serial by accident. They come through a genre listing, a trending page, a tag search or a recommendation. Your story needs to belong somewhere findable.

Readers decide fast. Chapter one is read by many, chapter five by fewer, chapter twenty by a small fraction. The drop-off is steep and public. That is not a reason for despair; it is information, delivered chapter by chapter, that no novelist gets.

Volume is expected. A web novel that ends at 80,000 words is short. Readers who like a serial want it to keep going, and the platforms reward stories that run.

Schedule is the contract. Readers follow update days. A missed day is a broken promise; a consistent day is the strongest retention tool there is.

Choose the story for the form

Not every idea suits serialisation. The ideas that thrive share some properties: a protagonist who can keep wanting things across hundreds of chapters, a world with room in it, a structure that produces its own next problem. Progression fantasy, LitRPG, cultivation, regression, dungeon and system stories, long romance arcs, isekai, and workplace or academy stories all do this natively. Literary fiction with a single quiet arc mostly does not.

Pick a genre you actually read. Serial readers know their genre's conventions intimately and will notice, in chapter one, if you do not. Then read the top of that genre's listing on your target platform for a week. You are looking for what the audience expects, not for something to copy.

Then write the premise as one sentence: a person, a situation, and why it cannot stay the way it is. "A dead noblewoman wakes up on the morning of the day she made her worst mistake" is a premise. "A fantasy world with a magic system based on debt" is a setting.

Plan an arc, not a novel

Serials run long and change as they go. A full outline to chapter 300 will be wrong by chapter 40, and the time spent on it is time not spent on chapters. What you need is an arc outline: a run of roughly 15 to 40 chapters with a clear promise at the start and a payoff at the end, and a paragraph describing where the series goes after that.

For each chapter in the arc, note three things: what the reader carries in from the last hook, the one thing that changes, and the last line or beat. That last column is the most important thing in your planning. If you cannot fill it, the chapter is not planned.

Keep the long plot loose on purpose. Reader response will show you which characters and threads deserve more room than you gave them, and a serial that cannot bend toward what works is a serial that loses the audience it was building.

The chapter is the unit

Everything in a web novel is judged at chapter scale. A chapter has to do four things:

1. Re-enter fast. Readers may have waited a day or a week. Remind them where they are in a line or two of scene, not a paragraph of recap.
2. Deliver one beat. Something changes: a fight, a decision, a discovery, a relationship shifting. Not three things, and not zero.
3. Be worth reading on its own. A chapter that exists only to set up the next one reads as filler, and filler is where readers leave.
4. End on a reason to click. A question, a reversal, a decision, a line that changes the situation. Not always a literal cliffhanger; see web serial cliffhangers for the rotation.

Pick a chapter length that fits your platform and keep it. Consistency matters more than the number; readers learn how long an update takes and plan around it. Our chapter length guide for serials has the working ranges.

The first chapter

The first chapter of a serial does more work in fewer words than any other chapter you will write, because it is the one most people read and the one most people leave. In roughly this order it needs: who we are with and one specific thing about them; what their situation is and why it is unstable; the genre promise (the reader should know by the end whether this is a dungeon crawl, a court intrigue or a slow-burn romance); and a hook.

What it does not need: the world's history, the magic system's rules, the cast, or the backstory. All of that arrives when the story needs it. A first chapter that opens on a prologue about the ancient war is the most common way a serial dies at chapter one.

We have a dedicated post on first chapters for Royal Road and one on Wattpad story hooks; the principles are the same, the emphasis differs by audience.

Build a buffer before you post

This is the single decision that separates serials that finish from serials that stall. Write a stock of chapters before you publish the first one. Ten to twenty is a common number for a new serial; the right number is the one that lets you miss a bad month without missing a post.

The buffer also lets you fix things. You will discover in chapter eight that chapter three planted the wrong clue. With a buffer, you fix chapter three. Without one, a thousand people have read chapter three and you are writing around the mistake for the rest of the arc.

Posting and schedule

Choose an update day (or days) you can actually keep, and post at the same time. Fill in the platform's metadata carefully: genre, tags, a cover, a blurb. The blurb is a pitch, not a summary; it should promise the genre and the premise and stop. Readers scan blurbs in seconds.

Then keep the schedule. If life intervenes, post a short note and a date rather than going silent; readers are generous with honesty and unforgiving of disappearance.

Read the response, but slowly

Platforms will show you views, follows, ratings and comments. New serial writers check hourly, and it is a good way to stop writing. Look once a week. The number worth watching is retention across the first few chapters: if many readers open chapter one and few reach chapter three, the problem is the opening and it is fixable in a revised chapter one.

Comments are where the useful information is. Readers will tell you which character they like, where they were confused, and what they expect next. Confusion notes point at a craft problem. Expectation notes tell you what promises you have made, which may not be the ones you meant.

Do not argue in the comments, and do not rewrite the story to please the loudest reader. Take notes, and let the arc outline absorb what you learn.

Habits that keep a serial alive

• A fixed writing session at a fixed time, sized to produce slightly more than the schedule needs. The buffer should grow, not shrink.
• A running story bible: characters, places, rules, and what each chapter established. Serial continuity errors are the most common complaint in comments, and a bible prevents most of them. Our story bible template is built for this.
• Arc reviews. At the end of each arc, spend a session reading the whole arc and planning the next one with what you have learned.
• A hiatus policy, decided in advance. When you will take breaks, how you will announce them, and what the buffer needs to be before you do.

Writing web novels with AI

Serial writers use AI drafting more than most fiction writers, because the volume is relentless and the structure is predictable. It works best at the beat level: you write the chapter plan with the hook, the model drafts the scene, you rewrite for voice and cut the summary endings models love. It works badly as a replacement for the arc outline, and it forgets your world unless you keep the bible in front of it; see keeping AI from forgetting your characters. Used well, it can double a writer's chapter output. Used as an autopilot, it produces chapters readers recognise and leave.

A minimum plan for your first serial

One sentence of premise in a genre you read. A 20-chapter arc outline with a last-beat column. A chapter length you can produce twice a week. Ten chapters written before posting. A fixed update day. A story bible started on day one. That is enough to begin, and beginning is the hard part.

Try it in SparkLore

The free web novel first episode tool drafts a serial-shaped opening chapter from a premise, with the genre promise and a hook built into the structure, which is a useful way to see what a first chapter for this form looks like before you write yours. Inside a project, the LitRPG serial template gives you an arc structure and a bible you can adapt to any progression genre. Create an account to keep the outline, the bible and the chapters in one place while the serial runs.