Snapshots
Create, preview, restore, pin and schedule RestoreCord snapshots: point-in-time backups of a Discord server's channels, roles, settings and messages.
Overview
Snapshots are point-in-time backups of a Discord server's structure. They are designed for recovery after accidental deletion, raids, destructive permission changes, or planned server rebuilds.
Snapshots and Pull Members solve different recovery problems. Snapshots restore structure; Pull Members restores verified people.
What Snapshots Include
- Channels and channel settings.
- Roles and role permissions.
- Server settings.
- Member role relationships for users visible in the snapshot.
- Emojis, on Enterprise, when emoji backup is turned on.
- Messages up to the configured per-channel message count.
Create a Snapshot
Start snapshot creation
Click Create Backup on the server card. RestoreCord will validate the server's linked bot before creating the snapshot.
Name the snapshot
Use a name that explains why it was created, such as Before role cleanup or Post raid recovery. Optionally add a short description.
Choose backup options
Set Messages per Channel, Attachment Mode (None, Images on Business+, All Files on Enterprise) and Emoji Backup (Enterprise) according to your plan and recovery needs.
Create and wait
Click Create. The backup appears on the Backups page with its progress; wait for it to finish before relying on it.
Manage Snapshots
The Backups page lets you search, group, sort, pin, preview, restore, edit, or delete snapshots.
| Control | Purpose |
|---|---|
| Search | Find snapshots by name, description, server, or snapshot ID. |
| Group by | Group snapshots by time, server, or no grouping. |
| Sort by | Sort by date, name, or size. |
| Pinned only | Focus on pinned snapshots for important recovery points. |
| Rename or edit description | Keep snapshot purpose clear after creation. |
| Preview | Inspect snapshots before restoring. |
| Delete | Remove snapshots you no longer need after the confirmation timer. |
Restore a Snapshot
Open snapshot details
Select a snapshot on the Backups page. Current snapshots show Preview and Restore when you have permission to manage them.
Choose a bot
Pick a valid bot. Shared bots can be available when the sub-user has snapshot permissions for a server.
Choose a destination server
Select a Discord server where the bot is installed. The bot's role needs Administrator — use Invite Bot to add it with that permission, then refresh the server list.
If the bot's role lacks Administrator, the restore stops with Administrator Permission Required: click Open Admin Invite, approve Administrator for the preselected server, then click Try Restore Again.
Set restore options
Choose how many messages per channel to restore, up to your plan limit. Decide whether to clear the destination server before restoring.
Confirm restore
Review the confirmation summary and click Restore Backup. The bot posts live progress in a #restore-progress channel; keep the destination server stable while it runs.
Clearing the destination server before restore can delete existing structure. Use a test server first if you are unsure how the snapshot will apply.
Restore order
A restore rebuilds the server in this order, so the server is usable well before the message history is back:
- Structure. Server settings, roles, categories and channels, then active threads and forum posts, then bans, AutoMod rules and invite links for the bots that were in the server.
- Important history. Messages in open tickets, then in rules, announcement and read-only channels.
- Everything else. Messages in closed tickets, then the other channels in sidebar order, then archived threads. Archived threads are recreated just before their messages are posted and archived again afterwards. Emojis and stickers are added in the background while messages are posted.
The progress message shows the restore's Job ID. Include it when you contact support about a restore.
TicketCord
If your RestoreCord account is connected to TicketCord, the restore also prepares your tickets:
- Open ticket channels get their messages first.
- Copies of TicketCord ticket panels and ticket cards are skipped, because their buttons could never work in the new server. TicketCord posts fresh ones.
- The TicketCord bot's invite link comes first in the list of bot invite links.
Once the structure is restored, a Reconnect TicketCord banner appears on the Backups page with the restore's job ID. Click Open TicketCord to bring your ticket settings, panels and open tickets into the restored server. While messages are still being posted, the banner says so; TicketCord reconnects each ticket once its history is complete.
Automation
Automated snapshots are configured in the server's Extras tab.
Go to Extras › Automated Backups
| Automation setting | Use it for |
|---|---|
| Frequency | Run snapshots hourly, daily, weekly, or on selected dates. |
| Attachment mode | Control how attachment data is handled by the scheduled snapshot. |
| Emoji backup | Include custom server emojis. Enterprise only. |
| Message count | Controls messages per channel within the plan limit. |
| Custom title and description | Make automated snapshots readable on the Backups page. |
Automated snapshots need Business or higher. Manual snapshots are available with per-plan, per-server snapshot limits.
Limits
| Plan | Snapshot limit | Message restore limit per channel |
|---|---|---|
| Free | 1 snapshot per server | 50 messages |
| Premium | 5 snapshots per server | 200 messages |
| Business | 30 snapshots per server | 500 messages |
| Enterprise | 50 snapshots per server | 2000 messages |
Practical Constraints
- The bot must be installed in the source server when creating a snapshot and in the destination server when restoring. To restore, the bot's own role also needs Administrator.
- Discord rate limits can make large restores take time.
- Some older snapshots need a one-time upgrade before you can preview or restore them.
- At the limit, a successful automated backup rotates out the oldest unpinned snapshot for that server. Pinned snapshots, and older snapshots that still need their one-time upgrade, are never auto-deleted.
- The snapshot reflects the server at creation time, not later changes.