Does the Supabase free plan include backups?

No. Automated backups start on the Pro plan ($25/month, as of August 2026): daily, kept for 7 days. On the Free plan you can’t access scheduled daily backups without upgrading. If you drop a table tonight, there is no restore button for it in the dashboard, so export your own copy rather than counting on backups that may only become available after an upgrade. The official backup docs say this directly and recommend that free-tier projects regularly export their data with the CLI and keep off-site copies. This page turns that advice into steps: what Free includes, the pause clock that makes it urgent, and three ways to get a real backup, none of which needs a paid Supabase plan. (For every plan, not just Free, see every Supabase backup option compared.)

Supabase Free plan and backups at a glance

Automated backups
None on Free; daily backups start on Pro ($25/month), kept 7 days
Pause rule
Paused after 7 days of low activity; a warning email arrives about a week before
Resume window
1 year from the pause, one click in the dashboard
After the window
Upgrading re-enables restore; the .backup file and Storage buckets stay downloadable
Free ways to back up
pg_dump or the CLI by hand, a scheduled GitHub Actions workflow, or BackupDrill's free plan (1 project, weekly)

Checked September 2026.

What each plan actually gives you

PlanAutomated backupsGetting data back
FreeNoneOnly what you export yourself
Pro ($25/month)Daily, kept 7 daysRestore from the dashboard
TeamDaily, kept 14 daysRestore from the dashboard
PITR add-on ($100/month per project)Continuous; restore to any second in the windowReplaces the daily backups; database only

Prices as of August 2026. One more catch applies to every plan: even where automated backups exist, they cover the database only. Storage files are never in them. And on newer projects the platform’s own backups cannot be downloaded: you can restore them in place or, on paid plans, into a new project, but you never get the file.

The pause clock makes this urgent

Free projects are paused after 1 week of inactivity, and you get at most 2 active projects. (Already paused? The paused-project guide has the resume steps and the full clock.) Pausing takes a snapshot, and that snapshot is what lets you restore a paused project from the dashboard for up to a year. It only protects you from the pause itself: it is taken when the project is paused, not before a migration goes wrong, so it won’t help with your own mistakes. After a year, in-place restore is no longer possible. The backup and Storage files can still be downloaded and moved to a new project, but you are recovering on Supabase’s timeline instead of your own. Side projects, prototypes that turned into real products, and small tools a client depends on often live on the free tier, and nobody is on call for them. That is why they need a backup that runs without you.

Option 1 — take a dump right now (two minutes)

This works on every plan, costs nothing, and gives you a copy you can restore into another Postgres once it has the extensions, Supabase roles, and Auth objects your schema references. Copy the Session pooler connection string from the Connect button at the top of the dashboard. Don’t use the Direct connection string: it runs over IPv6 and fails on IPv4-only networks.

export DB_URL="postgresql://postgres.<project-ref>:<password>@aws-0-<region>.pooler.supabase.com:5432/postgres"

pg_dump "$DB_URL" \
  --format=custom \
  --schema=public \
  --file="backup-$(date +%F).dump"

--schema=public captures your application schema; Supabase-managed schemas (auth, storage metadata) stay out, by design. If you use the official supabase db dump instead, note that its default output contains no rows, only schema definitions. The .sql export guide covers both commands and that trap in detail, and the manual backup guide adds the dashboard route and how to check the file restores.

Option 2 — set up automatic backups (fifteen minutes)

A one-off dump goes out of date quickly, and Supabase won’t schedule an export for you on any plan, so automatic backups on the Free tier mean a scheduler you bring yourself. The cheapest one that works is GitHub Actions: the GitHub Actions guide has a complete weekly workflow that dumps your database into a bucket you own, for free. Storage files can be copied in the same run, but only once you have created Storage S3 credentials for the project and added all four fields to the workflow. The database dump never includes them on its own.

Choose the frequency based on egress: every backup pulls data out of Supabase against the Free plan’s 5 GB/month allowance, which is shared with whatever your app already serves. Work it out with your own numbers (there are roughly 4.3 weekly runs a month) instead of copying someone else’s schedule. A 100 MB database is about 0.4 GB a month weekly and still only 3 GB daily, so daily is fine. At the 500 MB ceiling, weekly is about 2 GB and daily would exceed the allowance on its own. Storage is where it adds up: Free includes 1 GB, and copying all of it weekly is roughly 4.3 GB more, which on its own leaves almost nothing. Storage copies are full copies, not deltas, so if you have real uploads the lever is cadence: copy Storage less often than the database. Use a private repo: GitHub disables scheduled workflows in public repos after 60 days without activity, and a backup repo rarely sees any.

Option 3 — let a service run it (also free)

BackupDrill’s free plan covers one project with weekly backups into your own S3, R2, or B2 bucket. Backups stream straight into the bucket without being written to our disk, and you get an email if one fails. Your first backup also gets a restore drill: our worker downloads the snapshot to a temporary directory, restores it into a throwaway Postgres, checks it, then deletes both. Daily scheduled drills are what the paid plans add. If you would rather self-host the whole setup on a machine you run, the tools comparison covers those options too, including the free ones.

FAQ

Does Supabase make backups on the free plan?

No. Automated daily backups start on the Pro plan ($25/month), where they are kept for 7 days. On the Free plan, Supabase's own docs recommend that projects regularly export their data using the CLI's db dump command and keep off-site backups. On the free tier, backups are your job.

Can you back up a free Supabase project?

Yes, and you don't need a paid plan for it. Backups taken from outside (pg_dump against the connection string, supabase db dump, a scheduled GitHub Actions workflow, or a backup service's free tier) work the same on Free and Pro. What the Free plan lacks is Supabase doing any of this for you.

What happens if my free project gets paused before I back it up?

Free projects are paused after 1 week of inactivity. Pausing takes a snapshot, and for up to 1 year you can restore the paused project from the dashboard using it. After that it can no longer be restored in place. The backup and Storage files can still be downloaded from the dashboard and migrated to a new project, but you are now doing recovery work on a deadline you did not choose. A recent snapshot in your own bucket gives you another way to recover the data it contains.

How do I set up automatic backups on the Supabase free plan?

Supabase does not schedule backups on the Free plan, so automatic means a scheduler you run. Two work well and cost nothing: a GitHub Actions workflow on a weekly cron that runs pg_dump and uploads the file to a bucket you own, or a backup service's free tier that does the same on your behalf. Choose the cadence based on egress: every backup counts against the Free plan's 5 GB/month allowance, which is shared with whatever your app already serves. A small database can go daily; at the 500 MB ceiling daily would exceed the allowance while weekly is about 2 GB. Storage copies count too, so do the arithmetic with your own sizes. Whichever you pick, add a failure notification; otherwise a scheduled backup can stop without anyone noticing.

If I upgrade to Pro, do backups appear for the time before the upgrade?

Officially, daily backups begin when the upgrade takes effect. In practice, Supabase's troubleshooting docs currently say up to 7 daily backups are taken even for free projects and become accessible once you upgrade, with a note that this may stop. It is worth trying in an emergency, but it is not a backup strategy. The copy you can rely on is the one you exported.

Sources

  • Supabase docs — Database Backups
  • Supabase — Pricing
  • Supabase docs — Project Pausing
  • Supabase troubleshooting — Backup accessibility after upgrading
  • Supabase CLI reference — db dump
  • Supabase docs — Connecting to your database
  • PostgreSQL docs — pg_dump

Facts and prices last verified August 9, 2026 against the sources above. Written by the team behind BackupDrill.

Want the weekly backup running before you close this tab? Start free (the free plan covers one project), or keep it DIY with the open-source CLI.