Move your Lovable website to your own domain

You move a Lovable site to your own domain by exporting the code, building it and putting the files online with us. It takes a few steps, provided your project is static. You can see whether it is in a minute, in one file. After that, one job is left: switching your domain, while your current site stays online.

Lovable itself or your own hosting

Lovable can publish your project itself on a lovable.app address, and with a paid subscription also on your own domain. Your domain then points to Lovable. That route is fine if you are happy with everything in one place.

Moving to your own hosting means something different: the code moves, the domain then points to us, and you manage the files yourself. Handy if you want the site separate from the platform you built it on. With us it runs with SSL, Cloudflare in front and a daily backup. More about our approach for this tool is on hosting for Lovable websites.

Step 1: export with GitHub or download

There are two ways to get to the code.

GitHub sync. You connect Lovable to your GitHub account via the project settings (Project settings, Git, GitHub, Connect). Lovable then creates a new private repository and keeps it in sync with your project. This works on all subscriptions. The advantage: changes you make in Lovable later end up in the same repository, so you can have a new build made.

Download. In the project settings under Git (or at the bottom of the file tree in the code editor) there is an option to download the codebase as a zip. According to Lovable’s documentation, this is reserved for paid subscriptions.

In both cases you get the source code and the files for the database structure. The contents of your database and uploaded files are not included. You can read more about the differences between zip and GitHub in exporting an AI website as zip or GitHub.

Step 2: is your project static?

This is the question everything hinges on. Lovable uses two kinds of projects.

• React with Vite. Older projects. They build to static files in the dist folder. This fits ordinary hosting.
• TanStack Start. Projects created from 13 May 2026 use this. It renders pages on the server and needs a host that runs a server. An older app may have been converted to TanStack Start, so always look in your own package.json.

Open package.json in the main folder of your project and look for @tanstack/react-start.

grep "tanstack/react-start" package.json

If nothing comes back, your project is React with Vite and this article carries on. If a line does come back, a server is needed and your project calls for a custom offer. Send us a WhatsApp message with the GitHub link or the zip, and we will see what is possible and come back with a proposal.

Step 3: build the static site

Once you have the code locally, you build it like this. Lovable names Node.js 22 for this build.

npm ci
npm run build

Do you only have a bun.lock and no package-lock.json? Then use npm install instead of npm ci, or ask us to do it. The dist folder is the result: index.html, an assets folder and any images you have. That is the content that needs to go online. The general background is in hosting a React or Vite website without a Node server.

You do not have to do this yourself. Send us your zip or GitHub link, and we build and upload as part of the free migration.

Your backend stays where it is

A Lovable project usually uses a Supabase-compatible backend: login, database, storage and functions. If you only move the website, that backend keeps running in the same place and your new site simply calls it. So you do not need to take your data with you.

There are a few things to adjust, though.

• Environment variables. The addresses and public key of your backend are in VITE_SUPABASE_URL, VITE_SUPABASE_PUBLISHABLE_KEY and VITE_SUPABASE_PROJECT_ID. They are placed in the files at build time. If you change one, you build again. Never put a secret key in there, because everything with VITE_ is publicly readable.
• Allowed addresses and redirects. If your site uses login, your new domain must be in the backend as an allowed address and as a redirect after logging in. If you forget this, logging in on your own domain will not work.
• Lovable’s own features. Parts such as Lovable’s AI gateway and connected connectors run through Lovable. If you use those, they keep needing Lovable.

If you have a contact form that works through the backend, it keeps working as long as the backend is reachable and your domain is allowed. More options are in a contact form on your AI website.

All pages reachable: the rewrite to index.html

A React site with several pages handles its routes in the browser. If someone opens yourdomain.com/about-us directly, the server looks for a file with that name and does not find it. That is why unknown addresses must be sent to index.html, with a normal 200 status. This applies on every host. With us it is a setting that we switch on for you on request, a message via WhatsApp is enough.

One extra point: on its own hosting, Lovable serves prerendered versions to search engines and social media. On an ordinary host that layer is missing. This can affect how search engines and link previews see your pages.

Switching your domain while the old site stays online

This is the moment your domain moves to us. The order:

1. Put the files online on your new hosting and look at the site.
2. Go through everything: pages, images, logging in.
3. At your registrar, change the nameservers to the two we give you.

Until step 3, your old site stays online, even if it is still with Lovable. After that your domain goes to us, and it can take a while after the change before it is visible everywhere. If you connected your own domain at Lovable, you remove it there as soon as the new site is live. The full step-by-step plan is in connecting a domain name to your AI website.

The Website plan costs € 9 per month, or € 90 per year, see pricing. Order via the order form and choose “made with AI”. An overview of all routes is in putting your AI website online.