Grow a Discord community and know what works

A Discord server is easy to open and hard to keep alive. Most product servers follow the same curve: a burst of joins at launch, a few lively weeks, then a long quiet stretch where the only messages are the maker's own announcements.

Growing a community is less about getting people in than about giving them a reason to stay, and then noticing which of your efforts bring the people who do. This guide covers both.

Decide what the server is for

A server with a clear purpose grows more slowly and lasts longer. Before inviting anyone, finish this sentence in one line: "People come here to...".

Common honest answers for a product:

• Get help, from you and from each other.
• Follow what is being built, and influence it.
• Meet people with the same problem or the same craft.
• Play together, for a game or a game server.

Pick one as the main reason. It decides your channels, your tone and what you post. A server that tries to be support desk, social club and newsletter at once usually ends up as none of them.

Set it up small

A new server with thirty channels looks abandoned, because every channel is empty. Start with as few as you can:

• a welcome channel with the rules and what the server is for,
• an announcements channel that only you post in,
• one general channel,
• one channel for the main purpose: help, feedback or showing work.

Add a channel when a topic keeps overflowing the general one. Not before.

Write your rules in plain words and keep them short. Discord's own Community Guidelines apply to every server, and yours should say what is specific to you: what is on topic, how to ask for help, what gets someone removed.

Give people a reason to speak in the first minute

Someone who joins and says nothing on day one rarely comes back. The first minute matters more than any growth tactic.

• Greet new members yourself while the server is small. By name, with a question.
• Make the first message easy. An introductions thread with a prompt such as "what are you building?" works better than silence.
• Answer every question quickly. In the first months, your reply time is the product.
• Ask for opinions on real decisions. A poll about a feature you are actually undecided on gets answers. A poll for the sake of activity does not.

Where members come from

Members come from the places where people already see you. List them, and put an invite in each:

• your site: header, footer, help page, the screen after signup,
• your product: a help menu, an empty state, an error message that says where to ask,
• your posts on other platforms,
• your newsletter and your transactional emails,
• your documentation and your repository's README,
• videos and streams, in the description.

Not every source brings the same members. Someone who joins from inside your product already uses it. Someone who joins from a giveaway may never open it.

Use a different invite for each place

Discord lets you create several invite links for the same server. Use that. Create one invite per source, each set to never expire, and you can later see how many joins each one brought in your server's invite list.

For the step before the join, tag the link on your own site. If your posts send people to a page of yours that has the invite, a tag such as yoursite.com/community?ut=x-community-post tells you which post sent the visitors who then saw the invite.

The two together answer the question that member count alone cannot: which of my efforts bring members?

What to measure, beyond the member count

Member count is the number everyone quotes, and it only goes up. Members rarely leave; they mute. A server of 5,000 with ten people talking is smaller than a server of 300 with forty.

Numbers that say more:

• Members online at peak, day after day. It follows the real size of the community.
• New members per week, and from which invite.
• People who posted this week, compared with last.
• Questions answered by someone other than you. When this starts happening, the community exists.
• How many members use the product, if you can tell.

Discord gives server owners its own statistics inside the app. From outside, two totals are available for any server through a public invite: Discord's documentation on the invite resource describes an approximate member count and an approximate count of members online.

See which posts move the community

Here is the question most servers never answer: when you posted that thread on Tuesday, did the server grow?

To answer it you need the member curve and your posts on the same timeline.

upTake's Discord server stats connector does the first half. From an invite link, it reads those two totals every hour: members, and members online. No bot joins your server, and no names or messages are read. Hourly readings are kept for seven days and summed up into one line per day: members at the end of the day, the change since the day before, and the highest and average number online.

The second half is your log of posts and releases, which upTake already draws as markers on your chart. With both on the same chart, a jump in members has a date, and the date has a post next to it.

That is the comparison to look for: not which effort added the most members, but which one added people who show up.

Keep it alive without living in it

A community that depends on you being online all day will wear you out. A few habits spread the load:

• A weekly rhythm people can expect: a release note on a fixed day, a question of the week, a monthly call.
• Thank helpers in public. People who answer others are the core of the server. A role, a mention, early access.
• Bring your own reports in. If you receive a weekly report on your marketing, post it where your team sees it. upTake can deliver it to a Discord channel.
• Close what is dead. An empty channel makes the whole server look quiet. Archive it.

What to avoid

• Giveaways as a growth plan. They bring joins and little else.
• Mentioning everyone for every announcement. It is how members learn to mute you.
• Mass invites and direct messages to strangers. They are spam, and they bring nobody who stays.
• Chasing a round number. Ten thousand silent members is not a community.
• Too many bots at the start. A person greeting newcomers beats five automated welcomes.

The short version

1. Decide in one line what the server is for.
2. Start with four channels and short rules.
3. Greet every new member while you can, and answer fast.
4. Put an invite everywhere people already see you, a different one per place.
5. Watch members online and new members per week, not the total.
6. Put the member curve and your posts on the same timeline, and see what moved it.

A community grows from the people who talk. The measuring only helps you find where they came from.