How Long Should a Web Serial Chapter Be, and How Often Should You Post?
Choose the chapter length your story needs, then post as often as your weekly word count and your chapter buffer can sustain. The two numbers trade against each other: at a fixed weekly output, longer chapters mean fewer posts and shorter chapters mean more. We could not find a platform rule we can cite for either number, so this guide gives you a method and arithmetic instead, and you set the values.
Below is a five-step method with a worked schedule whose every figure you can check with a calculator. It uses two free, in-browser tools: the Reading Time and Pacing Calculator and the Web Serial Release Planner. Neither needs an account, and the numbers you type stay in your browser.
Disclosure and what we did not verify. WriteIDE makes these tools and the free WriteIDE desktop app. We tried to read Royal Road's own help pages on October 20, 2026 while preparing this post, but they sat behind an automated browser check, so this post makes no claim about a Royal Road or other platform rule for chapter length or posting frequency. Before you commit to a schedule, read the platform's own help pages and ask in its author forums. Advice marked "our opinion" is craft opinion, not data.
The five steps at a glance
| Step | Question | Tool or input |
|---|---|---|
| 1 | How many words can I finish in a typical week? | Your own word counts |
| 2 | What chapter lengths does that allow, and how long does each take to read? | Reading Time and Pacing Calculator |
| 3 | How many chapters should I post per week? | Chapters you finish, minus what you bank |
| 4 | How long does my buffer last at that cadence? | Web Serial Release Planner |
| 5 | What do I change when the answer is not sustainable? | Cadence, length or buffer |
How do I know how many words I can write in a week?
Measure, do not guess. Add up the words you finished in each of the last several weeks, and take a figure you could repeat on an ordinary week, not your best one. The planner's own hint for the same idea is "a pace you can hold, not a best week."
Everything below uses an invented author, Mara, who finishes 5,000 words in a typical week. The numbers are made up for this post so the arithmetic is easy to follow.
How long should a web serial chapter be?
There is no length we can cite as a platform requirement, so start from the two things you can measure: how many chapters your weekly output allows, and how long each chapter takes a reader. The Reading Time and Pacing Calculator turns a word count into minutes. It divides words by a reading speed, and its default is 250 words per minute.
That default sits inside the range found in the research. In a review and meta-analysis of 190 studies, the psychologist Marc Brysbaert estimated the average adult silent reading rate in English at 260 words per minute for fiction, and reported that most adults fall between about 200 and 320 for fiction. Individuals differ, so treat reading time as an estimate.
For Mara, each row below uses 5,000 words a week. Chapters per week is 5,000 divided by chapter length, rounded down, and reading time is words divided by 250, rounded up to a whole minute as the calculator does:
| Chapter length | Chapters she can finish per week | Reading time per chapter | Reader's reading per week |
|---|---|---|---|
| 1,250 words | 4 (4 × 1,250 = 5,000) | 5 minutes | 20 minutes |
| 1,650 words | 3 (3 × 1,650 = 4,950) | 7 minutes (6.6 rounded up) | about 20 minutes |
| 2,500 words | 2 (2 × 2,500 = 5,000) | 10 minutes | 20 minutes |
| 5,000 words | 1 | 20 minutes | 20 minutes |
Two things stand out. First, a fixed weekly output gives the reader about the same total reading each week whichever row you pick, so you are choosing the rhythm, not the amount. Second, the shorter the chapter, the more often you must finish one. In our opinion, pick the length at which scenes end naturally rather than cutting a scene to hit a number, and keep your usual length steady so readers know what a post feels like.
The calculator also shows a "serial pacing" label for any word count. That label is a rough guide written by us, and we do not have a public source behind it, so use it as a prompt to think, not as a standard to meet.
How often should I post?
Post at the rate you can keep up, then check that rate against your buffer. A buffer is the number of chapters you have written but not yet posted. The Release Planner works from three numbers: your buffer, the chapters you write per week and the chapters you post per week. Each week the buffer gains what you write and loses what you post.
Mara has 12 chapters banked, all 2,500 words, and writes two per week. Here are three posting rhythms with those same inputs. The weekly change is chapters written minus chapters posted:
| Plan | Posts per week | Weekly change in buffer | Result in the planner |
|---|---|---|---|
| A. Match the writing pace | 2 | 2 − 2 = 0 | Buffer holds at 12 chapters |
| B. Post more than she writes | 3 | 2 − 3 = −1 | Runway of 12 ÷ 1 = 12 weeks, so the buffer is empty after 12 × 7 = 84 days |
| C. Post less than she writes | 1 | 2 − 1 = +1 | Buffer grows by 1 a week; reaching 20 chapters ahead takes (20 − 12) ÷ 1 = 8 weeks |
For Plan B, the planner also shows how long a lead can be held. A lead of 2 chapters lasts about (12 − 2) ÷ 1 = 10 weeks, 5 chapters about (12 − 5) ÷ 1 = 7 weeks, and 10 chapters about (12 − 10) ÷ 1 = 2 weeks. These are the same inputs as the planner's starting values, so you can open the tool and see them.
The book-level view uses the Reading Time Calculator's serial section. A 90,000-word book at 2,500 words per chapter is 90,000 ÷ 2,500 = 36 chapters. At two a week that is 36 ÷ 2 = 18 weeks of content, and at three a week it is 12 weeks.
What should I change when the numbers do not work?
Plan B shows a schedule that works for 12 weeks and then stops. Three levers can fix it, and you can try each in the tools:
- Lower the cadence. Move from three posts to two, and the weekly change returns to zero.
- Shorten the chapter. If Mara writes 1,650-word chapters instead (the second row of the earlier table), her 5,000 words become three chapters a week, so writing three and posting three also gives a weekly change of zero. The cost is that each chapter holds less story.
- Build the buffer first. Plan C banks one extra chapter a week. Reaching 20 chapters ahead takes eight weeks, and then the 3-posts-a-week schedule has a longer runway before it empties.
Our opinion is that a slower schedule you never miss serves readers better than a fast schedule that has to stop, and that you should tell readers about a change in a short author note rather than going quiet. Neither point is a measured fact.
What do I check before I commit to a schedule?
- Run a week you have already lived. Put your real last-four-weeks average into the planner, not a plan.
- Measure the stories you compare against. Paste a few chapters of comparable stories into the calculator's "Count it from my text" mode and read the word counts, instead of trusting someone's memory of a norm. The text stays in your browser.
- Read the platform's own pages. Check help pages and author forums for rules or recommendations on updates, and note the date you read them.
- Plan the break. Decide ahead what a missed week looks like, and what you tell readers.
If you are wondering how posting patterns relate to Royal Road's lists, our Rising Stars Self-Check explains how the list works, and states plainly that it is not the real formula and does not predict anything.
Where does a writing app fit?
The calculators work from numbers you type. WriteIDE is a free desktop writing studio for LitRPG and progression-fantasy authors, and as of version 0.7.5 it shows scene, chapter and project word totals, and lets you set a daily word goal and review your writing activity and streaks, so your weekly figure comes from the manuscript instead of memory. Publish › Ready to post lists each chapter with a checklist and preview, prepares it with Copy for Royal Road or Copy for Patreon, and keeps a Mark posted date for each platform that you enter yourself. Nothing is posted or sent for you. WriteIDE runs on macOS, Windows and Linux, stores your project on your computer, and requires no account. It does not write your prose.
For more of the craft side, see how to write a LitRPG, the roundup of free tools for LitRPG authors, and mastering Royal Road formatting for placing a finished chapter.
Frequently asked questions
How many words should a web serial chapter be?
We cannot cite a platform rule, so choose by your story and your weekly output. At 5,000 words a week, 1,250-word chapters give four a week, 2,500-word chapters give two, and a single 5,000-word chapter gives one. The reader gets about the same amount to read each week either way.
How often should I post a web serial?
At the rate your weekly output and buffer can sustain. Put your buffer, your chapters written per week and your chapters posted per week into the Web Serial Release Planner, and it shows how long the buffer lasts. If you post more chapters than you write, the buffer shrinks until it is empty.
How long does it take to read 2,500 words?
About 10 minutes at 250 words per minute, which is the Reading Time Calculator's default. In a review of 190 studies, Marc Brysbaert estimated the average adult silent reading rate for fiction in English at 260 words per minute, which would make it about 10 minutes as well (2,500 ÷ 260 is 9.6). Your readers will vary.
What is a chapter buffer?
The chapters you have written but not yet posted. A larger buffer lets you keep posting through a slow writing week. The Release Planner shows how many weeks it lasts when you post faster than you write.
Should I post every day?
That depends on whether you can finish a chapter each day. In our opinion, do not choose a daily schedule unless your measured weekly output supports it, and use the planner to see how long the buffer lasts. We found no platform source that requires it.
Sources and when we checked them
- Marc Brysbaert, "How many words do we read per minute? A review and meta-analysis of reading rate," Journal of Memory and Language 109 (2019), article 104047, DOI 10.1016/j.jml.2019.104047. We read the paper's abstract on October 20, 2026 for the 260 words per minute average for fiction and the 200–320 range most adults fall in.
- The Reading Time and Pacing Calculator and Web Serial Release Planner on this site. Every worked figure above comes from the arithmetic those tools document on their pages, and we checked the planner's runway and lead calculations against its source code on October 20, 2026.
Written for WriteIDE 0.7.5, October 2026. Mara and her numbers are invented examples, and advice marked as opinion is craft opinion.
More in Workflow
Nine ways to show stats and system messages in a LitRPG chapter, each with a real example from our free tools: when to use it, how long it should be, and what to watch for.
10 min readLitRPG vs Progression Fantasy vs GameLit vs Cultivation: What Is the Difference?A plain comparison of LitRPG, progression fantasy, GameLit and cultivation: what each label usually promises, where the labels overlap, and how to choose one for your book. Sources cited, boundaries hedged.
10 min read10 LitRPG System Design Mistakes (and How to Fix Each)Ten common ways a LitRPG system goes wrong, from free level-ups to dead stats, with a hand-checkable example and a fix for each.
11 min readNotes worth sending
Release notes when a version ships, plus Lab notes and guides. No weekly filler.