How to structure a Discord server

The sidebar is the first thing anyone reads and the last thing anyone rebuilds. It is worth getting roughly right early, because every channel you add gets pinned messages, links and habits attached to it, and those are what make it expensive to move later.

This is about the shape of a server: how many channels, in what groups, in what order, and how to tell when the shape has stopped fitting. If you are starting from an empty server, read how to make a good Discord server first — it covers the decision this one assumes you have already made.

The sidebar is a table of contents, not an inventory

Every channel you add makes every other channel slightly harder to find. That trade is worth it when the new channel is genuinely a different conversation, and a straight loss when it is a slightly different flavour of an existing one.

A new member should be able to look at your sidebar once and guess what the server is for. If they have to scroll to find out, the structure is doing the opposite of its job.

Three rules cover almost every case:

1. One channel until it hurts. #general should split when it is too fast to follow or when one topic keeps apologising for taking it over — not before.
2. Every channel needs a different answer to "what do I post here". If you cannot explain the difference between two channels in one sentence, your members cannot either, and one of them will die.
3. Locked information channels are not really channels. #rules, #announcements, #faq are pages. They cost sidebar space but no conversation, so they are cheap — which is exactly why servers accumulate six of them.

Categories

A category is a permissions boundary that happens to look like a heading. Channels inside it inherit its permissions, which means the category is where you answer "who can see this group of things" once instead of once per channel.

So group by audience at the top level, and by topic inside that:

Categories that are not worth having

• A category with one channel in it. That is a heading with extra steps. Move the channel up or find it siblings.
• A category per topic in a small server. GAMING / MUSIC / ART with one channel each turns three channels into six sidebar rows and makes the server look emptier, not fuller.
• MISC or OTHER. Everything in it either belongs somewhere or should not exist.

Order matters more than people think

Discord shows categories top to bottom, and new members read top to bottom exactly once. That first pass is the only guaranteed attention your structure will ever get.

Put things in the order somebody needs them:

1. Information they need before participating — rules, what this is, role picker.
2. The main conversation — whatever the server is actually for.
3. Everything secondary — off-topic, memes, bot commands.
4. Voice.
5. Staff, at the bottom, invisible to most people anyway.

The common mistake is putting #general first because it is the most important channel. It is the most important channel for people who already know what the server is. A new member needs the thing above it.

Channel types worth knowing

Most servers use text and voice and stop there. Two of the others solve real problems, and one is worth knowing about mainly so you do not reach for it too early.

Naming

Channel names are read in a narrow column at small size, so the practical constraints are width and scannability. Everything else is taste.

Decoration is not automatically wrong — a single leading emoji is a fine way to mark category groups, and plenty of good servers use it. The failure is when the decoration is wide enough to truncate the actual name, because then the sidebar shows you a row of brackets and no information.

When to restructure

Restructuring feels productive and usually is not. The honest signals that a server has outgrown its shape:

• People post in the wrong channel constantly. That is the structure failing to communicate, not members being careless.
• A channel has become two conversations that interrupt each other.
• New members ask "where do I…" for something that has a channel. It is in the wrong place, or badly named, or too far down.
• More than about a third of channels have nothing from the last month. Archive, do not delete — remove the ability to post and leave it readable.

And the signals that are not signals:

• It feels untidy to you. You look at the sidebar fifty times a day; a member looks at it once a week.
• Another server has more channels. They also have more members.
• Someone suggested a channel. One person wanting a channel is not demand. Three people having the conversation anyway is.

Frequently asked

Next

Structure and permissions are the same subject seen from two sides — the categories above only work if you can express "staff only" correctly. Roles and permissions, explained is the other half.