Your Discord server got wrecked. Here's the way back.

Channels deleted, roles wiped, half the community banned. RestoreCord Recovery walks you through the order that sticks: lock the attacker out, rebuild from a clean snapshot, pull your verified members home and give them their roles back.

Snapshots, member pulls and role restores all work on the Free plan.

Incident log: Backup Target

Times in UTC, written down before anything was restored

Recovering
  1. 21:04 · 38 channels deleted

    Audit log entry from a moderator account

  2. 21:09 · Owner password changed, 2FA checked

    Unknown sessions signed out

  3. 21:12 · Admin roles stripped, 2 webhooks removed

    Bot token reset and saved in Dashboard → Bots

  4. 21:18 · Snapshot restore started

    Recovery point taken the night before

  5. Next · Member pull, then Restore Roles

    Queued until the structure is back

Chosen recovery point

The newest snapshot from before 21:04

Snapshot
Nightly · Backup Target
Taken
20 hours before the attack
Pinned
Yes
Messages per channel
500 (Business)
Destination
Same server, same invites
Clear server first
Off

What broke decides what you run

Not every incident needs every tool. Match the damage to the steps, and skip the ones that would only slow you down.

Contain firstSnapshot restoreMember pullRole restore
Nuked by a hijacked account
Channels or roles deleted by mistake——If roles were recreated
Members mass-banned or kicked—After unbanning—
Server deleted outrightInto a new server
Bot token leaked, nothing deleted yet———

Containment, before anyone presses restore

Rebuilding while the attacker still has a way in gives them a fresh server to wipe and buries the evidence. Tick these off first.

Owner account back under control

New password from a trusted device, two-factor confirmed, unknown sessions signed out, and the email behind it secured.

Administrator stripped from doubtful accounts

Take Administrator and Manage Server off anyone you're unsure about. Handing them back later costs nothing.

Strange webhooks and apps removed

Delete any webhook, integration or application your team didn't add. A leftover webhook is how rebuilt servers get spammed.

Bot token reset and saved

Reset it in the Developer Portal, paste the new one into Dashboard → Bots and save before running any server operation.

Audit log captured

Screenshot the destructive entries and note the UTC time of the very first one. It decides which snapshot is safe.

Restore point chosen

Pick the newest snapshot taken before that first entry, and preview it so you know exactly what you're bringing back.

Four restores, one after another

Each part of the server comes back through its own tool, and the order matters. Flip through them the way you'd run them.

Rebuild the structure from a clean snapshot

Choose the newest snapshot taken before the first malicious change, drag the bot's role above everything it has to recreate, and start. Channels, categories and roles come back first, then message history.

Snapshot restore

Running against Backup Target

Running

Categories and channels

Recreated with their permission overwrites

x
100%

Roles and permissions

New role IDs recorded for the mapping

x
100%

Message history

Re-posted up to the chosen count

x
58%

How far back each snapshot reaches

Messages kept per channel, per snapshot. Business and Enterprise can also take snapshots on a schedule, so there's always a recent recovery point.

Free

50

messages per channel, 1 snapshot per server

Premium

200

messages per channel, 5 snapshots per server

Business

500

messages per channel, 30 snapshots, scheduled

Enterprise

2,000

messages per channel, 50 snapshots, scheduled

Recovery guides for the incident in front of you

Each one goes deeper on a single kind of bad day.

The first hour after a nuke

Minute by minute: close every door, record the evidence, pick the right snapshot and rebuild.

Members back, roles missing

Why recreated roles lose their members and how the 7-day Pending Role Restore fixes it.

A staff member went rogue

Remove an admin who turned on the server, roll back their damage and tighten staff access.

Bot token leaked

Reset it without losing a single verified member, then check what the thief touched.

Recovery questions, answered straight

Take the snapshot before you need it

Recovery is only as good as your last snapshot and the members who verified. Set both up today and a nuke becomes a rough evening, not the end.