Your data
Does Base44 Back Up Your App?
Yes — but only the table records, only on eligible plans, and only inside Base44. Backups are automatic and free to set up (there's nothing to switch on), but they cover the table data Base44 manages for your app — not your uploaded files, not your app's users, and not the rest of the app. It's a safety net inside the rental, not a copy you own.
What it is
How Base44 backups work
Base44 backs up your app's data automatically as it changes. If records are edited, imported, or deleted by mistake, you can look back at what your tables held earlier, download a copy, or restore your data to that point in time. You find all of it under Dashboard > Data > Backup & Restore in the app editor: a list of every backup for your app, newest first, each showing when it was taken and how many tables changed at that moment.
Restoring rewrites the records in the tables you choose so they match the point in time you picked. You can put back a single table or every table at once, and you can undo a restore afterwards — Base44 saves your current data before the restore starts. Record IDs stay the same, so links between tables keep pointing at the right records. Records added after the point you restore to aren't deleted for good — they go to trash, where you can bring them back within 30 days. Restores run on production data only, and nothing else in the app changes.
That's a genuinely useful safety net — against the bad bulk import, the accidental delete, the "what did this table look like yesterday?" moment. What it isn't is a whole-app snapshot. That distinction is where the trouble starts.
The honest split
What’s covered — and what isn’t
Backed up
- Table records. The rows in the tables Base44 manages for your app — this is what "automatic backups" means here.
- Point-in-time review. See what your tables held at any saved point, and which tables changed.
- Single-table or full restore, with an undo if you change your mind.
- Per-table CSV download — the one way to keep a copy outside Base44.
- Deleted records, restorable for 30 days on any plan.
Not backed up
- Uploaded files. Files in your library or live app aren't table data — they sit outside the backup entirely.
- Your app's users. Accounts, logins, sessions — a data restore can't hand those back.
- Everything else about the app. A restore changes records only; nothing else in the app changes with it.
- A portable whole-app snapshot. There is no "download my app" backup — just per-table CSVs.
The pattern to notice: everything the backup can give back is also everything that never leaves Base44's building. See also the database you can't connect to — same wall, different door.
Retention
How long backups stick around — and who gets them
Automatic backups are an eligible-plans feature: independent checks of Base44's plans in October 2026 put point-in-time backups at about 7 days on Elite and about 30 days on Enterprise. Plans move around, so treat those as current-as-checked and confirm your own plan in the dashboard.
Below those plans, your backup strategy is whatever you export yourself. One floor stays put on every plan: deleted records can be restored for 30 days, no matter what you're paying. That's the last-chance net under everything else.
So below Elite, a bad bulk update is only as recoverable as your last export. Which brings us to the download button.
The exit hatch
The download button is a CSV, not an exit
Base44's docs describe exactly one way to keep a copy of your data outside Base44: open the Backup & Restore tab, expand an entry, and click Download CSV — next to the table you want. One table. Manually. There is no "download everything" button, no scheduled export to your own storage, no backup file you can point a migration tool at.
And the backup history itself lives in the app editor — you access it through your Base44 app, not as files you hold. Export what matters before you cancel (what cancellation leaves behind), because the CSVs you downloaded are the only copy that survives outside Base44.
This is the part that surprises people: "backed up" and "mine" are two different things. The backup protects you inside Base44 — from mistakes you make there. It was never designed to hand you your data and wave goodbye.
The fix
Own your backups
The answer to "does Base44 back up my app?" should never be the end of your thinking — it should be the start of your own backup habit. While you're on Base44: download the tables that matter as CSVs on a schedule you choose, and keep a separate copy of every uploaded file, because those never enter a backup at all.
The durable version is infrastructure with your name on it. A Postgres database in your own Supabase project gives you automated daily backups you configure, point-in-time recovery you control, and a database file you can pick up and move anywhere. That's the normal state of affairs for software: the backup is yours because the database is yours. That's what OffRamp sets up — your app rebuilt on Supabase, Vercel, and GitHub accounts in your name, with backups that answer to you, not to a plan tier.
FAQ
Questions, answered honestly
Does Base44 back up my app automatically?
Partially. Base44 backs up your table data automatically as it changes — on eligible plans, with nothing to switch on. But the backup covers table records only: not uploaded files, not your app’s users, and not the rest of the app.
How long does Base44 keep backups?
Point-in-time backups are kept about 7 days on Elite and about 30 days on Enterprise, per independent checks of Base44’s plans in October 2026 — and automatic backups are an Elite-and-up feature. On any plan, deleted records can be restored for 30 days. Confirm your plan’s current limits in the dashboard, since plans change.
Do Base44 backups include uploaded files?
No. Backups cover the table records Base44 manages for your app — uploaded files in your file library or live app aren’t part of the backup. Export them separately before you need them.
Do Base44 backups include my app’s users?
No. The backup restores table records — your app’s users, their logins, and sessions aren’t something a backup can hand back. When you migrate, users have to be rebuilt (for example, by re-inviting accounts and sending password-reset emails).
Can I download a full backup of my Base44 app?
Not in one click. You can download individual tables as CSVs from the Backup & Restore tab — table by table, manually. That’s the only way Base44 documents to keep a copy outside the platform. (See the export guide for the full picture.)
If I cancel Base44, do my backups stay available?
Don’t count on it. Backups live in the app editor’s Backup & Restore tab — they’re accessed through your Base44 app, not handed to you as files. Export what matters before you cancel, because the CSVs you downloaded are the only copy that survives outside Base44.
Your data should answer to you.
Connect your Base44 account from the OffRamp home page. The free analysis takes about a minute — what’s portable, every gap, and your fixed quote — and your Base44 app stays untouched throughout.
Start your free analysis