Guide No. 1Getting the code
How to export a Lovable site, and what to do with it next
- By
- Off to Press
- Updated
- Reading
- About 9 minutes
Sooner or later, most Lovable projects reach the same moment. The site is built, people like it, and someone asks: can we have the code? Can we put it on our own hosting? Can our marketing team edit it in WordPress?
The good news: Lovable doesn’t lock your code in. You can download it or sync it to GitHub whenever you like.
The less obvious part is what that code is, and why there’s no “export to WordPress” button. This guide covers the exact steps to get your project out, what’s inside, and the realistic routes to WordPress.
Inside the zipA typical Lovable export
In the folder
package.jsonthe libraries it depends onsrc/pages, components and styles- Stylingoften Tailwind-style classes, plus your colours and fonts
- Backend configif you use Lovable Cloud or Supabase
Not in the folder
- Your dataform submissions, users, uploaded files
Menu names in Lovable change from time to time. The steps below match Lovable’s documentation as of October 2026. If a label has moved, the same options live under your project’s settings.
Part 1Getting the code
Two ways to get your code out
Option A: Download the codebase (quickest)
If you just want a copy of the code as it stands today:
- Open your project in Lovable.
- Go to Project settings › Git.
- In the Download codebase section, download the project.
You can also download from the code editor: open the Code view and use Download codebase at the bottom of the file tree. Lovable’s documentation notes the code editor is available on paid plans.
You’ll get a folder containing the full source of your project. Nothing in it is tied to Lovable’s servers except any backend you connected (more on that below).
Option B: Sync to GitHub (best for ongoing work)
If you want the code to stay up to date as you keep building, connect GitHub instead. Lovable keeps the repository in sync in both directions.
- Add a GitHub connection. A workspace owner or admin goes to Workspace settings › Git › GitHub › Add connection (the same option is reachable from Project settings › Git › GitHub).
- Add your account. Click Add account and follow the github.com flow.
- Install the Lovable GitHub app. Choose your personal account or organisation, pick All repositories or Only select repositories, then Install & Authorize.
- Link the project. In Project settings › Git › GitHub, click Connect next to your connection. Lovable creates a new private repository and starts syncing.
Two things worth knowing:
- Lovable syncs one branch, usually
main. Work on other branches won’t flow back into Lovable. - If you disconnect later, the repository stays on GitHub. You don’t lose anything.
Which should you choose?
| If you… | Choose |
|---|---|
| Need a one-off copy for a developer or agency | Download |
| Will keep building in Lovable while someone else works on the code | GitHub sync |
| Want version history and the ability to roll back | GitHub sync |
| Just want to send your code to a developer | Either. A download is quickest |
Part 2What’s actually in a Lovable export
A modern web application, not a website file
Open the folder and you won’t find a set of HTML pages. You’ll find a JavaScript project.
According to Lovable’s documentation, older projects use React with Vite and render in the browser, while projects created from May 2026 use TanStack Start, which renders pages on the server. Every project of a given generation uses the same stack.
In practice you’ll usually see:
- A
package.jsonfile, listing the libraries the project depends on. - A
srcfolder, with your pages, components (buttons, cards, navigation) and styles. - Styling, very often utility classes in the Tailwind CSS style, plus a configuration of your colours and fonts.
- Configuration for a backend, if your project uses Lovable Cloud or connects to your own Supabase project for data, logins, forms or file storage.
What doesn’t come with it
The export is your front end and its configuration. If your site stores data (form submissions, users, uploaded files), that data lives in the backend, not in the folder. If you plan to leave that backend behind, export the data separately from wherever it’s stored.
Can you just host the export somewhere else?
Yes, if you’re comfortable with developer tooling. You’d install dependencies, build the project and deploy it to a host that supports it. That gives you independence from Lovable’s hosting, but not a different way of editing: your content still lives in code. For many teams, that’s the actual problem they were trying to solve.
Part 3Why there’s no “export to WordPress” button
Two different ways of making a page
WordPress and a Lovable project produce web pages in fundamentally different ways:
Your Lovable project
assembles each page from components written in JavaScript. The words on the page sit inside those components. To change a headline, you change the code, or ask Lovable’s AI to.
WordPress
stores content in a database and renders pages through a PHP theme. Editors change words, images and pages in the block editor; the theme decides how they look.
So moving a site means two tasks: the design becomes a theme, and the content moves out of the code into places editors can reach.
That’s also why there’s no official “Lovable WordPress plugin” (as of October 2026): nothing you install could know what your site looks like.
Part 4Your options for getting to WordPress
Four realistic routes, honestly compared
-
Route 1: Rebuild it in a page builder
A WordPress developer (or you) recreates the design using a page builder plugin such as Elementor.
- Good for
- small budgets, simple pages, teams already fluent in that builder.
- Watch out for
- it’s an approximation by design. Spacing, type and animations are re-created by eye with the builder’s options, so details drift. Page builders also add weight, which can hurt Core Web Vitals.
-
Route 2: Use an automated converter
Several tools now promise to convert AI-built sites into WordPress themes automatically.
- Good for
- a fast first draft, or a developer who’ll finish the output.
- Watch out for
- check what “editable” means in the result (proper blocks, or raw HTML inside one block?), and look closely at animations, which are commonly simplified or dropped. Budget time for finishing.
-
Route 3: Go headless
Keep your React front end, and use WordPress only as a content store that the front end reads from.
- Good for
- teams with developers who want to keep the React code.
- Watch out for
- two systems to host and maintain, and editors still can’t change layouts without a developer. Plugins that affect the front end (SEO plugins’ output, forms, page layouts) need custom integration.
-
Route 4: A custom theme rebuilt 1:1
Your design is rebuilt as a custom WordPress theme, all your content is imported into native blocks and content types, animations are re-created, and every page is checked against the original.
- Good for
- sites that have to look exactly as designed and be run by non-developers.
- Watch out for
- it’s only as good as the checking. Ask for page-by-page comparisons before you approve it.
This is the route we take at Off to Press: our own AI agents do the conversion, and a person checks every page against your original. See what’s involved in converting Lovable to WordPress.
Part 5Prepare your project before you move
A pre-migration checklist
Whichever route you pick, do these first. They save time and avoid nasty surprises.
- Freeze the design. Agree a version to convert. Changes during a migration are where budgets go.
- Export the code using Option A or B above, even if your developer only asks for the URL.
- List every page and URL. Include pages that aren’t in the navigation. This becomes your redirect map.
- Note every form and where it sends. Email address, CRM, spreadsheet, webhook.
- List anything that needs a login or reads from a database. Decide whether it moves or stays.
- Record metadata. Titles, descriptions, social images. If you used Lovable’s SEO review, keep its findings.
- Collect assets. Logo files, fonts (and their licences), original images at full resolution.
- Export your data from Lovable Cloud or Supabase if you’ll retire the backend.
- Decide who’ll edit what. This determines which content becomes editable fields and content types.
- Read the SEO side. Our migration SEO checklist covers redirects, canonicals and what to check after launch.
Part 6Short answers
Frequently asked questions
Does Lovable own my code?
Lovable lets you download your codebase and sync it to your own GitHub repository at any time. Check Lovable’s current terms for the legal detail.
Can I keep using Lovable after exporting?
Yes. Exporting doesn’t change your Lovable project. With GitHub sync you can keep building in Lovable and in code side by side.
Is my Lovable site bad for SEO?
Not necessarily. Lovable’s documentation says newer projects render pages on the server and older ones serve pre-rendered pages to search engines. Teams usually switch because of who edits the site and which tools they need, not because of search engines. If you’re weighing it up, read Lovable vs WordPress for content teams.
Do I need to export my code to work with you?
It’s what we ask for first: send us the zip, or a GitHub link. If you can’t export, your published site’s link is enough to start. The code makes the copy faster and more exact.