How to Remove a Bot From Your Discord Server (and Fully Deauthorize It)

To remove a bot from your Discord server, right-click the bot in your member list and choose Kick. But kicking alone does not deauthorize it — to fully cut off its access so it cannot rejoin, you also need to revoke its OAuth authorization in your Server Settings under Integrations.

Most guides stop at "kick the bot." That leaves the door unlocked. This walkthrough covers the full job: removing the bot, revoking its access so it can't quietly slip back in, cleaning up the roles and channels it left behind, doing it all on mobile, and switching to a new bot without breaking your setup.

Kicking vs. deauthorizing: the gotcha most people miss

When you add a bot to Discord, two separate things happen. First, the bot account joins your server like any other member. Second, you authorize it through Discord's OAuth system — that authorization is what grants the bot its permissions and lets it operate.

Kicking the bot only handles the first part. It removes the bot account from your member list right now. But the OAuth authorization can still exist on the server side. In practice, kicking is enough to stop a bot from doing anything immediately, because a kicked bot has no presence and no permissions until it rejoins. The catch is that a leftover authorization makes it trivial for the bot — or anyone holding its invite link — to re-add it later, sometimes without you noticing.

If you're removing a bot because you no longer trust it, or because you're cleaning house before handing the server to someone else, you want both steps done: kick it and revoke the authorization. That's the difference between "I removed it for now" and "it's fully gone."

Step 1: Remove the bot from your member list

This is the part everyone knows, but here's the precise sequence.

1. Open your server and go to the member list on the right side (on desktop, click the people icon in the top-right if it's hidden).
2. Find the bot. Bots have a BOT or APP tag next to their name, so they're easy to spot.
3. Right-click the bot's name.
4. Choose Kick [Bot Name]. If you intend to block it from ever rejoining via an invite, choose Ban instead — banning a bot account prevents that specific bot from being re-added by anyone.
5. Confirm.

You need the Kick Members permission (or Administrator) to do this. If the option is greyed out, your role doesn't have permission, and you'll need a server admin to remove it.

A quick note on Kick vs. Ban for bots: Kick removes it now but doesn't stop a re-invite. Ban removes it and blocks that bot's account ID from rejoining. For a bot you're done with permanently, Ban is the cleaner choice. For a bot you might re-add later (say, you're troubleshooting), Kick is fine.

Step 2: Revoke its OAuth access so it can't rejoin

This is the step that turns "removed" into "deauthorized." Even after kicking, the bot's authorization can linger under your server's integrations. Clear it out.

1. Open Server Settings (click the server name at the top-left, then Server Settings).
2. Go to Integrations (sometimes shown under the Apps category in newer layouts).
3. You'll see a list of bots and integrations connected to the server. Find the one you removed.
4. Click into it, then choose to remove the integration or revoke access. Confirm.

What this does: it strips the authorization grant that lets the bot operate on your server. After this, the bot can't act on the server, and re-adding it requires a fresh, explicit authorization through the invite flow — no silent rejoin.

If the bot already left and no longer appears under Integrations, you're done on this front. Some bots clean up their own integration entry when kicked; others don't. Always check, because the leftover entry is exactly the thing that quietly keeps a bot's foot in the door.

One more layer if you're being thorough: bots authorized through your user account (not just the server) can appear in User Settings → Authorized Apps. That list is per-account and worth a glance if you personally authorized the bot. Removing it there revokes the connection from your side.

Step 3: Clean up leftover roles, channels, and webhooks

A bot rarely leaves cleanly. Most create supporting structure when they're set up, and that structure stays behind after the bot is gone. Here's what to sweep up.

Roles. Many bots create a role for themselves (often named after the bot) and sometimes utility roles like "Muted," "Level 10," or "Verified." Go to Server Settings → Roles, find the orphaned ones, and delete the roles you no longer need. Be careful: if you used the bot's role to gate channel access, deleting it changes who can see what. Re-check the affected channels' permissions after.

Channels and categories. Logging bots, ticket bots, and welcome bots often add channels — #bot-logs, #welcome, a "Tickets" category, a #level-up channel. Decide which you still want. Right-click any unwanted channel and choose Delete Channel.

Webhooks. This is the one people forget. Many bots post through webhooks, and a webhook keeps working even after the bot is gone — it's a standalone posting endpoint. Go to Server Settings → Integrations → Webhooks and delete any webhook tied to the removed bot. If you skip this, you can end up with a "ghost" channel that still receives posts from a webhook you forgot about.

Slash commands. Discord usually clears a bot's slash commands once it leaves, but they can linger briefly in the command picker. If you still see them after a day, fully removing the integration (Step 2) forces a cleanup.

Once those four are handled — roles, channels, webhooks, commands — the bot is genuinely gone, not just hidden.

Removing a bot on mobile

You can do all of this from the Discord mobile app, with slightly different taps.

To kick the bot:

1. Open your server and tap the member list (swipe left or tap the members icon).
2. Tap the bot's name to open its profile.
3. Tap the three-dot menu.
4. Tap Kick (or Ban for a permanent removal). Confirm.

To revoke its authorization:

1. Tap the server name at the top to open the menu, then tap Settings (gear icon).
2. Scroll to Integrations (or Apps).
3. Tap the bot, then remove or revoke it.

The mobile flow mirrors desktop — same two steps, kick and revoke — just behind tap menus instead of right-clicks. Webhook cleanup is also available under Settings → Integrations → Webhooks on mobile.

Switching bots: migrating your setup cleanly

A lot of removals aren't really "I want fewer bots" — they're "I want a better bot." If you're replacing one tool with another, the order matters so you don't lose your configuration mid-swap.

The clean sequence:

1. Set up the new bot first, alongside the old one. Add it, configure your moderation rules, leveling, welcome messages, and tickets so the new bot is actually doing the job before you pull the old one. Our step-by-step guide to adding a Discord bot covers the invite flow and permission setup.
2. Verify the new bot works. Test a moderation trigger, send a test welcome, open a test ticket. Don't assume — confirm.
3. Then remove the old bot using Steps 1–3 above.
4. Clean up the old bot's roles and channels only after you're sure the new bot isn't depending on any of them.

This matters most for things like XP and leveling, which usually don't transfer between bots. If you're leaving MEE6 specifically, we wrote a dedicated walkthrough on migrating from MEE6 to PeakBot that covers what carries over and what you'll reconfigure.

A common reason people consolidate: running too many single-purpose bots. If your server has a separate bot for moderation, leveling, tickets, and welcomes, that's four authorizations, four roles, and four points of failure. PeakBot replaces MEE6, Carl-bot, Dyno, and TidyCord with one bot, with 30+ free features and no time limit — so removing three bots and keeping one is often the real cleanup. Each of those rivals has a genuine strength (Carl-bot's reaction-role granularity, Dyno's long track record, MEE6's name recognition), but running all of them at once is what creates the clutter you're now untangling. If you're not sure how lean to go, our take on how many bots a Discord server actually needs is a useful gut-check.

For deciding what your one all-in-one bot should handle, the full feature list lays out moderation, XP and leveling, tickets, and welcome messages in one place.

FAQ

Did removing the bot delete my data?

Not necessarily — kicking a bot removes it from your server, but the data it stored (XP levels, logs, configuration) usually lives on the bot's own servers, not in Discord. Some bots keep your data for a grace period in case you re-add them; others purge it. If you want your data deleted permanently, check the bot's privacy policy or contact its support, because Discord can't delete data a third party holds. For PeakBot, reach the team via the support server at discord.gg/peak.

How do I re-add a bot after removing it?

Re-adding a bot is just the normal invite flow again: get the bot's invite or "Add to Server" link, select your server, approve the permissions, and authorize. If you fully revoked its OAuth access in Step 2, you'll go through a fresh authorization — which is exactly what you want. There's nothing to "undo"; you simply add it again like the first time.

Will the bot rejoin on its own after I kick it?

A properly kicked bot won't rejoin by itself. It can only come back if someone uses its invite link again, or if a leftover authorization lets it re-add. That's the whole reason for Step 2 — revoking the integration closes the path for a silent rejoin.

Do I need to ban the bot, or is kicking enough?

Kicking is enough to remove a bot right now and stop it from doing anything. Ban it only if you want to permanently block that specific bot account from ever being re-invited by anyone — useful when you've decided you're done with a bot for good, or you're locking down a server before handing it off.

What happens to channels and roles the bot created?

They stay. Discord doesn't auto-delete the roles, channels, categories, or webhooks a bot set up. You have to remove the ones you no longer want manually, which is Step 3 above. Watch webhooks especially — they keep posting even after the bot is gone.