Skip to content
Guide

Backups and disaster recovery for Supabase apps

Daily backups, point-in-time recovery, the Storage gap and Lovable Cloud's restore button, compared with sources, plus the restore drill that proves your backups work.

Sources checked October 22, 202613 min readHow we check our content

Updated October 22, 2026: Sources re-checked; Lovable's backup restore path updated.

A white sculpted object beside its identical spare kept under a glass bell jar
AI-generated illustration

As of October 22, 2026, Supabase's Pro plan keeps a daily backup of your database for 7 days, the Team plan for 14 days and Enterprise for up to 30, while the Free plan has no automatic backups at all. None of these backups include the files in Supabase Storage.

Point-in-time recovery is a paid add-on that lets you restore to a chosen moment, down to the second, instead of last night, from about $100 a month for 7 days of history. A backup only counts once you have restored it, so the real plan is three parts: the right backup tier, a copy you control, and a restore you have rehearsed.

If your database disappeared tonight, how much of it could you get back, and how fast? That applies to any app on Supabase, including apps built in Lovable. Every platform fact below comes from Supabase's or Lovable's own documentation, checked on October 22, 2026, and listed under Sources. Prices and retention change, so check those pages before you rely on a number.

What does Supabase back up, and what does it not?

Supabase backs up your Postgres database: the tables, the data in them and the schema. That is most of what matters, but not all of it: files in Supabase Storage, passwords for custom database roles, Edge Functions, API keys, auth settings and your app's code are not in the backup.

  • Included: your tables and data and the schema. Supabase's Restore to a New Project also copies the user accounts held in Supabase Auth, with their hashed passwords.
  • Not included: files uploaded through Supabase Storage. Supabase's backup documentation says database backups do not include objects stored via the Storage API.
  • Not included: passwords for custom database roles you created yourself. Daily backups do not store them, so you reset them after a restore.
  • Not part of the database at all: Edge Functions, API keys, auth settings and your app's code. Those live in your repository and project settings, and need their own copy.

The Storage gap surprises people most. If your app keeps invoices, photos or uploaded documents in Storage, a database restore brings back the rows that point at those files, but not the files. Supabase also notes that restoring an old backup does not bring back Storage objects deleted after it. You need a separate copy of the buckets. If uploads are filling Storage faster than expected, see our guide to the Supabase storage quota in a Lovable app.

How do Free, Pro and point-in-time recovery compare?

Free has no automatic backups, Pro keeps 7 daily backups for $25 a month, Team keeps 14 for $599 a month, Enterprise goes up to 30 days, and point-in-time recovery, from about $100 a month, restores to any chosen point within seconds. The table below summarizes Supabase's backup and pricing pages as of October 22, 2026.

OptionWhat you getCost (as of Oct 22, 2026)How far back you can restore
Free planNo automatic backups. Supabase recommends exporting your data regularly with the CLI$0Only as far as your own exports
Pro planDaily backups$25 a monthAny of the last 7 daily backups
Team planDaily backups$599 a monthAny of the last 14 daily backups
EnterpriseDaily backupsCustomUp to 30 days
Point-in-time recovery add-onContinuous backup; replaces daily backupsAbout $100, $200 or $400 a month for 7, 14 or 28 daysAny chosen point in the window, to within seconds; Supabase states a worst-case recovery point of two minutes

Two conditions apply to point-in-time recovery. It is only available on Pro, Team and Enterprise, and the project must also run at least the Small compute add-on. Supabase lists Small at about $15 a month, while the Pro plan's compute credit covers only the $10 Micro size, so budget for the difference. Compute size matters under load too; our guide to what breaks first under load covers when a resize helps. Point-in-time recovery is billed by the hour, which is why the monthly figures are approximate.

The Free plan carries a second risk. Supabase's pricing page says free projects are paused after one week of inactivity. A production app should not run on a plan that can pause it.

Which backup tier does your app need?

It depends on how much data you can afford to lose, and that is a business question before it is a technical one. Two terms help. NIST defines the recovery point objective (RPO) as the point in time to which data must be recovered after an outage.

The recovery time objective (RTO) is how long the system can stay in recovery before it harms the business.

In plain words: RPO is how many hours of work you can afford to lose, and RTO is how long you can afford to be down. With daily backups, a failure late in the day can cost you nearly a full day of orders, sign-ups and edits. With point-in-time recovery, the loss shrinks to minutes.

  • A prototype with test data: the Free plan plus a weekly export of your own is usually enough.
  • A live app with paying customers: Pro at the least, with daily backups, plus an off-site copy.
  • An app where a lost hour means lost money or broken promises to customers, such as bookings, payments or orders: add point-in-time recovery.

Downtime counts too. Supabase's documentation says the project is inaccessible while it restores, and that the larger the database, the longer the downtime. Restoring in place also rolls back everything written after the backup. That is why a restore to a new project is often the safer first move: you inspect the copy, then decide what to bring back.

How are backups different for a Lovable Cloud app?

If your Lovable app runs on Lovable Cloud rather than your own Supabase project, Lovable manages the backups: roughly 14 days of daily database snapshots, which anyone with edit access can restore, with files in storage buckets left out. As of October 22, 2026, its database documentation says:

  • Lovable takes a daily backup of the project's database and keeps roughly 14 days of them.
  • You restore from More, then Database, then Manage, then Backups, to one of those daily snapshots, not to a moment in between.
  • Restoring is permanent. Data created or changed after the chosen backup is lost, and the schema is reverted too, so the app may no longer match the database.
  • Anyone with edit access to the project can restore.
  • Backups and exports cover the database only. Files in storage buckets are not included.

The fourth point deserves attention. Anyone who can edit the project can roll back your production data, so keep that list short. If you need restores to a moment in time, a copy in your own account, or control over who can restore, the usual route is your own Supabase project. Our guide to migrating off Lovable Cloud covers what moves and what stays behind.

How do you keep a copy of your data outside Supabase?

Use the Supabase CLI. Its backup guide exports three files: the database roles, the schema and the data. The restore loads them into another database with psql in a single transaction, so a failed restore leaves nothing half-loaded. If you have added triggers or policies to Supabase's own auth or storage schemas, the guide says to restore those separately.

  1. 01Export on a scheduleRun the three exports from a scheduled job, not by hand. A backup that depends on someone remembering is not a backup.
  2. 02Store it somewhere elseKeep the files in storage owned by your company, under a different account from the app. A backup in the same account fails with it.
  3. 03Copy the Storage bucketsSupabase's guide moves Storage objects separately, with a script that downloads each file and uploads it again. Schedule that copy too.
  4. 04Encrypt and limit accessAn export holds every user's data. Encrypt it at rest and give access to as few people as possible.
  5. 05Check it ranAlert when an export fails or comes back smaller than the one before. Silent failure is the common way backup jobs break.

Keep the code and schema history in GitHub as well. When every change to the database is a schema migration in the repository, you can rebuild an empty database exactly, and only the data has to come from a backup.

How do you run a restore drill?

Restore a real backup into a new, separate project and check that the app works against it. Supabase's Restore to a New Project feature does this on paid plans with physical backups, which Supabase says all projects on Postgres 15.8.1.079 and newer use.

It creates an independent project from a chosen backup, or from an exact point in time if point-in-time recovery is on. Schedule a drill every quarter and after any big change to the database.

  1. Pick the newest backup and restore it to a new project, never over production.
  2. Check your scheduled jobs first. Supabase warns that extensions such as pg_cron and pg_net start running in the new project as soon as the restore completes, so the copy can call outside services on its own. If that is a risk, Supabase suggests a logical restore with the CLI instead.
  3. Time it from start to a working app. That number is your real recovery time, not the one you hoped for.
  4. Note what did not come across. Supabase lists Storage objects, Edge Functions, auth settings and API keys as not copied to the new project.
  5. Point a copy of the app at it, sign in as a real test user and walk the journeys that matter most.
  6. Compare row counts on your key tables with production at the time of the backup.
  7. Delete the drill project afterwards. Supabase notes that restored projects are independent and billed separately.

Write the steps down as you go, with the person responsible for each. During a real outage nobody should be reading the documentation for the first time. That written runbook is the core of incident response for data loss.

What causes data loss in Supabase apps?

Data is lost to platform failures, and to unreviewed schema changes, AI prompts run against production, bulk updates or deletes without a filter, missing access rules and leaked full-access keys. Backups cover a platform failure, but the causes you can control are changes made by your team or by an AI tool:

  • A schema change that drops or rewrites a column, released together with the code so nobody reviews it on its own.
  • A prompt in an AI builder that rewrites a table, run straight against the production database.
  • A bulk update or delete without a filter, from a script, an admin screen or an SQL editor.
  • Missing access rules, so one user can change or delete another user's data.
  • A key with full access leaked in the browser or a public repository.

What should a Supabase disaster recovery checklist include?

A Supabase disaster recovery checklist should include a written RPO and RTO, a paid plan with point-in-time recovery where losing a day of data is not acceptable, scheduled off-site copies of the database and every Storage bucket, reviewed schema changes in version control, a short list of who can restore, and a timed quarterly restore drill.

  • A written RPO and RTO for the app, agreed with whoever answers to customers.
  • A paid plan for any app with real users, and point-in-time recovery where losing a day of data is not acceptable.
  • A scheduled off-site export of the database, in an account you own.
  • A separate scheduled copy of every Storage bucket.
  • Every schema change in version control, reviewed, and applied on its own.
  • A short list of people who can restore, and a record of who did.
  • A restore drill every quarter, timed, with the runbook updated after each one.

Plans start at $2,999 a month paid annually, $3,999 a month billed quarterly, or $4,999 month to month; see pricing. If data has already gone missing or a restore has gone wrong, our vibe-coding rescue starts by finding the real cause before changing anything. To see where your app stands today, take the free production-readiness check: 22–35 questions, a score out of 100 and your three biggest risks.

Sources

Each platform fact above comes from one of these pages, checked on October 22, 2026. We review this page every 30 days.

Common questions

Does the Supabase Free plan include backups?

No. As of October 22, 2026, Supabase's Free plan has no automatic backups, and Supabase recommends exporting your data regularly with the CLI. Daily backups start on the Pro plan, which keeps 7 days of them.

Are Supabase Storage files included in backups?

No. Supabase's database backups do not include objects stored through the Storage API. Copy your buckets separately, on their own schedule, to storage you own.

How much does Supabase point-in-time recovery cost?

As of October 22, 2026, about $100 a month for 7 days of history, $200 for 14 days and $400 for 28 days, billed hourly. It needs a paid plan and at least the Small compute add-on, and it replaces daily backups.

Can I restore a Supabase backup without overwriting production?

Yes, on paid plans with physical backups. Restore to a New Project creates a separate project from a chosen backup, so you can inspect the data before deciding what to bring back. Storage files, Edge Functions and API keys are not copied.

How often should I test a restore?

Every quarter, and after any large change to the database. Restore into a separate project, time it, sign in as a test user and check your key journeys. Until a backup has been restored, you do not know that it works.

More on this: Production architecture & security · Lovable app not working in production? How to make it production-ready

Built something in Lovable you want people to rely on?

We are the engineers who take it the rest of the way — secured, tested, released and supported.