How to back up a Supabase project built with Lovable
The answer depends on a choice you may not remember making. Lovable apps run on one of two backends: Lovable Cloud, the built-in backend, which runs on Supabase’s open-source foundation, or a Supabase project you connected yourself. The first gives you export paths but not the Supabase project. The second is a normal Supabase project, and everything about backing up Supabase applies to it directly.
Which mode is your Lovable app in?
Check the project itself, not your memory. On a team, someone else may have connected Supabase. If your Lovable project’s settings show a connected Supabase project, you are in connected mode: a real Supabase project sits behind the app, with a dashboard its owner can open. If the backend was enabled inside Lovable and no Supabase project is connected, you are on Lovable Cloud: a database section inside Lovable and no Supabase dashboard. Everything below depends on which one you have.
Connected Supabase: your project, your backups
Lovable’s docs are clear on this: with a connected project, infrastructure, including backups, is managed by you in Supabase. Lovable deploys code and edge functions; the database is yours. So the standard Supabase backup rules apply, starting with the one that surprises people: the Free plan has no automated backups, and plenty of Lovable projects sit on free-tier Supabase.
The fixes are the same as for any Supabase project. From most to least hands-on once set up: a one-off pg_dump right now, a scheduled GitHub Actions workflow (fifteen minutes to set up, and free at side-project scale; the guide covers the egress math), or a hosted service that backs up to a bucket you own and restore-tests the result. If your app accepts uploads, back up its Storage files too: a database backup does not include them.
Backing up a Lovable Cloud project
On Cloud, the Supabase project underneath is not yours. You work through Lovable’s Database section (table view, SQL editor, backups) rather than the Supabase dashboard, and external backup tools (ours included) have no project to connect to. What Cloud gives you is clearly defined: a daily backup of the database, kept for roughly 14 days and restorable in place. Restores are permanent, so anything written after the chosen snapshot is lost. The backups cover the database only; files in storage buckets are not in them.
For a copy you hold yourself, Cloud offers a database export: full structure and data, capped at 5 GB, one export per 24 hours. Know what it leaves out before you rely on it: Storage files, edge function code, and secrets are not in it, and neither are sign-in provider settings or API keys. User accounts and password hashes are included, so if you restore the export into a Supabase project, your users keep their passwords. Treat the export as your database backup. Run it on a fixed schedule, and when it completes, download it and move the copy off Lovable: an export left sitting inside the project disappears with it. Storage files need a separate step: the Storage view lets you select files and download them as a zip archive. It is tedious, but do it whenever you export, because nothing else covers them.
A copy outside the project is also what gets you back when an AI agent deletes the database. In April 2026 a Cursor agent deleted PocketOS’s production database, along with the backups it had access to, in one API call to Railway. Railway restored the data two days later from its own offsite backups, but the newest backup PocketOS could restore by itself was three months old. That case and others like it, with how each one ended, are on our vibe coding statistics page.
Once the app has real users and real data, plan the move to a connected Supabase project sooner rather than later. There is no one-click migration from Cloud, so the export-and-rebuild only gets bigger as the data grows.
If you are choosing today
Cloud is a good default for prototypes, since not having to set up a backend is the reason to build this way. Once the data would hurt to lose, connect your own Supabase project instead. You get the dashboard, the connection string, backups you control, and the option to use any backup tool with it, and you skip the export-and-rebuild migration. Connecting your own project is easy on day one and much more work to do later.
FAQ
Can I run pg_dump against a Lovable Cloud database?
Lovable Cloud runs on Supabase's open-source foundation, but the Supabase project underneath is not yours. You work through Lovable's own database tools (table view, SQL editor), not the Supabase dashboard. Back up with the database export Lovable provides: database only, capped at 5 GB, one per day, with Storage files, function code, and secrets excluded. Export early, because Lovable's docs say there is no one-click migration from Cloud to your own Supabase project.
Does Lovable back up my app's data?
On Lovable Cloud, yes: a daily backup of the database, kept for roughly 14 days and restorable in place. Restores are permanent, and anything written after the chosen snapshot is lost. Storage files are not covered. With a connected Supabase project, Lovable's docs say infrastructure, including backups, is managed by you in Supabase. So the normal Supabase rules apply: daily backups from the Pro plan, nothing automated on Free.
Should I use Lovable Cloud or connect my own Supabase project?
For prototypes, Cloud's no-setup backend makes sense. Once the data matters (customers, orders, anything you would mind losing), connecting your own Supabase project gives you the dashboard, the connection string, and backups you control. It also avoids a manual export-and-rebuild migration later, which gets bigger as your data grows.
Does BackupDrill work with a Lovable app?
With a connected Supabase project, yes, because it is a normal Supabase project. You connect it with Supabase OAuth (BackupDrill creates its own read-only backup role, so no database password is needed) or by running a three-line SQL snippet. You also add a bucket you own on S3, R2, or B2 with scoped credentials. Scheduled backups go into that bucket, restore drills check them, and once you add the project's Storage S3 keys, your uploaded files go into the same snapshot. With Lovable Cloud, no: there is no Supabase project of yours to connect, and that is true for any external backup tool, not just ours.
Sources
- Lovable docs — Lovable Cloud
- Lovable docs — Supabase integration
- Lovable docs — Database (Cloud backups)
- Lovable docs — Advanced settings (database export)
- Supabase docs — Database Backups
- Supabase — Pricing
Facts and prices last verified August 9, 2026 against the sources above. Written by the team behind BackupDrill.
Running a connected Supabase project behind your Lovable app? Start free. The free plan covers weekly backups for one project, and scheduled restore drills start on Solo. Or keep it DIY with the open-source CLI.