Restoring a Backup
If you enabled backup during a clone, you can restore the data at any time — even if the source project has been deleted.
What Is a Backup?
A backup is a snapshot of the data copied during a clone. It contains:
- The data from each table (rows)
- Metadata (table names, schema, row counts)
The backup is stored independently from your Supabase projects.
How to Restore
- Go to Dashboard > Clones > [the clone with backup]
- Check that a Restore button is visible (indicating a backup exists)
- Click Restore
- Confirm the target project
- The restoration starts
Progress is displayed in real time, just like a regular clone.
What Is Restored
- Schema — tables are created if they do not exist
- Data — the rows from the backup are inserted
Important: The restoration only covers base data. Edge Functions, storage files, Auth users, and other components are not included in the backup. To recover them, re-run a clone from the source project.
Limitations
| Limitation | Explanation |
|---|---|
| No deletion | The restoration adds data — it does not delete existing rows in the target |
| No rollback | There is no automatic rollback after a restoration |
| Schema changes | If the target schema has changed since the backup, column errors may occur |
| Limited components | Only table data is saved, not Edge Functions, storage, etc. |
When to Use Restoration?
- The source project is no longer available
- You accidentally modified the target and want to return to the post-clone state
- You want to apply the same data to another project
Next Steps
- Clone Options — Enable backup during a clone
- Verifying a Clone — Verify after restoration