An info-dump is a block of explanation — backstory, history, rules, technical detail — delivered while nothing else is happening. Readers recognise it immediately, even if they could not name it, because their eyes start to slide down the page. The fix is not to remove the information but to change when and how it arrives.
The working rule: give the reader information at the moment they need it to understand what is happening, and not much earlier.
Why writers do it
Info-dumps usually come from a good instinct: you know your world and your characters well and you want the reader to understand them. In a first draft, writing it all down is fine — it is how you find out what you know. The mistake is leaving it in the order you discovered it. Your research order is rarely the reader's order.
It is also common in fantasy and science fiction, where there is more to explain, and in first chapters, where writers fear the reader will be lost. A confused reader is often less of a problem than a bored one; a little curiosity keeps people turning pages.
Ask what the reader needs right now
Go through an explanatory passage line by line and ask, for each fact: does the reader need this to follow this scene? If not, mark it. Most of what gets marked is not wrong, only early. Move it to the scene where it first matters — the history of the war belongs where a character's choice depends on it, not in the opening pages.
Some facts never matter at all. They belong in your notes. A series bible is a good home for everything you know that the reader does not need to.
Attach information to conflict
Information is easiest to absorb when someone wants something. A character who must cross a border reveals more about the political situation, through the questions at the checkpoint and what she hides, than a page about the political situation ever could. Backstory lands best when it explains a present choice: we learn that he lost his brother at sea at the moment he refuses to get on the boat.
This is also why starting in the middle of events, in medias res, often works: the reader is too busy following what is happening to need a briefing.
Avoid "as you know" dialogue
Turning an info-dump into dialogue does not fix it if characters tell each other things they both already know. "As you know, Captain, the reactor has been unstable since the accident three years ago" is a lecture with quotation marks. Real people talk about what they do not agree on or do not yet know. Give the explanation to a character who genuinely lacks it — a newcomer, a child, a stranger — or let it surface through an argument. More on how people actually speak in how to write realistic dialogue.
Use small pieces and trust inference
Readers are good at working things out from fragments. A character who checks the sky before every sentence about the harvest tells you more about the climate than a description of it. A single unfamiliar word used confidently, without explanation, makes a world feel real; a glossary paragraph makes it feel like a textbook.
- One fact per sentence, inside action. Spread explanation through the scene rather than stacking it.
- Let objects carry history. A chipped cup, a locked room, a name nobody says aloud.
- Leave some questions open. Unanswered questions are what bring readers back to the next chapter.
Flashbacks and prologues
Flashbacks are not info-dumps if they are scenes, with their own stakes, and if they arrive when the reader is curious about the past. They become dumps when they exist only to explain. Prologues are a frequent hiding place for the same problem: pages of history before the reader cares about anyone. If your prologue is mostly explanation, try cutting it and seeing what the reader actually misses.
When a dump is acceptable
There are times when a short block of explanation is the right choice: a comic aside in a strong narrative voice, a detective's final summary, a moment where the pace deliberately slows after a big scene. Readers accept exposition from a voice they enjoy. The test is whether the passage is interesting in itself, not only useful.
How to check your draft
Highlight every paragraph in which nothing happens in the present — no action, no dialogue, no decision. Look at where those highlights cluster. A cluster in the first pages is the classic case; the advice in how to write your first chapter applies directly. Then ask a reader to tell you where they started skimming. They usually point to exactly the paragraphs you highlighted.
We make Arwy, where books are published chapter by chapter and readers can comment on a single line, which makes the "this is where I got lost" moment unusually easy to find. It runs on Android and in the browser; there is no iOS app yet.
Not sure whether your opening explains too much? Readers will show you where they skim. Arwy is on Google Play.
Writing something yourself? Everything we know about publishing it — free guides, how rights work, and what you can actually earn — is collected on Arwy for writers.
← All posts