Craft

    How to Avoid Info Dumps in a Web Serial: 6 Ways to Teach Your World Without Stalling

    9 min read Updated By the PlotWrite team

    Avoid info dumps in a web serial by giving the reader a fact only when the current scene needs it, and by attaching it to something happening: a choice, a risk, a surprise or a mistake. Split a big lore block into small beats across chapters, and keep System screens to one fact each.

    You built a magic system, a pantheon and a ranking ladder, and every piece of it is cool. Then chapter 1 opens with four paragraphs of history, and your reader leaves before the hero speaks. This guide shows how to get the world across without stopping the story. There are six techniques, short samples written for this article, and a checklist you can run on a draft before you post.

    TL;DR

    • An info dump is any stretch where the story stops so the author can explain the setting. Sanderson calls it the death knell of a story.
    • Run a need-to-know test: what does the reader need to understand in this scene, and what can wait?
    • Attach each fact to conflict, a choice or a mistake, so the reader learns it by watching it matter.
    • Split one big lore block into a drip of small beats. A 540-word dump can become six 90-word beats in a worked example below.
    • Keep System screens and stat blocks to one new fact each, and put the reaction right after.
    • Park the rest in an author note, a glossary or a footnote, for readers who want it.

    Write your serial with PlotWrite: it remembers every rank, skill and secret and checks each new chapter before you post.

    Start 7-Day Free Trial

    What counts as an info dump in a web serial?

    An info dump is any stretch where the story stops so the author can explain the setting. The scene has no choice, no risk and no change in it. It is only the world being described.

    Sanderson puts it this way in a 2022 Q&A. He also says some setting context cannot be avoided, and that readers tolerate more of it in epic fantasy than in other categories. The question is how long you pause the plot to deliver it.

    Same fact, two delivery modes
    AspectInfo dumpDelivered in a scene
    What the reader seesThe narrator explainingA character acting or choosing
    What the reader feelsWaiting for the story to resumeCuriosity, then a small payoff
    When the fact appearsBefore it mattersThe moment it matters
    How long it takesOften a block of paragraphsA line or two inside a scene
    “The info dump is when you deviate from character and plot to give us setting elements.”
    Brandon Sanderson, New York Comic Con Q&A, reported by Popverse (October 25, 2022)

    Why do serial readers punish exposition more than book readers?

    A web serial reader decides chapter by chapter. There is no sunk cost of a purchased book, and the next serial is one tab away.

    That makes the first chapters and every arc opening the riskiest places for exposition. A reader who has not yet met a reason to care will not read a paragraph of lore.

    Chapter-ending hooks do their work only if the chapter before them held attention. See how to write a cliffhanger readers can't skip.

    Technique 1: Run a need-to-know test

    Before you write a lore paragraph, ask one question. What does the reader need to understand to follow *this* scene?

    Most of the time the answer is one fact. Write that fact and cut the other nine to a list for later.

    • Needed now: the rule that makes the fight tense (the spell costs blood).
    • Needed soon: the rule the next chapter will test (blood magic is banned in the city).
    • Needed later: how the ban started, who enforced it, the three wars before it.

    The last group is what usually becomes the dump.

    Technique 2: Hang the fact on conflict

    A fact lands harder when someone is about to lose something because of it. Put the rule in the way of a character.

    Dump: *The Guild of Ash taxed every cultivator one tenth of their stones, a law passed after the Third Famine, enforced by licensed collectors.*

    In a scene: *The collector held out his palm. "One in ten, Mara. Same as the Famine tax, same as always." She had eleven stones. She counted them twice, hoping the number would change.*

    The second version has fewer facts, and the reader remembers more of them. The tax, its size and its history all arrive, and a character is under pressure the whole time.

    Technique 3: Drip it across chapters

    A serial gives you something a novel does not: time. Use it. Split a big lore block into beats and place each where it pays off.

    The chart below is a worked example, not survey data. It takes a 540-word explanation of a realm system and spreads it as six beats of about 90 words, one per chapter, each placed where a character needs it.

    Words of lore per chapter: one dump against a six-chapter drip (worked example)
    • Dump: chapter 1540
    • Drip: chapter 190
    • Drip: chapter 290
    • Drip: chapter 390
    • Drip: chapter 490
    • Drip: chapter 590
    • Drip: chapter 690

    Worked example written for this article, not survey data. Same 540 words of lore, two delivery plans.

    Technique 4: Fix 'as you know' dialogue

    Dialogue is the usual escape hatch, and it fails in a familiar way. Two characters tell each other things both already know, for the reader's benefit. Writers call this "as you know, Bob" dialogue.

    Before: *"As you know, Rael, the Spire has ten floors, and each floor is guarded by a Warden who grows stronger the higher you climb."*

    After: *Rael stared up the Spire. "Ten floors," he said. "And the one at the top is the one that killed my father."*

    Fix it by giving one speaker a reason to say the line. Give them a want, a doubt, or a wrong belief the other character can correct.

    7-day free trial

    Spreading lore across chapters means remembering what the reader already knows. PlotWrite keeps a page for every character, skill and place with what is true at each chapter, and checks each new chapter before you post. Works with the Claude or ChatGPT plan you already pay for.

    plotwrite.ink learns your writing style, keeps track of your characters and world rules, and can draft the next chapter in your voice with your Claude or ChatGPT plan or your own AI key. Built for Royal Road, Wattpad, and serial authors who post weekly.

    Start 7-Day Free Trial
    • No credit card
    • Cancel anytime
    • Full Architect access
    • Works with your Claude or ChatGPT plan or your own AI key

    Ready to try it on your own serial? See how PlotWrite keeps a LitRPG serial consistent

    Technique 5: Keep System screens to one new fact

    LitRPG gives you a dangerous shortcut. A blue box can explain anything, so the temptation is to explain everything.

    Bad screens read like a manual. Good screens show one new fact and hand the moment back to the character.

    Manual style:

    *[Skill: Iron Skin. Reduces physical damage by 5% per level. Costs 10 Stamina per second. Cannot stack with Stone Skin. Level 1 of 10.]*

    One fact, then a reaction:

    *[Skill learned: Iron Skin (Lv 1)]*

    *Ten stamina a second. Kell did the sum and winced. He had maybe six seconds of armour, and the wolf was still coming.*

    The cost, the clock and the stakes all arrive through the reaction. For layout, see how to format LitRPG system messages and how to write LitRPG stat blocks.

    Technique 6: Give curious readers somewhere else to go

    Some of your readers want the pantheon, the map and the full rank table. Give it to them, off the main path.

    • Author's note. Keep it short and put it at the end. See how to write an effective author note.
    • Glossary or wiki chapter. One reference chapter, linked from the fiction page or an early note.
    • Footnotes. A light touch can work. A 2022 Substack piece on avoiding info dumps points to Terry Pratchett's Discworld footnotes as a way to add depth without stopping the scene.

    The story chapter should stand on its own for a reader who skips all of it.

    A self-edit checklist before you post

    Run these on a chapter draft. The numbers are rules of thumb from this article's author, not research.

    Info dump check
    CheckFix if it fails
    Can you cut a lore paragraph without confusing this scene?Cut it, or move it to the chapter that needs it
    Does a character want something while the fact is delivered?Add a want, a risk or an obstacle
    Is one speaker telling another what both know?Rewrite as a question, an argument or a mistake
    Does the System screen hold more than one new fact?Split it, and add the reaction
    Is the opening chapter over 150 words of backstory in a row?Move the backstory to chapters 3 to 5

    Where does PlotWrite help with exposition?

    Dripping lore across chapters has a cost. You have to remember what you have already told the reader, and what you promised to explain later.

    PlotWrite is the memory for a web serial. The Story Bible keeps a page for every character, place, item and skill, with what is true at each chapter. You can see what has been revealed, and what has not.

    Before you post, Check chapter compares the new chapter with everything before it and flags contradictions. Plan and the In-Between track threads and beats, so a lore thread you promised in chapter 12 doesn't go quiet. These tools write no story text. If you use AI to draft prose, Royal Road's AI rules apply to that text, so check its current wording.

    Start with the 7-day free trial, no card needed.

    What's climbing Rising Stars, every Tuesday

    One short email a week: the serials climbing Royal Road's Rising Stars, why they're climbing, and one thing to borrow for your own launch. Free. Unsubscribe in one click.

    Frequently asked questions

    How much backstory is too much in chapter 1?+

    There is no fixed limit. As a rule of thumb, if a reader could skip a paragraph of backstory and still follow the scene, move it later. Chapter 1 has to earn the reader's trust before it asks for patience.

    Can I explain the System in a prologue?+

    You can, but a prologue that explains rules before any character has a problem is the most common info dump. Show the System through the first use instead, and explain only what that use needs.

    Is it ever fine to info dump?+

    Sometimes a short explanation is the right tool, especially when a character is learning something and the reader is learning with them. Keep it short and give it a reason to exist.

    How do I explain cultivation realms without a table?+

    Show a character being measured against a realm. Name the next realm they want, then reveal what separates it from the current one when they struggle to cross. See the cultivation novel formula.

    Should I put a glossary in my story?+

    A glossary is a good option for readers who want it, as long as the chapters read fine without it.

    Sources

    1. Popverse: Writing Tips from Brandon Sanderson (October 25, 2022)(thepopverse.com)
    2. Brandon Sanderson: Plot Q&A, Writing Lecture #4 (2025), posted February 11, 2025(brandonsanderson.com)
    3. Prose & Quan: Discworld and avoiding Information Dumps (March 22, 2022)(proseandquans.substack.com)

    Continue reading

    Built for serial authors who want to earn

    PlotWrite remembers every rank, skill and secret in your story and checks each new chapter before you post. Works with the Claude or ChatGPT plan you already pay for, or your own AI key.

    No credit card required · Cancel anytime · Full Architect access · Works with your Claude or ChatGPT plan or your own AI key

    More from the blog