Backup Pricing and Limits

RestoreCord snapshot counts, message caps per channel, Standard vs Premium attachments, and automatic-backup availability by plan.

Copy page

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
Free
Price
$0
Backups per server
1
Messages per channel
50
Attachments
None
Automatic backups
No
Plan
Premium
Price
$5/mo
Backups per server
5
Messages per channel
200
Attachments
None
Automatic backups
No
Plan
Business
Price
$10/mo
Backups per server
30
Messages per channel
500
Attachments
Standard
Automatic backups
Yes
Plan
Enterprise
Price
$20/mo
Backups per server
50
Messages per channel
2,000
Attachments
Premium
Automatic backups
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, excluded, or unreadable by the bot.

Standard vs Premium files

The attachment mode you pick when creating a backup decides which files are downloaded and stored alongside the messages.

Mode
None
Plan
All plans
Stores
Nothing — messages keep only the original Discord CDN link
Skips
Every file; the link breaks once the source message is gone
Mode
Standard (Images)
Plan
Business and Enterprise
Stores
Image attachments: PNG, JPG, GIF, WebP
Skips
Video, audio, archives, documents, and any file over 8 MB
Mode
Premium (All Files)
Plan
Enterprise only
Stores
Every attachment type, including video, audio, archives and documents
Skips
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 a separate toggle in the create dialog and is 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, emoji toggle and channel exclusions.
  • 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
How much change can you afford to lose?
What it decides
Backup frequency, and therefore whether you need scheduling (Business+)
Question
Does recovery need message history?
What it decides
Messages per channel — pick the smallest count that works
Question
Do your channels carry files that matter?
What it decides
Standard (images) vs Premium (all files)
Question
How long until a bad change is noticed?
What it decides
Backups per server, so an old known-good point still exists
Question
Do members need to come back too?
What it decides
Nothing here — that needs prior OAuth authorization and Pull Members

FAQ