Blog
How to verify a Supabase backup can be restored
A green backup job proves a file was written. Proving it restores takes four specific checks.
Read articleHow to back up Supabase with the CLI
The three supported dump commands, the restore check that matters, and the project components a database export does not contain.
Read articleHow to back up Supabase on the free plan
Free projects receive no automatic backups at all. Here are three ways to get one, and what each leaves out.
Read articleHow to download a Supabase database backup
Create a portable PostgreSQL dump and record the Storage, Functions and settings that are not inside it.
Read articleHow long should you keep Supabase backups?
Choose retention from detection time, recovery needs and legal limits, not only storage cost.
Read articleSupabase backup without sharing the database password
How ReviveDB uses a unique read-only Postgres login for each backup while keeping the broader Supabase OAuth permission explicit.
Read articleHow to restore a Supabase backup to a new project
A safe Supabase recovery keeps the source intact until the new project has passed database, Auth, Storage and application checks.
Read articleSupabase backup and restore checklist
A practical recovery sequence for the database, Auth, Storage, Edge Functions, settings and external services.
Read articleWhat pg_dump leaves out of a Supabase backup
A scheduled pg_dump protects the database. Supabase Storage files, Edge Functions and restore testing need separate work.
Read articleDo Supabase backups include Storage files?
No. Supabase database backups keep Storage metadata, not the files. Here is what to copy and how to check it.
Read article