Dialogue works in web fiction when it reads fast and does more than one job at once, which means every distinct character needs a voice a reader can tell apart on the page, banter has to reveal or advance rather than merely fill space, and exposition has to arrive as something a character would actually say. The medium sharpens all of this, because web fiction is usually read on a phone at speed, so long unbroken speeches and interchangeable voices are punished harder here than in print. Keep the tags plain, let word choice and rhythm carry who is speaking, and cut every line that only exists to be spoken.
Dialogue is the part of web fiction where a lot of otherwise promising writing quietly falls apart, and I think the reason is that speech looks easy, everyone does it all day, right up until you try to put a dozen distinct people in a scrolling column of text and keep them straight. Running a web fiction platform, I read a great many chapters where the prose is clean and the plot is moving and then four characters open their mouths and all four sound like the author, and the scene goes slack because there is no friction, no personality, nothing to tell one voice from the next. The medium makes this harder than it is in print, because a web serial is usually read fast, on a phone, in the gaps of someone's day, so a slab of monologue that a reader would tolerate in a hardcover gets skimmed or abandoned on a screen. So this is a guide to writing dialogue that survives that reading environment: fast, distinct, and always doing more than one thing at once. Everything below can be, and has been, successfully contradicted by writers better than me, but these are the patterns I keep coming back to.
What makes dialogue work in web fiction?
Dialogue works in web fiction when it reads fast and pulls double duty, carrying character and plot in the same breath rather than stopping the story so people can talk. The single most useful test I know is to ask what a given exchange is doing besides being spoken, because a line that only conveys information could be narration, and a line that is only witty is filler, but a line that reveals a relationship while also advancing the plan is dialogue earning its place. My feeling is that the writers who are good at this are ruthless about cutting, they let characters interrupt, trail off, answer a different question than the one they were asked, and they trust the reader to fill the gaps, which is exactly the speed a scrolling reader wants. The rhythm of the medium rewards brevity in a way print does not, and a short, loaded exchange lands harder in a phone-sized column than a page of eloquent back-and-forth ever will.
The other thing that makes web fiction dialogue work is that it respects the format's pacing. A line of speech sitting alone on its own gets emphasis simply because it stands apart in the white space, and long stacked paragraphs of talk collapse into a wall the eye slides off. Andrew Rowe's Sufficiently Advanced Magic and pirateaba's The Wandering Inn both carry enormous casts, and part of how they keep an exchange legible across dozens of speakers is by keeping individual turns short and letting the visual shape of the page pace the conversation. If you want the wider frame this fits into, my complete guide to writing web fiction is the hub the rest of the craft pieces hang off, and dialogue is one of the levers that most reliably separates a serial people binge from one they bounce off.
How do you give characters distinct voices?
You give characters distinct voices by handing each of them a consistent pattern of word choice, sentence length, and preoccupation, so that the diction alone tells the reader who is talking before the tag does. A blunt fighter speaks in short flat declaratives and does not hedge; a scholar qualifies everything and reaches for the precise word; a schemer answers a question with a question and never quite commits to a straight yes. The cover test is the one I use: cover every speech tag in a scene, and if you can still tell who is speaking from the language on its own, the voices are real, and if you cannot, they are the author wearing different hats. Cradle is a clinic in this, because Lindon's careful deference, Yerin's clipped sword-honed bluntness, and Eithan's insufferable theatrical overflow are so distinct on the sentence level that Will Wight barely needs to attribute a line for you to hear it.
The trap to avoid, and it is a common one in the genre, is rendering accent or dialect phonetically, dropping letters and stacking apostrophes to signal that a character talks rough. My advice, then, is to carry accent through vocabulary and rhythm rather than spelling, because misspelled speech slows a fast reader to a crawl and reads, in bulk, as condescension toward the character. A dwarf does not need to say "wha' d'ye think yer doin'" to sound like a dwarf; give them blunt short sentences, old-fashioned idiom, and a fixation on craft and debt, and the voice arrives without the reader having to decode anything. Voice is also one of the clearest ways to show intelligence on the page, which is why the craft of distinct dialogue overlaps so heavily with how to write a smart character: a mind that is genuinely a step ahead sounds different from one that is not, and the difference lives in what the character chooses to say and, more tellingly, what they choose not to.
How do you write party banter that doesn't drag?
Party banter works when every exchange does a second job beyond being funny, so that a joke also tells you about a relationship, a tension, or what the group is about to do. Progression fantasy runs on a recurring cast, the party that levels up together and bickers between fights, and readers genuinely love that banter, which is exactly why it is so easy to overfeed. When banter drags it is almost always because it has come untethered from the plot, a page of quips that could be lifted out of the chapter with nothing lost, and the reader feels the story idling even when the individual lines are sharp. Matt Dinniman's Dungeon Crawler Carl is the reference point here, because Princess Donut's imperious commentary is relentlessly funny and also constantly characterizing, revealing her vanity, her loyalty, and the odd tenderness underneath, so the comedy is never just comedy.
The practical discipline is to give each banter beat a purpose before you write it and cut the ones that fail the test. A good exchange between party members can plant a seed the reader will need three arcs later, expose a fracture that will matter when the group is under pressure, or deliver the plan for the next fight in a way that is more alive than the leader reciting it. Shirtaloon's He Who Fights with Monsters leans harder on banter than almost anything in the genre, and it holds up because the constant verbal sparring is doing character work, drawing the lines of who trusts whom and who is performing, even at its most flippant. Banter is also a place where dialogue and action collide, since so much of it happens mid-encounter, and the way you thread talk through a fight without stalling the tension is its own skill, one I get into in writing LitRPG combat scenes. The rule I keep is simple: if an exchange is only funny, it is a candidate for the cut, and if it is funny and doing something else, it stays.
How do you deliver exposition through dialogue without an info dump?
You deliver exposition through dialogue by only letting a character say what they would actually have reason to say to the person in front of them, and by letting the listener resist, question, or misread it so the information arrives under tension. The signature failure is the "as you know" speech, where one character explains to another something both of them already understand, purely so the reader can overhear it, and every reader can feel the seam where the story stopped to lecture. Web fiction is especially prone to this because the genres are system-heavy, full of magic mechanics and world history and stat interactions that the reader legitimately needs, and the temptation is to have a mentor sit the protagonist down and unload it all in one grateful monologue. My feeling is that the moment a character starts explaining the world at length with no resistance from anyone in the room, the dialogue has stopped being dialogue and become a manual with quotation marks around it.
The fix is to give the exchange a reason to exist independent of the information, so the exposition rides in on a conversation the characters had their own motive to have. Let the listener disagree, or already know half of it and correct the speaker, or be lied to so that the reader gets the true version and the character does not, and suddenly the same facts arrive wrapped in friction. Mother of Learning handles a genuinely dense magic system this way, drip-feeding mechanics through arguments, negotiations, and the protagonist's own trial and error rather than through a single expository fountain, so the reader is always learning the world while something is also at stake in the scene. The information you most want the reader to absorb is the information you should make them work slightly to get, because a fact a character fought over is remembered and a fact a character recited is skimmed.
How should you format and tag dialogue for a screen?
You format dialogue for a screen by keeping the tags plain, letting action beats carry emotion, and using short turns and white space to set the pace. Elmore Leonard's 2001 rules of writing put it most sharply, advising writers to never use a verb other than "said" to carry dialogue, because "said" is invisible and the eye skips over it, while exotic substitutes like "expostulated," "gritted," or "hissed" announce themselves and pull the reader out of the exchange. The related discipline is to stop propping up "said" with adverbs, since a line that needs "he said angrily" to land is usually a line that has not done its own work; let the words themselves be angry, or follow them with a beat, a character slamming a cup down or turning away, that shows the feeling without naming it. On a phone, where the reader is moving fast, plain tags and physical beats keep the rhythm clean and the attribution effortless.
This is also where the tool you write in quietly matters, because dialogue is where formatting and readability meet, and seeing your chapter in something close to the shape a reader will actually see it in helps you catch the wall-of-talk problem before you publish it. Writing in the IlorisNovel editor, which renders your chapter in a clean reading column rather than a cramped document view, makes it easy to notice when an exchange has stacked into an unbroken block and to break it into the shorter back-and-forth a scrolling reader wants. The mechanical stuff, plain tags, action beats over adverbs, a new paragraph for each new speaker, is not glamorous, but it is the difference between dialogue a reader glides through and dialogue they have to decode, and on a screen the reader who has to decode is the reader who taps away.
The through-line under all of it is that dialogue in web fiction is never just people talking; it is the fastest, most efficient tool you have for doing three things at once, showing who a character is, moving the plot, and giving the reader the pleasure of a voice they recognize. Give each speaker a diction you could pick out with the tags covered, make your banter carry freight beyond the joke, let your exposition arrive under tension instead of in a lecture, and keep the mechanics plain enough to vanish, and the talk in your serial stops being the part readers skim and becomes the part they keep showing up for.
Common questions about writing dialogue in web fiction
How do you write dialogue that reads fast in web fiction?
Keep speeches short, keep the speech tags plain, and let white space do the pacing. Web fiction is mostly read on a phone at speed, so a wall of unbroken monologue stalls the reader in a way it would not in a printed novel. Break long exchanges into shorter back-and-forth turns, use "said" as your default tag so the eye skips over it, and lean on the natural rhythm of a scrolling column, where a line of dialogue on its own gets weight the moment it stands alone.
How do you give characters distinct voices?
Give each character a consistent pattern of word choice, sentence length, and what they tend to talk about, rather than spelling out accents phonetically. A blunt fighter speaks in short declaratives; a scholar hedges and qualifies; a con artist answers questions with questions. If you can cover the speech tags and still tell who is talking from the diction alone, the voices are distinct. Dialect rendered in misspellings almost always slows a reader down more than it characterizes, so carry accent through vocabulary and rhythm instead.
How do you write party banter that doesn't drag?
Make the banter reveal character, advance the plan, or raise the stakes, so it is never only filler between fights. Progression fantasy leans hard on party banter because the genre runs on a recurring cast, and it works when each joke also tells you something, about a relationship, a tension, or what the group is about to do. When banter drags it is usually because it has no job beyond being funny; give every exchange a second purpose and cut the lines that only exist to be quipped.
How do you deliver exposition through dialogue without an info dump?
Only let a character say what they would actually have reason to say to the person in front of them, and let the listener push back or misunderstand so the information arrives under tension. The classic failure is the "as you know" speech, where one character explains to another something they both already know purely for the reader's benefit. The fix is to give the exchange a reason to happen, a disagreement, a question, a lie, so the world-building rides in on a conversation the characters had a motive to have.
Should you use dialogue tags other than "said"?
Mostly no. Elmore Leonard's advice, in his 2001 rules of writing, was to never use a verb other than "said" to carry dialogue, because "said" is invisible and exotic substitutes like "expostulated" or "gritted" pull the reader out. Use "said" and "asked" as your workhorses, let action beats carry emotion instead of adverbs, and reserve a louder tag for the rare moment that genuinely earns it. The goal is for the reader to hear the line, not notice the tag.
by Jacob Tam · August 3, 2026
I run IlorisNovel, a platform for web fiction writers. If this kind of craft writing is your thing, the rest of the blog lives here.