Discord channel types, by enum value

Discord’s channel model is a single numeric type field on every channel object. Most tooling problems with channels trace back to code that assumed the set was smaller than it is.

The full enum

Values 6 through 9 are absent. They were used by channel kinds Discord has since removed, and the gap is permanent — the enum is a registry, not a sequence.

Where this bites in practice

Threads are channels. A moderation bot that logs deletions by iterating text channels and filtering type === 0 will not see a single thread. Since forum channels contain nothing but threads, that bot is blind to whole sections of a modern server. The correct filter is a set: types 0, 5, 11, 12 and 10 all carry messages.

Categories cap at 50 channels. That is the real constraint behind “we ran out of room in Support” — not a server-wide limit but a per-category one. A server that organises by category and grows past fifty channels in one of them has to split the category, which changes channel ordering and any permission that was inherited from it.

Permission inheritance runs through the category. A channel’s effective permissions are the category’s overwrites combined with its own, so moving a channel between categories silently changes who can see it. This is the single most common cause of “a channel disappeared for everyone but staff” after a reorganisation.

Choosing between forum and media

Both hold only threads. The difference is presentation: a forum lists posts with their titles and reply counts, a media channel shows the first attachment of each post as a tile. Forums suit question-and-answer and support workflows where the title is the unit of meaning; media channels suit galleries where the image is. Neither supports ordinary messages at the channel root, which is why a bot that posts a plain message to a forum ID gets an error rather than a post.