Why does D&D 5e combat take so long?

Most of the time is not spent rolling dice; it is spent re-deriving information the table already decided once. Rolling initiative one monster at a time, hunting through a book for a condition, and re-explaining the map each round all add minutes that never show up as "fun." Fix the lookups and the handoffs, and the actual decisions and rolls move fast on their own.

How do I speed up combat without cutting content?

Pre-roll what you can before the table sits down: initiative, monster HP, and any saves you know are coming. Keep a one-line reminder of each creature's best move so you are not improvising tactics and math at the same time. None of that removes a single decision point for the players; it only removes the dead air around them.

Should I roll initiative for every monster separately?

Only when it matters. A pack of six identical goblins can act on one shared initiative count; a boss or a monster with a reaction worth tracking earns its own slot. Group turns collapse six rolls and six lookups into one, and the players rarely notice the goblins moved together instead of individually.

When should I just end a fight?

When the outcome is no longer in doubt and the table already knows it. If the party is mopping up the last hit point of a fleeing rat, narrate the kill and move on; if the players are debating whether to finish off a genuinely dangerous foe, keep rolling. The test is whether another round could still surprise anyone, not whether the monster is literally still alive.

Do the 2024 rules make combat faster?

A little. Weapon mastery and the tightened action economy remove a few of the old edge-case rulings, and clearer conditions cut down on rules debates. But the 2024 rules do not fix a slow table by themselves; the biggest speed gains still come from prep and from running a tight turn loop, not from which printing of the book you use.

How to Run D&D 5e Combat Faster

By Vito · Updated July 6, 2026

Why 5e Combat Drags

Ask a table why their fights run long and they will usually blame the dice, but the dice are rarely the problem. Watch a slow combat closely and the time goes to three repeatable leaks: initiative that gets rolled and re-rolled one creature at a time, rules questions that send someone flipping through a book (or three tabs of a PDF) mid-round, and turns where the player has clearly already decided what to do but the table stalls anyway waiting for the DM to catch up on monster HP or a forgotten condition.

None of that is inherent to the system. A tight 5e fight, run well, moves nearly as fast as the players can talk, because the DM is never doing arithmetic or research live at the table. Everything below is aimed at removing exactly those three leaks, not at cutting content the players would miss.

Prep That Speeds the Table

The single highest-leverage thing you can do before a fight starts is pre-roll it. Roll initiative for every combatant, including the monsters, before the session, and write the order down. Roll (or pre-average) hit points for every creature in the encounter at the same time. None of this is information the players ever see mid-fight anyway, so doing it in advance costs you nothing at the table and saves a real, repeated interruption every single round.

Pair the numbers with a one-line tactical reminder for anything smarter than an animal: "focuses the healer," "flees below half HP," "opens with its breath weapon." You are not scripting a decision tree, just giving yourself a note so you are not inventing tactics and doing math in the same three seconds. For a mixed encounter, decide ahead of time which monsters are worth their own initiative slot and which can be grouped; see the next section for why that split matters.

The Run-Time Loop

Once the fight starts, run a strict declare-and-resolve loop and resist the urge to narrate before you know the outcome. On each turn: ask the player what they are doing, get the roll, apply the result, then narrate it in one or two sentences and move immediately to the next creature in the order. Narrating a big flourish before you know whether the attack even hits wastes breath on outcomes that might not happen.

For monster turns, work from your pre-rolled initiative and your one-line tactical note; do not stop to weigh options you already ruled out in prep. Group identical monsters onto a single initiative count and resolve them as a block: six goblins acting together become one entry in the order instead of six, and the players almost never notice the difference in fiction. Save individual initiative slots for anything whose timing actually matters, like a boss with a reaction or a creature the party is specifically trying to interrupt.

Keep a running tally of HP and conditions where everyone can glance at it if your table likes that visibility, but do not let the tracker become a second job. The point of the loop is momentum: declare, resolve, narrate, next. A round that keeps that rhythm for eight combatants can finish in well under two minutes.

A Combat Cheat Sheet

Rules lookups are the leak that is easiest to fix and easiest to forget to fix. Before the session, jot down the handful of conditions and edge cases you know this fight will touch: what "prone" actually does to attack rolls, how advantage and disadvantage cancel, when a creature can use a reaction. You do not need the whole book; you need the six or seven rulings that come up in almost every fight, written where you can glance at them without breaking the loop above.

Keep the sheet to rulings, not reproduced tables from the book: a line reminding you that a prone attacker has disadvantage, not a copy of a printed chart. If a question comes up that is not on your sheet, make a fast ruling, say it out loud once, and keep moving; you can check the exact wording after the session and adjust for next time. A ruling you commit to in the moment is worth more at the table than a perfectly correct one you spend ninety seconds finding.

Trimming the Fat

Speed also comes from knowing when to stop rolling. If the outcome of a fight is no longer genuinely in doubt, whether that is a single fleeing rat at one hit point or a hopelessly outmatched patrol, narrate the ending and move on instead of resolving every remaining attack roll. The test is not "is the creature still alive?"; it is "could another round still surprise anyone at the table?" If yes, keep playing it out. If no, end it and get back to the story.

The same instinct applies to bookkeeping mid-fight: do not track resources or conditions the encounter will never touch, and do not make players restate their AC or bonuses every round when you already wrote them down before the fight started. Every minute you save on paperwork is a minute the table spends on the actual choices that make combat worth playing.

Where the Tools Fit

The Initiative Tracker does the pre-roll and running-order work above for free: load the combatants, roll or enter initiative once, and it keeps the order, HP, and conditions visible so you can stay in the declare-and-resolve loop instead of managing a scratch sheet. When a ruling question comes up mid-fight, the Rules Quick-Reference gives you the short version of a condition or interaction in seconds, which is exactly fast enough to answer without breaking momentum. If you need a monster on short notice, the Monster Generator produces a usable stat block and tactical note instantly, so an unplanned fight does not force you to stall the table while you build one from scratch.

This guide is about running the fight once it starts; for help building the encounter itself, read the D&D encounter balancing guide, and for what changed under the newer rules, read the 2024 encounter building guide. Between the two, you can walk into a session with a fair fight already designed and the tools open to run it fast.

Frequently Asked Questions

Why does D&D 5e combat take so long?: Most of the time is not spent rolling dice; it is spent re-deriving information the table already decided once. Rolling initiative one monster at a time, hunting through a book for a condition, and re-explaining the map each round all add minutes that never show up as "fun." Fix the lookups and the handoffs, and the actual decisions and rolls move fast on their own.
How do I speed up combat without cutting content?: Pre-roll what you can before the table sits down: initiative, monster HP, and any saves you know are coming. Keep a one-line reminder of each creature's best move so you are not improvising tactics and math at the same time. None of that removes a single decision point for the players; it only removes the dead air around them.
Should I roll initiative for every monster separately?: Only when it matters. A pack of six identical goblins can act on one shared initiative count; a boss or a monster with a reaction worth tracking earns its own slot. Group turns collapse six rolls and six lookups into one, and the players rarely notice the goblins moved together instead of individually.
When should I just end a fight?: When the outcome is no longer in doubt and the table already knows it. If the party is mopping up the last hit point of a fleeing rat, narrate the kill and move on; if the players are debating whether to finish off a genuinely dangerous foe, keep rolling. The test is whether another round could still surprise anyone, not whether the monster is literally still alive.
Do the 2024 rules make combat faster?: A little. Weapon mastery and the tightened action economy remove a few of the old edge-case rulings, and clearer conditions cut down on rules debates. But the 2024 rules do not fix a slow table by themselves; the biggest speed gains still come from prep and from running a tight turn loop, not from which printing of the book you use.

Open the Initiative Tracker

Let's Go!