Overview
Snapshots let you save named checkpoints of your sandbox’s entire state. You can then rollback or branch from any snapshot.Snapshots are different from pause/resume. Pause saves temporary state; snapshots create permanent, named checkpoints you can return to anytime.
Creating Snapshots
Listing Snapshots
Rolling Back
Restore sandbox to a previous snapshot:Branching
Create a new sandbox from a snapshot:- Trying different approaches
- A/B testing changes
- Creating isolated environments
CLI Usage
Use Cases
Safe Experimentation
Checkpoint before risky changes. Easy rollback if things go wrong.
A/B Testing
Branch to try different approaches. Compare results.
Environment Cloning
Create identical environments for different purposes.
Disaster Recovery
Always have a known-good state to return to.
Snapshot Storage
Snapshots are stored on our NFS infrastructure:| Tier | Snapshots/Sandbox | Retention |
|---|---|---|
| Free | 3 | 7 days |
| Pro | 10 | 30 days |
| Team | 50 | 90 days |
| Enterprise | Unlimited | Unlimited |
Best Practices
Snapshot before major changes
Snapshot before major changes
Always create a snapshot before refactoring, upgrading, or risky operations.
Use descriptive names
Use descriptive names
Name snapshots clearly: “before-db-migration”, “v2-working”, etc.
Clean up old snapshots
Clean up old snapshots
Delete snapshots you no longer need to save storage.
Branch for experiments
Branch for experiments
Don’t modify production sandbox. Branch for experiments.