Skip to content
← All guides

Production readiness

Supabase free project paused: why it happens and how to keep production running

By Jan Lipmann, appienceChecked against sources on 8 min read

Supabase pauses Free plan projects that get too little database activity over a week. Your data and settings are kept, and you can resume the project from the dashboard - as of 2026-11-21 Supabase allows that for up to 1 year after the pause. Projects on a paid plan are never paused for inactivity, so if people rely on the app, the lasting fix is a paid plan, not a keep-alive trick.

SupabaseLovablePostgreSQL

What you are seeing

The app looked fine last week. Now nothing that needs the backend works:

  • Sign-in fails, lists stay empty, saving does nothing - for every user at once, not just one.
  • Requests from the app to your Supabase project come back with HTTP status 540. Supabase uses that code for exactly one thing: the project has been paused and cannot process requests until the owner un-pauses it (HTTP status codes).
  • In the Supabase Dashboard the project is marked as paused and offers a **Resume project** button.
  • There are two emails from Supabase in the project owner's inbox: a warning roughly one week before the pause, and a confirmation once it happened (Project pausing).
Note: The app often looks quiet before this happens: a side project, a demo for investors, an app between launches. Supabase counts database activity, not how often you open the app builder or think about the project.

How to check it yourself

Everything below is read-only and uses only your own project.

1. Is your backend a Supabase project you own, or Lovable Cloud?

If you built the app with Lovable, click the Cloud icon in the editor's top bar. A screen with Database and Users views inside Lovable means Lovable Cloud: the backend is owned and managed by Lovable, it does not appear in your Supabase Dashboard, and Lovable's own pausing rules apply. A Supabase logo with your project name and links to the Supabase Dashboard means a Supabase project you manage yourself (Identifying a Lovable backend). The rest of this guide is about the second case - Lovable Cloud is covered in the FAQ below.

2. Ask the project directly

Your project URL and publishable (or legacy anon) key are in the dashboard under Connect or Settings > API Keys. Both are public values that already ship in your app. From a terminal:

curl -s -o /dev/null -w "%{http_code}\n" \
  "https://YOUR-PROJECT-REF.supabase.co/rest/v1/" \
  -H "apikey: YOUR_PUBLISHABLE_KEY"
540 means the project is paused. Any other code (200, 401, 404 and so on) means the project is running and the outage has another cause.

3. Check which plan the project is on

Open the organization that holds the project and go to Billing. Plans are set per organization, not per project: every project in an organization is on the same plan (Billing). Only Free plan projects are paused for inactivity. On Free, Supabase lists three reasons for a pause: inactivity, a request by the owner and, rarely, abuse (HTTP status codes). If the organization is on Pro, Team or Enterprise and the project still returns 540, contact Supabase support.

4. Check what you would lose without a backup

Supabase does not take automatic backups of Free plan projects (Pricing, checked 2026-11-21) and recommends exporting the data yourself (Database backups). Once the project is running again, run this in the SQL Editor to see how much data the app holds:

-- Exact number of rows in each of your tables
select
  table_name,
  (xpath('/row/cnt/text()',
    query_to_xml(format('select count(*) as cnt from %I.%I', table_schema, table_name), false, true, '')
  ))[1]::text::bigint as row_count
from information_schema.tables
where table_schema = 'public'
  and table_type = 'BASE TABLE'
order by table_name;

-- Total size of the database
select pg_size_pretty(pg_database_size(current_database())) as database_size;
The first query counts every row in every table of the public schema, using `query_to_xml` to run one count(*) per table. On large tables it takes a while. The second uses `pg_database_size`. Save the output - it is how you confirm later that a backup or a restore is complete.

Why it happens

“Supabase pauses Free Plan projects that show low activity over a 7-day period”
- Supabase docs, Project pausing

Supabase does this to save server resources. What counts is user database activity over the past week - queries from your app, API calls, or opening the project in the dashboard. Supabase says a few user requests to the database each day over the previous week is typically enough to avoid a pause, and also that a project you are actively using may still not have enough activity to be excluded (Project pausing). Its knowledge base adds that this isn't a guarantee (Supabase KB).

That is why apps with few but real users get caught: a booking tool for one small business, an internal app used once a week, a product waiting for its launch. Supabase cannot tell those apart from abandoned experiments. Pausing is a rule of the Free plan: Supabase states that projects on a paid plan are never paused for inactivity.

  • A pause keeps the data and settings. Resuming returns the project to its previous state (Project pausing).
  • The restore window is limited. As of 2026-11-21 the docs give 1 year from the pause, because backups are only kept for a limited time and older backups may not work with newer platform versions. Older Supabase posts mention 90 days (changelog, 2024) - go by the current docs.
  • After the window closes the project cannot be resumed from the dashboard. You can still download the database backup and Storage files from the paused project's Project Overview and move them to a new project (Restore after the window). Once a project is deleted, the data and its backups are gone for good.

How to fix it

1. Resume the project

  1. Open the Supabase Dashboard, select the organization, then the paused project.
  2. Click **Resume project** and confirm (Project pausing).
  3. Wait until the dashboard shows the project as running, then rerun the curl check from above. It should no longer return 540.
  4. Click through the app: sign in, load a list, save something, upload a file if the app uses Storage.
Note: Supabase moves a Free project to the latest minor version when a paused project is restored (Upgrading). Minor updates rarely break an app, but test the main flows after the restore rather than assuming nothing changed.

2. Take a backup now, while the project is running

A Free project has no automatic backups, and you can only connect to the database while the project is up. These are the commands from Supabase's own backup guide (Backup and restore using the CLI). They need the Supabase CLI and Docker Desktop. Take the connection string from Connect in the dashboard (use the Session pooler string if your network has no IPv6) and put your database password into it:

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"
Three files: database roles, the structure of your tables, and the data. Keep them somewhere other than your laptop, and never commit them to a public repository - data.sql holds your users' data.
  • These files cover the database only. Files in Storage are not included - Supabase notes the database holds only their metadata (Database backups). Download important Storage files separately.
  • Open data.sql and check that the tables and row counts match what the SQL check showed.

3. Decide how the app stays up from now on

Supabase gives one way to prevent automatic pausing: upgrade to a paid plan. Its knowledge base says that if people rely on what you are building, even with light traffic, you should upgrade (Supabase KB). As of 2026-11-21 the pricing page lists:

  • Pro from $25 per month, including $10 per month of compute credits, which covers one Micro instance (Pricing).
  • A spend cap that is on by default on Pro, so usage above the plan's quota is blocked instead of billed - for the usage items the cap covers (Control your costs). Compute is not one of them.
  • Daily backups on Pro, with the last 7 days available (Database backups).
  1. Check what else is in the same organization. Upgrading applies to every project in it, and plans cannot be mixed within one organization (Billing). Each project needs its own compute, so old experiments in the same organization can add to the bill. Move them to a separate Free organization first with a project transfer, or delete the ones you no longer need after exporting their data.
  2. Upgrade the organization from its Billing settings in the dashboard.
  3. Check the project's compute size in its infrastructure settings. A project upgraded from Free may still run on Nano compute, which paid organizations are billed for at the Micro price. Supabase does not switch it automatically because the change involves downtime - usually under 2 minutes, according to its docs - and recommends moving to Micro when convenient (Compute and disk). Do it at a quiet hour.
  4. Confirm the spend cap setting in the Cost Control section of the organization's billing page.
Warning: Scheduled "keep-alive" requests are a popular workaround on the Free plan. Supabase does say requests from your app count as activity, but it also says a few requests a day is usually enough and not guaranteed. A workaround that can fail silently is not a plan for an app with paying users or real data - and it does nothing about the missing backups.

If the project is past the restore window

  1. In the paused project's Project Overview, download the database backup (the .backup file) and all files from your Storage buckets (Restore after the window). Do not delete the old project before you have both.
  2. Create a new project and set up what is not in the backup: extensions, Database Webhooks, Realtime publications, Edge Functions, Auth settings.
  3. Restore the backup with psql, using the new project's Session pooler connection string. If the downloaded file ends in .gz, unzip it first. Then run psql -d [CONNECTION_STRING] -f /path/to/backup_file.backup. Errors such as object already exists are expected, because the new project already has Supabase's default schemas.
  4. Copy the Storage files with the CLI after supabase login and supabase link --project-ref [NEW_PROJECT_REF]: supabase storage cp /path/to/downloaded/files ss:///bucket_name -r --experimental --remote, once per bucket.
  5. The new project has a new URL and new API keys. Update them in your app - and for a mobile app, ship an update, because the version in the App Store still points at the old project.
  6. Run the row-count query from the check section on the new project and compare it with what you expected.

When to get help

  • The project is past the restore window and the app has users, Storage files and Auth settings to move - and a mobile app that needs an update to point at the new project.
  • The restore finished, but some screens are broken or data seems to be missing, and you cannot tell whether it is the restore, the version update or something unrelated.
  • You are moving from Free to Pro and want to know what else changes: compute size, backups, the spend cap, other projects in the same organization.
  • You have never tested a restore and want to know that your backups actually bring the app back.

Sources

Primary documentation this guide was checked against. Platforms change - if something here no longer matches, the source wins.

Frequently asked questions

Did I lose my data when the project was paused?
No. A paused project keeps its data and settings, and resuming it returns it to its previous state. As of 2026-11-21 Supabase lets you resume it from the dashboard for up to 1 year after the pause. After that you can still download the database backup and Storage files and move them to a new project, as long as the old project has not been deleted.
I got the warning email. How do I stop the pause?
Supabase says that after the warning you can prevent the pause by opening the project in the dashboard or by sending enough requests to it from your app. That stops this pause, not the next one - the same rule applies every week the project is on the Free plan.
Can I keep it alive with a scheduled ping instead of paying?
Supabase counts requests from your app as activity and says a few a day is usually enough, but not guaranteed. For a hobby project that may be acceptable. For an app people depend on, Supabase's own advice is to upgrade to a paid plan, where projects are never paused for inactivity - and a paid plan also adds daily backups, which a ping does not.
How much does it cost to stop pausing for good?
On 2026-11-21 Supabase's pricing page listed Pro from $25 per month, including $10 per month of compute credits that cover one Micro instance, with a spend cap on by default. Each additional project in the same organization needs its own compute. Prices change, so check the pricing page before you upgrade.
My app uses Lovable Cloud, not my own Supabase account. Does this apply?
Not directly. Lovable Cloud backends are managed by Lovable and follow Lovable's rules. Lovable's docs say it pauses a project's backend after about 7 days without activity, that traffic to the published app does not wake it, and that opening the project in the editor wakes a project paused for inactivity. Other pauses, for example when the workspace runs out of credits, show a card in the Database, Users and Storage views with the action that clears them (Lovable docs).
Can a Pro project be paused?
Not for inactivity. Supabase says projects on a paid plan cannot be paused and are not subject to automatic pausing. To pause a Pro or Team project on purpose, you first transfer it to an organization on the Free plan.

Related guides

Fixed-price audit

Want someone to check the whole app, not just this?

A review of data security, production readiness and App Store readiness for apps built with AI tools. 900 USD, a ranked list of fixes within 5 business days.