> Deleted Discord servers can't be undeleted, but a RestoreCord snapshot and verified members mean you rebuild instead of starting again from an empty guild.

Source: https://restorecord.rip/deleted-server-rebuild

# Discord server deleted? Rebuild it from a backup

A deleted Discord server can't be undeleted. With a RestoreCord snapshot and a verified member list, though, you rebuild it instead of starting over from an empty guild.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Create a new server, invite your RestoreCord bot with its role at the top, restore the last good snapshot into it, pull your verified members back and run Restore Roles within 7 days. Secure the owner account before any of it.

Discord treats a deleted server as gone for good, and support can't roll it back. That sounds final, but most of what made the server valuable never lived only inside it. The structure is in your snapshot. The members are in RestoreCord, through the authorization they gave when they verified. The rebuild is about bringing those two halves together in a new home.

## What you have to work with

| You have                           | It brings back                                                                         |
| ---------------------------------- | -------------------------------------------------------------------------------------- |
| A RestoreCord snapshot             | Channels, roles, permissions, settings, recent messages and the member-to-role mapping |
| Members who verified with your bot | The people, added to the new server by a member pull                                   |
| Your custom bot                    | The link between members' authorization and the new server                             |
| Neither                            | A manual rebuild plus invites; see our no-backup guide                                 |

Step 1

Contain

Secure owner, revoke access, rotate tokens

Step 2

Restore structure

Channels, roles, permissions, messages

Step 3

Pull members

Prior-authorized members only

Step 4

Restore roles

Re-assign saved roles to members who returned

Step 5

Reopen

Staff first, then the community

## Before you rebuild: why did it die?

If the server was deleted by a compromised account, rebuilding while the attacker still has access only gives them a second target. Change the owner password from a trusted device, check two-factor authentication, sign out unknown sessions and secure the email behind the account. If your bot token may have leaked, reset it in the Discord Developer Portal and update it in RestoreCord.

## Open a fresh server

Create the server from the account that will own it long term. Give it the old name and icon so returning members recognise it. Don't build channels by hand yet; the snapshot will do that.

## Invite the bot and fix its role

Invite the same RestoreCord bot your members verified with. Give it **Manage Roles** and **Manage Channels**, then drag its role to the very top of the role list. A bot can only create and assign roles below its own, so a low bot role is the most common reason a rebuild comes out incomplete.

## Run the snapshot restore

In the dashboard, open **Snapshots** and pick the last snapshot taken before the damage, which may not be the newest one. Preview it, choose the new server as the destination and set the messages per channel within your plan's limit. Structure comes back first, then message history. Large restores take time because RestoreCord respects Discord's rate limits; let it finish rather than starting another.

## Pull your members

Start a member pull into the rebuilt server. RestoreCord adds people who verified earlier and still have valid authorization, and there's no RestoreCord pull cooldown on any plan. Expect some skips:

* Members who revoked the app's access in Discord
* Accounts Discord rejects because of their state or server limits
* People who already rejoined through a public invite, who are counted as present

Don't announce your old member count as recovered. Report what the pull actually added, and keep a public invite available for everyone else.

## Hand out the old roles

After the restore, a **Pending Role Restore** banner appears in the dashboard. It holds every member's role mapping for 7 days. Run it once the first wave of members is in, and again after later waves. The details are in [restoring roles after a rebuild](https://restorecord.rip/restore-roles-after-rebuild).

## Reopen and protect the new server

* Re-test verification with a spare account and check the firewall settings.
* Confirm private channels are still private after the restore.
* Take a fresh snapshot of the rebuilt server right away.
* Open in stages: staff first, then a small group, then everyone.

No snapshot at all? Read [rebuilding without a backup](https://restorecord.rip/rebuild-without-backup). Want to know your recovery time in advance? Try a [practice rebuild](https://restorecord.rip/practice-server-rebuild). Back to [RestoreCord Rebuild](https://restorecord.rip/).

## Rebuild a deleted server

1. 1  
### Start a replacement server  
Use the account that will own it long term and turn on two-factor authentication first.
2. 2  
### Invite your RestoreCord bot  
Give it Manage Roles and Manage Channels and drag its role to the top of the list.
3. 3  
### Restore the last good snapshot  
Pick the last good snapshot, the new server as destination and the messages per channel.
4. 4  
### Pull members, then roles  
Start the member pull, wait for the first wave, then run Restore Roles.
[Open the snapshot guide on restorecord.com](https://restorecord.com/docs/guides/snapshots)

## Restore in place or start a new server?

If the original server still exists, you have a choice. Here is what each route keeps.

|                                                   | Restore in place | Rebuild in a new server |
| ------------------------------------------------- | ---------------- | ----------------------- |
| Keeps the server ID and existing invites          | —                |                         |
| Possible after the server was deleted             | —                |                         |
| Right choice when the old server can't be trusted | —                |                         |
| Snapshot restores channels, roles and messages    |                  |                         |
| Verified members can be pulled in                 |                  |                         |
| Roles handed back via Pending Role Restore        | 7 days           | 7 days                  |

## Deleted server questions

### 

### 

### 

## A deleted server is a rebuild, not a goodbye

With a RestoreCord snapshot and verified members, your community can be home again the same day.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
