How to back up your Lovable app: code, data and files
Last reviewed 21 November 2026
Version history makes it feel as if everything is saved. It isn’t. It covers your code, not your customers’ data or the files they upload. Here’s what Lovable already keeps, what it doesn’t, and a simple routine for the rest.
Connect GitHub so you always hold the code. Lovable keeps a daily database backup for about 14 days, but export your own copy before risky changes. Download uploaded files from Storage separately, because neither backups nor exports include them. Keep a private list of your secrets and settings, since nothing copies those.
What Lovable already keeps for you
| Part of your app | What Lovable keeps | The catch |
|---|---|---|
| Code | Every version, in version history | Reverting restores the code only, not your data |
| Database | A daily backup, kept for about 14 days (backup guide) | Restoring can’t be undone, and doesn’t bring back uploaded files |
| Uploaded files | No backups or older versions are documented | A deleted file may be gone for good |
| Secrets and settings | Nothing outside the project | No backup or export includes them |
| The whole project | Deleted projects can be restored for 60 days, from Workspace settings → Workspace → Recently deleted projects (Lovable’s guide) | That only helps if the project was deleted. After 60 days even Lovable support can’t bring it back |
A simple backup routine
- Connect GitHub. Your code is then copied to a repository you own after every change. Our export guide explains how.
- Bookmark versions that work in version history, so you know exactly where to go back to.
- Export the database before risky changes: More → Database → Manage → Settings → Export data. You can make one export every 24 hours. It includes user accounts and password hashes, so store it like customer data, not in a shared folder.
- Download uploaded files from More → Storage. They aren’t in the database backups or the export.
- Keep a private list of your settings: the names of your secrets (with the values in a password manager), sign-in providers, your domain’s DNS records and every outside service the app uses.
Before you restore anything
- A database restore can’t be undone. Export the current state first, even if it’s broken, so you don’t lose orders or sign-ups made since the backup.
- Files and data can fall out of step. Lovable notes that after a restore, files uploaded since the backup stop appearing in the app.
- Code and data can fall out of step too. Reverting the code doesn’t change the database, so older code may expect data in a shape that has since changed.
- Scheduled jobs and email sending may not come back reliably after a restore. Lovable suggests contacting its support before relying on that.
Is a remix a backup?
Not really. According to Lovable’s remix guide, a remix copies the code and the database structure, but not the data in it, secret values, custom domains or GitHub sync. It can also reach your live services, because keys and addresses written into the code still work. Use it to experiment, not as your safety net.
When to get help
If data has already been lost from a live app, stop making changes and export what’s there before trying anything else. Each restore or revert can make the next one harder. If your app has real customers and no backup routine, that’s worth sorting out before the next big change. See what a Lovable rescue involves.
Questions founders ask
Does Lovable back up my app automatically?
Partly. It keeps every version of your code and a daily database backup for about 14 days. Uploaded files, secrets and settings aren’t backed up, so handle those yourself.
Is a remix a backup?
No. A remix copies the code and the structure of the database, but none of the data, secret values or domains, and it isn’t kept in sync with the original.
Can I get a deleted Lovable project back?
Lovable says deleted projects can be restored for 60 days from Workspace settings, under Recently deleted projects.