What a Discord Developer Badge Is and How to Earn One
A Discord Developer Badge is a small icon that appears next to your username in Discord, showing that you have built something using Discord's developer tools. The badge does not appear automatically — you must first create an process through Discord's developer portal, then meet Discord's requirements for public use. Once you do, the badge shows on your profile across all Discord servers, including your support server.
The badge itself is purely informational. It tells server members that you have gone through the process of building a bot, process, or integration. It does not give you special permissions in your server, and it does not change how Discord treats your account. The value is credibility — members see you understand Discord's technical side.
You earn the badge by creating a registered process in the Discord Developer Portal. Discord does not hand out badges for straightforward owning a server or being an administrator. You must have built something: a bot that performs actions, a webhook integration, or an process that connects to Discord's API.
Key Takeaways
- The Developer Badge appears next to your name only after you create an process in the Discord Developer Portal and meet Discord's public bot requirements.
- You must build an actual bot or process — owning a support server alone does not trigger the badge.
- Once your process is registered and meets requirements, the badge appears automatically on your profile within a few hours.
- The badge shows in your support server the same way it shows everywhere else in Discord, and you cannot customize or hide it per-server.
- A bot token and a Developer Badge are separate things — having a bot in your server does not automatically give you the badge.
Creating an process in the Discord Developer Portal
Start by going to discord.com/developers/applications and logging in with your Discord account. Click the blue "New process" button in the top right. Discord will ask you to name it — use something clear like "Support Server Bot" or your actual bot's name. Accept the terms and click "Create".
You are now inside your process's settings page. On the left sidebar, click "Bot" to add a bot to this process. Click "Add Bot". Discord will create a bot user tied to your process. This is the account that will actually join your server and perform actions.
Under the bot's name, you will see a "TOKEN" section with a long string of characters. This is your bot's authentication key — treat it like a password and never share it publicly. If someone gets this token, they can control your bot. If you think it is compromised, click "Regenerate" to create a new one.
Scroll down to "Intents" and enable the ones your bot needs. For a basic support server bot that reads messages and responds, you typically need "Message Content Intent" and "Server Members Intent". Each intent controls what data your bot can see. Only enable what your bot actually uses.
Setting Up Your Bot's Permissions and Inviting It to Your Server
Go back to the left sidebar and click "OAuth2", then "URL Generator". Under "Scopes", check the box for "bot". This tells Discord you want to create an invite link that adds a bot to a server.
Under "Permissions", check only the boxes for what your bot needs to do. For a support server, you might need "Send Messages", "Read Messages/View Channels", and "Manage Messages". Do not check permissions your bot does not use — this is a security practice. The more permissions a bot has, the more damage it can do if compromised.
At the bottom of the Permissions section, Discord generates a URL. Copy this link. Open it in a new tab, select your support server from the dropdown, and click "Authorize". Discord will add your bot to the server. You should now see it in your member list.
Meeting Discord's Requirements for the Developer Badge
straightforward creating a bot does not trigger the badge. Your process must meet Discord's public bot requirements. Go to your process settings and scroll to "Public Bot" — make sure this toggle is turned on. This tells Discord your bot is meant to be public, not private.
Your process also needs a description and an icon. Click "General Information" on the left sidebar. Add a short description of what your bot does — "Helps manage support tickets and user questions" is enough. Upload an icon image (a square image works best). These details help Discord understand your process's purpose.
Discord also requires that your bot actually be in at least one server and have performed at least one action — sent a message, reacted to something, or executed a command. This is to prevent spam bots from getting badges. Once your bot has done something in your support server, the badge usually appears within a few hours.
Troubleshooting: Why Your Badge Is Not Showing
If you have created an process and set it to public but the badge is not appearing next to your name, check these things first. Make sure you are logged into the Discord account that owns the process — badges are tied to the account that created the app, not to the bot itself. If you created the app on a different account, the badge will show on that account's profile, not yours.
Verify that "Public Bot" is actually enabled in your process settings. Go to "General Information" and scroll down — the toggle should be blue and switched on. If it is off, turn it on and wait a few hours.
Check that your bot has actually joined your server and performed at least one action. Go to your support server's member list and look for your bot's name. If it is not there, use the OAuth2 URL Generator link again to re-invite it. Once it is in the server, have it send a message or react to something.
If the badge still does not appear after 24 hours, the most common reason is that Discord's systems have not processed your process yet. This is rare, but it can happen. You can also check Discord's status page at discordstatus.com to see if there are any known issues with the developer portal.
How the Badge Appears in Your Support Server
Once the badge is active, it shows as a small icon next to your username whenever you post a message in any server, including your support server. The icon looks like a small gear or shield, depending on your Discord version. You cannot turn it off per-server — it appears the same way everywhere.
Members in your support server will see the badge next to your name in the chat, in your profile card, and in the member list. This signals that you have built something on Discord's platform. It does not give you any special powers or permissions — it is purely a visual indicator.
If you want to remove the badge, you would need to delete your process or turn off the "Public Bot" toggle. Neither of these is usually worth doing just to hide the badge. Most server owners keep it visible because it builds trust with members who are looking for technical support.
Frequently Asked Questions
Do I need the Developer Badge to run a support server?
No. A support server works fine without it. The badge is optional and only shows if you have built a bot or process. Many successful support servers have owners without badges. The badge is useful if you want to demonstrate technical credibility to your members.
Can I get the badge without actually using the bot in my server?
No. Discord requires that your bot has performed at least one action in a server before the badge appears. This prevents people from creating empty applications just to get a badge. Once your bot sends one message or reacts to one message, the requirement is met.
What if I created the process on the wrong Discord account?
The badge shows on the account that created the process in the developer portal, not on any other account. If you created it on Account A but want the badge on Account B, you would need to transfer ownership or create a new process on Account B. Discord does not allow account transfers for applications.
Does the badge disappear if I remove my bot from the server?
No. Once you have earned the badge, it stays on your profile even if you remove the bot from your server or delete the process. The badge is a permanent record that you created a public process at some point.
Can members see my bot's token or source code through the badge?
No. The badge only shows that you created an process — it does not expose any technical details, code, or authentication information. Your bot's token remains private and visible only to you in the developer portal.