Supabase project paused: why it happens and how to unpause it

Supabase pauses Free plan projects after a 7-day stretch of low activity. Your data is not deleted and you are not billed; the project is switched off. To bring it back, open the dashboard, select the paused project, and click Resume project. You have 1 year to do that, not 90 days.

This guide covers the full timeline, the resume steps and where they fail, what to do if the year has already run out, and how to make a pause matter less by keeping a copy elsewhere.

Why Supabase pauses free projects

Pausing saves capacity. Plenty of free projects go quiet (a finished tutorial, a parked prototype, a client demo that shipped a year ago), so Supabase pauses those showing low activity over a 7-day period instead of keeping compute running for nobody. Paid-plan projects are never auto-paused.

More counts as activity than you might expect. According to the official docs, database queries, API calls, requests from an application connected to the project, and visiting the project in the Supabase Dashboard all register. Supabase’s own guideline is that a few user requests to the database each day over the previous week keeps a project awake. So a live app with real users rarely pauses. What gets paused is the project you stopped looking at, which is often the one whose data you would find hardest to reproduce.

Two common worries, answered. Paused projects are not billed: no compute, so no compute charges. And they stop counting toward the Free plan’s limit of two active projects, which is why pausing an old project is the supported way to free up a slot.

How to unpause your project

Resuming is four clicks:

  1. Open the Supabase Dashboard.
  2. Select the organization that owns the project, then the paused project itself.
  3. Click Resume project.
  4. Confirm. Restoration takes a few minutes for a small database and longer for a large one.

The project returns to its previous state, data and configuration included. Three things commonly go wrong at this step:

You are already at two active projects. The Free plan allows two running at once, and the count is not per-organization: it spans every organization where you are an Owner or Administrator, and within an organization it adds up projects across all of its Owners and Admins. So the project taking your slot may be in a different organization, or belong to a collaborator. Pause or delete one that counts toward the limit, wherever it is, then resume the one you want.

The restore itself fails. This is most likely on a project that was paused for a long time. Supabase notes that a backup taken outside the backwards-compatibility window may fail to restore, because the platform keeps changing while your project does not. Open a support ticket instead of retrying, and don’t put off a resume until next month.

There is no Resume button at all. That means the in-place restore window has closed. The section on restoring a project paused past the window covers what to do.

How long your data stays recoverable

The pause takes a snapshot, and a resume restores from that snapshot. Here is the timeline after the pause:

WhenStateWhat you can still do
7 days of low activityProject is pausedData is intact. Nothing is reachable: no API, no database connection.
Day of pause → 1 yearResume availableOne click in the dashboard brings the project back, data and configuration included.
After 1 yearOne-click resume endsUpgrading to a paid plan re-enables it. Otherwise the backup and Storage files remain downloadable for migration to a new project.
If the project is deletedNothingDeletion removes the database, Storage files, and every backup Supabase held. Supabase publishes no schedule for when this happens, only that it is permanent.

Everything above the last row can be recovered from the dashboard. After deletion there is no recovery path inside Supabase at all. Deleting a project is documented as permanent: the database, Storage files, automated backups, and any PITR snapshots all go. Supabase does not publish a schedule for deleting long-paused projects. Download a copy while you can: older backups can become harder to restore as the platform changes.

What about the 90-day rule you read about?

It is out of date, and Supabase’s own URL keeps it going. The official troubleshooting article still lives at a URL ending in restore-project-after-90-days-pause, so searching for a paused project turns up the number 90 in the link, in older blog posts, and in Reddit threads written before the change. The page itself says something different: projects paused for more than 1 year can no longer be restored through the dashboard.

So if your project paused eight months ago, ignore the 90-day number and resume it. If it paused fifteen months ago, see the section on restoring a project paused past the window. And if a search result told you 90 days, check the number against the Project Pausing page in Supabase’s docs before acting on it. Retention numbers change, and this one changed in your favor.

Is a paused project permanently frozen?

No. Search results often mix up three states that behave very differently. A paused project is switched off: the database accepts no connections, the REST and Storage endpoints stop answering, and the data sits in the snapshot Supabase took at the moment of the pause. Nothing is read or written, which is why it can look frozen from the outside, but everything is intact and one click away for a year.

Deleted is the only permanent state, and Supabase documents it as irreversible: database, Storage files, and every backup it held go together. You reach it by deleting the project yourself; Supabase publishes no schedule for deleting long-paused free projects on its own. A project whose one-year resume window has closed is not deleted either. It is past the window, which the next section covers.

If your tables look empty right after a resume, the restore is probably still running: it restores the snapshot and takes a few minutes on anything but a tiny database. Wait for the dashboard to report the project as healthy, then count rows in two tables whose size you know before deciding anything was lost.

How to restore a project paused past the window

There are two ways, and the first is easy to miss. Upgrading the paused project to a paid plan re-enables expired one-click restore options, so the resume button can come back for the price of one month of Pro. The same docs add that a backup taken outside the backwards-compatibility window may still fail to restore, and Supabase points you to Support when it does. Try this before anything manual.

If that does not work, you can still download the project’s data until it is deleted, and recovery becomes a migration into a new project: download the .backup database file and every Storage bucket from Project Overview, restore the database into a new project, copy the Storage files up with the CLI, and re-apply project settings. Supabase’s troubleshooting guide “How To Restore a Project Paused for More Than 1 Year” has the commands, and its “Restore Dashboard backup” page covers the parts that trip people up: the file may arrive gzipped, the errors about auth and storage already existing are expected, and a Postgres 15 or older psql can fail against the Session pooler with a GSSAPI error, so use a current client. Follow their procedure rather than a copy of it, because they update it as the platform changes. Our restore guide covers the two steps people get stuck on: telling which format the .backup file is in so you reach for psql or pg_restore correctly, and pushing the downloaded Storage files back up with the CLI.

Three things to know before you start. Get these wrong and a long afternoon can end with data you cannot recover.

The encryption root key has to be copied while the project is still running. If this project uses Vault or any encrypted column, a new project gets its own key and cannot read data encrypted under the old one, and the Management API returns that key only for active projects. A paused project will not hand it over. So resume first (upgrading counts), copy the key, and only then migrate. If resume is impossible, that data may never be decryptable, and it is better to find that out now than after rebuilding everything else.

Your Auth users are in the schema whose errors you are told to ignore. The duplicate-object messages about auth are expected, but that is also the schema carrying your user accounts. When the restore finishes, count rows in auth.users and in two tables whose size you already know, before trusting any of it.

The application has to be cut over, not just the data. The new project has a different URL and different API keys, and none of the Auth configuration comes with the data: providers, redirect URLs, email templates and the JWT secret are project settings, not database rows. Existing sessions will be invalid, and OAuth redirects pointing at the old project ref need changing at the provider too.

Unlike the resume button, none of this changes the source project: if a restore goes wrong you still have the downloaded files and can start the target again. Download the files today even if you rebuild next week. Supabase publishes no deletion schedule, and older backups get harder to restore as the platform changes.

How to keep a project from being paused

The obvious approach works: keep enough real traffic on it. Supabase describes the trigger as low activity over a 7-day period rather than publishing a precise threshold, and its guideline is a few database requests a day, so aim well above one. Where there are no real users, teams add a scheduled ping: a cron job or a GitHub Actions workflow that calls an endpoint which queries the database. Follow the guideline, not the minimum: a few requests spread across each day, not a single one that has to succeed every time. A request that never reaches Postgres does not count at all.

A keep-alive ping prevents one problem, the pause, and nothing else. It does not help when a migration drops a column, when someone runs a DELETE without a WHERE clause, when a compromised key wipes a table, or when the project is deleted outright. It is also one more thing that can stop working without anyone noticing, and then the project pauses anyway.

Upgrading to a paid plan removes auto-pausing entirely and adds daily backups kept 7 days. Both help, but neither puts a copy of your data anywhere outside Supabase.

Resumed it, and it paused again a week later

This happens a lot, and it is not a bug. The inactivity check runs every week: each week Supabase looks at the previous 7 days of user database activity, and a project that was resumed but then received almost no queries meets the low-activity bar again. Resuming does not exempt a project from the next check. Visiting the project in the dashboard does count as activity (the docs list it as a way to prevent a pause after the warning email), but it prevents that one pause, not the ones after it. Only regular database activity or a paid plan does that.

You do get notice. According to the official docs, Supabase emails the project owner roughly one week before a pause takes effect and again once it has happened, so a project that keeps pausing has been sending a warning every time. Treat that email as your cue to add real traffic, schedule a keep-alive that queries the database, or, if the project is finished, take a copy and let it pause.

Keep a backup outside the project

Every path on this page comes back to the same point: the data needs to exist somewhere other than the paused project. You notice a pause right away, because the project stops answering. Deletion is quieter, and there is no way back from it.

A weekly dump into a bucket you own gives you another way to recover the data saved in it. You can set that up yourself for free: the GitHub Actions guide has a complete scheduled workflow, and the free plan guide covers the two-minute manual version for right now, with the manual backup guide going deeper on dashboard, CLI, and pg_dump. BackupDrill’s free plan does the same on a schedule for one project, streaming each backup into your own S3, R2, or B2 bucket, and restore-tests the first backup so you find out it restores before you need it to.

FAQ

Are you charged for paused projects on Supabase?

No. A paused project uses no compute, so there are no compute usage charges while it is paused. It also stops counting against the Free plan's two-active-project limit, which is why pausing an old project is the supported way to make room for a new one. Supabase pauses projects to save resources; it is not a penalty or a push to pay.

What are the rules for a Supabase free project being paused?

Supabase pauses Free plan projects that show low activity over a 7-day period. Its own guideline is that a few user requests to the database each day over the previous week is enough to keep a project active. Database queries, API calls, requests from a connected application, and visiting the project in the Supabase Dashboard all count as activity. Paid-plan projects are not auto-paused.

Can I restore a Supabase project that has been paused for more than 90 days?

Yes. The 90-day figure is out of date. The current window to resume a paused project from the dashboard is 1 year, even though Supabase's own troubleshooting page still has 90-days in its URL. After a year the one-click restore is gone, but you still have two options. Upgrading the paused project to a paid plan re-enables expired restore options, although a backup taken outside the backwards-compatibility window may fail to restore. And the database backup and Storage objects can still be downloaded from the Project Overview page and migrated into a new project.

How do I stop my Supabase project from being paused?

Enough real traffic prevents it. Supabase's guideline is a few database requests a day across the previous week. It describes the trigger as low activity and does not publish an exact threshold, so one request a day may not be enough. Teams often add a cron job that calls a lightweight endpoint that queries the database. That keeps the project awake but protects nothing else: a keep-alive ping does not help with a dropped table, a bad migration, or a deleted project. For those you need a backup stored outside Supabase. Upgrading to a paid plan also ends auto-pausing.

Is a paused Supabase project permanently frozen or deleted?

Neither. Paused means the project is switched off: the database accepts no connections, the API and Storage endpoints stop answering, and the data sits in the snapshot Supabase took when it paused. You can resume it from the dashboard for 1 year. After that, upgrading to a paid plan re-enables the restore, and the database file and Storage buckets stay downloadable so you can migrate to a new project. The only permanent state is deletion, which Supabase documents as irreversible, and it publishes no schedule for deleting long-paused free projects on its own. If your tables look empty after a resume, wait for the restore to finish and check the row counts again before assuming data is gone.

Why does my Supabase project keep pausing again after I resume it?

Because the inactivity check runs every week, not once. Every week Supabase looks at the previous 7 days of user database activity; a project that was resumed but then received almost no queries meets the low-activity bar again and is paused again. Resuming it does not exempt it from the next check. Visiting the dashboard counts as activity and can prevent an upcoming pause after the warning email, but only that one. Supabase sends a warning email about a week before each pause and a confirmation once it has happened. If a project keeps pausing, its only traffic is probably you resuming it. A few real database requests a day over the week keeps it awake; a paid plan removes auto-pausing altogether.

Sources

  • Supabase docs — Project Pausing
  • Supabase troubleshooting — Restore a project paused past the window
  • Supabase docs — Billing FAQ (paused projects and free project limits)
  • Supabase docs — Database Backups
  • Supabase docs — Restoring a downloaded dashboard backup
  • Supabase docs — Backup and restore using the CLI (encryption root key)
  • Supabase docs — Upgrading (paused projects and expired restore options)
  • Supabase docs — Connecting to your database

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

Resumed the project and want the next quiet year to be uneventful? Start free with weekly backups for one project into your own bucket, or do it yourself with the open-source CLI.