Snapshots
A snapshot is a full copy of a world's folder at one moment. Restore it later and the world is put back exactly as it was, down to every block and chest.
Taking a snapshot
/bp snapshot create castle
Leave off the world name to snapshot the world you are standing in:
/bp snapshot create
The copy runs in the background. While it runs:
- If the world is loaded, everyone in it is moved to the fallback world, and the world is saved and unloaded so the copy is consistent.
- The world folder is copied into its own
snapshots/folder. Older snapshots are not copied into the new one. - If the world is now over the snapshot limit, the oldest snapshots are deleted (see Pruning).
- The world is loaded again if it was loaded before.
When it finishes you see the new snapshot ID:
Snapshot 'snap-2026-09-23-041530' created.
IDs are snap- followed by the date and time in UTC, in the format YYYY-MM-DD-HHMMSS.
A locked world is reloaded as open after a snapshot. Run /bp lock again if it needs protecting.
Listing snapshots
/bp snapshot list castle
Snapshots are listed newest first, with their creation time in UTC. Automatic backups are labelled:
Snapshots for 'castle':
pre-restore-2026-09-23-052210 | 2026-09-23 05:22:10 UTC (auto-backup before restore of snap-2026-09-23-041530)
snap-2026-09-23-041530 | 2026-09-23 04:15:30 UTC
As with create, you can leave off the world name to list snapshots for the world you are standing in.
Restoring a snapshot
/bp snapshot restore castle snap-2026-09-23-041530
Tab completion suggests the snapshot IDs for the world you typed. A restore:
- Moves everyone out of the world and unloads it.
- Takes an automatic backup of the world as it is right now, named
pre-restore-<timestamp>, ifauto-backup-before-restoreis on (the default). - Deletes the world's current files, keeping the
snapshots/folder. - Copies the snapshot into place.
- Loads the world again if it was loaded before. A closed world stays closed.
Undoing a restore
Because of the automatic backup, a restore is never a one-way door. If you restored the wrong snapshot, list the snapshots and restore the pre-restore-... entry that was just created.
With auto-backup-before-restore: false, whatever was in the world since the snapshot was taken is gone for good when you restore. Leave it on unless disk space is tight.
Deleting a snapshot
/bp snapshot delete castle snap-2026-09-23-041530
Removes the snapshot's files and its entry in the world's record. The world itself is not touched and stays loaded.
Pruning
max-per-world (default 25) limits how many snapshots each world keeps. Each time a new snapshot is taken, Blueprint deletes the oldest ones until there is room for it, so a world never holds more than the limit straight after /bp snapshot create.
- Pruning deletes the oldest entries whatever they are, including
pre-restore-backups. - Pruning only happens when a snapshot is created. Automatic backups made during a restore can take a world over the limit until the next snapshot.
- Set
max-per-world: 0to keep every snapshot forever.
Where snapshots are stored
Snapshots live inside the world they belong to:
blueprint/
└── castle/
├── blueprint.yml ← Blueprint's record, including the snapshot list
├── region/
├── ...
└── snapshots/
├── snap-2026-09-23-041530/
└── pre-restore-2026-09-23-052210/
This means:
- Deleting a world deletes all of its snapshots. Copy the folder somewhere else first if you want to keep them.
- Renaming a world keeps its snapshots. They move with the folder.
- Snapshots use real disk space. Each one is a full copy of the world, so a 200 MB world with 25 snapshots uses around 5 GB.
- A clone carries a copy of the source's
snapshots/folder, but the clone does not list or use those files. Deletesnapshots/from the clone's folder to reclaim the space.
Turning snapshots off
Set snapshots.enabled: false to stop anyone creating new snapshots. Listing, restoring, and deleting existing snapshots still work.