Have you ever, in your entire lifetime, managed to overhear an incredibly important conversation between two evildoers whose words just happen to totally unravel the big mystery you've been secretly solving? No that's never happened to you? It happens in books all the time. And when it does, it usually occurs as an infodump. Lots of writers do it. Do you, too?
Here's the Information You Need
The overheard conversation is just one example of infodumping. A much better one is the monologue, which is very frequently used for this purpose. You know how in the cheesy adventure movie the villain finally captures the hero and then the villain, instead of killing the hero, goes into a lengthy explanation of all his motives so that the hero can marvel at his cleverness? This is infodumping. It's giving the reader, or viewer as the case may be, a ton of data that explains various plot points which have occurred throughout the story.
And it is often quite tedious. Everyone likes dialogue when it's realistic, but most people don't want to read huge blocks of dialogue when it ought to be a narrative instead. Infodumping is an easy way to reveal certain facts about the plot, and some critics will say that it's too easy. In books, events should unfold naturally in order to maintain realism. When characters overhear shady conversations or have the luck of being treated to lengthy monologues, it tends to ring a little false.
And it is often quite tedious. Everyone likes dialogue when it's realistic, but most people don't want to read huge blocks of dialogue when it ought to be a narrative instead. Infodumping is an easy way to reveal certain facts about the plot, and some critics will say that it's too easy. In books, events should unfold naturally in order to maintain realism. When characters overhear shady conversations or have the luck of being treated to lengthy monologues, it tends to ring a little false.

















