> ## Content Index
> Fetch the complete content index at: https://seeindie.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to grow a Discord server for your game
- URL: https://seeindie.com/blog/grow-a-discord-server/
- Published: 2026-08-13T11:00:00.000Z
- Updated: 2026-08-20T15:45:57.000Z
- Description: Your game Discord isn't a discovery channel — it's how the players you already have become the ones who tell their friends. Here's how to grow it.
- Author: Isabella-Viktoria Quilez
- Tags: social, community

You don't really grow a Discord server for your game. You point the people who already found your game at a room that's worth staying in, then make staying easy.

Discord isn't going to find players for you. It's where the players you already have turn into the ones who tell their friends. That reframe changes everything below.

Most "grow your Discord" advice is written for streamers and giveaway servers, not for a solo dev with a demo and 30 wishlists. The mechanics are the same. The goal isn't. Community building around a game is slower and quieter than the growth-hack stuff, and it's mostly about making a room that's actually worth joining.

The short version 
- **A game Discord is a retention and word-of-mouth engine,** not a discovery channel.
- **Turn on Community mode first.** Nothing good is available until you do.
- **Set up onboarding** so a new person knows what to do in the first ten minutes.
- **Fewer channels than you think.** An empty channel is worse than no channel.
- **Your first \~50 members come from you** and from wherever players already meet your game.
- **What keeps people is you being in the room,** plus a reason to come back.

On this page [The honest part](#discord-not-discovery) [Community server](#community-server) [Onboarding](#onboarding) [First 50 members](#first-members) [What keeps people](#keep-people) [Is it working?](#server-insights) 

## First, the honest part: Discord won't find players for you

I want to get this out of the way, because it changes everything you do next. There's no search box on Discord that surfaces your little server to strangers. The one built-in way people discover servers — [Server Discovery](https://support.discord.com/hc/en-us/articles/360047132851-Enabling-Your-Community-Server?ref=seeindie.com) — is limited to servers with more than 1,000 members (plus Discord's Partnered and Verified servers). So on day one, Discovery isn't a lever you have.

Which means growth comes from *your* surfaces, not Discord's: your Steam page, your newsletter, a pinned post on your socials, the end screen of your demo, you being helpful in other people's communities. Discord is the destination, not the road.

The game-marketing consultant Chris Zukowski puts it well (his opinion, not a study, but it matches what I've seen): Discord is "rented land," it's not a discovery channel, and it's a poor replacement for an email list. His way of layering it — wishlists are for the many, Discord is for the superfans, the mailing list is for the super-superfans. A working server doesn't get you found. It compounds playtime, reviews and word of mouth after someone already cares.

If that sounds like a downgrade, it isn't. Superfans write the first reviews, tell their friends, and keep playing your demo until launch. This is the same point as the [social media pillar](https://seeindie.com/blog/social-media-for-game-developers/): social isn't a traffic motor for indies, it's where a small community forms.

## Set up your Discord community server first

You can't do most of what follows on a plain server. Onboarding, Server Insights, announcement channels, the growth tools — all of it sits behind flipping your server into a **Community server** (Server Settings, then Enable Community). It's free and takes a few minutes.

What Community mode needs 
- **A verified email** — members need one before they can message or DM (doesn't apply to anyone you've given a role).
- **Media scanning** — the explicit media filter scans media from all members.
- **A rules channel** — clearly posted guidelines.
- **A Community Updates channel** — where Discord sends admin and mod announcements.
- **Compliance** with Discord's Community Guidelines.

Once that's on, you unlock the server management tools that make the rest possible: announcement channels, [Server Insights](https://support.discord.com/hc/en-us/articles/360047132851-Enabling-Your-Community-Server?ref=seeindie.com), Raid Protection, and Community Onboarding.

One heads-up while you're in here: if you've used the old **Welcome Screen**, Discord is phasing it out. Its own doc says you can no longer edit Welcome Screen if it's still enabled, and points you to Community Onboarding instead. So skip Welcome Screen. Onboarding is the thing to learn.

## Set up onboarding so new people don't bounce

This is the highest-leverage twenty minutes you'll spend. Discord describes the problem better than I can: new people "don't understand what 'bots' are, what roles do, or which of your many channels to check out. And when they get confused and overwhelmed, they just leave." ([Community Onboarding FAQ](https://support.discord.com/hc/en-us/articles/11074987197975-Community-Onboarding-FAQ?ref=seeindie.com))

That's the whole retention problem in two sentences. Someone clicked your invite because they liked your game. If the server greets them with 30 channels and a verify-bot, they're gone before they say hi. Community Onboarding fixes this with three pieces.

**Default Channels.** These are what every new member sees the moment they join. Discord's best practice is to pick channels with healthy activity that are friendly to newcomers, like #general, a polls channel, or an LFG channel. Don't put everything here. Put the two or three places you actually want a new person to land.

**Customization Questions.** You ask a short question, and each answer grants roles and adds channels. Something like "What brings you here?" with answers like "I'm playing the demo," "I'm here for dev updates," "Just lurking, hi." Each answer quietly shapes their channel list so they only see what's relevant.

**Make most of your channels assignable.** Discord warns that any channel you don't attach to a default or a question, newer members "may not ever find." So every real channel should be reachable through onboarding.

A couple of practical notes. To enable onboarding you need at least 7 default channels, and at least 5 of them have to let everyone view and send. You can only set it up on desktop. And if someone leaves and rejoins later, they go through onboarding again.

### Give new people a to-do list, not a rulebook

Inside onboarding there's a feature called **Server Guide**, and it's the piece I'd set up carefully. It's a little landing surface every new member sees right after joining, and per Discord's [Server Guide FAQ](https://support.discord.com/hc/en-us/articles/13497665141655-Server-Guide-FAQ?ref=seeindie.com) it has three parts:

- **A Welcome Sign** — a short message from you. For a solo dev this is your "hi, I'm the person making this game" moment. Use it.
- **New Member To-Do's** — the good bit: 3 to 5 small tasks that nudge someone into actually doing something. "Say hi in #general," "grab your platform role," "post a screenshot of your best run." The first message a person sends is roughly the moment they stop being a tourist and start being a member — a to-do list gets them there faster than a wall of rules.
- **Resources** — turn a read-only channel into a clean page (rules, roadmap, FAQ) that opens at the top instead of the bottom of a message thread.

One thing to know: once Server Guide is on, new members won't see the old Welcome Screen at all. Which is fine, because Server Guide does the job better.

### The counter-intuitive bit: take down your bot gate

If you've got a verify-bot that makes people click a reaction, solve a captcha, and read three channels before they can talk, take it down. I know it feels safer. Discord actually tells you to remove it: "consider removing bot-powered restrictions that add confusion and turn away new members."

**Use Raid Protection instead of a locked door.** Server Settings → Safety Setup → Raid Protection uses machine learning to spot join-raids and spam waves, and can automatically require a captcha from new joiners for the next hour if something looks off. You get the safety without making a genuine new fan prove they're human just to say hello. 

## How to grow your Discord server: your first 50 members

The first fifty are the hard part, and it's worth naming why: the value of a chat room *is* the other people in it. An empty server reads as dead, and nobody wants to be the only one talking. So the early game isn't marketing, it's bootstrapping the room until it feels alive.

Discord's [member referrals guide](https://discord.com/community/growing-your-community-through-member-referrals?ref=seeindie.com) is refreshingly blunt about where you start: invite your own people first, "starting with you." Pull in friends, playtesters, the three people who already replied to your dev tweets. Inviting friends is the oldest growth trick on Discord, and it still works: a room where a handful of familiar faces are already chatting is inviting. An empty one isn't.

Bootstrapping the first members 
- **Use a permanent, unlimited invite link.** Default links expire after 7 days, so the one on your [Steam page](https://seeindie.com/blog/steam-store-page/) quietly dies. Set one to never expire, and use it everywhere.
- **Put the link where players already meet your game** — the end-of-demo screen, your Next Fest page, the newsletter, a pinned tweet. Not everywhere on the internet.
- **Make sharing copy-paste easy** — pin a short invite template in an announcement channel so members can grab it without thinking.
- **Track and gently gamify invites** — you can see who's inviting people, and how many join, under Server Settings → Invites. Hand a small role to your top inviters. Keep it light.
- **Give people a reason to show up at a time** — events. A playtest evening, a dev stream, a game night. Discord says events give new members a reason to enter in the first place.

### What about server directories and shoutouts?

You'll see advice to grow your Discord server through server listings like Disboard, optimising the listing with tags, or paying to advertise in other Discord servers. It's not wrong exactly, but be honest about who it brings. Directory browsers and cross-server shoutouts pull in people shopping for any active server, not fans of your video game. They pad your member count and mostly never speak.

For a gaming community built around one game, the members worth having come from external outreach where people already care: a devlog on Reddit, a YouTube video, your newsletter, the demo's end screen. Slower, and that's the point. Define your niche narrowly (your game, your genre, the specific thing that makes it yours) and let that do the filtering. That's how you reach the right people, your actual target audience, instead of drive-by joiners. Fifty people who love your kind of game beat five hundred who joined off a server listing and muted you by morning.

## What keeps a gaming community together

Acquisition gets the attention, but retention is the whole game. A server that leaks everyone it gains never compounds. Here's what holds people, and most of it is free.

**You have to be in the room.** This is the big one for a solo dev, and Discord says it plainly: even just hanging out in voice or greeting newcomers as they arrive "is a quick, effective way to drive engagement." A dev who shows up beats any bot. People didn't join to talk to your welcome message, they joined to be near the person making the thing.

**Ship the community the game.** The reason a *game* server has a pulse is that stuff is happening: early builds, patch notes, "which of these two enemies feels worse to fight," bug reports you actually reply to. A forum channel (Community servers get these) works better than a chat channel for the stuff you want to keep, like bug reports or a "show your best run" board, because posts don't scroll away. Zukowski's example (again, his opinion) is Valheim, which grew through open development, betas, showing the work, not press. Your server's job is to be the front row for that.

**Start conversations in quiet channels.** Discord's own tip is to drop a low-effort leading question to skip the awkward small talk, something like "what's the first game that genuinely scared you?" It feels small. It's how a channel wakes up.

**Kill your dead channels.** A new server launches with 25 channels and every one is empty, so the whole place feels abandoned. Discord says the same thing twice, in onboarding and in Insights: too many channels spread the conversation too thin and drag engagement down. Fewer, busier channels beat more, emptier ones, and grouping the ones you keep into clear categories makes the place easier to read. Archive without guilt.

**Notice your regulars.** The handful of people who show up every day are the backbone of the community. Give them a role, ask their opinion on a design call, let them help welcome newcomers. Recognising real contributions is one of the quieter things that keeps people around, and it hands a few of them a sense of ownership. This is how a server stops being your project and starts being a place where people build relationships.

**Put events on a schedule.** One event is nice. When you host events on a rhythm, you get what Discord calls "a never-ending cycle of server activity." Even a monthly thing gives people a reason to keep the tab open.

## Know if it's working: the two numbers Discord gives you

Once you're a Community server, Server Insights shows you whether any of this is landing. Two numbers matter most, and Discord publishes its own benchmarks for them in [Understanding Server Insights](https://discord.com/community/understanding-server-insights?ref=seeindie.com) (these are Discord's own goal figures, not an independent study, so treat them as a target, not a law).

30%

of members talking = Discord's healthy benchmark

Discord — Server Insights

50%

of visitors ideally become communicators

Discord — Server Insights

1,000

members before Server Discovery even unlocks

Discord — Enabling Community

| What Insights measures | What it means                                       |
| ---------------------- | --------------------------------------------------- |
| Visitor                | Anyone who clicked into a channel                   |
| Communicator           | Anyone who posted in a text or voice channel        |
| New member retention   | The share of new members who come back after a week |

**Communicators** is the health metric. Discord's benchmark is 30% of your members talking, and its aspirational shape is around half your members visiting with half of *those* actually chatting. If loads of people visit but nobody talks, your room is a museum, not a community.

**New member retention** — the percent who return after a week — is the single best signal of whether the room is worth staying in. If people join and never come back, the problem is almost always the first ten minutes, which loops right back to onboarding. Insights even has a Welcome section showing what new members click and whether they send a message; if they don't, Discord's advice is to change the welcome text or highlight different channels. Watch retention, fix the front door, repeat. (Discord itself weighs engagement and retention when it reviews Partner applications, so these aren't vanity numbers.)

## Build relationships, not headcount

If you take one thing from this: a game Discord grows when it's a place people actually want to be, not when you game a directory. Show up, ship the game to the people in the room, and build relationships with the few who stick around. The number goes up as a side effect. Chase the number first and you get a big, silent server nobody opens.

## The mistakes that quietly kill a small server

Common mistakes 
- **Too many channels at launch.** Start with a handful. Add when a channel is genuinely overflowing.
- **A verify-bot maze at the door.** Take it down, use Raid Protection.
- **A 7-day invite link on your Steam page.** Make it permanent.
- **Building the server before anyone cares about the game.** An empty room can't be saved by settings.
- **Treating it as a launch megaphone.** If you only post when you want something, people mute you.
- **Never being in there yourself.** For an indie, your presence *is* the product.
- **Faking activity with a leveling bot.** XP and ranks feel like a grind on a small server. Real conversation beats a leaderboard.

## Common questions

Do I even need a Discord for my indie game? 

Not on day one. If you have almost no audience yet, your energy is better spent on wishlists and an email list. Discord earns its keep once you have a handful of people who genuinely care and want to talk to you and each other. It's for depth, not reach, and it quietly doubles as your support server, where bug reports and feedback land once people are playing.

How many members should I aim for on my Discord server? 

Fewer than you'd think, and the raw number barely matters. A 40-person server where people actually talk is worth more than a 4,000-person server that's silent. Watch the communicator and retention numbers in Server Insights, not the member count.

Should I use giveaways or bots to grow my Discord server? 

Be careful. Giveaways pull in people who want the prize, not your game, and they leave the moment it's over. Discord even warns that a confusing bot setup turns genuine new members away. Grow slower, with people who care about the game.

When can my server show up in Discord's Server Discovery? 

Once it passes 1,000 members, or you become a Partnered or Verified server. Below that, Discovery isn't available, so don't count on Discord to send you strangers. Your own channels do that job.

Community Onboarding or the old Welcome Screen? 

Onboarding. Discord is phasing out Welcome Screen and no longer lets you edit it if it's still on. Onboarding does more anyway: it hands each new person a channel list that fits why they joined.

How much time does running a game Discord take? 

The recurring cost is mostly just showing up. Fifteen minutes a day of reading, replying and greeting newcomers does more than any automation. If you can't spare that yet, it might not be the right season for a server.

## Sources

- [Discord — Enabling Your Community Server](https://support.discord.com/hc/en-us/articles/360047132851-Enabling-Your-Community-Server?ref=seeindie.com) (Help Center)
- [Discord — Community Onboarding FAQ](https://support.discord.com/hc/en-us/articles/11074987197975-Community-Onboarding-FAQ?ref=seeindie.com)
- [Discord — Server Guide FAQ](https://support.discord.com/hc/en-us/articles/13497665141655-Server-Guide-FAQ?ref=seeindie.com)
- [Discord — Understanding Server Insights](https://discord.com/community/understanding-server-insights?ref=seeindie.com)
- [Discord — Growing Your Community Through Member Referrals](https://discord.com/community/growing-your-community-through-member-referrals?ref=seeindie.com)
- [Chris Zukowski — How To Market A Game](https://howtomarketagame.com/?ref=seeindie.com) (practitioner opinion)