Lovable · Export and domain eligibility
Lovable Free: Zip Export, Git Sync, or Custom Domain?
This page covers what you can take off Lovable Free: Git sync versus zip download, in-editor edits, and a custom domain. Zero-credit live-app outcomes stay on credits vs hosting. Plan prices stay on Lovable. Cross-builder generation-versus-hosting is the deployment-limits matrix. This is not a Git tutorial.
Direct answer
Can I export Lovable code and use my own domain on Free?
- Git sync
- Fact Official Git-sync docs: github.com two-way sync is available on all plans. Connecting a project creates a new repository. You cannot import an existing repository into Lovable.
- Zip / codebase download
- Fact Full
.zipcodebase download is documented for paid plans, from the code editor or Project settings → Git. A single open file can be downloaded on any plan. - Code editor
- Fact On Free the editor is read-only. Editing and saving files requires a paid plan. Manual edits do not consume credits.
- Publishing and domains
- Fact Publishing to a
lovable.appURL is available on all plans. Custom domains require a paid plan. - Last verified
- Sep 10, 2026, 8:00 PM UTC
Four different gates, not one “export”
| Capability | Free | Paid |
|---|---|---|
| Git sync to github.com | Fact Documented on all plans. | Same core two-way sync. GitHub Enterprise Cloud data-residency and GitHub Enterprise Server are Enterprise-plan paths. |
Download codebase as .zip | Fact Not the documented Free path. | Editors with access can download the project. Enterprise admins can restrict zip downloads to workspace admins and owners. |
| Edit code in Lovable | Fact Read-only editor. | Edit and save. Each save is a version-history entry. |
| Custom domain | Fact Not included. Use the lovable.app address. | Paid-plan capability. Workspace-owned domains can be bought or connected. |
What this page does not do
- It does not answer whether zero credits take a published site down. See credits vs hosting.
- It does not document GitHub/GitLab setup steps. Official Git-sync pages already do that.
- It does not treat third-party “export is paid-only” posts as Fact. Those posts omit the all-plan Git-sync path.
- It does not infer that a specific workspace’s Enterprise download restriction is on. That remains Unknown — account_dependent.
TraceCheck maintainer: review when Lovable changes Git-sync plan gates, zip-download eligibility, Free editor read-only status, or custom-domain paid-plan rules. Do not treat zip and Git sync as the same export path.