You see Discord Error 30005 when you try to create or add a role to your server, and the message says you have reached the maximum number of roles. The official limit per server is 250 roles, but you may hit this error even when you have far fewer roles listed. This error occurs because Discord counts role templates, integration-managed roles, and bot-created roles separately from the ones you see in your role list. This article explains what counts toward the 250 role limit, how to identify hidden roles, and how to free up space without deleting important roles.
Key Takeaways: Discord Error 30005 Role Count Fix
- Server Settings > Roles > View All Roles: Shows only user-created roles, not system or bot roles.
- Integration-managed roles from bots and webhooks: Each counts toward the 250 role limit, even if not visible in the list.
- Role templates from Server Settings > Templates: Can create hidden roles that occupy slots without appearing in the main role list.
Why Discord Error 30005 Occurs Despite the 250 Role Limit
Discord enforces a hard limit of 250 roles per server. However, the role count shown in Server Settings > Roles only displays roles that are manually created by server administrators. Several other types of roles count toward the limit but are not shown in that list:
Integration-Managed Roles
When you add a bot like MEE6, Dyno, or Carl-bot, it can create roles that are managed by that integration. These roles appear in the member list but not in the main role list. They still consume one of the 250 slots. Common integration roles include auto-assign roles, level-up roles, and reaction roles.
Role Templates from Server Templates
If you use Discord’s Server Templates feature to copy roles from another server, the template may include hidden roles that are not visible in the role list. These roles are stored in the server’s database and count toward the limit. You cannot see them in the role list, but they exist.
Webhook and Bot-Owned Roles
Some webhooks and bots create roles for specific functions, such as temporary voice channel access or moderation logs. These roles are owned by the bot or webhook and are not editable by server administrators. They still occupy a role slot.
Steps to Identify and Remove Hidden Roles That Cause Error 30005
To fix Error 30005, you need to find roles that are not visible in the main role list and remove or disable them. Use the following steps:
- Check the Server Settings Role Count
Open Discord and go to your server. Click the server name at the top left, then select Server Settings. Click Roles in the left sidebar. At the top of the role list, you will see a count like “Roles (45/250)”. This number includes all roles, both visible and hidden. - Enable Developer Mode to See Hidden Roles
Go to User Settings > Advanced and toggle Developer Mode on. Right-click any role in the role list and select Copy ID. You can use this ID to query the role via the Discord API, but it does not show hidden roles directly. - Use the Discord API to List All Roles
Open a web browser and go tohttps://discord.com/api/v10/guilds/YOUR_SERVER_ID/roles(replace YOUR_SERVER_ID with your server ID). The JSON response lists every role in the server, including those not visible in the role list. Look for roles with"managed": true— these are integration-managed roles. - Remove Unused Integration-Managed Roles
For each managed role you find, go back to Server Settings > Roles. Click Create Role and then click the Manage Integrations button next to the bot that owns that role. Disable or remove the bot’s role-creation feature. For example, in MEE6, go to the bot’s dashboard and turn off auto-assign roles. - Delete Server Templates That Contain Hidden Roles
In Server Settings > Server Templates, review any saved templates. If a template includes roles, it may have created hidden roles when applied. Delete the template by clicking the three dots next to it and selecting Delete Template. - Remove Unused Bots and Webhooks
Go to Server Settings > Integrations. Review the list of bots and webhooks. Remove any that you no longer use by clicking Remove next to each. This action also removes the roles they created. - Force Refresh the Role List
After removing roles, restart Discord or switch to a different server and back. The role count should update. If it does not, wait 5 minutes and check again.
If Discord Still Shows Error 30005 After Removing Roles
Role Count Does Not Decrease After Deletion
Sometimes the role count in Server Settings does not update immediately. Wait up to 15 minutes for Discord to sync. If the count remains the same, log out of Discord and log back in. Then check the role count again.
Bot-Only Roles Appear in Member List but Not in Role List
Roles assigned to bots only (not to human users) still count toward the limit. To find these, use the Discord API as described above. Look for roles with "bot_id": true in the JSON. You can delete these roles using the API by sending a DELETE request to https://discord.com/api/v10/guilds/YOUR_SERVER_ID/roles/ROLE_ID. Be careful: deleting a bot role may break the bot’s functionality.
Server Template Applied with Hidden Roles
If you applied a server template that included roles, those roles may be hidden but still count. The only way to remove them is to delete the template and then recreate the roles manually. To do this, go to Server Settings > Server Templates, delete the template, then go to Roles and delete any roles that were part of the template. Recreate only the roles you need.
Discord Role Types That Count Toward the 250 Limit
| Role Type | Visible in Role List | Counts Toward Limit |
|---|---|---|
| User-created roles | Yes | Yes |
| Integration-managed roles | No | Yes |
| Bot-owned roles | No | Yes |
| Template-created hidden roles | No | Yes |
| Webhook-created roles | No | Yes |
You now know how to identify all roles that count toward the 250 limit, including hidden ones. Use the Discord API to list every role in your server and remove any that are managed by integrations, bots, or templates. As a next step, review your bot integrations and disable role creation for bots that you do not need. For advanced management, consider using a bot that tracks role usage and can automatically delete unused roles.