> Nuked, wiped or deleted Discord server? RestoreCord restores the channels and roles from a snapshot, pulls your verified members back and returns their roles.

Source: https://restorecord.rip

RestoreCord is online as of today

# Your server died? RestoreCord brings it back.

Nuked by a rogue admin, wiped by a raid or deleted outright, a dead Discord server doesn't have to mean a dead community. RestoreCord restores the structure from a snapshot, pulls your verified members home and gives every one of them their roles again.

[Start my rebuild](https://restorecord.com/register)[My server was deleted](https://restorecord.rip/deleted-server-rebuild)

Snapshots, member pulls and the backup previewer are all on the Free plan.

## The numbers behind a rebuild

Plan limits straight from RestoreCord's feature table, so you know exactly what a recovery has to work with.

### Pull cooldown

None

On every plan, Free included

### Role mapping kept

7 days

Shown as a Pending Role Restore

### Messages per channel

50 to 2,000

Snapshot limit, Free to Enterprise

### Restorable members

Unlimited

No member cap on any plan

## A rebuild, from the first alert to the welcome post

This is what bringing a server back looks like when the pieces were in place beforehand: containment, restore, people, roles, and a calm reopening.

### Rebuild log: Pixel Garden

From a wiped server to an open one

Back online

1. Server wiped by a compromised admin  
Channels and roles deleted, audit log saved as evidence
2. Access contained  
Owner MFA checked, rogue admin and webhooks removed
3. Snapshot restored  
"Before role cleanup" restored, structure first, then history
4. Members pulled and roles handed back  
Pending Role Restore run after the first wave
5. Reopened in stages  
Staff, then a small group, then everyone

### #announcements

The first post in the rebuilt server

P

Pixel Garden StaffAPPToday at 18:40

We're back. Same channels, same roles, same people.

What happened and what's next

The old server was wiped. We restored our last good snapshot and pulled verified members back in. Roles are returning in waves as people arrive.

Missing a role?

Give it a few hours, then ask in #help

Official invite

Only from our website

Rebuilt with RestoreCord

## Four moves, in this exact order

Recovery is a sequence, not one button. Each step depends on the one before it, which is why RestoreCord keeps them separate.

### Lock down what's left

Secure the owner account with MFA, revoke unknown admins, integrations and webhooks, and rotate any exposed bot token.

* Rebuilding into a live compromise repeats the damage
* Write down UTC times and audit-log entries first

## Before you call the server rebuilt

Run through this list before the doors open again. It catches the gaps that only show up once a thousand people are back inside.

Every admin account is secured

MFA is on for the owner and staff, and sessions nobody recognises have been signed out.

Secrets were replaced

Bot tokens, API keys and webhook secrets that might have leaked are rotated.

Private stays private

Permission overwrites match your design and staff channels aren't visible to everyone.

The skipped roles were handled

Role restore finished and anything it skipped was assigned by hand or left to its integration.

Verification works end to end

A spare account verified, the firewall rules fired and webhook logs arrived.

A fresh snapshot exists

The rebuilt server was snapshotted once it was stable, and the next restore test is booked.

Find out how long your rebuild takes, before you need it

A practice restore into a spare server shows what your snapshot really holds and how long recovery runs.

[Run a rebuild drill](https://restorecord.rip/practice-server-rebuild)

## Rebuild questions

### 

### 

### 

### 

### 

## Make the next loss a short one

Set up RestoreCord now, take a snapshot and let members verify. If the worst happens, half your rebuild is already done.

[Protect my server](https://restorecord.com/register)[Rebuild without a backup](https://restorecord.rip/rebuild-without-backup)
