Back up your game and recover from mistakes
Four layers of safety, from a one-click file backup to checkpoints and Git, and which to use when.
Updated November 8, 2026
Bricklayer is designed so mistakes are easy to undo. A real backup on top of that means you never have to worry.
Layer 1: Save a copy of the place
The simplest backup there is, and the one to make before you open an existing game in Bricklayer for the first time.
- In Roblox Studio, choose File → Save to File As.
- Save the
.rbxlfile in a backups folder, with the date in the name, likeMyObby-2026-11-08.rbxl.
To restore, open that file in Studio.
Layer 2: Checkpoints
Run Bricklayer: Save a Checkpoint from the Command Palette before a risky change. Checkpoints give you a known-good point to return to without leaving the editor.
Layer 3: Undo and reject
- Every AI file change waits for approval, so the cheapest undo is Reject.
- Studio changes are undoable with Ctrl+Z.
- Approved file changes can be reverted in Bricklayer, or you can ask the AI to undo its last change.
See Review, approve, and undo AI changes.
Layer 4: Git (optional)
Your project is a normal folder, so Git works on it. If you already know Git, commit after every working feature and you can go back to any point. You do not need Git to use Bricklayer. Using your own tools.
Published games
Roblox keeps a version history for places you publish, which you can manage from the Creator Dashboard. It only covers what you published, so keep local backups too.
A rhythm that never loses work: playtest, it works, save a checkpoint. Once a day, or before anything big, also Save to File.
Did this answer your question?
Related articles
Still need help? or start a thread in the community forum.