> Back up channels, roles, permissions and messages with RestoreCord snapshots. See what each plan keeps, how often to back up and how to preview a restore.

Source: https://restorecord.online/discord-server-backup

# How to back up a Discord server with RestoreCord

Discord has no undo button for a deleted channel, a wiped role list or a compromised admin. A snapshot is your undo button. Here's what it captures, how many you get and how often to take one.

[Get started free](https://restorecord.com/register)[Explore snapshots](https://restorecord.com/snapshots)

Short answer

Add your server to RestoreCord, open Snapshots and create one. It saves channels, categories, roles, permissions, settings and recent messages. Preview it any time, and on Business schedule automatic backups.

## Why Discord servers need backups

Most server disasters are fast. A rogue moderator deletes twenty channels in a minute. A compromised owner account gets used to strip every role. A well-meaning admin reorganises permissions and locks half the server out. Discord keeps no history you can roll back to, so without a copy you rebuild from memory.

A RestoreCord **snapshot** is a point-in-time copy of your server's structure and recent conversation, stored outside Discord and ready to restore from your dashboard.

## What a snapshot captures

* Channels and categories, in their original order
* Roles, with their colours and permissions
* Channel permission overwrites, so private channels stay private
* Server settings
* Recent messages in each channel, up to your plan's limit

In the snapshot

* +Categories and channels
* +Roles and permission overwrites
* +Server settings
* +Messages (plan-limited per channel)
* +Attachments (Business and Enterprise)
* +Emojis (optional toggle)

Not in the snapshot

* −Members — pulled separately
* −Role assignments — restored separately
* −Voice/message activity and presence
* −Files over 8 MB
* −Channels the bot cannot read
* −Excluded channels you deselected

## Limits by plan

| Plan       | Snapshots kept | Messages per channel | Extras                                      |
| ---------- | -------------- | -------------------- | ------------------------------------------- |
| Free       | 1              | 50                   | Backup Previewer                            |
| Premium    | 5              | 200                  | Backup Previewer                            |
| Business   | 30             | 500                  | Automated backups, images and GIFs          |
| Enterprise | 50             | 2,000                | Videos, audio and other files, emoji backup |

Snapshots save the server, not the people. Members come back through a separate pull of everyone who verified with your bot. Read [how member restore works](https://restorecord.online/restore-discord-members) to cover both halves.

## How often to take one

A good routine is a scheduled snapshot for ongoing protection, plus a manual one before anything risky: a rebrand, a permissions overhaul, a big moderation action or handing a new admin the keys. Name manual snapshots after the event, like **Before the rebrand**, so you can find the right one at a glance months later.

On Business and Enterprise, automated backups run on a schedule you set, so a recent restore point exists even if nobody remembers to make one. On Free and Premium, make it a habit on the same day each week.

## Check it before you need it

The **Backup Previewer**, included on every plan, lets you browse a snapshot's channels and messages without restoring anything. Open your newest snapshot once in a while and confirm the channels you care about are there. A backup you've never looked at is a backup you're trusting blindly.

Snapshot preview — read-onlyAurora Community · March 4, 14:05

AC

Community

announcements

general

support

Voice Lounge

general

Mira14:02

Snapshot captured before the permission redesign.

Kelan14:04

Roles and overwrites look right in the preview.

Aurora Bot14:05

Backup completed — 42 channels, 18 roles, 6,300 messages.

Online — 3

Mira

Kelan

Aurora Bot

## Restoring

When something goes wrong, work through it in this order:

1. 1Pick the snapshot in the dashboard, using the Backup Previewer to confirm it's the right one
2. 2Restore it into your server, or into a fresh server if the original is gone
3. 3Check that your bot has the permissions it needs and that its role sits above the roles it recreates
4. 4Pull your verified members back in once the channels and roles are in place

What comes back depends on Discord's permissions and on what the snapshot included, so a snapshot taken on a higher plan restores more of the conversation.

Haven't connected a bot yet? Start with [setting up verification](https://restorecord.online/discord-verification-setup), or go back to the [RestoreCord home](https://restorecord.online/).

## Your first restore point

1. 1  
### Open your server in the dashboard  
Choose the server you want to protect and go to its snapshots.
2. 2  
### Create a snapshot  
Name it so you'll recognise it later, such as Before the rebrand, and let RestoreCord capture the server.
3. 3  
### Preview the contents  
Browse channels and messages in the Backup Previewer to confirm the snapshot has what you expect.
4. 4  
### Schedule the next ones  
On Business and Enterprise, set automated backups so a recent restore point always exists.
[Read the snapshots guide](https://restorecord.com/docs/guides/snapshots)

## Discord backup questions

### 

### 

### 

## Take your first snapshot today

The Free plan includes a snapshot with up to 50 messages per channel. It takes a minute to create one.

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