How to export your Base44 code, and what you really get
Last reviewed 21 November 2026
Base44 lets you take a copy of your app’s code. That’s worth doing, but it isn’t the same as being able to run the app anywhere. The code still talks to Base44’s backend, and your data and users stay there. Here’s what you get, and what leaving would really involve.
On the Builder plan or higher, connect GitHub for an automatic two-way sync, or download a ZIP. You get a React and Vite project with backend functions and table definitions, but not your data, users, secrets or version history. The code still runs on Base44’s backend, which can’t be self-hosted, so leaving Base44 completely means replacing that backend.
Two ways to get the code
- GitHub sync (Builder plan or higher): two-way and automatic. Only the app owner can connect it, and the connection belongs to the workspace. Changes merged to the
mainbranch sync back into Base44, but users see them only after you publish. The branch must be called main, and if there’s a merge conflict, Base44’s AI fix uses credits. See Base44’s GitHub guide. - ZIP download (Builder plan or higher): from the app editor’s more actions menu, choose Export project as ZIP. You need edit access, and it isn’t available from a phone.
After connecting GitHub, you can’t restore versions from before the connection, so make sure the current version is the one you want first.
What’s in it, and what isn’t
| Included | Not included |
|---|---|
| The app’s code, a React and Vite project | Your app’s data. Export each table as CSV |
| Backend functions | Your users and their logins |
| Table definitions and permissions | Secrets and API keys |
| Base44’s SDK, which the code uses to reach the backend | Version history |
Export data from Dashboard → Data, one table at a time, as described in Base44’s data guide.
Why the code still needs Base44
Base44’s developer tools guide is direct about it: exported code still uses Base44’s backend, and running it elsewhere still uses your live Base44 data. The database, sign-in and integrations are run by Base44, and it doesn’t support self-hosting them. Base44’s pricing page says you own your code, data and users. Both are true: you own them, but the running app depends on Base44.
Working on it outside Base44
A developer can clone the repository and run it locally with Base44’s command-line tool. Two cautions from Base44’s docs: running locally against the remote backend writes to your live data, and local test data disappears when the local server stops. The backend tools are marked as beta.
Leaving Base44 completely
That means replacing the database, sign-in and integrations with your own backend, moving the data and users, and rewriting the parts of the code that use Base44’s SDK. It’s a real project, not an export. Before you decide:
- Connect GitHub so you hold an up-to-date copy of the code either way.
- Export your data regularly.
- List what the app uses Base44 for: data, sign-in, email, AI, file storage and integrations.
- Ask a developer to estimate replacing each one, compared with staying.
Questions founders ask
Can I export Base44 code on the free plan?
No. Both GitHub sync and ZIP download need the Builder plan or higher, according to Base44’s docs.
Can I host my Base44 app somewhere else?
You can host the front end, but it still uses Base44’s backend. Base44 doesn’t support self-hosting the backend, so leaving fully means replacing it.
Does the export include my users and data?
No. Data is exported separately as CSV, one table at a time, and users, secrets and version history stay in Base44.