Discord Permission Calculator + Invite URL Generator

Build Your Bot's Permissions

Start from a preset, then refine. Or paste a permission integer in the output below to decode it back into a checklist.

How Discord Permissions Actually Work

Discord stores every permission as a single bit in a 64-bit integer. SEND_MESSAGES is bit 11 (value 2^11 = 2048), BAN_MEMBERS is bit 2 (value 4), and so on. To grant a bot multiple permissions, Discord OR's all the values together into one big number — that's the permissions= parameter you see in OAuth2 URLs.

SEND_MESSAGES (bit 11)        = 2048
EMBED_LINKS   (bit 14)        = 16384
ADD_REACTIONS (bit 6)         = 64
                                ─────
Combined integer (bitwise OR) = 18496

Most online calculators do this with regular JavaScript numbers, which break silently above bit 53 (the JS Number.MAX_SAFE_INTEGER). Discord added USE_EXTERNAL_APPS at bit 50 in 2024, SEND_POLLS at bit 49, and CREATE_EVENTS at bit 44 — all still safe in regular numbers, but if Discord adds even one more permission this calculator silently produces wrong results everywhere else. This calculator uses BigInt so it stays correct as the permission set grows.

Permission integer vs role permission: The integer in your invite URL sets the default permissions assigned to the bot's auto-created role when it joins a server. Server admins can override this from Server Settings → Roles → [Your Bot]. So even if you request ADMINISTRATOR in your invite, an admin can demote the role to read-only after the fact. Request the minimum your bot needs — admins are far more likely to approve a bot asking for 5 specific permissions than one asking for the universe.

Three Permission Mistakes That Will Bite You

1. The ADMINISTRATOR trap

Checking ADMINISTRATOR grants every other permission automatically and bypasses every channel-specific override. Sounds convenient — except every legitimate bot listing site (top.gg, discord.bots.gg) deprioritizes admin bots, server admins suspect them on sight, and a single compromised token gives an attacker full control of every server your bot is in. Never ship a bot with ADMINISTRATOR by default. If your bot needs to manage roles or channels, request only those specific permissions.

2. Forgetting applications.commands

If you're using slash commands (and you should be — Discord deprecated message-content access for new bots in 2022), the OAuth2 invite must include both the bot scope and the applications.commands scope. Without the second one, your bot joins the server but its slash commands never appear in the picker. This calculator includes applications.commands by default. If you're building a legacy message-prefix bot only, uncheck the scope.

3. Channel overrides > role permissions

Discord computes final permissions per channel using a precedence chain: @everyone role permissions → role permissions (highest role wins) → channel-specific role overrides → channel-specific member overrides. So a bot with SEND_MESSAGES at the role level can still be silenced in a single channel via a channel override. If your bot "isn't responding" in one specific channel but works elsewhere, that's the cause 90% of the time. Check the channel's Permissions tab.