All posts

Supabase paused your project: why, and how to keep your app up

Your app was built with Lovable or Bolt on Supabase's free plan, and suddenly nobody can log in. Then you find an email from Supabase: your project was paused. Here is why, how to get your app back today, and how to stop it happening again. Vendor facts come from Supabase's own docs, checked in November 2026.

Short answer: Supabase pauses free projects after about a week with too little database activity. Your data stays. Open the Supabase dashboard, select the project and click Resume project. Then make your own copy of the data. For an app that people rely on, the only fix Supabase's docs promise is a paid plan.

1. Why Supabase paused your project

Supabase's project pausing guide says it "pauses Free Plan projects that show low activity over a 7-day period". The pricing page says free projects are paused after 1 week of inactivity, with a limit of 2 active projects.

  • What counts as activity. The guide talks about "user database activity", with no exact number. A few user requests to the database each day is typically enough. It also warns that a project you do use can still be paused if that use is too small.
  • The warning. Supabase emails the project owner twice: a warning roughly one week before the pause, and a confirmation once it is paused. After the warning, you can stop the pause by visiting the project in the dashboard, or by sending requests to it from your app.
  • Who gets the emails. The project owner. If someone else created the Supabase account for you, the warning went to them.

Not every pause is about inactivity. Supabase's status code page says free projects can also be paused on the owner's request, or in rare cases for abuse. The billing FAQ adds overdue invoices and going over the plan's limits again and again. Read the email to see which one it is.

2. What your users see

Your pages may still load, because they are often hosted elsewhere. But everything that needs Supabase stops: sign-in, loading and saving data, file uploads and Edge Functions. Supabase's docs describe two signs in the network requests:

  • Status code 540. The status code page says the project "cannot process requests until it is un-paused by the owner".
  • A DNS error, NXDOMAIN. Supabase's DNS error page says a paused project stops serving its hostname, even though the project still exists.

Your users don't see codes. They see an error message, an empty page or a login button that does nothing.

3. How to restore it

The pausing guide gives these steps:

  1. Open the Supabase dashboard.
  2. Select the organization, then the paused project.
  3. Click Resume project and confirm.

The guide says the project returns to its previous state, including data and configurations. It does not say how long this takes. When the project no longer shows as paused, sign in on your phone in a private window and do the main thing your app is for.

  • The 2-project limit. The pricing page says the free plan gives you 2 active projects and as many paused ones as you want. If two other free projects are active, you may need to pause one first.
  • The time limit. The pausing guide and the upgrading page say you can restore a paused project for up to 1 year. An announcement from 2024 said 90 days, and a screenshot on the upgrading page still shows "90 Days Remaining". So restore it now.

After the time limit, the upgrading page says you can download the backup file and your Storage files from the project dashboard, and restore them into a new Supabase project. Upgrading to a paid plan while paused brings the one-click restore back, but the old backup may fail to restore. Then contact Supabase support. On a new project, Supabase's restore guide says you must set up Edge Functions, auth settings and API keys, Realtime settings, and database extensions and settings again, and your app must point to the new address and keys.

4. Your data: what stays, and the copy to make now

The pause does not delete your data. But don't count on a Supabase backup:

  • Supabase's backup docs say daily backups are for Pro, Team and Enterprise projects. For free projects, they recommend regular exports with the Supabase CLI and backups kept somewhere else.
  • The production checklist says database backups are not available for download on the free plan.
  • Database backups do not include the files your users uploaded to Storage.

A paused project can't process requests, so you can't export it while paused. Resume it, then make your own copy the same day. Supabase's CLI backup guide shows the supabase db dump commands for roles, schema and data. Copy your Storage files separately. For a setup that keeps running, see what Supabase, Neon and Firebase back up.

And don't delete a paused project to make room. The backup docs say deleting a project permanently removes all its data and backups.

5. How to stop it happening again

a. A paid plan

This is the fix Supabase documents. The pausing guide says projects on a paid plan cannot be paused and are not subject to pausing for inactivity. The production checklist says to upgrade to Pro "to guarantee that we won't pause your project for inactivity". You upgrade from Billing Settings in the dashboard, and Pro adds daily backups. For what a small app costs each month, see small web app running costs. Keep your card up to date: the billing FAQ says an overdue invoice pauses your projects and moves you back to the free plan.

b. Real use

If people use your app every day, their sign-ins and data requests usually make enough database activity. An app used once a week or once a month is most at risk.

c. Scheduled "keep-alive" requests

A common workaround is a scheduled job that sends a small database request now and then. Supabase's pausing guide does not mention this, and I found nothing about it, for or against, in their terms or acceptable use policy. So it is not an official feature, and it can stop working:

  • Supabase decides what counts as enough activity. The exact rule is not published and can change.
  • A keep-alive can't undo a pause. Once paused, only the owner can resume the project.
  • The scheduler can stop quietly. GitHub, for example, disables scheduled workflows in a public repository after 60 days without repository activity.

For a demo or a side project, that risk may be fine. For an app customers pay for, it means a business resting on a free plan that pauses by design. The honest fix there is the paid plan. If you do run a keep-alive, add a heartbeat check like any other scheduled job, as in scheduled jobs for a small app.

d. Move the database

You can also move the database to another host. That is a project, not a quick fix: user accounts, files, keys and login redirects all have to move. See moving a Lovable or Bolt app to your own GitHub and hosting.

In every case: watch it

Make sure the Supabase account owner is an email address you read. And add an uptime check on a page that reads from the database, not just your home page, which can stay green while every Supabase request fails. See uptime checks and error alerts.

Checklist for a paused Supabase project

  1. Read the email: inactivity, an unpaid invoice, or usage over the limits?
  2. In the dashboard, open the project, click Resume project and confirm.
  3. Sign in and do the main thing on your phone, in a private window.
  4. Make your own copy with supabase db dump, and copy your Storage files.
  5. Don't delete a paused project to free a slot.
  6. Decide: a paid plan for an app people rely on, or accept that it can pause again.
  7. Make sure the warning emails reach you, and add a check that touches the database.

Before a launch, also go through the launch-ready checklist.

Want this fixed for you?

I finish and fix apps built with Lovable, Bolt, Cursor or Replit, including restoring a paused Supabase project, setting up backups that are tested, and a setup that doesn't fall asleep when it matters. Or send me the details and I'll reply within 24 hours.