How to back up a Lovable app's data
Lovable keeps every version of your code and can push it to GitHub. None of that contains your data. The people who signed up, the rows they created and the files they uploaded sit in the backend, and a Lovable app has one of two: Lovable Cloud, or a Supabase project in your own account.
Check which backend your app uses
If you can open the project in your own Supabase dashboard, the app uses your own Supabase project. If the database is only reachable through Lovable, it runs on Lovable Cloud.
| Lovable Cloud | Your own Supabase project | |
|---|---|---|
| Who runs the infrastructure | Lovable | You, in your Supabase account |
| Backups and pausing | Handled inside Lovable Cloud | Managed by you in Supabase |
| Export | Export data in the Cloud advanced settings | pg_dump, the Supabase CLI or a backup service |
| ReviveDB can connect | No | Yes, through Supabase OAuth |
Lovable's Supabase integration documentation puts backups, instance size and pausing on your side once you use your own project.
If your app runs on Lovable Cloud
Lovable Cloud is built on Supabase, but the project sits in Lovable’s account rather than yours. Its database view offers backup restores, and an export is available in the advanced settings. Check the Lovable Cloud documentation for the current scope and limits of that export.
If the data matters, download that export now and then and keep it somewhere other than Lovable. Moving to your own Supabase project later is possible, but Lovable documents it as a manual export and import, not a button.
ReviveDB only connects to projects in your own Supabase organization, so we cannot back up a Lovable Cloud backend.
If your app uses your own Supabase project
Then your app follows the normal Supabase rules. Lovable does not change them:
- Free projects get no automatic backups. See how to back up Supabase on the free plan.
- Paid plans get daily database backups, kept for 7 days on Pro. They do not include the bytes of Storage files.
- Free projects are paused after a week with too little database activity. A prototype you showed to three people and then left alone is exactly that. See what happens when a Supabase project is paused.
- Supabase backups live inside the project they protect. Deleting the project removes them too.
What a backup of a Lovable app should contain
| Component | What a Lovable app typically keeps there |
|---|---|
| Database | The tables Lovable created through its migrations, and their rows |
| Auth | Users who signed up or logged in |
| Storage files | Uploads, avatars and generated images |
| Edge Functions | Server-side code, such as calls to payment or AI APIs |
| Secrets | API keys you added; only their names can be recorded, the values must be re-entered |
A pg_dump gets you the first two rows of that table. The rest needs a separate copy.
Backing up a Lovable app with ReviveDB
Connect the Supabase project behind your Lovable app through Supabase OAuth; you do not paste a service-role key. ReviveDB backs up the database and Auth, Storage files, Edge Function code and deploy metadata, along with Storage bucket settings, stores each recovery point in the EU and restore-tests the database of every backup in an isolated PostgreSQL instance. Your live project is not affected.
The Free plan covers one project with a weekly backup plus one manual backup per day, and keeps the latest three recovery points. If you are about to give Lovable a prompt that rewrites your tables, start a manual backup first.