Infodumping

Definition

Infodumping is less about volume than about narrative regime: the voice turns into an encyclopedia, action-time stops, the reader shifts from a story to a lecture. Three paragraphs can be infodump; ten well-integrated lines may not be.

What it's for (and why we cave)

Authors infodump because they're afraid the reader won't understand. It's almost always a problem of pacing and trust: information can almost always be spread across 50 pages, sneaked into dialogue, or left implicit. The useful rule: just-in-time delivery — information arrives precisely when the reader needs it to understand the scene.

Variants by genre

• Hard SF: maximum temptation (physics, biology).
• Fantasy: royal genealogies, pantheons, geographies — toxic chapter 1.
• Historical: 30 years of European politics in a prologue.
• Crime / thriller: technical protocol (forensics, hacking) ladled out.
• Romance: the ex's backstory in two pages when one scene would do.
• YA / NA: magical school system delivered like an enrollment brochure.
• Literary adaptations of video games / TTRPGs: a manual legacy.

Techniques to avoid infodumping

• Friction dialogue: two characters who disagree explain by contradicting each other.
• Constrained action: we learn the rule when it blocks the hero.
• Inserted document: codex excerpt, letter, memo — short, dated, situated.
• Ignorant POV: one character who discovers, another who resists explaining.
• Term economy: an invented word glossed once, never redefined.
• Ellipsis: cut before the exhaustive explanation; the reader fills in.

Common pitfalls

• A prologue laying out 4,000 years of history before any character appears.
• "As you know, Bob...": dialogue where experts explain what they already know.
• The world bible copy-pasted raw into the manuscript.
• The narrative voice suddenly slipping into Wikipedia tone.
• Over-correction in reverse: everything under-implicit, the reader lost.

Examples

• Dune (Herbert) — virtuoso: the Princess Irulan epigraphs license the info instead of hiding it.
• The Lord of the Rings — Council of Elrond: long, but staged through disagreement.
• The Fifth Season (Jemisin) — info trickled in fragments, never in blocks.
• Ted Chiang — Story of Your Life: the science is revealed through the narrator's experience.
• The Three-Body Problem (Cixin) — infodumps used openly, but signaled as such.
• Ann Leckie — Ancillary Justice: worldbuilding through POV interiority, never head-on.
• Andy Weir — The Martian: technical exposition delivered as in-character problem-solving.

Writing tips

• Apply the three-line maximum rule for consecutive exposition in the first 50 pages. Beyond, break it up: dialogue, action, ellipsis.
• Use scene constraint: every piece of information must emerge from friction (a character stuck, an object resisting, a missing word). No obstacle = infodump.
• Highlighter test: after the first draft, highlight pure exposition paragraphs. Target: under 5 % of total volume in the first 100 pages.
• Zero-page glossary: every invented term is glossed in context at first occurrence, never in a lexicon or redefined later. Three unglossed occurrences and the reader is gone.

Go deeper: The 7 worldbuilding sins and Show don't tell exercises.

Revision checklist

• Does the reader need this information now to understand the next scene?
• Does it come through a disagreeing character or a situated document, not the narrative voice?
• Can you cut 50% without losing meaning?
• Does the narrative voice's tone stay consistent or jump to Wikipedia?