Project backups
Point-in-time snapshots of every project, stored locally. Auto-backups happen during active editing; manual backups can be triggered any time. Restore overwrites the live state — and takes a before-restore backup automatically so you can roll back if needed.
Where to find it
Top bar → History icon (next to Save).
How it works
| Storage | IndexedDB table projectBackups. Each backup is a full project snapshot — includes layer images, frame metadata, slices, references, etc. |
| Limit per project | 8 by default (getQuota('maxBackupsPerProject')). Older backups are pruned automatically. |
| Auto-backup interval | Every 10 minutes during active editing (configurable in Preferences). Throttled via localStorage, so closing the tab doesn't reset the timer. |
| Manual backups | Any time. Optionally label them ("before-refactor", "v1-final", etc.). |
| Restore safety | The current state is auto-backed up as "Auto: before restore" before any restore replaces it. |
Workflow
Manual backup before a risky change
- About to do a big refactor? History → Create backup with label "before-refactor".
- Make your change.
- If it goes wrong: History → "before-refactor" → Restore.
- The current (broken) state is auto-saved as "Auto: before restore" first, so you can undo the restore if needed.
Auto-backup safety net
Just keep editing. After 10 minutes of activity the editor takes a snapshot. After 8 backups, the oldest ones rotate out. You don't have to think about it.
Configuration
The auto-backup interval is in Preferences:
- 0 minutes — auto-backups disabled (manual only).
- 1–60 minutes — interval between auto-backups for any single project.
The 8-backup-per-project limit is currently a plan quota. On the free tier this is generous for typical projects; the limit can be raised by editing the project's quota config.
Tips
- Don't rely on backups as your only safety net —
.mstackexports are the canonical "I want to keep this forever" format. - Backups are browser-local — clearing IndexedDB removes them. They don't sync across devices.
- For team / cloud workflows, export to
.mstackand version-control or share the file.
Related
- Preferences — adjust the auto-backup interval
- .mstack format — long-term archive format
- Monetization foundations — where the 8-backup quota lives