How long should a D&D session be? What the polls say, what the clock says, and when to stop

The average D&D session length, from the data that exists

There is no census of D&D tables, so every figure is a poll of whoever answered, and the four worth reading disagree in a useful way. The largest self-reported poll, on the EN World forums in 2016, had 151 DMs and players pick their average session: 41 per cent said four hours, 27 per cent three, 20 per cent five and 13 per cent six or more. A smaller poll on the same forum in 2020, with about sixty respondents who could tick more than one box, had 61 per cent choosing "less than 4 hours" and 41 per cent "4-6 hours". Sly Flourish’s 2016 survey of 6,600 DMs — the biggest sample of DMs on record — published its session-length results only as charts, but its write-up lists "running 4 hour sessions" and "running sessions weekly" among the answers so common they correlated with nothing else.

The fourth figure is the one that was measured rather than remembered. In August 2026 the transcription service Archivist published the lengths of the sessions its users had recorded, defined as the last spoken timestamp minus the first: the average was exactly three hours, 43.7 per cent of sessions ran between two and three hours, and only about 10.5 per cent ran four hours or longer. Sources and dates for all four are in the table at the end of this page.

So the honest average is two numbers. People remember the evening, which is around four hours door to door; the recorder hears the game, which is around three. The hour in between is arrival, food, the catch-up on everyone’s week, the bathroom breaks and the ten minutes at the end where nobody has quite left. That hour is not waste — it is a good part of why people keep showing up — but it is worth knowing it exists when you plan a session or price a recording.

Why three to four hours is where most tables land

Three hours of play is roughly what fits one real combat and two or three scenes of talking, exploring or planning, with a break in the middle. A fight in fifth edition at mid levels with five players and a handful of enemies routinely takes the better part of an hour once initiative is rolled; add the scene that leads into it and the scene that follows, and you have used most of an evening on one meaningful thing happening. Shorter than that and sessions end mid-fight, which is the single most common complaint about short sessions. Longer than that and the second half is noticeably worse than the first.

The drop-off in the last hour is real and everyone at the table can feel it. Decisions get faster and sloppier, players check their phones between turns, the DM starts summarising rather than playing out, and the notes — if anyone is keeping them — thin out to nothing. A session that ends at three and a half hours with everyone still leaning in beats one that ends at five with half the table gone quiet, and the second one is harder to recap, because the part nobody remembers is the part that happened last.

The other force is scheduling. Four hours is the longest block that fits a weekday evening after work and dinner, and a four-hour Sunday slot still leaves a weekend. Weekly tables run shorter than monthly ones for the same reason: a group that only meets every six weeks will play for six hours because it has to, and a group that meets every Thursday does not need to.

How long a D&D session should be online

Online sessions run shorter, and should. Talking into a headset for four hours is more tiring than talking across a table — there is no body language to rest on, everyone speaks slightly over everyone else, and a dropped connection costs five minutes every time. Two and a half to three hours is a good target on Discord, Zoom or a virtual tabletop, with one proper break rather than the drifting ten minutes an in-person table takes naturally.

Two things make an online session feel longer than its clock time. One is combat on a VTT, which is slower than at a table until everyone knows the interface. The other is the missing arrival hour: online, people join at the start time and leave at the stop time, so three hours online is three hours of game, not two hours of game inside a four-hour evening. If your online sessions feel oddly exhausting at the same length as your old in-person ones, that is why. They are denser.

If the group is split across time zones, aim shorter still and meet more often. Two hours weekly keeps a campaign alive better than four hours fortnightly, because the gap between sessions is where campaigns die, and that gap is twice as long on the fortnightly schedule.

New players, one-shots and first sessions

A first session for people who have never played should be shorter than your normal game, not longer: two to three hours, with one easy fight early so they learn the rhythm of a turn before it matters. New players are doing something tiring that the rest of the table has automated, and a long first session is how you lose a player who would have loved the second one.

A one-shot is the exception that runs long. Three to four hours is the standard convention slot for a reason: a complete story with a beginning, a fight and an ending needs most of that, and there is no next week to finish in. Write the one-shot to the slot, and when the clock says forty minutes left, start the last scene whether or not the middle one has finished.

When a long session stops paying: six hours and up

Some tables run six, eight or ten hours, usually because they meet rarely. It works for them, and the data above says it is uncommon: about one logged session in sixty runs past six hours. What breaks past the fourth hour is not fun so much as everything downstream of it.

Energy first: a marathon has two or three sessions’ worth of decisions in it, and the ones made in hour seven are made by tired people. Then memory: a ten-hour day produces more to remember than anyone will write down, and the recap of it is a list rather than a story. Then the practical limits. The Craig Discord bot records up to six hours in one go on its free tier; a phone left recording for ten hours fills its storage or its battery; and transcription services that meter by the hour price a marathon at two or three ordinary sessions, with upload caps of their own — this site’s is eight hours and 500 MB per file, which is why the sentence after this one exists.

If you do run long, build the day as two sessions with a real meal between them, stop the recording at the break and start a second one, and write the five end-of-session lines twice. Treat the second half as a new session in your notes, because by the time you reread them it will feel like one.

How long a D&D campaign should be, in sessions rather than hours

The sibling question has no dataset behind it that this page could cite, so here is the honest shape of the answer instead of a number. Published adventures are written for a level range, and a party that plays a four-hour session weekly gains a level somewhere between every two and every four sessions at most tables, so a book that runs from first to around tenth level is a campaign of roughly twenty to forty sessions: six months to a year of weekly play, two years at a fortnightly table. A campaign to the top of the level range is the multi-year kind, and most of those end for scheduling reasons rather than story ones.

Length in sessions is also the number that matters for your notes. A twelve-session arc fits in a head; a forty-session one does not, which is roughly the point at which "who was that NPC" starts being asked every week and the campaign memory habits stop being optional. If you are choosing a campaign length, choose the one your group’s calendar can actually finish; a short campaign that ends is worth more than a long one that trails off, and it is the only kind that produces an ending anyone remembers.

Session length changes what you have to remember

Every hour of play is an hour of things that happened: names said once, promises made in passing, a ruling someone will hold you to. A two-hour session produces a recap a player will read; a six-hour one produces a document. If your sessions are long, the end-of-session habit matters more, not less — the five things to write down at the end of every session are the same five whether it ran two hours or eight, and the longer the session the less of it survives in anyone’s head by morning.

The same goes for the recording, if you make one. At the settings most phones use, a four-hour session is a file in the low hundreds of megabytes; the recording guide has the file-size arithmetic and the setup that gets four usable hours out of one phone. A transcript of a four-hour session runs to roughly a short novel’s worth of words, which is more than anyone will read start to finish and exactly why the useful form of it is a search box and a recap rather than the text itself.

Deciding when to stop, and a session planner to fill the hours

The right length for your table is the one that ends while people still want more, which is a decision you make before the session, not a thing the clock does to you. Pick a hard stop, tell the table, and plan the last scene to start twenty minutes before it. How to start a D&D session, and how to end one covers the stopping point, the cliffhanger and the ten-minute wrap-up in detail.

If you want the hours budgeted before you sit down, the session prep checklist carries a D&D session planner: a timed outline of a four-hour session you can copy and fill in, alongside the nine-step prep list. It is the "what goes in the hours" half of this question; this page is the "how many hours" half.