How to Make a Discord Server Private (2026 Guide)

To make a Discord server private, disable Server Discovery, revoke all existing invites and replace them with single-use 24-hour invites, raise the Verification Level to "Highest", role-gate every channel via permission overwrites, and add a verification gate (Membership Screening or a verification bot). For full lockdown, also disable DMs from server members and turn on the Phone Verification AutoMod rule.

Key Takeaways

• A "private" Discord server has zero public exposure: no Discovery listing, no shared invites, no public vanity URL
• Verification Level: Highest forces a verified phone number on every joiner
• Role-gated channels (using permission overwrites) keep unverified joiners from seeing real content
• Single-use, time-limited invites are the single biggest leak-prevention move
• Anti-raid is a separate problem from privacy — both need to be solved together for a truly locked server

Step 1: Decide What "Private" Actually Means for You

"Private" is a spectrum on Discord. Before you start clicking, decide which level you need:

Privacy level	What's blocked	Best for
Friends-only	Public Discovery, public vanity, shared invites	Family, study groups, small clans
Invite-only	All of the above + single-use invites only	Paid communities, alpha groups
Vetted-entry	All of the above + verification gate before any channel access	Whitelist groups, NDA servers
Locked vault	All of the above + Highest verification + DM lock + audit log review	Internal team, security-sensitive ops

I run a vetted-entry server for a 60-person comp Fortnite team and it took me about three iterations to dial in the right setup. The mistake I see most often: people lock the front door but leave a window open via a half-finished onboarding channel that anyone can read after joining.

Step 2: Disable Server Discovery and Public Vanity

Open Server Settings → Discovery. If your server has Community features enabled (you may have turned this on for forum channels or stage channels), Discovery is a separate toggle.

1. Go to Server Settings → Discovery
2. Set Enable Discovery to Off
3. Remove any Discovery banner, description, and categories
4. Go to Server Settings → Vanity URL and clear the vanity link if you set one

A vanity URL like discord.gg/yourservername is permanent shareable advertising. If you want privacy, you cannot have one.

What if you need Community features but want privacy?

You can run Community features (forums, announcements, welcome screen) without being in Discovery. Just keep Discovery off while keeping Community on. The two settings are independent — a common confusion.

Step 3: Nuke Existing Invites and Replace Them

Every existing invite is a leak risk. Wipe them all.

1. Server Settings → Invites
2. Click the Pause Invites toggle if you want a temporary freeze
3. Otherwise: hit Delete on every active invite (especially the auto-generated "never expire" ones from when channels were created)
4. Audit who has Create Invite permission — by default, everyone does. Strip it from @everyone in Server Settings → Roles → @everyone → Permissions by toggling Create Invite off

Generating safer invites

When you do generate a new invite, click the gear icon on the invite popup and set:

Setting	Recommended
Expire after	24 hours (or 30 minutes for high-security)
Max uses	1
Grant temporary membership	On (kicks user when they go offline if they don't get a role)

The "Grant temporary membership" option is underused. Combined with a verification flow, it auto-cleans anyone who joined and ghosted before getting a real role.

Step 4: Raise Verification Level to Highest

Server Settings → Safety Setup → Verification Level.

Discord's five tiers:

Level	Requirement to message
None	Nothing
Low	Verified email
Medium	Discord account 5+ minutes old
High	Member of this server 10+ minutes
Highest	Verified phone on Discord account

Set this to Highest. Yes, it'll filter out people who refuse phone verification — that's the point. If your community is small and tight-knit, this is the right call. If you're worried about excluding privacy-conscious members, drop to High as a compromise.

Step 5: Role-Gate Every Channel

This is the step that separates a kind of private server from a truly private one. By default, @everyone can see and speak in every channel. You need to flip that.

The verified-only model

1. Create a role called Verified in Server Settings → Roles → Create Role
2. For every real channel (not the welcome/verify channel), open the channel's settings → Permissions → click @everyone → set View Channel to red X
3. Click Add Members or Roles → add Verified → set View Channel to green check
4. Leave the welcome and verification channels visible to @everyone

Now anyone who joins sees only the welcome and verify channels until they earn the Verified role. They literally cannot read or send anywhere else.

Why permission overwrites beat private categories

You can mark a category as Private in the category settings and have channels inherit, which is faster but less flexible. Use permission overwrites at the channel level when you need finer control (e.g., one announcement channel visible to all verified, but a separate VIP channel only visible to a higher role).

For full reference, Discord's permissions documentation explains how overwrites cascade.

Step 6: Add a Verification Gate

Membership Screening is Discord's native verification flow. Enable it under Server Settings → Safety Setup → Membership Screening. You can require new members to read rules and click an agreement before they can interact with any channel.

For stronger verification, use a bot. PeakBot has a verification module under the features page that supports:

• Click-to-verify (button + role assignment)
• Captcha verification (image-based, anti-selfbot)
• Q&A verification (custom question, manual approval)
• Account-age gate (block accounts younger than N days)

The Q&A approach is the strongest. New joiners answer one question (e.g., "Who invited you?") and a moderator approves them manually. It's slow on purpose. PeakBot's Pro plan at $8.50/mo also includes the AI Server Builder, which can generate the full verified-only channel structure with permissions baked in — saves about an hour of clicking. Compare it to the alternatives on peakbot.pro/compare/mee6.

Step 7: Configure AutoMod Against Raids

Privacy isn't just about who enters — it's also about who survives once inside. Server Settings → Safety Setup → AutoMod has six rule types in 2026:

Rule	What it catches
Spam	Repeated messages, mass mentions
Harmful Links	Phishing and malware URLs
Mention Spam	More than N mentions in one message
Profanity	Customizable wordlist
Sexual Content	Native filter
Slurs	Native filter

Turn on all six for a private server. Set Mention Spam to a threshold of 5. Set Spam to alert moderators rather than auto-delete (so you can review patterns).

Anti-raid hardening

Beyond AutoMod, consider:

1. Slow Mode on the welcome channel (5 seconds)
2. Phone Verification AutoMod (auto-quarantine accounts without phone verification)
3. Account-age gate at 7+ days via PeakBot
4. Raid mode toggle — a panic button that blocks new joiners temporarily

PeakBot's raid mode triggers automatically when the bot detects more than 10 joins in 60 seconds, which is the classic raid pattern. Read the docs for tuning thresholds.

Step 8: Lock Down DMs and Profile Exposure

Server-level privacy is half the battle. Member-level privacy is the other half.

1. User Settings → Privacy & Safety → Direct Messages
2. Toggle Allow direct messages from server members to Off for the server in question (per-server setting in 2026)
3. In the server itself, encourage members to do the same via the welcome channel rules

This stops social engineers from joining your server, scraping the member list, and DMing people pretending to be admins.

Do I need a bot to make my server private?

Strictly speaking, no — Discord's native settings cover the basics. But there are three things bots do meaningfully better than native settings:

1. Q&A verification with manual approval — native Membership Screening can't gate based on a custom answer
2. Account-age filtering — native verification only goes to phone-verified, not "must be 30 days old"
3. Auto-quarantine with role assignment — native AutoMod can timeout but can't move users to a quarantine role

If your privacy needs are casual, native settings are fine. If you're running anything mission-critical, a bot like PeakBot adds the missing layers. The free tier covers verification and anti-raid; you only hit Pro at $8.50/mo for the AI Server Builder. Full price breakdown at peakbot.pro/pricing.

Step 9: Run a Privacy Audit

Once everything's configured, audit it. Create a fresh, second Discord account on a different email and try to:

1. Find your server in Discovery — it shouldn't appear
2. Search for the vanity URL — should 404
3. Open an old invite link — should say "Invalid Invite"
4. Join via a current invite — should land in a verification-only state
5. Click any real channel from the sidebar — should be invisible

I run this audit monthly because permission overwrites drift over time, especially after creating new channels and forgetting to inherit category permissions properly.

Common audit failures

Failure	Root cause	Fix
New channel visible to unverified	Channel not synced to category permissions	Right-click channel → Sync Permissions
Old invite still works	Pause Invites is per-invite, not global	Delete invite, don't just pause
Bot offline so verification breaks	Bot host went down	Check bot status page, swap to backup verification

Frequently Asked Questions

Can someone find my private Discord server through Google?

Only if you've published the invite link somewhere Google can crawl. Discord itself doesn't expose private servers to Google — the Discovery directory is the only Google-indexed surface. Disable Discovery, scrub any old Reddit/Twitter/forum posts where you shared invites, and your server is invisible to search engines. The vanity URL is the most common leak — clear it.

Does setting a server to private kick existing members?

No. Privacy settings only affect future discovery, joining, and visibility. Existing members keep their roles and access. If you want to clean house, you'll need to manually kick or use a bot's bulk-prune feature. Discord has a built-in Prune Inactive Members option under Server Settings → Members that removes members who've been offline for 7-30 days.

What's the difference between Membership Screening and a verification bot?

Membership Screening is Discord's native flow: read the rules, click "I agree", you're in. It's free but offers no actual verification — it's a checkbox. A verification bot like PeakBot can require captcha completion, account-age checks, custom Q&A with manual approval, and IP-based duplicate-account detection. Use Membership Screening as the first line, a bot as the second line for high-value servers.

Will Highest verification level scare people away?

Some, yes. Highest requires a verified phone on the user's Discord account, and a small minority of users (often privacy advocates or burner-account holders) won't comply. For most communities, the trade-off is worth it: the people you filter out are exactly the people you want to filter out. If you're running an open creator community, drop to High instead. For a private team, stay at Highest.

Can I make a private server invite-only without disabling everything else?

Yes. Privacy is a stack — you can take the minimum step (delete public invites, generate one-time invites only, strip Create Invite from @everyone) without disabling Discovery, Community, or AutoMod. This gets you 80% of the privacy benefit with 20% of the effort. Layer on more steps as your community grows or your threat model tightens.

Do private servers have a member cap?

No. Private and public servers share the same caps: 500,000 members per server, 250 roles, 500 channels. You won't hit any of these by going private. The cap most private servers run into is the bot count: 50 bots per server, hard limit. Don't waste slots on bots that overlap features.

Conclusion

Locking down a Discord server is a layered job: kill the public surfaces (Discovery, vanity, old invites), raise the entry bar (Highest verification, single-use invites, verification gate), and harden the inside (AutoMod, role-gating, DM lock). Skip any layer and the privacy claim falls apart.

PeakBot makes the verification + anti-raid + role-gating stack one click instead of one hour. The AI Server Builder at $8.50/mo Pro can generate a fully role-gated, verification-gated server template from a single sentence like "private clan server, vetted-entry only, 50 members". Start at peakbot.pro, pick a plan from pricing, or browse the feature list. The FAQ covers privacy edge cases, and the blog has more security walkthroughs.