DOWNLOAD & EXPORT
How to download your Lovable project
You can download your source code from Lovable or sync it to GitHub and download an archive there. Start with the code if you want a local copy. Moving a working app also means accounting for its database, files, and connected services.
Choose a download method
Use a ZIP for a snapshot you can open and inspect. Use Git sync when you want to keep editing or deploy from a repository. Neither choice by itself changes where your live app runs.
| Method | Availability | Best for |
|---|---|---|
| Lovable codebase ZIP | Paid plan and project edit access; Enterprise administrators can restrict downloads. | A one-time local copy |
| Git sync, then GitHub ZIP | Git sync is available on all plans; connecting a repository requires the appropriate project and workspace permissions. | A repository for ongoing work, plus downloadable snapshots |
Download the codebase directly
Open your project’s Code tab. At the bottom of the file panel, choose Download codebase. You can also find it in Project settings → Git. Save the ZIP and extract it into a new folder. The single-file Download control is different: it saves only the open file.
If the codebase button is disabled, check your plan, project edit access, and any Enterprise download restriction with the workspace administrator. Do not confuse the ability to view the published app with permission to export its source.
Export through GitHub on the free plan
In Project settings → Git → GitHub, select the intended workspace connection. An administrator may need to add the connection first. Connecting the project creates a repository and starts two-way sync. Check the connected account and sync status before downloading.
Open the resulting repository on GitHub. Select the branch you need, open Code, and choose Download ZIP. Extract the archive to read the source. This does not require a terminal. A ZIP is a snapshot; it does not include Git history or automatically receive future changes. For ongoing development, use a clone of the repository instead.
What did you actually download?
Inspect the extracted folder before calling it a backup. A project can contain source code, build configuration, static assets committed to the repository, and database migration definitions. The definitions describe changes to a database; they are not a copy of the customer records currently inside it.
Uploaded photos and documents can live in a storage service rather than in the repository. An image that appears in your app may therefore be absent from the archive. Inventory those files separately, including whether access is public or restricted.
| Item | What to check |
|---|---|
| Source and build files | Verify the expected files and lockfile are present. |
| Database definitions | Identify schema files without assuming they contain live records. |
| Customer uploads | Find the storage buckets and download process. |
| Service credentials | Identify required settings; keep secret values out of source control. |
Continue editing locally
Open the extracted folder in your editor and read its README and package.json. Use the project’s documented runtime, package manager, and startup instructions. Keep the original archive intact so you can compare your changes.
Before running unfamiliar code, review installation scripts and configuration. A local development error can mean a missing environment setting or dependency, rather than a broken export. Work on a copy and use test services where possible; a local app can still make calls to a live backend.
Move the whole app off Lovable
Write down two decisions: where the application will run and where its backend services will run. Moving the frontend does not automatically move the backend. If all you need is a code copy, stop here; there is no reason to turn an export into a migration project.
If you do want a complete move, trace the app’s sign-in, records, uploads, payments, email, and AI calls. Assign each dependency a destination and a check that will demonstrate it works there.
Troubleshoot an incomplete export
| Problem | Next check |
|---|---|
| No codebase download | Confirm access and plan; use the official Git sync route if appropriate. |
| Wrong files in GitHub | Compare the connected repository, selected branch, and sync status. |
| App fails locally | Read the first startup error and compare required settings with the README. |
| No customer data in the ZIP | Arrange a separate database export; source files are not live records. |
| Images missing | Check whether the URLs point to remote storage rather than repository assets. |
Printable export checklist
Use your browser’s Print command to keep this checklist. No email address is needed to read or print it.
- Record the project, branch, and date of your source copy.
- Extract the archive and confirm the README, build configuration, and expected source files.
- List database records, uploads, and external services separately.
- Record configuration names without placing secret values in shared notes.
- Decide whether you need local editing, new hosting, a backend move, or all three.
- Keep the existing app running until a replacement has been checked.
Official sources
Product instructions were checked against these documents on 2026-10-15. This is documentation research, not a claim of testing on your app.