How to Set Up Discord Forum Channels (2026 Guide)

To set up a Discord forum channel, first enable Community in Server Settings → Enable Community, then go to your channel sidebar, click the + next to a category, choose Forum, name it, set Post Guidelines and tags (up to 20), pick a default sort and reaction emoji, and save. Forum channels turn each new message into its own thread, perfect for help desks, suggestion boards, and topical Q&A.

Key Takeaways

• Forum channels require Community to be enabled at the server level — it's not a per-channel toggle
• You get up to 20 tags per forum channel, which become the structure for filtering and search
• Post Guidelines display every time someone clicks "New Post" — use them to enforce title quality
• Default reaction emoji acts as an upvote system for posts
• Forum threads auto-archive after 1 hour to 1 week of inactivity, configurable per channel

Step 1: Enable Community on Your Server

You can't create a forum channel until Community is on. This unlocks forums, announcement channels, the welcome screen, server insights, and Server Discovery (which you can leave off if you want privacy).

1. Open Server Settings → Enable Community
2. Click Get Started
3. Walk through the four-step checklist:
   • Verification Level set to Medium or higher
   • Explicit content filter set to scan all messages
   • Define a Rules channel
   • Define a Community Updates channel
4. Click Finish Setup

If your server has fewer than 100 members, Discord will warn you that some Community features require larger servers — ignore it for forum channels, which work at any size.

Reverting Community is painful

Once Community is on, turning it off requires going to Server Settings → Community → Disable Community and confirming. You'll lose all your forum channel configurations if you do this, so commit to it.

Step 2: Pick the Right Category

Forum channels live inside categories like any other channel. Choose a category that thematically fits — usually Help, Community, or Discussion.

If you don't have a fitting category yet, create one first:

1. Right-click any blank space in the channel sidebar → Create Category
2. Name it (e.g., Help & Support)
3. Set permissions (default @everyone View Channel = on)
4. Save

I run my forum channels in a dedicated Help Desk category with three channels: #bug-reports, #feature-requests, and #general-questions. Splitting by intent makes triage 10x faster than one mega-forum.

Step 3: Create the Forum Channel

1. Hover over the category → click the + icon
2. Select Forum as the channel type (it sits between Text and Voice in the picker)
3. Name the channel (lowercase, dashes, no emojis in the slug for accessibility)
4. Choose Public or Private
5. Click Create Channel

You'll land directly in the channel's settings panel, which is where the real configuration begins.

Forum vs text channel — when to use which

Feature	Text Channel	Forum Channel
One conversation at a time	Yes	No (each post = thread)
Tags	No	Yes (up to 20)
Default sort	Latest message	Recent activity, latest post, or top
Pinning	Per-message	Per-post
Best for	Casual chat	Help, Q&A, suggestions, showcases
Threads can be private	Via creating private threads	Native

If your channel sees more than five distinct topics per day getting tangled together, switch it to a forum.

Step 4: Write Post Guidelines

The Post Guidelines panel shows up every single time someone clicks New Post. This is the most underused feature in forum channels.

Open Channel Settings → Post Guidelines. You get up to 2,000 characters of formatted markdown. Use it to:

1. Set title format (e.g., [Bug] Short description)
2. List required info (e.g., "include your OS, browser version, and steps to reproduce")
3. Link to the FAQ to deflect duplicates
4. Define what tags to pick

A good Post Guideline I use:

Before posting: search existing posts. Read the docs.

Title format: [Tag] Short clear description

Required info: server ID, what you tried, what happened, what you expected.

Tag your post with the most specific tag available. Posts without tags get auto-archived in 24h.

That last line — auto-archive — is enforced by a moderation bot, not Discord natively, but the threat alone keeps tag compliance high.

Step 5: Configure Tags

Tags are the navigation backbone of a forum channel. Members filter by tag, and you can set tags as required-on-post.

1. Open Channel Settings → Tags
2. Click Create Tag
3. Name (e.g., Bug, Feature Request, Resolved, Pinned)
4. Pick an emoji (it shows next to the tag, helps scanning)
5. Toggle Moderator-only if you want to reserve a tag for staff (e.g., Resolved, Stickied)

You can have up to 20 tags per forum channel. Don't use them all on day one — start with 5-7 and grow as patterns emerge.

Recommended tag set for a help-desk forum

Tag	Emoji	Moderator-only?	Purpose
Question	❓	No	General help
Bug	🐛	No	Reproducible issue
Feature Request	💡	No	Suggestions
Resolved	✅	Yes	Closed by mod
Stickied	📌	Yes	Pinned by mod
Answered	👍	Yes	Marked complete by OP
Duplicate	🔁	Yes	Closed as duplicate

The mix of public and mod-only tags is what makes the system work. Members create the post, mods finalize the state.

Require a tag on every post

Toggle Require people to select a tag when creating a post in Channel Settings → Tags. This is non-negotiable for any well-run forum. Without it, half your posts will be untagged within a week.

Step 6: Pick a Default Sort and Reaction

In Channel Settings → Overview:

Sort option	What it does	Best for
Recent Activity	Last reply bumps post to top	Active discussion forums
Latest Post	New posts to top, ignore replies	Showcases, announcements
Top	Most reactions to top	Suggestion boards

For a suggestion or feature-request forum, Top combined with a default reaction emoji turns the forum into an upvote board.

The default reaction is set in Channel Settings → Default Reaction. Pick an upvote emoji (👍 or a custom server emoji). Every new post starts with that reaction available as a one-click button at the top.

Step 7: Set the Default Layout

In Channel Settings → Default Layout:

• List View: text-heavy, classic forum look
• Gallery View: card-based, image previews

Use Gallery View for showcase forums (e.g., #fan-art, #build-showcase). Use List View for help desks. Members can override their personal preference, but the default sets the tone.

Step 8: Configure Auto-Archive

Forum threads can auto-archive after a set period of inactivity. Channel Settings → Overview → Hide After Inactivity:

Setting	Use case
1 hour	Very active triage forums
24 hours	Standard support
3 days	Discussion forums
1 week	Slow archives, long projects

Archived threads aren't deleted — they're just hidden from the main view. Anyone can re-open by sending a new message. This keeps the forum's main view clean without losing history.

Step 9: Set Up Moderation

Forum channels need different moderation than text channels because each post is a separate thread, and bad posts can sit unread by mods for hours.

AutoMod for forums

AutoMod rules apply to forum posts and replies the same way as text channels. Server Settings → Safety Setup → AutoMod:

1. Enable Spam Detection
2. Enable Harmful Links
3. Enable Mention Spam (threshold: 5)
4. Add a Custom Wordlist for off-topic phrases (e.g., "free nitro", "discord.gg/" if you don't want competitor invites)

Bot moderation that fills the gaps

Native AutoMod handles spam and slurs. It doesn't handle:

1. Auto-tagging based on title keywords (e.g., posts with "bug" in the title get Bug tag)
2. Auto-archive based on tag (e.g., posts tagged Resolved archive immediately)
3. Duplicate detection across the forum
4. Stale-post bumps to mods if no reply in 24h

PeakBot's forum module covers all four. Free tier on the features page shows the full list — forum auto-tagging is included on free, the AI Server Builder (which can generate forum channel structures from plain English) is the $8.50/mo Pro feature. Compare to the alternatives at peakbot.pro/compare/mee6.

For deeper protocol detail on threads (which forum posts technically are under the hood), Discord's threads documentation is the authoritative reference.

Do I need Community enabled forever for forum channels?

Yes. If you disable Community, every forum channel converts to a text channel, all tags vanish, and existing forum posts collapse into one tangled message thread. There's no way to keep forums without Community. The trade-off: Community unlocks features but also enables Discovery (which you can leave off) and Server Insights (which is a nice-to-have for any server with 100+ members anyway).

Step 10: Onboard Members

A forum is only useful if members know how to use it. Two onboarding moves that compound:

1. Pin a post titled "Read Me First" that walks through tag selection, search, and post format. Use the Stickied mod-only tag.
2. Welcome screen entry under Server Settings → Welcome Screen pointing to the forum with a one-line description.

I also pin a Best Examples post showing 3-4 well-formatted past posts. New users mimic what they see. If the only visible posts are sloppy, new posts will be sloppy.

Frequently Asked Questions

What's the difference between forum channels and threads in regular text channels?

Threads in text channels are temporary side-discussions branching from a main message. Forum channels make threads the primary unit — every new message is its own thread automatically. Text-channel threads are great for quick tangents inside an active chat. Forum channels are right when you have many parallel topics that shouldn't share airtime, like help requests or feature suggestions.

Can I convert a regular text channel to a forum channel?

No. Discord doesn't offer in-place conversion. You have to create a new forum channel and either ask members to re-post or use a bot to bulk-import past messages as new forum posts. Most servers just create the new forum, archive the old text channel by removing send permissions, and pin a notice pointing members to the new forum.

How many forum channels can a server have?

Forum channels share the 500-channel cap with all other channel types. In practice, you'll hit your moderation capacity before the channel cap. Most well-run servers have 2-5 forum channels max — one per major topic. More than that and members can't tell which forum to post in. If you find yourself wanting many forums, consolidate using tags within fewer forums.

Why don't my forum tags show up for members?

Two common causes. First, tags are set to Moderator-only (check the tag's settings). Second, the channel itself has restricted View Channel permissions for the role asking. Members must be able to see the channel to see its tags. If permissions look right but tags still don't show, refresh Discord — there's a known cache issue that resolves on restart.

Can I make a forum channel private?

Yes. Forum channels respect role permissions like any other channel. Set @everyone to View Channel: off and grant a specific role View Channel: on. Forum posts inside that private forum inherit the channel's privacy. You can also create per-post privacy by giving the post creator the option to Lock their post (mods can do this from any post's settings).

How do I find old forum posts quickly?

Use Discord's search bar at the top of the channel and combine in: #forum-name with tag: Bug (Discord's search supports tag filters in 2026). You can also click any tag in the forum sidebar to filter. For more advanced search, a bot like PeakBot indexes forum content and lets you search via slash command with regex. The docs cover the search syntax.

Conclusion

Forum channels turn a noisy text channel into a clean, searchable, tag-filtered system — but only if you do the setup right: enable Community, write Post Guidelines, require tags, set a sensible auto-archive window, and bolt on moderation that catches what AutoMod misses.

PeakBot's free tier handles forum auto-tagging, stale-post bumps, and duplicate detection out of the box. The AI Server Builder at $8.50/mo Pro can spin up a forum-channel-heavy server template from a sentence like "community help server with bug, feature, and question forums" in under 60 seconds. Start at peakbot.pro, check pricing, or read the feature list. The FAQ handles edge cases, and the blog has more guides like this.