Getting Started with Discord Backups
Create your first Discord server backup with RestoreCord, preview what it captured, and restore it into a spare server to prove it works before you need it.
Attach a bot, click Create Backup, then prove it restores.
Before you start
- A custom bot installed in the server — keep its token out of chat (secure it)
- The server added in the dashboard, with the bot able to see the channels you want captured
- An empty Discord server to test restores into
Create the backup
On the Servers tab, each server card shows Manage, Pull Members and Create Backup. Create Backup opens the Create New Backup dialog: backup name, description, messages per channel, attachment mode and emoji backup.
The dialog pre-fills a name; rename it after what it protects, like before-permission-redesign. Then set the scope:
| Option | Pick | Why |
|---|---|---|
| Messages per channel | The smallest count that meets your goal | Higher counts slow both capture and restore |
| Attachment mode | None, Images (Business+) or All Files (Enterprise) | See pricing and limits |
| Emoji Backup | On if your custom emojis matter (Enterprise) | Emojis are only captured when this is on |
To skip specific channels, create the backup through the Snapshots API with excludedChannels; the dialog always captures every channel the bot can read.
Watch the job until it finishes. If it fails on permissions or rate limits, fix the cause — do not assume a recovery point exists.
Preview it
The previewer opens the backup as a read-only Discord client, so you can see what was really captured.
The preview's top bar reads Preview Mode with the backup name and capture date, and shows the server's channel list and the messages in the selected channel as they were captured. Click the channel name or the members icon at the top of the chat to open the member list.
- Check channel order, roles and a few real messages, links and attachments.
- A padlock means the bot could not read that channel, so its messages are missing.
- Pin known-good backups so scheduled rotation cannot delete them.
Test the restore
| Step | Do this |
|---|---|
| Prepare | Install the same bot in an empty server with Administrator on its own role, and drag that role above the roles it must create |
| Restore | Pick the backup, the message count, and whether to clear the destination |
| Measure | Time it and note what was skipped — that is your real recovery time |
| Verify | Channel order, roles, permission overwrites, and that private channels stayed private |
Restored messages are re-posted, not reinstated — Discord cannot recreate a deleted message with its original author and timestamp.
Troubleshooting
| Symptom | Check first |
|---|---|
| Backup button is greyed out | No custom bot is attached to that server |
| Channel's messages missing from the backup | The bot could not read it — the previewer shows a padlock |
| Administrator Permission Required when restoring | The bot's role lacks Administrator — click Open Admin Invite, authorize, then Try Restore Again |
| Restore fails on roles or channels | Bot role position — it must sit above the roles it creates |
| Restore stalls | Discord rate limits — let the task finish instead of starting a second one |
| Attachments missing after restore | Attachment mode was None, the file was over 8 MB, or the source file was already deleted |
| Roles not applied to members | Members were not pulled back before the role restore ran |