Supabase reset database is a powerful workflow that lets teams quickly return a Postgres schema and data to a clean state during development or testing. This operation helps maintain predictable environments and reduces time spent debugging residual data issues.
Below is a concise reference that outlines common patterns, precautions, and daily workflows teams rely on when managing schema and data resets in Supabase projects.
| Reset Type | When to Use | Impact on Data | CLI / SQL Tool |
|---|---|---|---|
| Schema + Data (Drop & Create) | Local development, test suites | All tables emptied, sequences reset | supabase reset |
| Schema Only | Migrate structure without touching seed data | Tables preserved if not changed | supabase migration reset |
| Targeted Truncate | Preserve reference tables, clear user rows | Selected tables emptied, sequences handled | TRUNCATE TABLE ... RESTART IDENTITY |
| Point-in-Time Restore | Recover from accidental deletes in staging | Data returned to a prior timestamp | Backups + pg_restore |
Understanding Supabase reset database mechanics
How the command orchestrates a clean slate
The supabase reset command drops all database objects defined in your schema, recreates them from migrations, and can reseed initial data. It is designed to mirror the experience of creating a fresh Postgres instance, but without leaving your local project directory.
Under the hood, the CLI connects to your project's database, disables triggers, and drops objects in a dependency-safe order. Once the schema is rebuilt, it replays your migration files in sequence, ensuring the final state matches your source definition.
Differences between reset and migration rollback
While migrations can be rolled back individually, reset is a blunt instrument that returns the database to a pristine baseline. Use rollback when you need to undo a single change, and use reset when you want to start over completely without manual downgrades.
Reset workflows for development and testing
Local development cycle with rapid restarts
During active feature work, developers often reset the database at the end of a session to prevent test pollution. This practice keeps integration tests deterministic and avoids subtle bugs caused by leftover rows or conflicting keys.
Combine reset with seed scripts that populate lookup tables and mock users so that each fresh run starts from a known, repeatable state. The result is a fast inner loop where you can iterate on components and API routes with confidence.
Integrating reset into CI pipelines
CI environments benefit from resetting before each test suite to guarantee isolation between runs. By executing supabase reset and then running migrations, you ensure that test artifacts never leak across jobs or branches.
For large projects, you can optimize this flow with snapshotting or caching strategies, but the core principle remains the same: a clean database surface reduces flaky tests and makes debugging straightforward.
Production safeguards and staging strategies
Protecting critical data while enabling experimentation
Never run supabase reset against a production primary database. Instead, apply it in staging or ephemeral preview environments where data can be discarded safely. Treat production changes as reversible migrations with verified backups, not destructive resets.
Use role-based access controls and environment variables to ensure that reset capabilities are only available to trusted workflows. This minimizes the risk of accidental execution and keeps production data governance aligned with compliance requirements.
Backup-driven recovery as a safety net
Before performing any destructive operation in staging, trigger an automated backup so you can restore to a prior point if needed. Pair this with scheduled backups for important pre-production datasets to balance agility with safety.
Best practices for managing database state with Supabase
- Run supabase reset only in local and CI environments, never in production.
- Keep seed scripts idempotent so that repeated executions after a reset remain consistent.
- Use targeted TRUNCATE for selective data clearing when you want to preserve schema and reference data.
- Automate backups for staging and pre-production to enable quick recovery after destructive operations.
- Document the reset flow in your repository README so new contributors can onboard quickly and safely.
FAQ
Reader questions
Will supabase reset database delete rows from tables added outside migrations?
Yes, reset drops and recreates the entire schema based on your migration files, so any tables or changes not reflected in migrations will be lost.
Can I reset database without affecting connected applications?
Connected applications will experience connection drops during the reset process. Use project health checks and retry logic to handle transient disconnects gracefully in development environments.
Does supabase reset also clear storage and edge functions data? Reset targets the Postgres database only; Storage buckets and Edge Functions state remain untouched unless you explicitly remove them through their respective dashboards or CLI commands. How do I restore data if I ran reset on the wrong environment?
If automated backups exist for that environment, use the project restore feature or point-in-time recovery to revert to the last known good state before the reset occurred.