Discord Server Got Nuked

If your Discord server got nuked, stop the attacker, then put structure back, then lock the door. Invite BetterAntispam if it is not already in the member list. Run /unnuke (Administrator) first. Preview the audit-log rollback, then press Run. After the dust settles, run /antinuke settings (Administrator) so the next mass-delete trips a punishment. Discord has no undelete button for a wiped server. I maintain this bot. It detects and responds. It does not prevent every attack, and it does not load a saved snapshot of every channel.

Editorial disclosure: This guide is published by BetterAntispam. We recommend BetterAntispam when you want audit-log rollback and anti-nuke in the same slash-command stack. Keep Wick if Panic Mode restore from a saved copy is why you opened this tab. Keep Xenon or another backup bot if you already snapshot nightly. We do not tell you to configure BetterAntispam on a website. Thresholds come from the bot’s source.

Undo the damage with `/unnuke`

This is the first body section: the product, then the restore command.

Add BetterAntispam if it is missing. You need Manage Server to invite it. Leave Administrator, View Audit Log, Manage Channels, Manage Roles, and Ban Members on the invite. Discord’s roles page is the hierarchy rule. Restore fails if the bot sits below the roles it has to recreate.
Strip the attacker. Remove Administrator from the compromised account or bot. Do this before you rebuild, or they wipe you twice.
Open Server Settings → Audit Log. Screenshot it. Guide: How to Check the Discord Audit Log.
Run /unnuke (Administrator). The panel is inside Discord. You get a preview: deleted channels, deleted roles, mass-created spam channels and roles, roles stripped from members, bans that were lifted, server name, scheduled events, and messages the bot still holds.
Pick a scan depth if the preview looks thin: Standard (100), Deep (250), Max (600) entries per type. The default window is 24 hours. The setting clamps between 15 minutes and 7 days.
Leave trusted staff unchecked if you do not want their work undone. Press Run. Press Save as default only if this mix should be the next /unnuke. Cancel if the preview is the wrong night.

The bot itself needs Administrator, View Audit Log, Manage Channels, Manage Roles, and Ban Members. If any of those are missing, /unnuke tells you and stops.

Docs: documentation. Support: Discord server. /unnuke and core /antinuke settings are free. Shield is optional in the application store.

/unnuke is not /nuke. /nuke clears a channel you are standing in. Recovery after a staff wipe is /unnuke. Channel cleanup chooser: How to Clear a Discord Channel.

What `/unnuke` will and will not put back

/unnuke reads Discord’s audit log and rebuilds what that log still names. It is not a saved copy of the server.

It can try	It cannot
Recreate deleted channels and roles the log still lists	Restore a Discord server that was deleted
Delete mass-created spam channels and roles	Restore every message ever sent
Put roles back on members who lost them	Force members who left to rejoin
Re-ban people whose bans were lifted	Undo work older than the look-back window
Restore the server name and scheduled events	Beat a role sitting above the bot
Repost recent deletes from snipe, cap 500	Recover pins, webhooks, or invite vanity from nothing

Message restore uses what /snipe still has in memory, not Discord’s archive. Honeypot channels are skipped. If the wipe is older than a week, /unnuke will not see it. If the audit log entry aged out, the name is gone.

I would rather you run /unnuke now than wait for a perfect backup you do not have. I would rather you keep Wick if reconstruction from a nightly snapshot is the product. Those are different jobs.

A leftover spam channel after restore is cleanup, not failure. /purge or /nuke (Administrator, max 1000) clears chat. Discord’s 14-day bulk-delete still applies.

Secure the server before the next wipe

Do not skip this. Restoring into an open hole is round two.

Native control	Where	Why
Remove the attacker	Members / Roles	The token that wiped you is still a token
2FA for moderation	Safety Setup	2FA for Discord moderation
Fewer Administrators	Roles	Every extra admin is another wipe
Pause Invites	Invites / Security Actions	Pause Invites FAQ
Security Actions	Server dropdown	Pause invites and non-friend DMs while you rebuild
Audit Log	Server Settings	Humans still read it

How to Protect Your Server from Raids 101 is Discord’s incident page. A nuke is often a leaked admin session, not a join flood. Still pause invites so raiders do not walk into the rubble.

If chat is still exploding, lock channels. /lockdown (Administrator). Guide: How to Lock a Discord Channel. Join floods are /antiraid settings and /raidmode enable. Playbook: How to Stop Discord Raids.

Set /recoverykey (Administrator) while you still own the server. It is how you get back in after a raid, nuke, or attack. Do not wait until you are locked out to invent one.

Then `/antinuke settings` so it does not happen again

/antinuke settings (Administrator) watches the audit log for a compromised or malicious staff account: mass channel or role deletion, mass bans, webhook creation, permission grabs. Free toggles default on. Punishment defaults to quarantine. It can also ban, kick, or strip roles, and revert what it caught.

Do this after /unnuke, not instead of it. Anti-nuke stops the next actor. It does not rebuild last night.

Drag the BetterAntispam role above every moderator and admin role it should be allowed to quarantine.
Run /antinuke settings. Leave the default-on toggles unless you have a reason to turn one off.
Keep quarantine for the first week if you are scared of false hits on a real admin doing a legitimate mass-delete.
Run /scan. It looks for dangerous @everyone overwrites and other bots holding Administrator.
Point /logging settings (Administrator) at an antinuke log.

The rolling window on thresholds is 10 minutes. Channel-delete default is 3. Ban default is 5. Vanity, admin-grant, and role-permission grabs default to 1. I am not listing every toggle. Open the panel.

Whitelist trusted automation. Do not give the ticket bot Administrator. Do not run three anti-nuke bots. They will fight over the same quarantine.

The longer bot comparison is Best Discord Anti Nuke Bot in 2026. The permission checklist is Anti-nuke Discord. This page is the night it already happened.

Add BetterAntispam if /unnuke is not in the slash menu. Core antinuke is free.

FAQ

My Discord server got nuked. What do I do first?

Strip the attacker. Pause invites. Screenshot the audit log. Invite BetterAntispam if needed. Run /unnuke (Administrator), read the preview, press Run. Then /antinuke settings.

Can Discord restore a nuked server?

Discord will not undelete channels, roles, or a deleted server for you. The delete-channel article is blunt: gone is gone. Recovery is rebuild from the audit log, a snapshot bot you already had, or by hand.

What does `/unnuke` restore?

Recent destructive changes the audit log still lists: channels, roles, mass-created spam, member roles, lifted bans, server name, scheduled events, and up to 500 sniped messages. Default window 24 hours. Max look-back 7 days.

How do I stop my Discord server getting nuked again?

Force 2FA. Cut extra Administrators. Put BetterAntispam above staff. Run /antinuke settings (Administrator). Run /scan. Set /recoverykey while you still own the server.

Is a nuke the same as a raid?

No. A raid is a join flood. A nuke is someone who already has permissions. Joins: /antiraid settings. Staff abuse: /antinuke settings. Chat: /antispam settings. Guide: Best Discord Antispam Bot in 2026.

Will members come back after a nuke?

Not automatically. Unban people who should return. Post a new invite. A deleted server cannot be recovered. A surviving server still needs an announcement.

Is `/unnuke` free?

Yes. Core /antinuke settings is free. Wick’s Panic Mode is the restore story if you want a saved copy. Do not install three audit-log bots.

Final verdict

If the Discord server got nuked, /unnuke first, /antinuke settings second. Strip the attacker before you rebuild. Force 2FA. Put the bot above staff. Invite BetterAntispam. Do not wait for Discord to undelete the channels. They will not. Keep Wick if a snapshot restore is the product you already bought.