Skip to main content
Server Backup saves your Discord server itself into an encrypted snapshot: channels, roles, permissions, server settings, emojis, stickers, bans, members’ nicknames and roles, and the recent messages of every channel. Restore it into this server after a mistake, or into another server you manage.
Available on every plan, including Starter. Your plan decides how many backups you keep, how much of the server each one holds, and which of the advanced tools — attachments, change tracking, Time Machine, import — you can use. See Limits by plan.
This is not Vetox Backup. Vetox Backup saves the settings Vetox holds for your server — your Auto-Mod rules, Welcomer, Tickets and the rest. Server Backup saves the Discord server — the channels, roles and messages themselves. They are separate pages, separate snapshots and separate plans. Most servers want both.
Open it at Backup → Server Backup in your server’s dashboard, or run /backup in Discord.

What a backup contains

What is captured depends on the options you choose and your plan. Everything below is optional except the first row.
Private threads are never captured. Their membership cannot be reproduced, so restoring one would create a private thread with the wrong people in it. Public threads and forum posts are captured normally.

What is never captured

These belong to Discord or to other apps, and Vetox will not recreate them. Restoring a backup does not bring them back:Invites · the audit log · other apps’ integrations and webhooks · scheduled events · the soundboard · onboarding prompts · Discord AutoMod rules · boosts
Roles managed by another app or by an integration — a bot’s own role, a Twitch subscriber role, the Nitro Booster role — are recorded in the snapshot but are never created or edited. Discord owns them.

Creating a backup

1

Open the Backups tab and press Create backup

It is the primary action at the top right of the list.
2

Name it (optional)

A name makes it findable later. Without one the backup shows as Untitled with its ID.
3

Choose messages per channel

How many recent messages to keep from every channel. More messages mean a larger backup and a slower restore. Starter stores none.
4

Choose what else to include

Threads, Member data, Bans, Attachments, Emojis and Stickers. Options above your plan are shown but disabled.
5

Press Create backup

The job runs in the background. You can leave the page — progress is waiting when you come back.
A server can create one manual backup every 10 minutes, and can only run one backup or restore job at a time. Both are per server, not per person. While the cooldown runs, the Create backup button’s tooltip tells you when the next one is possible.

Attachments

With Attachments on, Vetox downloads each captured message’s files from Discord and stores the bytes with the backup, so a restore re-posts the real files. With it off — and always on Starter — only the Discord link is kept. Those links expire, so an old backup restores the message text with the file names, not the files.
Attachment storage is capped per backup and per file (see Limits by plan). Once a backup passes its cap the capture continues and the remaining files are kept as links, with the warning “Some attachments were kept as links because this backup reached your plan’s storage limit.”

If the backup is too large for your plan

A capture is never abandoned for being big. When it reaches your plan’s size ceiling, Vetox stops adding to the section it is on, records that section under Cut short by your plan on the backup, and finishes. You get a usable backup that is missing part of its largest section — usually messages.

The Backups tab

Every snapshot of this server, newest first, with a used of max count against your plan. Each row’s menu offers Restore…, Details and Delete. Clicking the row opens the Snapshot Viewer. A Servers / Channels filter switches between whole-server snapshots and channel backups.
Safety copies are the automatic pre-restore snapshots described below. They do not count against your backup limit, and they disappear on their own after 7 days.

When a backup is locked

If your plan changes and you now hold more backups than it allows, nothing is deleted. The extras are locked: they stay visible with an amber lock, and the tooltip reads “This backup is beyond your current plan’s limit. Upgrade to restore it again.” Delete a newer backup or upgrade, and they unlock.

Restoring

Loading a backup replaces this server’s channels and roles with the ones in the backup. Members are never kicked, but anything created since the backup was taken will be gone.
1

Pick a backup and choose Restore…

From the row menu, the Snapshot Viewer, or My Backups for a backup from another server.
2

Read the plan

Vetox reads your live server and tells you exactly how many channels and roles will be deleted and how many will be created before anything happens. If any roles sit above Vetox’s own role, the plan says so: those roles can be neither deleted nor recreated, so move Vetox’s role to the top of the role list first, or continue without them. If the backup holds announcement or stage channels and this server is not a Community server, the plan says how many are being left out.
3

Choose a preset, then adjust

Three presets set every switch at once. Change any individual switch afterwards.
4

Type the server name

The confirmation field must match your server’s name exactly. This is the last point at which nothing has been changed.
5

Watch the progress card

Phase, count, elapsed time and any warnings, with a Cancel button throughout.

Presets

Additive is the safe one. It creates the backup’s roles and channels alongside what you already have and deletes nothing. Use it to pull a category back from an old snapshot without touching the rest of the server.

How often you can restore

Restores and reverts are rationed daily: 10 per server and 20 per person across all of your servers. A restore, a channel load and a revert each count; resuming a failed restore does not. Both budgets reset 24 hours after the first counted action, and they are separate from the 10-minute creation cooldown.

What happens to your members

A restore never kicks, bans or removes anybody. Members stay exactly where they are.With Member roles and nicknames on, members who are still in the server get back the roles and nickname they had when the backup was taken. Members who have left are skipped. With it off, members keep whatever they have now.

The safety copy

Before a restore deletes anything, Vetox takes a snapshot of the server as it is right now — channels, roles, settings, emojis and stickers, plus threads on Basic and above. No messages, members or bans. Enough to undo the restore, small enough to finish before it starts.
If the safety copy fails, the restore never starts. Nothing is deleted. Safety copies are kept for 7 days, do not count against your backup limit, and appear in the list with the type Safety.

If a restore stops partway

A restore records a checkpoint as it goes. If it fails — Vetox restarted, the connection dropped, Discord refused something — the progress card offers Resume, and the job picks up at the step it stopped on rather than starting over.
Resuming never duplicates. Anything already recreated is recognised and skipped, and messages continue from the exact point they stopped.

Permissions

Restoring replaces channels and roles, so it is deliberately narrower than viewing. One setting, Settings → Permissions, decides who may do what — the same three levels Xenon users know: Only the server owner can change the level — a setting that the people it restricts could rewrite would gate nothing. The /backup commands in Discord follow the same level, and under the owner-only level the dashboard greys out Create backup, Back up a channel and Import for everyone but the owner. Viewing backups follows your ordinary dashboard access — the Backup section in Access Control. A backup created on another server carries one more rule: only the person who created it can restore it, wherever it goes. See My Backups.

What Vetox needs to restore

Give Vetox Administrator before a restore, and make sure its role sits above every role it has to recreate.Without Administrator, Vetox needs all ten of Manage Server, Manage Channels, Manage Roles, Manage Webhooks, Ban Members, Manage Nicknames, Manage Expressions, Manage Messages, Read Message History and View Channel.
Discord will not let a bot grant a permission it does not hold itself. Where that happens the restore does not fail — it creates the role without those permissions and warns “Some permissions could not be granted because Vetox does not have them itself.” Roles sitting above Vetox in the list are reported and left untouched.

Announcement and stage channels

Discord only allows announcement and stage channels in a Community server. If yours is not one, Vetox leaves those channels out of the restore rather than trying and failing on each — the plan tells you how many before you confirm, and the finished job repeats it as a warning.
Turn Community on under Server Settings → Enable Community in Discord, then restore again, and those channels are created with everything else. Nothing else about the restore changes either way.
A backup taken before September 2026 does not record how many of its channels are announcement or stage ones, so its plan cannot subtract them in advance. The restore still leaves them out and still warns — you simply see the count afterwards rather than before. A new backup of the same server carries the count.

Discord’s channel and role limits

A server holds at most 250 roles and 500 channels, and Discord lets a bot create at most 250 roles or 500 channels on one server within 48 hours. A large restore — or several restores in a row — can hit either.This limit is Discord’s, not Vetox’s. Cancelling the restore, deleting the objects again, or removing and re-inviting Vetox does not lift it. If a restore hits it, the job stops with “Discord allows a bot to create only 250 roles or 500 channels…”, keeps its checkpoint, and Vetox records when Discord said the limit lifts.
While the limit is active the Server Backup page shows an amber Discord’s creation limit is active band with the time it lifts, the failed job’s card says “Discord lifts the limit …”, and /backup status in Discord reports the same countdown. You then have two choices: wait and press Resume once the window reopens, or restore again with Roles, Delete existing roles, Channels and Delete existing channels turned off (in Discord: options:!delete-roles !roles) so that nothing has to be created.

Schedule

Schedule turns on automatic backups. Automatic backups rotate: when a new one lands, the oldest automatic backups beyond the number your plan keeps are deleted. Manual backups are never rotated away.
The schedule shows Next run and Last run so you can confirm it is working.

Settings

Delete all backups cannot be undone. It asks you to type the server name first, and it removes stored attachments along with the snapshots.

Changes

Change tracking and revert require Basic or above. Turn it on under Settings → Track server changes.
With tracking on, Vetox records every structural change to the server as it happens — channels, threads, roles, emojis, stickers and server settings, created, edited or deleted — together with the Discord user who made it, read from your audit log. The Changes tab lists them newest first, filtered by type, by who made the change, and by date. View changes shows a before-and-after diff of exactly which fields moved.
Change records never contain message content. They hold server structure and the actor’s user ID and name. Nothing else.

Reverting one change

Revert undoes a single change without restoring a whole backup: A revert runs as a job like a restore — progress, warnings, cancel — and counts as a destructive action under the permission level, because it changes your server.
If something newer has changed the same object since, Vetox refuses and tells you: “Something newer has changed the same thing since. Confirm to revert anyway.” Choosing Revert anyway also undoes that newer change.
Change tracking has an hourly ceiling per server. A storm of changes — a mass rename, a raid — records “Too many changes at once” and stops recording until the hour turns. Nothing else is affected, and your scheduled backups still cover the period.

Time Machine

Time Machine requires Max or above.
Time Machine rebuilds how your server was set up at any moment you pick, by taking the newest backup from before that moment and replaying every tracked change up to it.
1

Pick a moment

Anywhere inside your change history window. The page shows the earliest instant you can reach.
2

Preview

The reconstructed channels and roles, plus a comparison against your server as it is right now.
3

Create snapshot

Turns the reconstruction into a real backup you can browse, export and restore like any other.
Time Machine starts at your first backup. Ask for a moment before it and Vetox answers “There is no backup from before that moment, so it cannot be reconstructed.” It needs a backup to build on — the change log alone is not enough.
The preview compares channels, roles, emojis and server settings only. Threads and stickers are shown in the reconstruction but are never counted as added, removed or changed, because the live server reading behind the comparison caps threads at the newest 25 and carries no stickers at all — so there is nothing honest to report for those two. Settings compare on the server’s name and icon.

Gaps

A gap is something the change log did not record — a change lost to the hourly ceiling, or one that happened while tracking was off. Vetox fills it from the closest backup it has and tells you how many gaps a reconstruction contains. A snapshot created from that point carries the same warning.
Gaps are a fact of the change log’s coverage, not a fault. The way to close one going forward is a fresh backup.

Snapshot Viewer

Clicking a backup opens it. Nothing here changes your server — it is a reader. Stored attachments are downloadable from the message that carried them. Files are always served as downloads, never opened in the page.
A backup can only be browsed once its capture has finished. A backup still running, or one that failed before its snapshot was written, says so instead.

Export and import

Export

Available on every plan. Export downloads the backup as a .json file in Discord’s own server format: the server object, roles, channels with their permission overwrites, emojis and stickers.
Messages, members and bans are not in an export. They are not part of Discord’s server format, and they are the privacy-sensitive half of a backup. To move those, restore the backup rather than exporting it.

Import

Importing a backup file requires Basic or above. Applying a Discord server template is free on every plan, and so is Export.
Import turns a Discord-format server file into a backup you can preview and restore. Files are limited to 5 MB. The Import dialog also accepts a Discord server template — paste the link Discord gives under Server Settings → Server Template (https://discord.new/…) or the template’s code. Vetox fetches the template and turns its channels, roles and settings into a backup, which you then restore into this server like any other. That is how you load a template into an existing server, something Discord itself only offers for new ones.
The file must genuinely follow Discord’s server format. A file that does not is rejected outright, naming the first field that failed — Vetox never half-applies one. This applies to files produced by other tools and to hand-written or AI-generated ones.

Channel backups

Channel backups require Basic or above.
A channel backup stores the most recent messages of one channel or thread, with their attachments, so you can post them into any channel of any server you manage.
1

Back up a channel

From the Backups tab, or with /chatlog create in Discord. Pick the channel and how many messages to keep. Text, announcement, forum and thread channels are supported.
2

Optionally start further back

Start before this message takes a message ID and stores the messages before it — the way to continue where an earlier channel backup stopped.
3

Restore into a channel

Pick the destination. Messages are posted oldest first, with their pins.
A channel restore deletes nothing. The stored messages are added to whatever is already in the channel. Large channel backups take a while to post — the progress card shows the count.A message that has nothing Discord can re-send — no text, no files and no embeds, such as a system notice or a sticker-only post — is skipped, and the job’s warnings say how many were: “Some messages had nothing to re-post (no text, files or embeds) and were skipped.”
Channel backups have their own limits and their own count, separate from whole-server backups, and they appear under the Channels filter.
In Discord they have their own command, /chatlog, with six subcommands — create, list, info, load, delete and purge. /chatlog purge removes only chatlogs; your server backups are untouched.

Limits by plan

Every number here is enforced by Vetox. A dash means the feature is not available on that plan.
Starter keeps the parts that matter most: you can back up your channels, roles and settings, restore them, browse a snapshot and export it. What premium adds is depth — messages, members, bans, attachments, history — and frequency.

When your plan changes

The rule is lock, do not delete. Nothing is ever removed because a subscription ended.
Your schedule and tracking settings are clamped down on a downgrade, and are not restored when you upgrade again. After a downgrade the automatic interval, the number kept, messages per channel and change tracking are reduced to the lower plan’s values — and they stay there. Set them again after upgrading.Your backups are unaffected: over-limit ones lock, and unlock the moment you are back within the limit.

Privacy and retention

Backups are your server’s data, held by Vetox on the server owner’s behalf. Snapshots and stored files are encrypted at rest with AES-256-GCM. Each backup has its own key, protected by master keys Vetox holds. They live on infrastructure Vetox operates and are never uploaded to a third-party storage service. A backup is sealed when created and never edited afterwards.
Vetox staff do not open the contents of backups. The one exception is a support request from the server owner: with the owner’s consent, staff work through the owner’s own dashboard views, and every such access is recorded in the audit log.
If you ask Vetox to delete your personal data, you are removed as the creator of any backups and as the recorded actor of any tracked change. Because a backup is never edited after it is created, messages you wrote that an administrator captured in their server’s backup stay inside it until that backup is deleted — the same as they would in any copy of the server’s data held by its owner. Ask that server’s administrators if you need a specific backup removed.
Full detail is in the Privacy Policy.

Troubleshooting

A server can create one manual backup every 10 minutes. Automatic backups are unaffected. Wait, or use the backup you just made.
This server or your account has spent its daily allowance of 10 per server / 20 per person. Try again tomorrow.
One backup or restore at a time, per server. Wait for the running job, or cancel it from its progress card.
Delete a backup you no longer need, or upgrade. Safety copies do not count towards the limit.
You hold more backups than your current plan allows, so the oldest extras are locked. Delete a newer backup or upgrade to unlock them.
The server’s permission level leaves this action to the owner. Either the owner performs it, or the owner changes the level under Settings → Permissions.
The permission level is Only the owner can use the relevant commands. Ask the owner to take the backup, or to relax the level.
The confirmation field must match the server’s current name exactly, including capitals and emoji. Copy it from the dialog’s prompt.
Give Vetox Administrator, or all ten permissions listed under What Vetox needs to restore, and drag its role above the roles being restored.
Those roles were reported and left untouched — Discord does not let a bot edit a role above its own. Move Vetox’s role higher and restore again.
Discord only allows those in a Community server. Turn Community on under Server Settings and restore again to include them — see Announcement and stage channels. Everything else in the backup restores either way.
You have reached Discord’s creation allowance for this server. Deleting things, cancelling, or re-inviting Vetox does not refund it. The page and /backup status show when it lifts; wait for that and press Resume, or restore again with roles and channels turned off. See Discord’s channel and role limits.
Emoji and sticker slots depend on your server’s boost level. The rest of the restore completed; the extras were skipped.
Capture fewer messages per channel, turn off attachments, or upgrade for a larger ceiling.
Pick a longer interval, or upgrade. The refusal names your plan’s minimum.
The stored file is damaged or missing and cannot be restored. The record is kept so you can see it happened. Create a fresh backup, and contact support if it recurs.
The bot was restarting or offline. Nothing further was changed. Try again in a moment; a restore that had already started offers Resume.
The feature is paused for maintenance. Your backups are untouched and nothing has been deleted.

/backup commands

Every subcommand, option and the load options grammar.

My Backups

Your backups across every server, and restoring into another one.

Vetox Backup

The separate snapshot of Vetox’s own configuration.

Access Control

Grant the Backup section to someone other than the owner.

Feature limits

Every tier limit in one table.

Permissions

Role hierarchy and what Vetox needs.