Backup Pricing and Limits
RestoreCord snapshot counts, message caps per channel, Images vs All Files attachments, and automatic-backup availability by plan.
Snapshot capacity, message depth and attachment coverage all scale with your plan. Pick the smallest tier that meets your recovery goal, then verify it with a real restore.
Plan limits
| Plan | Price | Backups per server | Messages per channel | Attachments | Automatic backups |
|---|---|---|---|---|---|
| Free | €0 | 1 | 50 | None | No |
| Premium | €5/mo | 5 | 200 | None | No |
| Business | €10/mo | 30 | 500 | Images | Yes |
| Enterprise | €20/mo | 50 | 2,000 | All Files | Yes |
Yearly and lifetime pricing, trials and discounts are shown on the pricing page, which controls at checkout.
“2,000 messages per channel” is a cap, not full history. Actual capture is lower when channels are empty or unreadable by the bot.
Images vs All Files
The attachment mode you pick when creating a backup decides which files are downloaded and stored alongside the messages. Automated backup settings use different labels for the same modes, shown in brackets below.
| Mode | Plan | Stores | Skips |
|---|---|---|---|
| None | All plans | Nothing — messages keep only the original Discord CDN link | Every file; the link breaks once the source message is gone |
| Images (automated: Basic) | Business and Enterprise | Image attachments: PNG, JPG, GIF, WebP | Video, audio, archives, documents, and any file over 8 MB |
| All Files (automated: Premium) | Enterprise only | Every attachment type, including video, audio, archives and documents | Individual files over 8 MB |
The 8 MB per-file cap applies to both modes — larger attachments are skipped silently, so keep your restore test on channels that actually carry big files.
Emoji capture is the separate Emoji Backup toggle in the create dialog. It is Enterprise only and independent of the attachment mode.
Automatic backups
- Available on Business and Enterprise; schedules run hourly, daily, weekly or on selected dates.
- Scheduled runs reuse the saved message count, attachment mode and emoji toggle.
- At the plan limit, a successful scheduled backup rotates out the oldest unpinned snapshot for that server.
- Pinned snapshots are never rotated — pin known-good milestones, but leave unpinned room for the schedule.
- A schedule does not verify restores. Keep a separate restore-test calendar.
Choosing a limit
| Question | What it decides |
|---|---|
| How much change can you afford to lose? | Backup frequency, and therefore whether you need scheduling (Business+) |
| Does recovery need message history? | Messages per channel — pick the smallest count that works |
| Do your channels carry files that matter? | Images (Business) vs All Files (Enterprise) |
| How long until a bad change is noticed? | Backups per server, so an old known-good point still exists |
| Do members need to come back too? | Nothing here — that needs prior OAuth authorization and Pull Members |