Get your Notion back,
and all.
Back up to storage you control. Know what will restore before you need it.
- Backups never kept on Restora's servers
- Backups go to your Drive, S3 or disk
- Relations, rollups, views, hierarchy
- You see exactly what's in each backup
Restore
Backup is easy. Restore is the hard part.
Most tools export or archive. Restora rebuilds — recreating databases, reconnecting relations, recomputing rollups and restoring views and hierarchy. A backup you can't put back isn't disaster recovery. It's a souvenir.
Watch a restore run
Go back to a moment
Every backup is a point you can return to.
Backups aren't one file that keeps getting overwritten. Each run is its own point on a timeline, with what changed since the last one written next to it — so “restore the version from before Tuesday” is a thing you can actually do.
Pin a single database as its own recovery point before a risky edit. Compare any point against your live workspace before you touch anything. Nothing changes until you say so.
What shipped recently
Know before disaster
Every backup reports what it captured — and names every gap it can detect.
The real question isn't “did the backup run?” — it's “will I get everything back?” So every backup comes with a Coverage Report: counts, and named exceptions. The one file that didn't make it has a name, not a rounding error.
No percentages in any report. Restora can only capture what Notion shares with it: when a database links to one that isn't shared, Notion hides that relation from Restora — the backup names it, and sharing the linked database includes it in your next backup.
See yours — free on every backup
Architecture
We don't keep your backups.
Your backup goes to your device, Google Drive, or S3 — Restora doesn't keep a copy. Scheduled backups and restores pass through our server while they run, and nothing is kept once they finish. If Restora disappeared tomorrow, your backup files would still open and read without us.
-
Step 1
Your Notion workspace
Read through the official API, only for what you've shared with Restora.
-
Step 2
Restora, in passing
The backup streams through; no copy is kept here.
-
Step 3
Your own storage
Local disk, Google Drive, or any S3-compatible bucket. Plain, open JSON you can read.
Pro's scheduled backups store your connection credentials, encrypted, so they can run without you — that exception, and everything else retained, is itemised in the privacy policy.
Also included
The rest of the toolkit.
Scheduled backups
Free on your own machine with the CLI, or from our servers on Pro — daily or weekly, laptop off.
Google Drive, S3, R2, B2
Pick where backups land. Your bucket, your credentials, your retention.
Drift Auditor
A free, read-only diff between your backup and what's live now. With Pro, each scheduled backup is compared with the last one.
restora guard
Snapshot before an AI agent or bulk edit runs, then see which rows, pages and properties it changed.
Open-source CLI & MCP
MIT-licensed @restora/cli, and a local read-only MCP server so Claude or Cursor can answer questions from a backup.
Deleted-rows-only restore
Put back just the rows that vanished. It only adds missing rows and never edits or deletes existing ones, so the worst case is a duplicate row.
Moving to a different Notion workspace? The same engine rebuilds one inside another account. Moving a workspace →
The honest part
What comes back, and what doesn't.
No tool restores Notion perfectly, and any tool that says otherwise hasn't tried. Here's the real line, current as of today. The full list appears in-app before every restore.
Comes back
- Databases, rows, properties and page content
- Relations, including two-way and self-relations
- Rollups, and formula properties with their expressions
- Table, board, list, calendar, timeline, gallery, form, chart and map views — maps with their locations
- Page hierarchy, icons, covers and internal links
- Files and attachments, up to your plan's per-file cap
- Comments, replayed with the original author named
- People values, when the person still resolves
Doesn't
- Page IDs — a restore creates new databases, so links or automations that depend on the original Notion IDs may need updating
- Edit history, and original timestamps and authors
- Sharing and permissions — Notion's API doesn't expose them
- Page-, feed- and dashboard-layout views — Notion's API can't recreate them
- Inline comments anchored to a block or text selection, and resolved threads
- Relations beyond 100 links per property — two-way relations rebuild through the mirrored side; one-way relations keep the first 100
- Files above your capture cap — named, with size and reason
- A database embedded in a page — restored as a link to the rebuilt one
Pricing
Back up free. Recover with Pro.
Back up your workspace for free, and pay only when you need to restore. A free Restora backup
keeps the relations, rollups and views a Notion export .zip
drops — so the day you restore, everything actually reconnects.
Free
$0 forever
A real backup — not a text-only export. It keeps the structure a Notion
.zip throws away. No card needed.
Includes:
- Manual backups, plus scheduled ones on your own machine (CLI)
- Save to Google Drive, S3, or a local folder with the free CLI — in the web app, Free backups download to your device
- Browse, search and read your backup any time
- Drift Auditor,
restora guard, and a local read-only MCP server - Attachments captured up to 20MB per file
- Free sandbox demo restore
Restore is the one paid step. Your backup is plain, open JSON in your own storage either way.
Pro
Recommended
Protection that runs without you.
$6.99 /month
or $69.99/year — $13.89 less than 12 months of monthly. Plus any applicable tax.
It backs up on a schedule whether your laptop is open or not, emails you when Notion reports a deleted page or database, and checks each backup so you find problems before you need it.
Everything in Free, and:
- Point-in-time restore — whole workspace, one database, or just the deleted rows
- Automatic cloud backups to your own Drive or S3 — laptop off
- Email alerts when Notion reports a deleted page or database
- Each backup self-checked (very large backups skip the check), and restore rehearsal to prove it
- Backup timeline — open or compare any recovery point
- Attachments up to 150MB per file
Only need one recovery? 30-Day Restore Pass — $9.99 one-time. Restore only: it restores a backup file you upload, up to 80MB. Larger backups restore from your Drive or S3 with Pro, and automatic backups and alerts stay with Pro.
14-day money-back guarantee. Cancel anytime by emailing support@restora.cc — Pro stays active through the period you've paid for.
FAQ
Straight answers.
How is Restora different from other backup tools?
Many backup and export tools give you files to keep. Restora is built for recovery back into Notion — rebuilding supported databases, relations, rollups, formulas, views and page structure.
Do I have to pay before seeing if it works?
No. Backups are free, and a free demo restores sample databases before you pay anything.
What's the difference between Pro and the one-time Restore Pass — and do I need a backup first?
Yes — create a Restora backup first, for free. The Restore Pass ($9.99 once) gives you 30 days to restore backup files you upload, up to 80MB each. Pro ($6.99/month, or $69.99/year) lets you restore any time and adds automatic backups, drift monitoring and a backup timeline. Restora restores from Restora backups, not a Notion .zip export.
Why is there a free tier if I still pay to restore?
Manual backups are free and stored in storage you control, and you also get the free Drift Auditor. You pay when you want Restora to restore a backup, or for Pro features such as automatic backups.
Where does my backed-up data go?
Your backup archives go to storage you control. Restora doesn't store the contents of your backup archives on its servers.
How do I know the backup actually captured everything?
Every backup includes a Coverage Report with exact counts of what was captured, and every gap Restora can detect is named — never hidden behind a percentage. Restora only sees what Notion shares with it, so share every database your pages link to.
What does a restore not preserve?
Restored pages get new Notion IDs, so links or automations that depend on the original IDs may need updating. Edit history, original timestamps and original authors aren't recreated, and restored comments are created as new comments. Restora shows the full list of known limitations before every restore.
Does Restora back up pages too, or just databases?
Both. Restora backs up databases and regular Notion pages, including their hierarchy. Some Notion-specific layouts and embedded features have restore limitations, which Restora shows before you restore. An inline database is restored separately and linked from the page. A linked view of a database placed on another page isn’t recreated today: the database and its rows come back, and Restora names each linked view so you can re-add it.
If I back up a page, are its sub-pages included?
Only if you select them. Use “+ N inside” to add the whole branch, or “Select everything” to include everything Restora can access.
Why not just duplicate my workspace to a second Notion account?
A duplicate is manual, goes stale and still lives inside Notion. Restora can back up automatically to storage outside Notion, keeps a backup timeline, and lets you recover a page, database or larger workspace copy without replacing your live workspace.
Back it up before you need it.
Start free. No card required. Make the backup now, so the recovery point is there when something goes wrong.