Part of our Design, Video and Creator Tools guides
For community managers running a Discord Stage live
Host a Discord Stage That Doesn’t Fall Apart in Front of Everyone
The exact click paths, permission checks, and real capacity numbers — in the order you’ll actually use them. Plus a one-page pre-flight checklist you can hand to a volunteer mod.
Q&A: building your community calendar
Most Stage guides explain the feature. This one prevents the failure.
Sequenced like a pre-flight, not an article
Every step is ordered by when you’ll do it — T-48 hours, T-10 minutes, T-0 — not by topic.
Capacity numbers by tier, not a vague ceiling
The number that applies to your server, including what changes the second video starts.
Every instruction is a click path
Server Settings → Roles → [role] → Stage permissions. Copy it, follow it, with the app open.
The failure is never the talk. It’s the fourteen minutes before it.
It’s 7:58pm. Your event is in two minutes. Sixty people have RSVP’d and the channel just went live. You don’t yet know which of these is about to happen:
Everyone can talk.
A role created two years ago granted speak permission by default, and nobody has touched it since.
Your co-host can’t share their screen.
Screen-share permission was granted to the wrong role — the one with three members, none of them on camera tonight.
Member 51 gets locked out.
You started video, the seat cap kicked in, and the invite you sent an hour ago no longer works.
Your mods are guessing.
Nobody was assigned the request-to-speak queue, so the Q&A becomes a staring contest.
None of these are hard to fix. They’re just hard to notice at 7:58pm.
What a Stage channel is — and when it’s the wrong choice
A Stage is a voice channel with a raised platform. Speakers are moved on stage by a moderator; everyone else listens with their mic off by default. They can raise a hand to request the mic, and they can talk in text chat the whole time.
Three things worth knowing before you build one
| Audience | Up to 10,000 on a Community-enabled server |
|---|---|
| Video seats | 50 free · 150 Tier 2 · 300 Tier 3 (plus 30 per additional boost past 14) |
| Discovery | The channel jumps to the top of your channel list the moment it goes live |
Use a Stage when the format is one-to-many: a talk, a panel, an AMA, a launch, a watch-along with commentary.
Use a voice channel instead when everyone needs to talk — standups, co-working, small workshops, anything with more than a handful of active participants.
Figures verified against Discord’s published documentation, November 2026.
What you actually get, in plain terms
| The feature | What it does for your event |
|---|---|
| Speakers separated from the audience | Your panel sounds like a panel, not a room of people breathing into mics |
| Request-to-speak queue | Q&A that ends on schedule instead of drifting |
| Moderator mute and move controls | One person can fix a problem without interrupting the talk |
| Up to 5 simultaneous video feeds | A panel where you can see faces — without bandwidth collapse |
| One active screen share at a time | Slides and demos work without a second app |
| Text chat alongside the Stage | Links and questions stay out of the audio |
| Auto-promotion when live | Members see it without three announcements |
The three screens that decide whether your event works
Set these before you promote the event — not the night of.
Built with people who run these for a living
Recommendations in this guide were shaped with input from GroovyUnicyclist#1612, and NaviKing#3820 contributed the moderation model: staff enough moderators to cover both the channel and the wider server, or the room gets away from you.
[CLIENT TESTIMONIAL — to be inserted]
Community manager, name and server size to be added
The free download
The Stage Pre-Flight Runbook
One page. Print it, or keep it open in a second window while you set up.
| What’s inside | Why it’s there |
|---|---|
| Role and permission matrix | Who needs speak, mute, move, and share — and the four legacy defaults to reset |
| Capacity table by tier | Your real seat count, and the line where video silently cuts people off |
| T-48h / T-10min / T-0 checklist | The same steps, in the order you’ll do them |
| 10-minute rehearsal script | Exactly what to test with a co-host, including the boring parts |
| Failure cheat-sheet | Six things that go wrong live, and the one click that fixes each |
If it misses something, tell me and I’ll add it
The Runbook is free, it’s one page, and it’s versioned. If you run it and hit a failure it doesn’t cover, reply to the email and describe it — it goes into the next revision, credited to you if you want.
No autoresponder sequence. No daily check-in. One email with the PDF, and that’s it unless you ask for more.
Run it before your next event night
Thursday is the most common night for community events, which makes Wednesday evening the worst time to discover a permissions problem. Run the checklist once, calmly, on a weekday afternoon — it takes four minutes and it’s the difference between hosting and firefighting.
Questions people ask before their first Stage
Up to 10,000 listeners on a Community-enabled server. Video is the real constraint: 50 seats on a free server, 150 at Tier 2, and 300 at Tier 3, plus 30 seats for each additional boost past 14.
The video seat cap applies the moment video or screen share begins, and no new members can join past it. Either right-size your tier before you promote the event, or start audio-only and add video once the room has settled.
No. A free Community server can host a Stage with up to 50 people on video. Boosts only raise the video ceiling — they don’t gate the feature.
There is no built-in record button on a Stage, so you’ll need a capture tool running on the host machine. Tell the room you’re recording before you start, and get it in writing if the session is paid.
Open Server Settings → Roles, check the roles that existed before you created the Stage, and set Speak to off for @everyone. Grant Speak only to speaker and host roles.
Yes. You get up to five simultaneous video feeds plus one active screen share. The person sharing doesn’t have to be one of the five.
Attending works everywhere. Hosting and moderating — moving speakers, managing the queue — is a desktop job; the controls you need are not all present on mobile.
Three honest options: run audio-only so the video cap never applies, open a second overflow channel for the stream, or move the broadcast to an external platform and keep Discord for the conversation.
Your next event can be the boring, well-run kind
Boring is the goal. Nobody remembers a Stage where the audio worked and the Q&A ended on time — they just come back to the next one.
Keep reading: Discord not working troubleshooting · How to schedule on Twitch
