Supabase backup for your whole project.
Your data, user accounts, uploaded files and server code, backed up outside Supabase. Every database backup is restored as a test.
Everything you would need to start over
See what is checkedYour data and users
Every table and every user account in one copy. Each backup is restored as a test, so you know it works.
The files your users upload
Images, documents and anything else stored in your project. Supabase's own backups leave these out.
Your server code
Your Edge Functions with their deploy settings, so you can put them back without the CLI.
Works with Supabase projects from the tools you already use
Supabase
Lovable
Bolt
- v0
- Cursor
Replit
Where Supabase stops
Compare every Supabase backup option| What is backed up | Supabase backups / PITR | ReviveDB |
|---|---|---|
| Your app's data | Included | Included |
| User accounts and logins | Included | Included |
| Files your users upload | Not included | Included |
| Your server code | Not included | Included |
| Restore-tested | Not tested | Every backup |
| Safe if the project is deleted | Not included | Included |
Start free, upgrade for daily backups
View all plansFree
€0Free plan · no card required- Projects
- 1
- Database limit
- 1 GB
- Supabase Storage
- 1 GB / project
- Backup storage
- 5 GB / account
- Backup processing
- 5 GB / month
- Backup frequency
- Weekly
- Retention
- Latest 3 recovery points
- Recommended
Pro
€9/moIntroductory price- Projects
- 3
- Database limit
- 10 GB each
- Supabase Storage
- 25 GB / project
- Backup storage
- 50 GB / account
- Backup processing
- 20 GB / month
- Backup frequency
- Daily
- Retention
- Up to 30 days
Scale
€29/moFor larger workloads- Projects
- 10
- Database limit
- 10 GB each
- Supabase Storage
- 25 GB / project
- Backup storage
- 100 GB / account
- Backup processing
- 70 GB / month
- Backup frequency
- Daily
- Retention
- Up to 60 days
Need hourly backups or more capacity? Contact us
Common questions
From the blog
View all postspg_dump: "aborting because of server version mismatch" on Supabase
Your pg_dump is older than the Postgres version of your Supabase project. Install a pg_dump of the same major version or newer.
Read articlepg_restore: "input file appears to be a text format dump" with a Supabase backup
The backup you download from the Supabase dashboard is a plain SQL file, so it goes through psql instead of pg_restore.
Read articlepg_dump on Supabase: "query would be affected by row-level security policy"
pg_dump stops on tables with RLS when the role cannot bypass it. The usual flag makes the error go away and leaves those tables empty in the dump.
Read article