# Supabase project paused: restore it or export the data

> Why Supabase pauses free projects after 7 days of low activity, how to resume one, restore the backup after the window, and how to stop it recurring.

Source: https://scribase.com/supabase-project-paused

Supabase pauses Free Plan projects that show low activity over 7 days. A paused project refuses every request until you resume it. You can resume it from the dashboard for up to a year, and you can always download its last backup.

## Why it was paused

Supabase pauses Free Plan projects that show low activity over a 7-day period to save server resources. Their docs say a few user requests to the database each day over the previous week is usually enough to avoid it.

Projects on a paid plan are not paused for inactivity. So the two permanent fixes are: keep real traffic on the project, or move it to a plan (or a provider) that does not pause.

## Sources

- [Supabase: Project pausing](https://supabase.com/docs/guides/platform/free-project-pausing)

## Resume it from the dashboard (within 1 year)

1. **Open the paused project** — In the Supabase dashboard, select the organization, then the paused project.

2. **Click "Resume project" and confirm** — The project returns to its previous state with its data and configuration. Free projects move to the latest minor Postgres version when they are restored, so give it a few minutes and test your app afterwards.

3. **Take a copy right away** — Free projects do not get downloadable daily backups (Pro keeps 7 days, Team 14, Enterprise 30). Supabase recommends Free users export regularly with the CLI. The next section has the exact commands.

```sh
# Session pooler string from the Connect dialog (IPv4, port 5432)
export DB_URL="postgresql://postgres.<ref>:<password>@aws-0-<region>.pooler.supabase.com:5432/postgres"

supabase db dump --db-url "$DB_URL" -f roles.sql --role-only
supabase db dump --db-url "$DB_URL" -f schema.sql
supabase db dump --db-url "$DB_URL" -f data.sql --use-copy --data-only
```

## Sources

- [Supabase: Project pausing](https://supabase.com/docs/guides/platform/free-project-pausing)
- [Supabase: Database backups](https://supabase.com/docs/guides/platform/backups)
- [Supabase: Backup and restore using the CLI](https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore)

## When resuming does not go cleanly

The dashboard flow above is what is supposed to happen. In practice, people clicking "Resume project" have hit all of the following, each reported on the public issue tracker with a project ref and a date:

- Resume stuck on "Coming up..." with no further progress, and the REST API still unreachable.
- The dashboard shows "Healthy" after resuming, but every one of the project's public hostnames returns NXDOMAIN, so the app still cannot connect.
- The project, or the entire organization, disappears from the dashboard outright: not listed as paused, not listed at all, while the old API endpoint and keys stay live underneath.
- The supabase_functions schema is missing after a restart, which breaks Database Webhooks until someone notices and recreates it by hand.
- A restore reports the project as ACTIVE_HEALTHY while Postgres underneath is still shutting down, so the first queries fail with error 57P03 ("database system is shutting down") right after the dashboard says it is back.

## Sources

- [supabase/supabase#51284: project stuck on "Coming up..." after resume](https://github.com/supabase/supabase/issues/51284)
- [supabase/supabase#48819: Healthy in the dashboard, every hostname returns NXDOMAIN](https://github.com/supabase/supabase/issues/48819)
- [supabase/supabase#50096: project and organization missing from the dashboard](https://github.com/supabase/supabase/issues/50096)
- [supabase/supabase#48427: production project missing, possible data loss](https://github.com/supabase/supabase/issues/48427)
- [supabase/supabase#48870: supabase_functions schema missing after a restart](https://github.com/supabase/supabase/issues/48870)
- [firstChoiceTransportation#4: restore reports ACTIVE_HEALTHY while Postgres is still shutting down](https://github.com/BTheCoderr/firstChoiceTransportation/issues/4)

## Export the data without resuming

A paused project does not accept database connections, so pg_dump and supabase db dump cannot reach it. What you can do from the project dashboard is download the backup file and the Storage objects. After the restore window ends, those downloads are the only way to get the data, and deleting the project removes them for good. Download first, delete later.

1. **Download the backup and Storage objects** — From the paused project page in the dashboard. If the backup ends in .gz, unzip it.

```sh
gunzip db_cluster.backup.gz
```

2. **Restore it into a new Supabase project** — Use the new project's Session pooler string. Errors such as "object already exists" are expected, because the new project already has the default Supabase schemas.

```sh
psql -d "$NEW_PROJECT_SESSION_POOLER_URL" -f db_cluster.backup
```

3. **Copy Storage files back, one bucket at a time** — Database backups do not contain Storage objects; the database only stores their metadata.

```sh
supabase login
supabase link --project-ref <new-ref>
supabase storage cp ./downloaded/<bucket> ss:///<bucket> -r --experimental
```

4. **Or restore it on your laptop** — The Supabase CLI can start a local stack from the downloaded file. Supabase notes the earliest Postgres image that supports this is 15.1.0.55.

```sh
supabase init
supabase db start --from-backup db_cluster.backup
```

## Sources

- [Supabase: Restore a project after the pause window](https://supabase.com/docs/guides/troubleshooting/restore-project-after-90-days-pause)
- [Supabase: Database backups](https://supabase.com/docs/guides/platform/backups)

## Stopping it from happening again

- Real usage keeps a project active. A scheduled job that queries the database daily is the common workaround people use; whether it counts as activity is up to Supabase, so treat it as fragile, not a promise. The keep-alive page below has a copy-paste GitHub Actions workflow that does exactly that, with no outside dependency.
- Upgrading the organization to a paid plan stops inactivity pausing for its projects.
- Keep your own off-site dump on a schedule regardless of plan, with the three db dump commands above.

## Sources

- [Supabase: Project pausing](https://supabase.com/docs/guides/platform/free-project-pausing)

[Get the keep-alive workflow](https://scribase.com/supabase-keep-alive)

## How Scribase handles idle projects

Scribase runs the same Supabase API (supabase-js, Auth, Storage, Realtime, REST, Functions) and does not pause idle projects, so there is no resume step and none of the failure modes above (stuck "Coming up...", NXDOMAIN after a resume, a vanished dashboard, a missing schema, a half-up restore) can happen, because nothing is ever paused in the first place. An idle project scales its compute to zero and wakes on the next request, so the app that was quiet for two weeks still answers on day fifteen. Each project is $5 a month on Hobby or $25 on Pro.

Moving a project is one importer run: schema, auth users with their password hashes, data, RLS policies and Storage objects, finished with row counts and checksums per table. Export is a button in the console, so you can leave the same way.

If the project is still reachable (not yet paused past its restore window), the rescue tool runs that import for you: paste the paused project's connection string, and it lands in a free 72-hour project with no account and no card. Keep it if it works; claim it to make it permanent, or let it expire and nothing is kept.

## Sources

- [Scribase pricing](https://scribase.com/pricing)

## FAQ

**How long does Supabase keep a paused project?**

Their docs say a paused project can be restored from the dashboard for up to 1 year after it was paused. After that, the backup file and Storage objects can still be downloaded from the project page until the project is deleted.

**Can I pg_dump a paused Supabase project?**

No. A paused project refuses connections. Either resume it and then run supabase db dump or pg_dump, or download the backup file from the paused project page.

**Do paid Supabase projects get paused?**

No. Supabase states that paid projects are not paused for inactivity.

**Does resuming change my Postgres version?**

Free projects move to the latest minor version when they are restored, according to the Supabase docs.

**Is pausing the only Free plan restriction, or is there also a project limit?**

There is also a project limit: Supabase's Free plan caps an organization at 2 active projects (a paused project does not count against that cap, but it stays unusable until resumed). Scribase does not pause idle projects and has no cap on how many projects an organization can create.

## Related

- [Supabase keep-alive workflow](https://scribase.com/supabase-keep-alive)
- [Export a Supabase database with pg_dump](https://scribase.com/supabase-pg-dump)
- [Check a connection string](https://scribase.com/tools/connection-string)
- [Migrate from Supabase](https://scribase.com/migrate/supabase)
- [Supabase alternative](https://scribase.com/supabase-alternative)