Discord Permissions Calculator
Tick permissions to get the exact bitfield, decode any permissions number back to a checklist, and build a ready-to-share bot invite link. All 52 current flags — including Pin Messages, Create Polls & Bypass Slowmode.
Decode a permissions number
That doesn't look like a valid number — use decimal (e.g. 8) or hex (e.g. 0x8).
Decoding also ticks the checkboxes above, so you can tweak an existing bot's permissions and copy the new value.
Bot invite URL generator
Find the ID in the Discord Developer Portal → your app → General Information → Application ID. The ID is public (it's in every invite link), and nothing you type here leaves your browser.
How it works
- Every Discord permission is a single bit in a 64-bit number: Administrator is 1 << 3 (8), Send Messages is 1 << 11 (2048), all the way up to Bypass Slowmode at 1 << 52.
- Tick boxes above — the bits are OR-ed together into the permissions integer shown live in the sticky bar (decimal for invite URLs, hex for code).
- Got a number from an existing invite link, an API payload or a bot's docs? Paste it into Decode to see exactly which permissions it grants.
- Drop your app's client ID into the invite generator and share the URL — server admins clicking it will see exactly the permissions you selected.
Flags marked 2FA can only be used on servers with server-wide two-factor auth if the acting account (including a bot's owner) has 2FA enabled.
Full permission reference
All 52 flags with bit positions, hex and decimal values
| Permission | API flag | Bit | Hex | Decimal |
|---|
Matches the official Discord API documentation. Bit 47 is currently unassigned, which is why it's missing from the table.
About this tool
When you invite a bot, the permissions number in the URL pre-fills the checkboxes a server admin approves. Bot developers need to generate that number; server owners often want to decode one to check what a bot is actually asking for before clicking Authorize. This page does both, with the complete 2026 flag list — many older calculators are missing the newest bits (Set Voice Channel Status, Create Polls, Use External Apps, Pin Messages, Bypass Slowmode), so their numbers come out short.
The math uses BigInt, so bits above 31 (everything from Request to Speak upward) are exact — no floating-point rounding. Everything runs locally in your browser; no API calls, nothing stored.
FAQ
What is a Discord permissions integer?
Discord stores a role's or bot's permissions as a single number — a bitfield. Each permission is one bit: Administrator is 1 << 3 (8), Send Messages is 1 << 11 (2048), and so on. Adding the bits of every granted permission produces the permissions integer you see in invite URLs and API payloads.
How do I use the permissions number in a bot invite link?
Put it in the permissions query parameter of the OAuth2 authorize URL: https://discord.com/oauth2/authorize?client_id=YOUR_APP_ID&permissions=NUMBER&scope=bot. The scope must include bot for the permissions to apply, and applications.commands lets the app register slash commands.
Should I give a bot Administrator?
Almost never. Administrator (bit 8) grants every permission and bypasses all channel-level overwrites, so a compromised or buggy bot can do anything in your server. Grant only the specific permissions the bot documents needing — you can always add more later.
Why does my number differ from older calculators?
Discord keeps adding permissions. Recent additions include Set Voice Channel Status (1 << 48), Create Polls (1 << 49), Use External Apps (1 << 50), Pin Messages (1 << 51) and Bypass Slowmode (1 << 52). Calculators that predate them produce smaller totals for "all permissions" and can't decode newer bitfields fully.
What does the 2FA tag mean?
On servers with server-wide two-factor authentication enabled, moderation-grade permissions (Kick, Ban, Administrator, Manage Server/Channels/Messages/Roles/Webhooks/Threads/Expressions and monetization analytics) can only be used by accounts — including bot owners — that have 2FA turned on.
Is anything uploaded when I use this calculator?
No. The permission list and all the math live in this page's JavaScript; nothing you type — including your application's client ID — leaves your browser.