Discord is where your pod already lives: the scheduling, the decklist arguments, the "anyone up for a game?" ping. What it is not is a Magic client. There is no card game inside Discord, no bot that deals a hand you can hide from four other people, and no realistic prospect of one.
So the real question is not "how do I play Magic in Discord" but "what do I pair Discord with, and how do I set it up so pod night doesn't start with twenty minutes of troubleshooting". Here is a setup that holds up, plus the reasons the obvious alternative (screen sharing) doesn't.
The setup that works
Discord does the humans. A separate table does the cards.
- A voice channel for the game. Audio only as the default; video is nice but optional, and expensive on bandwidth when four people are also streaming a table.
- A pinned message in the pod's text channel with tonight's table link. One message, edited each week, beats a scroll-back hunt.
- A shared table open in a browser tab next to Discord.
That third piece is the choice, and the split is the same one that runs through all of remote Commander:
Real cards and webcams — SpellTable or Convoke. Your physical decks, a camera each. Discord stays as the voice channel. Do not try to make Discord video be the table: its video is compressed for faces, not for reading nine-point rules text.
Digital cards in a browser — EDHMat, TableCommander, Kiku.gg and others. Everyone gets their own window on the same board, so everybody can look at what they want, including their own hidden hand. Nothing to install, no camera in the loop.
For a pod that just wants to be playing, a table nobody has to sign up for is the shortest path: Open a table in one click →
Why screen sharing is the wrong default
The instinctive move — one person shares their screen, everyone else watches — falls apart in Commander specifically, and it is worth knowing why before you spend an evening on it.
- Hidden information stops working. Whatever is on the sharer's screen is on everyone's screen. Their hand is public, or they never look at it.
- One person drives. Three players spend two hours saying "can you scroll up? can you zoom in on the green one?"
- Video compression eats card text. Screen share is tuned for slides, not for a paragraph of reminder text at 20% scale.
- Latency stacks. The sharer's game, plus encode, plus network, plus decode. Turns take longer than they should.
Screen sharing is fine for spectating — someone joining halfway to watch — and fine for a two-player game where you care less about hidden hands. As the primary way four people play a four-hour game, it is a tool being asked to do a job it was not built for.
A pod-night runbook
Steal this and adapt it. The actual setup is about a minute.
- Someone claims host. Rotate it. It is not a burden, but it should be assigned, or four people wait for each other.
- Host creates the table and pins the link. With EDHMat that is one click and a paste — no account, no lobby configuration, no invites to accept.
- Everyone joins the voice channel and clicks the link. They pick a display name and sit down.
- Decks get pasted while people chat. This is the slowest step (a hundred cards resolving), so do it during the table talk rather than in silence.
- Host starts the game. Hands are dealt, libraries shuffled.
- Agree the house rules out loud before turn one. Free mulligans? Bracket? Thirty seconds now saves an argument on turn six.
Making the games good
Say what you are doing. In paper Magic people read your hands. Over voice they cannot. Announce attacks, announce triggers, announce that you are done. A table that talks does not need a rules engine.
Use the log. In a manual tabletop, the written record is the tie-breaker. EDHMat writes every draw, move, tap, token and life change into an append-only log in the same order for everyone, so "when did that enchantment get there?" is answered by scrolling instead of arguing.
Keep bookkeeping out of voice. Life totals, commander damage and counters belong on the table, not in someone's head. Every decent tabletop tracks them.
Two windows beats one. Voice in the app, table in the browser, side by side. Nobody should be alt-tabbing away from the game.
Turn video off if the game gets choppy. Four video streams plus four browser tabs is a lot for a home connection. Audio plus a shared board is enough.
Where Discord is genuinely irreplaceable
Not as a table — as the pod. Finding three other people who want to play at 9pm on a Tuesday is the actual bottleneck of remote Commander, and Discord is the thing that solves it. The Commander LFG servers are large and active, and a pod with a home channel plays far more often than one without.
Keep Discord for that. Pair it with something that deals cards.
Next
- How to play Commander online with friends — every option, compared.
- The best SpellTable alternatives — if you are moving off SpellTable specifically.
- Importing a decklist — the step that stalls first-timers.
Frequently asked questions
Can you play Magic directly in Discord?
Not really. Discord gives you voice, video and a place to organise, but it has no card game in it. You pair it with a separate table — a webcam tool with real cards, or a browser tabletop with digital ones.
Do I need to screen share to play Magic on Discord?
Only if one person is driving the game and the others are watching. It is a poor default for Commander: the person sharing controls the view, nobody can look at their own hand, and the stream lags. A shared table where every player has their own window is better.
What is the best way to run a Commander pod on Discord?
Voice in Discord, cards in a browser tabletop, and the table link pinned in the channel. Keep video optional — most pods find audio plus a shared board is enough, and it uses far less bandwidth.