When your Discord bot approaches 100 servers, you will see a notice in the Developer Portal requiring verification. This is a mandatory process for any bot that can join more than 100 servers. Without verification, the bot cannot join additional servers beyond the 100-server limit. This article explains why the threshold exists, walks through the entire verification application process, and covers common pitfalls that cause rejection.
Key Takeaways: Passing Discord Bot Verification
- Discord Developer Portal > Applications > Your Bot > Verification: The only place to submit a verification request for the 100-server limit.
- Privacy Policy and Terms of Service URLs: Both must be live, accessible web pages that match your bot’s functionality exactly.
- Two-factor authentication (2FA) enabled on your Discord account: Required to submit a verification request.
Why Discord Requires Bot Verification at 100 Servers
Discord introduced bot verification in 2020 to protect users from malicious bots that could scrape data, send spam, or perform other harmful actions at scale. The 100-server threshold is the point at which a bot reaches enough reach that Discord considers it a potential risk to the platform. Once a bot is in more than 100 servers, any security vulnerability or malicious behavior in the bot could affect a large number of users.
The verification process forces bot developers to prove their identity, provide a working privacy policy and terms of service, and demonstrate that the bot does not request unnecessary permissions. Discord reviews each application manually. Approval typically takes 1 to 3 business days, though it can take longer if the application is incomplete or if the bot requests privileged intents without clear justification.
What Changes After Verification
Before verification, your bot can join up to 100 servers. After verification is approved, the bot can join an unlimited number of servers. The bot also receives a verified checkmark on its profile page, which increases user trust. However, verification does not change rate limits or API access in any other way. Those are controlled separately by the bot’s application flags and intent settings.
Steps to Submit a Discord Bot Verification Request
Follow these steps exactly. Missing any one of them will cause the form to be rejected or delayed.
- Enable two-factor authentication on your Discord account
Open Discord and go to User Settings > My Account. Click Enable Two-Factor Auth and follow the prompts. Verification cannot be submitted without 2FA enabled. - Prepare a Privacy Policy page
Create a public web page that explains exactly what data your bot collects, how it stores that data, and how users can request deletion. Host this on a domain you control. Free services like GitHub Pages or Netlify work. The URL must be HTTPS. - Prepare a Terms of Service page
Create a separate public web page that states the rules users must follow when using your bot. Include disclaimers about liability and a clause about Discord’s Terms of Service. This page must also be HTTPS. - Open the Developer Portal and navigate to your bot
Go to the Discord Developer Portal at discord.com/developers/applications. Click on your bot’s application. In the left sidebar, click Bot. Scroll down to the Verification section. - Complete the verification form
Click the Start Verification button. Fill in every field:– Why did you build this bot? Write 2-3 sentences describing the problem your bot solves. Be specific. Example: “This bot automates moderation by detecting spam links and muting repeat offenders. It was built to reduce moderator workload in large gaming communities.”
– What data does your bot collect? List every data point your bot stores: user IDs, server IDs, message content, timestamps, etc. If your bot stores nothing except what is required to function, say so.
– How does your bot use this data? Explain each data point’s purpose. For example: “User IDs are stored to track warning counts. Server IDs are stored to keep per-server configuration.”
– Privacy Policy URL: Paste the full HTTPS URL of your privacy policy page.
– Terms of Service URL: Paste the full HTTPS URL of your terms of service page.
– Support server invite link: Provide a permanent invite link to a Discord server where users can contact you for support. The invite must never expire and must grant access to at least one channel. - Review and submit
Double-check that all URLs are correct and accessible. Submit the form. You will receive a confirmation email. Discord may send follow-up questions or request changes. Respond promptly.
Common Reasons Discord Bot Verification Gets Rejected
Bot Requests Privileged Intents Without Justification
Privileged intents include Server Members Intent, Message Content Intent, and Presence Intent. If your bot requests any of these, you must explain exactly why in the verification form. Discord will reject the application if the explanation is vague. For example, saying “the bot needs Message Content to function” is not enough. You must state: “The bot reads message content to detect swear words and automatically delete them.”
Privacy Policy or Terms of Service Page Is Broken or Incomplete
Both pages must load over HTTPS without errors. They must be in plain English and cover all data collection and usage. A placeholder page with “Coming soon” text will be rejected. If your bot updates its data collection, update the privacy policy before resubmitting.
Bot Has No Support Server or the Invite Link Expires
Discord requires that users can reach you if something goes wrong. The support server invite must be set to never expire. If the invite expires, Discord cannot verify that users can contact you. Create a dedicated support server with at least one text channel and generate a permanent invite link from Server Settings > Invites > Edit Invite Link > Set Expires to Never.
Bot Uses a Self-Bot or Automates User Accounts
Discord prohibits self-bots — bots that run on a user account instead of a bot account. If your bot appears to be a self-bot, the verification will be denied and your application may be flagged. Always use a proper bot token from the Developer Portal.
Discord Bot Verification Requirements: Unverified vs Verified
| Item | Unverified Bot | Verified Bot |
|---|---|---|
| Maximum servers | 100 servers | Unlimited servers |
| Privileged intents | Cannot use them without manual approval | Can use them after approval in the form |
| Privacy Policy required | No | Yes, must be live HTTPS page |
| Terms of Service required | No | Yes, must be live HTTPS page |
| Support server required | No | Yes, with permanent invite |
| 2FA required on owner account | No | Yes |
| Bot profile checkmark | No | Yes |
The biggest practical difference after verification is the removal of the server cap. A verified bot can grow without limit, which is essential for public bots aimed at large communities. However, verification also forces you to maintain proper documentation and a support channel, which improves the bot’s reliability for users.
After you submit the verification request, monitor the email address associated with your Discord account. Discord may ask for clarification or request changes to your privacy policy. Respond within 48 hours to avoid delays. Once approved, your bot can immediately join new servers beyond the 100-server limit. To prepare for future growth, set up a dedicated support server with clear rules and a bot command for users to request data deletion. This will keep your bot compliant with Discord’s Developer Terms of Service and avoid future enforcement actions.