Backups
On desktop and mobile, Svodly keeps local snapshots of a book — like a time machine. Before risky actions (sync, import) the app saves the state itself, so you can roll back to the date you need at any moment. Everything is stored on the device, without the cloud.
What a snapshot is
A snapshot is the full state of one book at the moment it was created: all transactions, accounts, categories, counterparties, budgets and book settings. It is stored locally as a separate file in the same JSON format as when you export. Each book has its own set of snapshots.
A snapshot is a local backup, not a sync log. It does not “go up” to the cloud and is not transferred between devices: each device has its own snapshots.
Where to find it
- Desktop — Settings → Backups.
- Mobile — the ··· menu in the corner of “Summary” → Backups.
- Web — there are no local snapshots (see “There are no backups on the web” below). The section shows a hint that backups are available in the desktop and mobile apps.
When snapshots are created automatically
Backups trigger on events — so you always have a rollback point before the data could change in bulk. The triggers are configurable and stored separately on each device (they do not go to the cloud):
| When | Default | Platform |
|---|---|---|
| Before sync (before receiving data from the cloud) | on | desktop, mobile |
| After sync (when new data has been applied) | off | desktop, mobile |
| Before import (CSV / Excel / JSON) | on | desktop |
| Before undoing an import | on | desktop |
| Every N transactions (10 / 50 / 100) | off | desktop |
To avoid piling up extra files, snapshots for the same reason within ~15 minutes are not duplicated. The set of triggers is changed in the backup settings.
Create a snapshot manually
The “Create backup” button (on desktop — “Manual backup”) takes a snapshot right now — handy before a big edit or a reorganization of categories. Manual snapshots are marked separately and are not deleted automatically when old ones are cleaned up.
How long they are kept
So that snapshots don’t take up much space, old ones are thinned out by the rule “the further back, the rarer”:
- for the last 24 hours — all are kept;
- a day to a week — one per hour;
- a week to a month — one per day;
- a month to a year — one per week;
- older — deleted (except manual ones).
On top of that, an overall cap and retention period apply: in the backup settings you can set how many days to keep snapshots (7 / 30 / 180 / 365; the default is 30). This rule does not touch manual snapshots.
Restoring
- Open Backups and choose a snapshot by date (the reason is shown next to it — before sync, manual, etc.).
- Tap “Restore” and confirm replacing the current book data.
- The book will instantly return to its state at the moment of the snapshot.
If the book was connected to the cloud, sync for it is automatically turned off on restore — otherwise the next sync would overwrite the restored state with data from the cloud. Once you’ve made sure everything is in place, turn sync back on from the “Sync” screen — the current (restored) state will become the source and spread to your other devices.
There are no backups on the web
The web version has no local snapshots by design: the book is already stored in the cloud, and it is the cloud that plays the role of the backup — the data is duplicated on the server. If you need to return to an earlier state on the web, restore the book from a JSON file you exported in advance, via import.
A good habit on any platform is to export to JSON from time to time. This is a portable copy that does not depend on the cloud or any particular device: the file is with you and can be read even without Svodly.
Where to go next
- Import & export — a portable copy of a book in a file and undoing imports.
- Sync — what happens to a book after restoring, if the cloud is connected.
- Troubleshooting — step-by-step restoring from a backup and common questions.