Supabase takes a daily backup of every Pro, Team and Enterprise project. Pro keeps 7 days, Team 14 and Enterprise up to 30. Free projects get none, and the docs recommend exporting with supabase db dump yourself.
Whether you can download one of those backups depends on its type. Projects on Postgres 15.8.1.079 and newer get physical backups: you can restore the project from them in the dashboard, but there is no file to download. Supabase's knowledge base says the same for projects with PITR, where the downloadable backup.gz is no longer generated.
For most current projects, a copy you hold yourself means taking a logical dump:
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 $DB_URL is the connection string under Connect in the dashboard. The direct host resolves to IPv6, so from a network without IPv6 use the Session pooler string. Dump as postgres: with a role that cannot bypass row-level security, pg_dump stops on the first table with a policy (pg_dump on Supabase: "query would be affected by row-level security policy").
A dump kept in your own bucket is also the only copy that outlives the project. When you delete a Supabase project, its backups are deleted with it.
Storage files are in none of these backups, the dashboard ones or the dump. The database holds the storage.objects rows, so a restore brings back the list of files without the files. Copy the buckets through the S3-compatible endpoint:
aws s3 sync s3://<bucket> ./storage/<bucket> \ --endpoint-url https://<project-ref>.storage.supabase.co/storage/v1/s3 \ --region <project-region> What a Storage copy should record besides the files is in Do Supabase backups include Storage files?
Edge Function code is not in the database either. supabase functions download <name> gets the deployed source. The other parts of a project a dump misses are in What a Supabase database backup leaves out.
Before you rely on a dump, restore it into a throwaway Postgres and compare row counts per table with the source. psql carries on after a failed statement unless you run it with -v ON_ERROR_STOP=1, so without that flag an exit code of 0 says little. The full set of checks is in How to test the database layer of a Supabase backup.
I keep a table of what each plan includes and what each option leaves out at https://revivedb.dev/supabase-backup. I build ReviveDB, a backup service for Supabase. Everything above works without it.

