> Discord server nuked, hacked or wiped by a rogue admin? RestoreCord restores channels and roles from a snapshot, pulls verified members back and returns roles.

Source: https://restorecord.fail

# 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.

[Start recovering](https://restorecord.com/register)[First hour after a nuke](https://restorecord.fail/server-nuked)

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

## 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 first     | Snapshot restore | Member pull             | Role 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 outright               | Into 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.

## 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](https://restorecord.fail/server-nuked)

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

### [Members back, roles missing](https://restorecord.fail/restore-member-roles)

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

### [A staff member went rogue](https://restorecord.fail/rogue-admin)

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

### [Bot token leaked](https://restorecord.fail/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.

[Protect my server free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
