Como Evitar Info Dumps na Tua Escrita
An info dump is any passage where the story stops moving so the writer can explain something — the history of a kingdom, how the magic system works, a character's backstory. The information might be necessary. The delivery is the problem. When you park the narrative to deliver a lecture, readers skim or put the book down.
The good news: every piece of exposition can be restructured so it arrives through story instead of interrupting it.
Why Info Dumps Happen
Writers info-dump for one reason: anxiety. You are afraid the reader will not understand something, so you over-explain. You spent weeks building a magic system and want the reader to appreciate it, so you lay it all out in chapter two. You know a character's tragic backstory and feel the reader needs it now, so you insert a three-paragraph flashback before the character has done anything to make the reader care.
The antidote is trust. Trust that readers are smart, curious, and willing to be confused for a little while. A reader who has questions keeps reading. A reader who has been given all the answers has no reason to continue.
Technique 1: Deliver Information at the Point of Need
Do not explain something before the reader needs to know it. Explain it at the moment it becomes relevant — or better yet, slightly after, when the reader is already wondering.
Info dump approach:
The Marchetti family had controlled the docks for three generations. In 1952, Enzo Marchetti had won the port concession through a combination of bribery and violence. His son Luca expanded the operation into smuggling during the 1970s, and now his grandson Marco...
Point-of-need approach:
The dockworkers stepped aside when Marco walked through. Nobody spoke to him, but everyone watched. When Ren asked who he was, the foreman just said, "Marchetti," as if the name explained everything — and in this city, it did.
The second version tells the reader everything they need: Marco is powerful, feared, and connected to a name that carries weight. The specific history can trickle in later, when it serves a scene.
Technique 2: Use Conflict as a Vehicle
Information delivered during conflict feels like story, not lecture. When characters argue about something, they naturally explain it to the reader while advancing the plot.
"You can't just open a rift in the middle of the market district." "I can if I anchor it properly." "You said that about the last one, and it killed three people and took a week to close."
In three lines of dialogue, the reader learns: rifts can be opened, they require anchoring, they are dangerous, the character has failed before, and there is disagreement about whether to try again. No one stopped to explain anything. The information emerged from friction between characters with different positions.
Technique 3: Show the Consequences, Not the Rules
Instead of explaining how something works, show what happens when it goes right or wrong. The reader infers the rules from the outcomes.
Info dump:
Channeling magic required physical contact with a natural element. The channeler would draw energy from the element, converting it into a usable form. However, drawing too much energy would deplete the source and cause a backlash effect...
Consequence-first:
Kira pressed her palms into the river mud and pulled. Energy surged up her arms — cold, electric, almost too much. The reeds along the bank withered and turned black in a widening circle around her. She let go before the circle reached the tree line. Last time she had not let go fast enough, and the dead patch took a full season to recover.
The reader now understands the system through experience rather than explanation. The rules are implicit in the scene, and the reader feels clever for piecing them together.
Technique 4: Distribute Information Across Scenes
A common mistake is delivering all the information about a topic in a single passage. Instead, break it up. Give the reader 20% now, another 30% three chapters later, and the rest when it matters most.
Consider how Tolkien handles the Ring. In The Fellowship of the Ring, we learn it makes you invisible. Chapters later, we learn it is dangerous. Later still, we learn the full history. The information arrives in layers, each one raising the stakes. If Gandalf had explained everything in the first chapter, the sense of growing dread would be lost.
Technique 5: Use a Character Who Does Not Know
A character who is new to a world, organization, or situation provides a natural reason for others to explain things. But the key is that the newcomer asks specific questions driven by their immediate needs — not general questions designed to trigger a lecture.
Weak: "Tell me everything about the Guild."
Strong: "Why does everyone keep bowing when we pass that building?"
The second question is specific, prompted by observation, and will yield a focused answer. The first invites an encyclopedic monologue.
The Revision Test
When you spot a passage that might be an info dump, ask:
- Does the reader need this information right now? If not, cut it or move it later.
- Can a character discover this through action or conflict? If yes, dramatize it.
- Can I cut this by half and still be understood? Almost always, yes.
Readers remember what they piece together far better than what they are told. Give them the pieces.
Organize your world's lore in Plotiar. Keep worldbuilding details in dedicated notes so you can reference them while writing — and reveal them to readers at exactly the right moment. Try it free.