How to Play D&D on Discord: The Complete Setup

What You Need

The whole setup fits in one table. The sections below go through it piece by piece.

Set things up roughly in that order. Bad audio ruins a session faster than anything else, and notes are the piece people forget until three months in.

Voice

Your players will notice this part most, so spend time on it.

• One voice channel per table. Name it after the campaign, like curse-of-the-hollow. If you run more than one game, give each its own channel.
• Turn on noise suppression. Discord’s built-in noise suppression (in Voice & Video settings) removes keyboards, fans, and dogs. Ask every player to check it before session one.
• Push-to-talk for noisy players. If someone plays from a busy room, push-to-talk saves everyone else’s sanity.
• Check input sensitivity. If a player’s voice keeps cutting off mid-sentence, their sensitivity is set too high. Automatic sensitivity is a good default.
• Use a headset. Earbuds with a mic are fine. Laptop speakers plus laptop mic is where echo comes from.

Music and ambience

Background music makes a huge difference, and it’s also where most Discord setups get complicated. Many of the popular music bots that streamed from YouTube were shut down over the years, so don’t build your setup around one specific bot. Three options hold up:

• The DM shares audio. Stream a browser tab or app with sound. Simple, but the DM controls the volume for everyone.
• A soundboard or ambience tool that plays into the voice channel. Good for sound effects at the right moment.
• Everyone plays the same playlist locally. Post a link and let each player set their own volume. Low-tech and surprisingly pleasant.

Channels and Roles

Most messy Discord games have one thing in common: rolls, jokes, rules questions, and the map link all end up in #general. Give each kind of message its own home. Five or six channels is plenty, and each should have a job you can say in five words.

Then add two roles:

• @DM can post in #announcements, pin messages, and manage channels.
• @Player can see the campaign’s channels. If your server has other people on it, hide the campaign category from everyone without this role.

Two more Discord features are worth using: Scheduled Events for session dates (players get a reminder and can mark “interested”), and threads for side conversations, like one player’s downtime scene, so they don’t take over the main channel.

A bigger server with rotating groups needs a different layout. See our guide to running West Marches on Discord.

Copy this into a note and build your server from it:

ROLES
@DM        manage channels, post announcements
@Player    see campaign category

CATEGORY: [CAMPAIGN NAME]
#announcements   (DM only, players read)
#table-talk      (out of character)
#in-character    (roleplay between sessions)
#dice            (all rolls here)
#characters      (sheets, portraits, backstories)
#recaps          (one post per session)
[campaign-name]  (voice, players only)

BEFORE SESSION ONE
[ ] Everyone tested mic + noise suppression
[ ] Dice bot works in #dice
[ ] Map / VTT link pinned in #table-talk
[ ] First session added as a Scheduled Event

Dice and Maps

Dice

You can let everyone roll physical dice and trust them, and plenty of groups do. A dice bot has two advantages: everyone sees every roll, and nobody has to do the math.

• Avrae is the best-known D&D 5e bot. Besides rolling, it can import characters from D&D Beyond and track initiative.
• Simple dice bots just roll what you type, like /roll 1d20+5. Enough for most tables and any system.

Whichever you pick, keep rolls in #dice. For a full comparison, see our list of the best Discord bots for D&D.

Maps

Discord has no built-in battle map, so pick one of these:

Whatever you choose, players keep talking in the Discord voice channel. The VTT is for the map and the dice; Discord is for the people. Pin the map link in #table-talk and never move it, so nobody spends the first five minutes of a session hunting for it.

Keeping a Record

At a physical table your group shares a notebook, maybe a whiteboard. On Discord, anything nobody wrote down disappears when the voice channel empties. Three weeks later someone asks “what was the name of the guy with the map?” and the answer is somewhere in two hours of audio nobody kept.

At minimum, post a short recap in #recaps after each session. Our session recap template takes about ten minutes to fill in. A post can be as short as this:

Someone has to write it, every time, right after a long session. That’s usually the DM, and it’s usually the first habit to slip. If you’d rather not, Kazkar joins the voice channel when you type /summon, and after /banish it writes the session up as a chronicle and adds the new NPCs, places, and items to a linked campaign wiki.

Recording is a decision for the whole table, so bring it up before you start, ideally at session zero. To compare options, see how to record a TTRPG session and our comparison of Craig and Kazkar.

Your First Session on Discord

Don’t make your first night a three-hour dungeon crawl. Start with a short session zero:

1. Tech check (15 minutes). Everyone joins voice, tests mics, rolls one die in #dice, and opens the map link.
2. Session zero (45–60 minutes). Tone, boundaries, schedule. Our session zero checklist covers what to agree on.
3. A short opening scene (30 minutes). Introduce the characters and end on a hook. Thirty minutes of real play teaches you more about your setup than a week of planning.

After a couple of sessions the setup stops being something you think about. The map is where it always is, rolls land in one channel, and last week’s recap is waiting at the top of #recaps when everyone logs in. That’s the point of the hour you spent: the evening starts with the game.

Frequently Asked Questions