Put your Lovable app on your own domain, step by step
Short answer: You can put a Lovable app on your own domain without Lovable's paid plan. Get the code out through GitHub, build it once so you have a dist folder, and drop that folder on dropthehassle.com: it goes live on a free HTTPS link straight away, no account needed. Then buy a .com there (no DNS settings to touch) or point a domain you already own with one A record. If your app uses Lovable Cloud or Supabase, that backend stays where it is and keeps working.
You already built it. Now it's live under your name. This page is for you if Lovable asks for a paid plan before you can use your own domain, or if you just want your app somewhere you control. No coding knowledge needed, but you will copy three short commands, or ask an AI tool to run them for you.
Your AI can publish. It can never spend your money.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 30 September 2026.
First, one thing to know
Lovable shows you a working app, but what's inside your project is the recipe, not the finished dish. Before anyone can host it, it has to be built: turned into a folder of plain files (usually called dist) that a browser can open. You do this once each time you want to publish a new version.
Step 1. Get your code out of Lovable
- In Lovable, connect your project to GitHub. GitHub is a free website that stores code; the connection is available on every Lovable plan.
- Open your project on github.com, click the green Code button, then Download ZIP.
- Unzip it. You now have a folder with your project in it.
(On a paid Lovable plan you can also download the code directly.)
Step 2. Build it once
Option A: on your own computer.
- Install Node.js from nodejs.org (the "LTS" version). It's the free program that does the building.
- Open a terminal in your project folder. A terminal is the window where you type commands: on a Mac, right-click the folder and choose Services, then New Terminal at Folder (or open Terminal, type
cdwith a space, drag the folder into the window and press Enter); on Windows, open the folder, click the address bar, typecmdand press Enter. - Type these two commands, pressing Enter after each and waiting until it finishes:
npm install
npm run build
A new folder called dist appears. That's your finished site.
Option B: let an AI do it. If you use Claude Code, Cursor or Codex, open the project there and ask: "Build this project and deploy the dist folder with npx -y dropthehassle deploy. Show me the live link and the claim link." Then skip to step 4.
Step 3. Upload the dist folder
- Go to dropthehassle.com and click Upload (free). You do not sign in first.
- Click Drop your folder. The next screen says Drop your folder or .zip. Drop the
distfolder, or a .zip of it. The other control, or browse, picks a folder on your computer. It does not pick a zip. - A few seconds later your app is live on a free address like
yourname.dropthehassle.app, with HTTPS (the padlock). No account, no card.
A zip that still has dist inside another folder is fine. That dist folder is what goes live. A zip of the project before you build is refused.
Step 4. Claim it within 7 days
Click Claim this site, type your email, and enter the 6-digit code we send you. Now the site is on your account. Until you claim it:
- the claim link works for 7 days; after that an unclaimed site is removed;
- search engines are asked not to list it (it's marked "noindex");
- there's a small bar at the bottom. It says Made with DropTheHassle and has a Claim this site link. Visitors can close it. It also has a Report abuse link;
- it can be at most 25 MB. After claiming, uploads can be up to 100 MB.
Step 5. Put it on your own domain
- Buy the domain here. Search a name in your dashboard and pay yourself. The domain is attached to your site automatically, so there are no DNS settings to touch. A .com is EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year.
- Use a domain you already own. Keep it where you bought it and add one A record. An A record is one line in your domain's settings that says which server your site lives on. You set it once, at the company where you bought the domain, using the address shown on your screen. HTTPS follows by itself.
If your app has a backend (Lovable Cloud or Supabase)
We only host the front end (the pages people see). Your backend (the database, logins and server functions in Lovable Cloud or Supabase) stays where it is and keeps its own plan and costs. The published site keeps talking to it, as long as:
- the
.envfile (it holds the address of your backend) is in the project folder before you build; - your new domain is on the list of allowed login addresses, if people sign in. In Supabase that's Authentication, then URL Configuration. For Lovable Cloud, check Lovable's docs for where it keeps this setting.
Good to know
- Sub-pages and refreshes work. When an address isn't a real file, the site serves your
index.html, so/aboutor/dashboardstill opens after a refresh. - Only finished files. A folder that still needs building is refused, and so is anything that needs its own server to run (PHP, a Node or Python server).
- Your AI can publish, but it can never spend your money. Buying a domain is always your own click.
- Stuck on a domain you connected inside Lovable? See Lovable custom domain not working.
Questions
Can I use my own domain on Lovable's free plan?
Not inside Lovable: custom domains in Lovable need a paid plan. You can still put the app on your own domain by building it once and publishing the dist folder on DropTheHassle. The free link costs nothing. A .com is EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year.
How do I get my Lovable app off Lovable?
Connect the project to GitHub (every plan can), download the code as a ZIP from GitHub, run npm install and npm run build, and upload the dist folder that appears.
Will my Lovable Cloud or Supabase backend still work?
Yes. The backend stays where it is, and the published site keeps talking to it. Make sure the .env file is in the folder before you build, and add your new domain to the allowed login addresses if people sign in.
My Lovable domain is not working. What now?
If you connected the domain inside Lovable and it's stuck (SSL pending, Offline, a Cloudflare error), follow the fixes on our Lovable custom domain not working page. If you'd rather skip DNS, publish the built folder here and buy the .com with the site.
Do refreshes and sub-pages work?
Yes. When an address isn't a real file, the site serves your index.html, so a page like /about still opens after a refresh.
What does it cost?
The yourname.dropthehassle.app link is free and needs no card. A .com is EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year.