The desktop tool that handles Supabase's permission quirks, trigger conflicts, and sequence drift — automatically. Your data stays on your machine.
Supabase Cloud has strict permission rules. A standard restore fails in 4 different ways every single time.
Event triggers, role grants, and superuser statements in roles.sql and schema.sql get rejected by Supabase Cloud. You can't restore without a superuser account you don't have.
Foreign key triggers fire during data import and reference tables that don't exist yet. The restore crashes halfway through with cryptic "relation does not exist" errors.
After restore, your serial/identity sequences are out of sync. New inserts immediately fail with duplicate key violations. Every. Single. Time.
Supabase's internal schemas (_analytics, realtime, extensions, etc.) pollute your backup. Trying to restore them causes cascading failures on a fresh project.
Snapabase wraps pg_dump, psql, and Supabase CLI with the logic that makes Supabase restores actually work.
Separates Roles, Schema, Data, and Edge Functions into individual files. Granular control over what you restore and when.
Core FeatureAuto-detects and comments out superuser-only statements before restore. Works on Supabase Cloud without any manual editing.
Supabase-SpecificWraps data import with DISABLE/ENABLE TRIGGER USER. FK constraints and row-level triggers stay silent during import.
Supabase-SpecificSyncs all serial and identity sequences to max(id) after restore. No more duplicate key errors on first insert.
Supabase-SpecificSet daily or weekly automatic backups. Runs silently in the background. Checksum SHA-256 on every file for integrity.
AutomationYour connection strings and data never touch any external server. Everything runs on your machine using your local pg_dump and psql.
PrivacyWhy other approaches leave you with a broken restore at 2am.
| Feature | Supabase Dashboard | Snapabase |
|---|---|---|
| Local backup file you own | ✗ | ✓ |
| Restore to different project | ✗ | ✓ |
| Permission error handling | ✗ | ✓ |
| Trigger conflict prevention | ✗ | ✓ |
| Sequence auto-reset | ✗ | ✓ |
| Edge Functions backup | ✗ | ✓ |
| Custom backup schedule | Pro+ only | ✓ |
| Data stays on your machine | ✗ | ✓ |
| Works on Free plan | ✗ | ✓ |
Download the app (Windows / macOS). Paste your Supabase connection string. Snapabase verifies the connection and detects pg_dump, psql, and Supabase CLI on your machine.
postgresql://postgres:[password]@[host]:5432/postgresClick Backup. Watch the real-time log as your database is exported in 4 separate layers. Each file is checksummed with SHA-256.
Select a backup, choose a target connection, click Restore. Snapabase handles all the permission filtering, trigger management, and sequence resets automatically.
Configure daily or weekly backups. The scheduler runs in the background even when the main window is closed.
Snapabase relies on official PostgreSQL and Supabase CLI tools. Ensure they are installed before launching.
Download the installer and note the /bin folder path.
The fastest way to install and update Supabase CLI.
Using Homebrew is recommended for automatic path management.
If macOS blocks the app, go to Privacy & Security and click "Open Anyway".
Ensure you have selected the correct path to psql.exe in the Snapabase Settings tab.
Check if your Supabase project is "Paused" in the dashboard. Resume it to continue.
Your connection strings and backups never leave your machine. Snapabase is 100% local-first.
No subscription. No per-seat fees. Pay once, use forever on up to 3 machines.
Secure checkout via Lemon Squeezy · Instant license key delivery