You avoid infodumping by changing how the world reaches the page, not how much of it you build. Deliver each piece of lore at the moment a character actually needs it, filter every detail through a point of view with a reason to notice it, and let the reader assemble the wider world from scattered clues rather than a lecture. The world can be as deep as you like as long as almost none of it is explained directly.
This is for the writer who has built something genuinely large, a magic system with real internal logic, a couple of warring nations, a religion with a schism in its past, and who now cannot figure out how to get any of it onto the page without three paragraphs of history that bring the chapter to a halt. There are no universal rules here, and plenty of beloved books break every guideline below, but there is a craft logic underneath the choice, and once you can see it the problem stops feeling like a wall. The mistake almost every new world-builder makes is to assume that because they know something about the world, the reader needs to be told it. My feeling is that the opposite is usually true: the reader needs to feel that you know it, and being told is the one delivery method that reliably kills that feeling.
The good news, and the thing I want to establish before anything else, is that infodumping is not a worldbuilding problem. It is a delivery problem, one slice of the larger craft I lay out in worldbuilding for web fiction. You do not fix it by building less. You fix it by changing the route the information takes to reach the page, and that route is what the rest of this is about. If you are still wrestling with whether to build all of this up front at all, that is a separate question, and I have argued the case for building the world late rather than early in a companion piece, why worldbuilding should come last. This piece assumes you have the world already, or enough of it, and only need to get it into the story cleanly.
What actually counts as an infodump
An infodump is any passage that stops the story to explain the world directly to the reader, and the reliable tell is that the information is aimed at the audience rather than at anyone standing in the scene. The classic shape is the block of narrated history that opens a chapter, three centuries of political backstory delivered before a single character has done anything, but it hides in dialogue just as often, and in the false-modest "for those who do not know" aside, and in the character who conveniently thinks through the entire cosmology while waiting for a kettle to boil. The test I use is simple, and I think it catches most cases: if I cut the passage, does anything change for the people in the scene? If the answer is no, the passage was for me and my pride in having built the thing, not for the story.
What makes an infodump land badly is not that it contains information. Stories are made of information. It lands badly because it asks the reader to hold a pile of facts that have no home yet, no character who cares about them, no decision resting on them, no tension pulling them forward. Facts without stakes are just homework, and readers of web fiction in particular vote fast; they will not do homework in chapter three on the promise that it pays off in chapter thirty. The same fact, delivered at the moment a character's life depends on it, reads as tension rather than tedium. The information did not change. Its timing and its owner did.
Deliver each fact at the moment a character needs it
The single most reliable fix for infodumping is to withhold every piece of lore until a character in the scene actually needs it, and then to deliver it as part of what they are doing rather than as a pause in it. This is the difference between telling the reader, up front, that mana burns out the meridians of anyone who channels past their tier, and showing a character reach past their tier in a fight because the alternative is dying, and feeling the meridians tear as they do it. The rule arrives welded to a choice and a cost, so the reader learns it the way the character learns it, under pressure, with something at stake. Will Wight's Cradle runs almost entirely on this principle; the sacred-arts system is deep, but you are rarely told a rule you are about to see broken, and the explanations that do appear are short because the fights have already taught you most of what you need.
Think of every fact in your world as having a natural home, which is the first scene where a character's want or fear or decision runs into it. That is where the fact belongs, and delivering it earlier is what creates the dump. When you catch yourself explaining something the reader has no reason to care about yet, the fix is usually not to cut the fact but to move it, forward, to the scene where it finally matters, and to let the character's need carry it in. How much of a system you reveal, and how hard you make its rules, is a related decision that deserves its own attention, and I have gone deep on it in how to build a magic system; the short version is that the rules a character will exploit to win must be shown, and the lore they will never act on can usually stay off the page entirely.
Let the reader assemble the world from clues
Readers are much better at building a world from scattered evidence than we give them credit for, and the technique of trusting them to do it has a name, incluing, coined by the author Jo Walton to describe the practice of seeding a world through small concrete clues the reader assembles on their own rather than through explanation. You mention a coin, a scar, an oath sworn to a god nobody worships anymore, and you do not stop to gloss any of it. The reader files each detail, and somewhere around the third or fourth the shape of the thing clicks into place, and the click is a pleasure precisely because they did the work. Explain the same three details outright and you have robbed them of that pleasure and slowed the scene doing it.
Frank Herbert's Dune, published in 1965, is the master example, and it is worth studying precisely because the iceberg beneath it is enormous. Herbert built an entire ecology, an economy, a religion, and a political order, and he puts almost none of it on the page as explanation. The Bene Gesserit, the Kwisatz Haderach, the spice, the water discipline of the Fremen, all of it arrives as terms characters use without pausing to define, because to them the terms are ordinary. Herbert even exiled the encyclopedic material to appendices at the back, which is the honest admission that it is reference, not story. A Game of Thrones does something similar with its houses and their histories; you are never lectured on the Targaryen dynasty, you absorb it from the way people fear and invoke it. My advice, then, is to write your world the way its inhabitants would speak of it, which is casually, incompletely, and with the assumption that everyone present already knows the basics. The gaps that leaves are not holes. They are the reader's invitation in.
Filter every detail through a point of view that has a reason to notice it
The cleanest delivery mechanism you have is a narrator or viewpoint character with genuine reasons to notice some things and ignore others, because a filtered world reads as lived-in while an exhaustive one reads as catalogued. A blacksmith walking through a market notices the quality of the iron on the stalls and the price of coal; a spy in the same market notices the exits and who is watching whom. Neither of them notices, or explains, the full history of the market, because people do not narrate the obvious to themselves. When you route every detail through what this specific person, in this specific mood, would actually clock, the exposition stops feeling authorial and starts feeling like perception, and perception is invisible in the way that explanation never is.
This is also the great advantage of a genuinely ignorant viewpoint character, and it is why so much web fiction opens with someone new to the world. Pirateaba's The Wandering Inn runs an immense setting through Erin, an ordinary person dropped into it who learns the rules by tripping over them, so the reader learns exactly as fast as she does and never faster. N.K. Jemisin's The Fifth Season, published in 2015, does the harder version, dropping you into the middle of orogeny and the Stillness with no preamble at all and trusting the accumulating experience to teach you, which it does. The point in every case is that the point of view is doing the filtering for you. If you are tracking which of your several viewpoint characters knows what at any given time, and it gets genuinely hard to hold in your head across a long serial, that is exactly the kind of thing the platform's wiki and the connected world builder are built to keep straight, so the reveals stay consistent and nobody knows a secret two chapters before they were told it.
Cut the dialogue that exists only to explain
Expository dialogue delivers worldbuilding well only when both speakers have a real reason to be having the conversation, and the reliable failure is the as-you-know-Bob exchange, where one character tells another something they both plainly already know so that the reader can eavesdrop. The moment a line exists purely to inform the audience, readers feel the strings, even if they could not name what bothered them. The fix is not to remove the information from the dialogue but to give the characters a reason to fight over it. Let one of them be wrong about the history. Let them want different things from the same fact. Let one genuinely not know, and have a real stake in learning, so the explanation is also a negotiation, a confession, or a warning.
Ursula K. Le Guin was very good at this, letting her characters withhold and misremember and argue about their own world so that the exposition always carried an emotional charge. The version I try to hold in my head when I catch myself writing a lecture in quotation marks is that dialogue is not a delivery pipe for facts, it is two people wanting things, and any lore it carries has to ride along inside the wanting. If I strip the want out and I am left with a clean transfer of information, I have written a dump with quotation marks around it, and the honest move is to rewrite the scene so the characters have somewhere to be and something to lose while they talk.
Keep the world off the page so you are not tempted to cram it in
A surprising amount of infodumping comes from fear, specifically the fear of losing the thing you built if you do not get it onto the page, so the practical discipline that prevents it is to keep the full world somewhere outside the manuscript. When the entire history, the maps, the pantheon, and the system rules live in a story bible or a wiki you can trust, the pressure to smuggle them into a chapter drops away, because they are safe; you are not going to forget them, and you can reveal exactly the slice each scene needs knowing the rest is on file. This is the quiet mechanical reason that keeping a reference outside the prose tends to produce leaner prose. The world does not have to be in the chapter to be real. It only has to be somewhere you can reach.
Running a web fiction platform, the pattern I see most in authors who dump is not that they built too much, it is that they had nowhere to put what they built except the story itself, so the story became the filing cabinet. Give the world a home of its own, a wiki with entries that @mention each other, a timeline you can check when you need to know what was already public knowledge in a given arc, and the chapters relax. My feeling, after watching a lot of serials find their feet, is that the writers who reveal a world most gracefully are almost never the ones who built the least. They are the ones who trusted that a deep world felt through a narrow, needful, human point of view will always read as richer than the same world explained in full, and who kept their appendices, like Herbert, at the back where they belong.
Common questions about revealing worldbuilding
What is an infodump in fiction?
An infodump is a passage that stops the story to explain the world to the reader directly, usually a block of history, cosmology, or system rules delivered by the narrator or by a character who has no in-scene reason to be saying it. The tell is that the information is aimed at the reader rather than at anyone in the scene, and that nothing would change for the characters if the passage were cut. Information is not the problem; information without a character who needs it is.
How do you reveal worldbuilding without infodumping?
Reveal it in the moment a character needs it and no sooner. Attach each fact to a want, a fear, or a decision the character is making, so the lore arrives as part of the action rather than as a pause in it. Let small concrete details imply the larger system, and trust the reader to assemble the world from clues the way they assemble a person from gestures. The world can be as deep as you like as long as almost none of it is explained outright.
How much worldbuilding should you show the reader?
Far less than you build. A useful ratio is that the reader should see the sliver the current scene touches and feel the rest as pressure behind it. Frank Herbert built an entire ecology and religion for Dune and puts almost none of it on the page directly; the depth is felt because the characters act as though it is real, not because it is explained. If you have built ten times what appears in the prose, you are probably close to the right proportion.
Is expository dialogue a good way to deliver worldbuilding?
Only when both speakers have a genuine reason to be talking about it. The failure mode is as-you-know-Bob dialogue, where one character tells another something they both already know purely so the reader can overhear. Dialogue delivers lore well when the characters disagree about it, want different things from it, or when one of them genuinely does not know and has a real stake in finding out. The lore has to ride inside a conversation the characters would have anyway.
Where should all the worldbuilding I am not showing actually live?
It should live somewhere outside the manuscript so you are not tempted to cram it into a chapter to avoid losing it. A wiki or a story bible holds the full history, the maps, and the system rules as reference, which frees the prose to reveal only the slice each scene needs. Keeping the world off the page is often what makes disciplined reveals possible in the first place, because you stop treating the chapter as the only safe place to store what you know.
by Jacob Tam · August 27, 2026
I run IlorisNovel. If you want to see what it feels like to keep the whole world in one place while you write, you can try the editor and world builder with no account.