Server Backup: What It Actually Saves, and What It Does Not
A backup restores your server's structure, not its content. What that means in practice and how a restore runs.

The important part first, because it is the most common misconception: a server backup does not save messages.
What it saves is your server's structure. Categories, channels with their settings and permissions, roles with colors, permissions and order, the @everyone permissions, server settings. What is written in the channels is not included, and that is not on us: Discord does not return deleted messages to anybody.
Once that has sunk in, it becomes clear what a backup is for and what it is not.
What it is good for
After a nuke. Somebody deleted channels and roles. The structure comes back, fully, including permissions and role order. The conversations are gone, but the server is usable again instead of being rebuilt over weeks.
Before a big restructure. You want to rearrange the channel structure or redo permissions. Take a backup first and the way back is guaranteed.
As a template. A finished server can be transferred to a new one. That is what the marketplace is for, more on that below.
What it is not good for
No substitute for moderation, no archive, no backup of messages, attachments or ticket histories. Ticket histories are archived separately and permanently on their own dashboard, independent of the server backup.
How a restore runs
A restore runs in several phases and in a specific order, because Discord forces it. Roles have to exist before you can set channel permissions referring to those roles. Categories have to exist before the channels inside them.
What comes back along the way and is easy to forget: role colors, role positions, role icons, the @everyone permissions and the properties of forum and media channels.
A restore survives a bot restart. If the process dies mid-restore, the interrupted run is detected and started again, instead of leaving the server half rebuilt. The same holds for applying an AI Server Builder result and for /moderation roleall.
The marketplace
Backups can be published as public templates, with a name, description and category. A preview of the channels and roles is generated automatically so others can see what they are getting before importing.
Who this is for: anyone building a new server who does not want to start from nothing will find ready-made structures there. And anyone who has built a structure that works can pass it on.
What to do right now
If your server has existed for more than a few weeks and you have no backup, that is the one point from this article that actually counts. Creating a backup takes under a minute, and the moment you need it is by definition the moment you can no longer create it.
Sensible afterwards: take a fresh one before every larger restructure. A backup from last year restores last year's server.
Details on creating, restoring and the marketplace are in the Server Backup documentation.
More articles
How to Add a Bot to Your Discord Server, and Which Permissions It Really Needs
Adding a bot takes a minute. Giving it the right permissions is what keeps your server safe. A step by step guide, and how to spot a bot you should not trust.
GuidesSetting Up Discord Verification: Which Method Stops Which Problem
Button, math task, Discord login or external link: each kind of verification keeps something different out. How to choose the right one, and the two mistakes that break almost every setup.
GuidesAnti Nuke: What Happens When an Admin Account Gets Taken Over
A raid comes from outside, a nuke from inside. How the protection layer works, why it scores threats instead of using fixed rules, and what it cannot do.