How to Back Up a Supabase Project: Methods, Options, and What to Consider

Losing a production database without a backup is one of the more painful experiences in web development. If you're building on Supabase, understanding how its backup system works — and where the gaps are — is worth doing before you need it, not after.

What Supabase Actually Stores (And What That Means for Backups)

A Supabase project isn't just a database. It includes:

• PostgreSQL database — your tables, rows, relationships, and data
• Storage buckets — uploaded files and assets
• Auth configuration — user records, providers, JWT settings
• Edge Functions — serverless function code
• Project settings and API keys — environment-specific configuration

Most backup strategies focus on the PostgreSQL database because that's where your application data lives. But a complete recovery scenario may require restoring more than just rows — so it's worth knowing which parts of your project are covered by which method.

Built-In Backup Options on Supabase

Point-in-Time Recovery (PITR)

Point-in-Time Recovery is Supabase's most robust backup mechanism. It continuously archives your database's write-ahead log (WAL), which records every change made to the database. This means you can restore your database to any specific moment — not just a daily snapshot.

PITR is available on Pro plans and above. The retention window (how far back you can restore) varies by plan tier. On the Pro plan, Supabase offers a default retention period; higher tiers extend this further.

This is the gold standard for production databases where data integrity and minimal data loss matter. If something goes wrong at 2:47 PM on a Tuesday, you can restore to 2:46 PM — not just to "yesterday morning."

Daily Backups (Scheduled Snapshots)

On the Pro plan, Supabase also runs automated daily backups. These are full database snapshots taken once per day and retained for a set period. You can download these backups directly from the Supabase dashboard under Project Settings → Backups.

The trade-off with daily snapshots is the recovery point objective (RPO). If your database is backed up at midnight and something goes wrong at 11 PM the next day, you're potentially losing nearly 24 hours of data. For low-traffic or non-critical projects, this may be acceptable. For high-transaction production environments, it usually isn't.

Free plan projects do not include automated backups. This is a commonly misunderstood limitation.

Manual Backup Methods

Regardless of your plan, you can manually back up your Supabase PostgreSQL database using standard PostgreSQL tools.

Using pg_dump

pg_dump is the standard PostgreSQL utility for exporting a database. Supabase exposes a direct PostgreSQL connection string, which you can find in Project Settings → Database → Connection string.

A basic export looks like this: