How to run D&D on Discord: the server, the channels, the bots and the record
A campaign needs far less Discord than most server templates hand it. This is a layout for one table, the reason each channel exists, the two bots worth adding, and the part most setups forget: where the record of a session goes when the call ends.
· 8 min read
What you need to play D&D on Discord, and what you do not
You need a server, one voice channel, somewhere for dice and somewhere for the recap. That is a complete setup, and a group can be playing on it twenty minutes after deciding to. Everyone needs a Discord account and a headset; nobody needs to pay for anything.
You do not need a virtual tabletop to start. Plenty of tables play on voice alone and share an image when a map matters. If you add one later, it sits beside Discord, not instead of it: many groups on Roll20 or Foundry still talk on Discord.
You also do not need thirty channels. The usual way a campaign server dies is that nobody can find anything in it, and the fix is to start small and add a channel only when a conversation keeps getting lost.
A D&D Discord server template: eight channels for the table, two for the DM
Build this by hand once. It takes about ten minutes, and every channel in it has a job that some other channel was doing badly.
Campaign server layout (copy the names; the notes say what each is for)
D&D CAMPAIGN SERVER THE TABLE (category) #announcements next session, cancellations. DM posts only #scheduling polls and who can make it #table-talk everything out of character THE CAMPAIGN (category) #session-recaps one post per session, nothing else #handouts maps, letters, images the party has seen #party-loot shared inventory and money, kept by a player #dice every bot roll goes here VOICE (category) The Table the one voice channel DM ONLY (category, hidden from the Player role) #dm-notes #bot-testing ROLES DM manages channels, pins and events Player sees everything except DM ONLY
Why each channel exists, and the ones to add later
Announcements is separate from chat so that "we are moved to Thursday" is never forty messages up. Make it an ordinary text channel where only the DM role can post. Scheduling is separate from announcements so the argument about dates has somewhere to happen. Session recaps is its own channel with nothing else in it, so that scrolling it is reading the campaign in order. Dice has a channel because bot output buries conversation faster than anything else.
Common additions, once the table asks for them: an in-character channel for scenes between sessions, a quotes channel, a rules-questions channel so rulings can be found again, and a private channel per player for secrets and notes passed to the DM. Good names say what goes in them. A new player should be able to guess where to post without asking. Pin the link to your campaign website (primer, house rules, who is who) in the announcements channel so it is never more than one click away.
Roles and private channels: who can see what
Two roles are enough. Give yourself DM and everyone else Player, then make the DM category private to the DM role. Discord’s own guide to role-exclusive channels covers the clicks: you choose which role can see a channel when you create it, and people without that role do not see a private text channel in their list at all. A voice channel needs one more check. Discord’s older article says people who cannot join a restricted voice channel still see it in their list; its newer roles article says making a channel private removes the View Channel permission for everyone else. Look at the server as a player would, and do not give a secret voice channel a name that is itself a spoiler.
Set permissions on the category, not channel by channel. Keep the channels under DM ONLY synced to it, so that changing who can see the category changes all of them at once. Then check it the simple way: ask a player what they can see.
A per-player channel, visible to that player and you, is the cleanest way to pass a note at an online table. It also keeps each player’s secrets in one place you can find again.
Saving your layout as a Discord server template
Once the server is how you like it, Discord can turn it into a server template: a link that creates a new server with the same categories, channels, roles and permissions. It is the fastest way to start your next campaign, or to hand your setup to another DM. You generate it from Server Settings on the desktop or browser app; the mobile app cannot create one.
Two limits are worth knowing before you rely on it. Forum, announcement and stage channels, the types that need a Community server, are not included in a template, which is one more reason the layout above uses plain text channels. And a template link stops working if its creator deletes the template. That is why this page gives you a layout to build and not a link to click: a link to somebody else’s template lasts exactly as long as they keep it.
Voice, video and text while you play
Use one voice channel. A second one is only useful when the party splits and you want to run a private scene, and you can make it on the night. Ask everyone to wear headphones, because one open speaker puts an echo of the whole table into the call, and a noisy microphone is fixable if you catch it in the first session.
A voice channel has its own text chat, opened from the chat bubble beside its name. It is the right place for the things said during play that are not speech: a link to a spell, an image of the room, a whispered question. Keeping those out of the main channels means the campaign channels hold only what should be found later.
Video is optional and changes the game more than people expect. Faces help roleplay and cost bandwidth. If one connection is weak, voice only for everyone is fairer than one frozen square.
D&D Discord bots: the two worth adding
A dice and character-sheet bot is the first. Avrae is one built for the job: it rolls with advantage and crits built in, reads a character sheet from D&D Beyond, Dicecloud or a Google Sheet so a player can attack or make a save with one command, and runs an initiative tracker in a text channel. Add it, keep its rolls in the dice channel, and have everyone link their sheet before the first session, not during it. If the table would rather roll physical dice on trust, that works too, and you have one bot fewer to maintain.
A recording bot is the second, covered below. Past those two, be slow to add more. Every bot is something that can go offline at seven on game night, and scheduling and polls no longer need one. Ambient music is the usual third request; playing it from your own machine at low volume is less fragile than a bot.
Scheduling the next session without a bot
Discord has two built-in tools that cover it. A poll takes up to ten answers and can stay open for up to a week, which is enough to ask "which of these four evenings". A scheduled event gives the session a start time with the voice channel attached, so the table can see it coming, and anyone who marks themselves Interested is notified when it starts. Give the DM role permission to create events and use the same title every time.
The tools matter less than the habit. Agree the next date at the end of each session, while everyone is still in the call, and post it in announcements before you log off. The last ten minutes of a session is where that belongs.
Recording the session, and where the recap goes
This is the part most server setups leave out, and it is the difference between a campaign people can follow and one they have to remember. Record the voice channel with a tool built for it. The usual one is Craig, a bot that joins the channel on a /join command and records every speaker to a separate track until you type /stop. Its free tier records up to six hours and keeps the files for seven days, so download them the same night. The Craig guide has the full setup, and ask the table before you record anything.
Then use the recap channel. One post per session, written within a day, in a channel nothing else is posted in. Players who missed the night read it, players who were there correct it, and six months later it is the only complete account of the campaign that exists. How to write a session recap covers what goes in one, and it is shorter than you think.
If you want a transcript and a recap drafted from the recording, recording and transcribing D&D on Discord walks through which download to take and what to do with it.
Scenes between sessions: threads
Shopping trips, letters, downtime and the conversation two characters did not get to finish all work in text between sessions. Start a thread for each from the in-character channel so it does not swamp the channel itself. A thread is hidden from the channel list after a period of inactivity, three days by default, but it is not deleted, and searching the channel still finds what was said in it. For a game that is mostly or entirely text, running play-by-post is its own craft.
The first session on a new server: a ten-minute check
Do this at the start of session one, with everyone in the call, and the next forty sessions go more smoothly.
- Everyone joins and gets the Player role. Ask one of them to read out the channels they can see, and make sure DM ONLY is not on the list.
- Sound check. Each person says a sentence; fix the quiet microphone and the echo now. If you record with Craig, its /voice-test command exists for exactly this.
- Everyone rolls once in the dice channel with their own character.
- Ask about recording, out loud, and get a yes from each person.
- Pin the table rules in table-talk: when you play, how cancellations work, what the channels are for.
- Create the event for session two before anyone leaves.
Mistakes that quietly kill a campaign server
Too many channels on day one. Empty channels make a server feel dead, and people stop opening it.
Recaps posted in general chat. They scroll away in a day and nobody can find session twelve when it matters. The recap channel only works if nothing else goes in it. A channel holds up to 250 pins, which is plenty, but a channel that needs no pins because it holds only recaps is better.
Scheduling that belongs to nobody. If it is not one person’s job to post the poll, it is not posted. It does not have to be the DM, and it is a good job to hand to a player.
DM notes in a channel that was never made private. Check what the Player role can see before you paste the villain’s plan anywhere.
Discord, Avrae and Craig features named above, with sources
Every third-party figure quoted above, with where it came from and when it was checked. Prices move — if a date here is old, verify before relying on it.
| What | Value | Source |
|---|---|---|
| Discord server templates: what they copy | "Server Templates will let you clone existing categories, channels, roles, and permissions"; creating one is "currently only available on the desktop and browser app" (article text last edited July 2025) | sourceas of 2026-11-13 |
| Discord server templates: what they leave out | "Community-enabled channel types (e.g. Forum, Announcement, and Stage) are not transferable and are not included within Server Templates"; "If the Template creator deletes the Server Template, the link will no longer work" | sourceas of 2026-11-13 |
| Discord private channels | Private text channel: "Users who do not have the ability to access this channel will not see it on their channel list". Voice: "people who can’t access a voice channel will still be able to see the channel in their list" (article text last edited June 2020; the newer article in the next row reads differently) | sourceas of 2026-11-13 |
| Discord private channels: the newer roles article | "When you set up a private channel, Discord automatically enhances security by removing the View Channel permission from the @everyone role" (article text last edited July 2025) | sourceas of 2026-11-13 |
| Discord categories and permissions | Channels can sync with their category: "If you change the permissions on a category, all channels that are synced will automatically update" (article text last edited September 2020) | sourceas of 2026-11-13 |
| Text chat inside a voice channel | "the dedicated text chat within the voice channel", opened from "the Open Chat bubble to the right of the voice channel name" | sourceas of 2026-11-13 |
| Discord polls | "You can add up to 10 answers"; a poll stays open for "1 hour, 4 hours, 8 hours, 24 hours, 3 days, or 1 week" | sourceas of 2026-11-13 |
| Discord scheduled events | An event can be set for a voice channel, a stage channel or "Somewhere Else"; creating one needs the Create Events permission; pressing "Interested" means "you’ll also receive a notification when the event is officially live" | sourceas of 2026-11-13 |
| Discord pinned messages | "Each channel and DM supports up to 250 pinned messages"; "Any member can view pinned messages" | sourceas of 2026-11-13 |
| Avrae | "a Discord bot designed to help you and your friends play D&D online": a dice roller with advantage, disadvantage and crits built in; "can read character sheets from D&D Beyond, Dicecloud, or a Google Sheet"; an initiative tracker "in a text channel" | sourceas of 2026-11-13 |
| Craig: start, stop and test commands | /join (optionally naming a channel) and /stop; /voice-test: "Easily test your audio quality in a voice channel." | sourceas of 2026-10-03 |
| Craig: free tier | "a separate audio track for each speaking user"; "Record for up to 6 hours"; "keep them for 7 days" | sourceas of 2026-10-03 |
| Discord threads | Hide After Inactivity defaults to 3 days; "Closing a Thread doesn’t mean it will be deleted"; "Searching in a channel will include results from all threads in that channel" | sourceas of 2026-10-03 |
How we sourced this: The Discord rows dated 2026-11-13 were read from Discord’s own help centre through its article API on the same domain, because the article pages answer automated browsers with a challenge page. Most of those articles were last edited between 2020 and 2024 (the oldest carry their date in the row, and two of them disagree about private voice channels), so their wording can lag the app; we describe what each article says, not what we clicked. The Avrae row is from its own homepage. The Craig and threads rows are repeated from our Craig, Discord recording and play-by-post guides and carry those pages’ dates. No bot here was tested by us at a live table.
Related guides
- Stars and Wishes: how to get honest feedback from your D&D players
Stars and Wishes takes five minutes after a session: one thing you loved, one you want next. How to run it, a survey to copy, and what becomes of a wish?
- Curse of Strahd DM notes: a campaign tracker for everything the book cannot know
The book knows Barovia. It cannot know your Tarokka reading, who the party angered or what they promised. A Curse of Strahd tracker to copy. What is on it?
- A D&D session zero checklist, and the questions to ask your players
A session zero checklist to copy: questions for players, safety tools, table rules and the names to settle before session one. What does yours miss?