Skip to content

Supabase project pausedMy Supabase project is paused and my app is down

Supabase pauses Free plan projects after a quiet week, and every request from your app fails until the project is back. Here’s how to restore it, what to check afterwards and how to stop it happening again, or hand it over at a fixed price.

Short answer

Open the project in the Supabase dashboard and click Resume project. Supabase says a paused project can be restored for up to 1 year after it was paused. Once it’s back, check your tables and row counts and that the app connects again. For an app with real users, move the project to a paid plan: Supabase doesn’t pause paid projects.

Restore it, check it, keep it running

  1. 01

    Resume the project

    “You can restore a paused project for up to 1 year after it was paused” Supabase, Project pausing

    In the dashboard, open the paused project, click Resume project and confirm. Wait until the dashboard shows the project is back before you test the app.

  2. 02

    Check the data and the app

    Count the rows in your main tables against what you expect, sign in with a test account and run the main flows. One GitHub report describes a table found empty after a restore, and a Supabase collaborator replied that a restore doesn’t delete tables. Checking takes minutes either way.

  3. 03

    Why it paused

    “Supabase pauses Free Plan projects that show low activity over a 7-day period to save server resources.” Supabase, Project pausing

    Supabase pauses Free plan projects with low database activity over a week, and emails a warning about a week before. A staging project, or an app between launches, can go quiet for that long.

  4. 04

    Stop it happening again

    “Projects under a paid plan cannot be paused and are not subject to automatic pausing for inactivity.” Supabase, Project pausing

    For an app people rely on, the lasting fix is a paid plan. Scheduled jobs that query the database to keep it active are an unofficial workaround that Supabase doesn’t offer or support.

Checked against the vendor’s docs on : Supabase docs: Project pausing; GitHub report: table data lost after restoring a paused project (October 2025).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Supabase email rate limit exceeded · Supabase security review before launch

Questions

More on this error

What happens after the year?

Supabase’s docs don’t say. They give the reason for the limit, that backups are kept for a limited time, so restore the project as soon as you can.

Will I lose data when it pauses?

Supabase says restoring returns the project to its previous state, including data and configurations. Check your main tables afterwards anyway.

Can you restore it for me?

The project and its plan stay in your Supabase account, so you click Resume project and choose the plan. We check the data and the app afterwards and fix anything that broke, as a pull request you review and deploy.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; we reply by email, usually within one business day.