
Discord permissions calculator and bot invite link generator
Tick what your bot needs to get the permissions integer and a ready invite link, or paste a number or someone else's invite link to see exactly what it grants.
Permissions bitfield
Build a permission set
Each preset ticks a small, clearly described set that you can change afterwards.
No permission matches that filter. Try a word such as message, voice or ban.
Result
Permissions integer
0
- Hex
0x0- Ticked
- 0 of 52
Nothing ticked yet, so the integer is 0. Pick a preset or tick a permission above.
Bit map0x0
Point at a square to see which permission it is. Click it to tick it.
One square per bit, read like a number: bit 63 top left, bit 0 bottom right. Every four squares make one hex digit. Dashed squares have no permission. JavaScript's 32-bit << and | make bit 31 negative and can't reach bits 32 and up, which is why BigInt is needed.
NoneAdministrator is ticked
It gives the bot every permission, and channel settings can't take any away. Anyone who gets the bot's token could do anything on the server. Discord asks apps to request only the permissions they need.
Risk if the token leakedNothing requested
Tick permissions to see what a leaked bot token could do with them.
Our rough rating, not Discord's.
Tips for these permissions (0)
Bot invite link
In the Developer Portal: your app, then General Information, then Application ID. It isn't secret: every invite link contains it. Never paste your bot token here or anywhere else.
More options
Discord selects this server in the picker if the person opening the link can add bots there (guild_id).
Your invite link
Opening the link asks which server to add the bot to. You need the Manage server permission on that server.
This browser can't do the 64-bit math this calculator needs (BigInt). Open the page in a current version of Chrome, Edge, Firefox or Safari.
How to calculate your bot's permissions
- Pick a preset or tick each permission your bot needs. Type in the filter box to find one, such as ban or voice.
- Read what the result card flags: Administrator, risky permissions, and ticks that don't work without another one.
- Copy the permissions integer or the same set as discord.js or discord.py code, or enter your bot's client ID: the Application ID on the General Information page of your app in the Developer Portal.
- Copy the invite link and open it. Discord asks which server to add the bot to; you need the Manage server permission there.
- Checking someone else's bot? Paste its invite link into the Read box first, untick what it doesn't need and copy the new link.
How the permissions integer works
Every Discord permission is one bit of a single number. Send messages is bit 11, so on its own it's 1 << 11 = 2,048, and View channels is bit 10, or 1,024. A bot that needs both asks for 1,024 + 2,048 = 3,072. Because each permission has its own bit, adding them up is the same as combining them with OR. Reading a number works the other way round: every bit that is 1 is a permission. The bit map lights up those bits, and every four bits make one hex digit, which is why Send messages is 0x800.
Discord's list now runs from bit 0 to bit 52, with no permission at bit 47, so all 52 permissions together are 8,866,461,766,385,663. Discord sends permissions as strings and recommends a big-integer type for them; this page uses JavaScript's BigInt. Since 30 October 2026 the API can also return the permissions a member or role ends up with, as a string: paste that number into the Read box to see what's in it.
Advertisement
Which permissions are risky?
Administrator (bit 3, value 8) is the big one: it includes every permission and channel overwrites stop applying, so a bot with it can do anything on the server, and so can anyone who gets hold of its token. Discord marks eleven permissions as elevated, tagged 2FA in the calculator, such as Kick members, Ban members, Manage server, Manage roles and Manage webhooks. On a server with server-wide 2FA they only work if the bot owner's account uses two-factor authentication. Discord's own advice is to request only the permissions your app needs.
Some permissions depend on others. Without View channels a bot can't see a channel, so its other permissions there do nothing, and since 16 November 2026 bots only get a hidden placeholder for such a channel, without its name or other details. Denying Send messages also blocks Embed links, Attach files, Mention @everyone and text-to-speech, and most voice permissions need Connect. Threads don't inherit Send messages: that is Send messages in threads. Since 23 February 2026 pinning needs Pin messages instead of Manage messages, and bots need Create expressions and Create events to add emoji, stickers and events. The calculator checks all of this as you tick.
Everything stays in your browser
The calculator, the link builder and the link check run in JavaScript on your device. Nothing you tick, type or paste is sent to Livecounts.nl, Discord or anyone else, and the page never asks for your bot token. If you paste something that looks like a token or client secret, the page warns you and doesn't keep it. Only your client ID is remembered in this browser, for next time. Opening the invite link takes you to discord.com, and our visit statistics (Google Analytics) can record the address of the link you clicked.
Sources, checked 21 November 2026: Discord Developer Docs, Permissions (flag table, 2FA marks, hierarchy, implicit permissions, timeouts, threads), OAuth2: Bot Authorization Flow (link parameters, scopes, 2FA requirement), Application: installation contexts (Manage server, integration_type), Reference: Snowflakes, OAuth2 and Permissions, Gateway: Message Content intent, Get Guild Member Permissions and the Change Log (permission changes of 23 February 2026, channel obfuscation of 16 November 2026); MDN, Left shift (<<); the source code of discord-api-types (PermissionFlagsBits, which discord.js exports) and discord.py (Permissions) for the code tabs.
Frequently asked questions
What is the permission integer for Administrator?
8. Administrator is bit 3, and 1 << 3 is 8, so an invite link with permissions=8 asks for it. It gives the bot every permission and channel settings can't take any away, so ask for the exact permissions your bot needs instead.
Why can't my bot kick or ban someone even though it has the permission?
Because of the role hierarchy. A bot can only kick, ban or change the nickname of members whose highest role is below the bot's highest role, and it can only give out roles below its own. Move the bot's role higher in the server's role list.
Do I need both the bot and applications.commands scopes?
Discord's docs say applications.commands is included by default with the bot scope, so bot alone also adds your slash commands, and ticking both does no harm. Without bot, no bot user joins the server and the permissions aren't part of the link.
Why does 1 << 40 give the wrong number in JavaScript?
JavaScript's << and | work on 32-bit integers and the shift count wraps at 32, so 1 << 40 gives 256. Several permissions sit above bit 31, such as Time out members at bit 40. Use BigInt, where 1n << 40n is 1099511627776, or another big-integer type, as Discord's docs recommend; the API sends permissions as strings.
Is it safe to paste my client ID or an invite link here?
Yes. A client ID isn't secret: every invite link contains it. Everything is calculated in your browser and nothing you paste is uploaded. Never paste your bot token into any website, because it works like a password. If something that looks like a token is pasted here, the page warns you and doesn't save it.
More free tools
Advertisement