blog

Supabase Data Missing After Restore, or Project Deleted?

Rows or files gone after a Supabase restore, or the whole project deleted? What Supabase can bring back, what it can't, and where else to look.

6 min readSupabaseFixes

You restored your Supabase project, or brought back a paused one, and something is missing: yesterday's sign-ups, the last orders, uploaded images. Or worse, the project itself is gone from the dashboard.

Before you panic, find out which situation you're in. Some "missing data" isn't missing at all. Some is gone by design, and some can still be recovered from somewhere else. This guide walks through each case, based on Supabase's documentation on backups, pausing and deletion.

Step 1: Make sure the data is really missing

Three common situations look like data loss but aren't.

Your app is pointing at a different project

If you have more than one Supabase project (a test copy, an old version, a project created by Lovable or Bolt), your app may be talking to a different one than the one you restored.

Find the address your app uses: it looks like https://<project-ref>.supabase.co. You'll find it in your app's environment variables or settings. Then open the project in the Supabase dashboard and compare the reference in the dashboard's address bar. If they don't match, the data may be fine; you're looking in the wrong place.

Row Level Security hides the rows

Supabase has a troubleshooting article for exactly this: Why is my select returning an empty data array and I have data in the table? It names two common causes: Row Level Security is turned on but no policy matches the request, or your query's filters match no rows.

Signs it's RLS: the rows are visible in the dashboard's Table Editor, but your app gets an empty list with no error. This is easy to hit after moving to a new project if the policies weren't recreated, or when the user is no longer signed in. Supabase's article suggests checking whether the request actually carries a signed-in user, because policies that rely on auth.uid() match nothing without one.

You're signed in as a different user

If your app shows "my orders" or "my projects", a different account sees different rows. Sign out and in again with the account that owns the data.

If none of these explain it, read on.

Case 1: You restored a backup and recent data is missing

This is how restores work. Supabase's backup docs say:

  • Pro, Team and Enterprise projects are backed up daily. Pro projects can access the last 7 days of daily backups, Team projects 14 days, and Enterprise projects up to 30 days.
  • Restoring to an earlier point replaces the current database state. Changes made after the restore point aren't included.
  • The project is unavailable while the restore runs, longer for bigger databases.

So if you restored this morning's backup at 6 p.m., everything written between the backup and the restore is gone from the live database. Supabase can't merge "the old data plus the new rows" for you.

What you can do:

  • If you have Point-in-Time Recovery (an add-on for Pro, Team and Enterprise projects), you can restore to a much more precise moment. Supabase's docs say it allows restores to any chosen point with up to seconds of granularity. Note that with PITR enabled, Supabase no longer takes daily backups.
  • If you exported the database yourself before restoring, you can copy the missing rows back from that export.
  • If neither exists, the rows written after the backup can't be recovered from Supabase. Check other systems that saw the same events: payment providers, email logs, form tools.

Next time: Supabase's docs recommend restoring to a new project first if you want to keep your current data. You can then copy only what you need from the restored copy, without overwriting anything live.

Case 2: Files from Storage are missing

Supabase's backup docs state that database backups do not include objects you store via the Storage API. Restoring an older backup doesn't bring back files you deleted after it was taken.

Rows in your tables may still point to file names that no longer exist, so images appear broken. If you deleted files by mistake, a database restore won't help. Look for copies wherever the files came from: users' devices, an email, or a download you made earlier.

Case 3: Something else broke after a restore

A couple of things behave differently after a restore:

  • Custom database roles: Supabase's docs say daily backups don't store passwords for custom roles, so you need to reset them after a restore. If a tool connects with such a role, it fails until you do.
  • Replication and subscriptions: if you use logical replication, Supabase's docs say you must drop subscriptions before restoring and re-create them afterwards.

These look like "the data isn't there" from the outside, but the data is fine. The connection is what's broken.

Case 4: You resumed a paused project

When a Free plan project is paused for inactivity and you click Resume project, Supabase's project pausing guide says the project comes back to its previous state, including data and configurations. If something seems missing after resuming, go back to Step 1: wrong project, RLS or a different user are far more likely than lost rows.

The guide also says paused projects can be restored for up to 1 year after they were paused. Past that, Supabase's article on restoring a project paused for more than a year says the project can't be resumed in the dashboard. Instead you download the database backup and your Storage files, create a new project and load them into it. Download them before the paused project is deleted: once it is, all its data and backups are permanently removed. Our guide on restoring a paused Supabase project covers the normal resume and how to stop pauses from happening.

Case 5: The project was deleted

Supabase's backup docs are clear: when you delete a project, Supabase permanently removes all its data, including any backups, and this can't be undone.

So the recovery has to come from copies outside that project:

  1. Your own exports. Search your computer for .sql or .backup files from earlier exports.
  2. Migration files. If your project has a supabase/migrations folder (common in code exported from AI builders), it can rebuild your tables and policies in a new project. It won't contain your data, but it saves you from recreating the structure by hand.
  3. Lovable's built-in backend. If your app uses Lovable Cloud rather than your own Supabase account, backups work differently. Lovable's docs say it takes one backup per day and keeps up to roughly 14 days, under More → Database → Manage → Backups. They cover the database only, not storage files, and a restore can't be undone.

Once you have something to restore, create a new Supabase project, load the data, and update your app with the new project's address and keys. Until then, sign-in and data won't work; see Supabase "Failed to fetch" error for what that looks like in the browser.

How to protect yourself from now on

Free plan: make your own backups. Supabase's docs say they automatically back up Pro, Team and Enterprise projects, and recommend that Free projects regularly export their data with the Supabase CLI. Their backup and restore guide uses these commands (it also needs Docker Desktop and your database connection string):

supabase db dump --remote=[CONNECTION_STRING] -f roles.sql --role-only
supabase db dump --remote=[CONNECTION_STRING] -f schema.sql
supabase db dump --remote=[CONNECTION_STRING] -f data.sql --use-copy --data-only -x "storage.buckets_vectors" -x "storage.vector_indexes"

Keep the files somewhere other than your laptop. Storage files aren't in these dumps, so keep copies of important uploads too.

Before any restore, export or restore to a new project first. A restore can't be undone.

Don't let a project sit paused. A paused project is one step from the restore window running out. Read Supabase's pause warning emails, and use our free checkup to see whether your app's Supabase project is paused. If Supabase itself has a problem, our Supabase status page shows it.

FAQ

Why is my newest data missing after restoring a Supabase backup?
Because a restore puts the database back to the moment the backup was taken. Supabase's docs say restoring to an earlier point replaces the current database state, so anything added or changed after that point is not included.
Why are my uploaded files missing after a restore?
Supabase's backup docs say database backups don't include objects stored via the Storage API. Restoring an older backup doesn't bring back files you deleted after that backup was taken.
Can I recover a deleted Supabase project?
Supabase's docs say deleting a project permanently removes all its data, including the backups, and that this can't be undone. Your remaining options are copies outside that project: your own exports, a downloaded backup, or your migration files.
My tables look empty in the app, but the data is in the dashboard. Is it lost?
No. That's almost always Row Level Security: with RLS on and no policy that matches the request, a select returns an empty list without an error. Check the table's policies and whether the user is signed in.

Fixed it? Run a free Pingbuddy checkup on your live site. It shows whether your site answers and how fast, when your SSL certificate and domain expire, whether your Supabase project is paused and whether secret keys are visible in your public code.

Run free checkup →