Discord error 30013: Maximum number of guild channels reached (500)
Last verified against Discord Developer Docs - Opcodes and status codes
Maximum number of guild channels reached (500)What error 30013 means
The guild has 500 channels, the per-server cap, and Create Guild Channel failed. The count includes text, voice, categories, announcement, stage and forum channels; active threads do not count toward it, which is the main escape hatch.
The bots that hit 500 are ticket systems and per-user or per-game channel creators. A ticket bot that creates a channel per ticket and archives by renaming instead of deleting will fill a busy server in weeks. Temporary voice channel bots that fail to clean up after a crash leave orphaned channels behind.
What it looks like
{
"message": "Maximum number of guild channels reached (500)",
"code": 30013
}Why it happens
- Ticket or support bot creating a channel per ticket without deleting closed ones
- Temporary voice channel bot that missed deletions (crash, missing permissions, rate limit)
- Large community with many categories and per-topic channels
- Setup or migration script that created channels repeatedly
How to fix Discord error 30013
- 1GET /guilds/{guild.id}/channels and count; identify channels created by your bot (store IDs, or match naming pattern)
- 2Delete closed-ticket and orphaned channels; export transcripts first if needed
- 3Switch ticket and temporary conversations to threads, which do not count toward the channel cap
- 4Add a cleanup job that runs on startup to remove temporary channels left by a previous crash
How to stop it recurring
Prefer threads over channels for anything temporary. If you must create channels, store their IDs with a creation time and purpose, and give every creation path a matching deletion path that runs even after restarts.
Show the current channel count in an admin dashboard or status command, and warn at 450 so the server owner has time to archive before creation starts failing. Archive transcripts to a file or external store, not to yet another channel.
Channel budgets reward threads: they scale past the 500 cap, archive themselves, and keep the sidebar usable. The channel cap and thread auto-archive windows are both on the Discord limits page; bulk cleanups of old ticket channels should pace their deletes or they trade this error for 20029.
Official reference: Discord Developer Docs - Opcodes and status codes. See all Discord error codes or the Discord limits and quotas.
Related codes
- 30005: Maximum number of guild roles reached (250)Maximum number of guild roles reached (250)
- 30030: Maximum number of server categories reached (5)Maximum number of server categories has been reached (5)
- 20029: Server write rate limitThe write action you are performing on the server has hit the write rate limit
Error 30013 - quick answers
What does Discord error 30013 mean?
The guild has 500 channels, the per-server cap, and Create Guild Channel failed. The count includes text, voice, categories, announcement, stage and forum channels; active threads do not count toward it, which is the main escape hatch. The bots that hit 500 are ticket systems and per-user or per-game channel creators.
How do I fix Discord error 30013?
1. GET /guilds/{guild.id}/channels and count; identify channels created by your bot (store IDs, or match naming pattern) 2. Delete closed-ticket and orphaned channels; export transcripts first if needed 3. Switch ticket and temporary conversations to threads, which do not count toward the channel cap 4. Add a cleanup job that runs on startup to remove temporary channels left by a previous crash
Should I retry after error 30013?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Discord by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.