Creating backups
/backup create shows a live progress display, then the result with the backup ID, what was backed up and how many of the server's manual backups are stored. Nothing to write down: the backup is encrypted with the bot's key, and only the server owner can load it - onto this server, or with a transfer code onto another one (6a).
What's backed up#
| Area | Details |
|---|---|
| Server settings | Name, icon, banner, invite background (as images), verification level, content filter, default notifications, AFK channel and timeout, system channel and its flags, rules/updates/safety channels, Community, boost progress bar, description, locale |
| Roles | Name, permissions, colors (incl. gradients), hoist, mentionable, icon (image or emoji), order; bot and booster roles are recorded but not recreated |
| Categories & channels | Text, announcement, voice, stage, forum, media: name, position, topic, NSFW, slowmode, bitrate, user limit, region, forum tags, default reaction, sort order, layout |
| Permissions | All channel permissions for roles and individual members |
| Emojis, stickers, sounds | Custom emojis (with role restrictions), stickers, soundboard sounds - including their files |
| AutoMod | All rules (needs "Manage Server") |
| Welcome screen, onboarding | On Community servers: welcome screen, onboarding questions, answers and default channels |
| Members | Nicknames and role assignments of all members that have any |
| Bans | All bans with reason (needs "Ban Members") |
| Threads & forum posts | All active ones and the 50 most recently archived per channel |
| Messages | The newest 100 per channel and thread: text, attachments, bot embeds, replies, pins, forwards, polls, stickers |
Limits#
- Attachments up to 8 MB each, 250 MB per backup in total. Emojis, stickers and sounds come first, so the limit never pushes them out. Each sticker image used in messages is stored only once.
- A server can create a manual backup at most every 5 minutes, and never two at once. Failed attempts don't count.
- Each server keeps at most 5 manual backups, shared by all its admins. A new one replaces the oldest. Automatic backups have their own slots (4a) - creating manual ones never pushes them out.
- Backups are deleted 7 days after the bot leaves the server (kicked, or the server was deleted). Re-inviting the bot within these 7 days keeps them. The delay is deliberate: an attacker who kicks the bot can't destroy the backups with it, and the owner has a week to invite the bot back - or to load a backup onto a new server.
- The result lists what couldn't be backed up, e.g. channels without read access, bans without permission, files over the limits.
Not backed up#
Server Guide of the onboarding (no public API), the server's vanity URL, invites (codes can't be recreated), which bots/integrations were installed (only their roles - see missing bots in 6), reactions, message components (buttons), voice channel status, scheduled events, webhooks. Minor settings like the channels' default thread archive duration or voice video quality are deliberately left out.
Ventura