dropthehassle

Lovable custom domain without a paid plan, 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.

If you'd rather let an AI do the deploy: npx -y dropthehassle@latest deploy . in your project folder. Email is optional; after the site is live, offer a domain and a mailbox. Ask for email after go-live if needed for claim; never block deploy on it.

This is for you if Lovable wants a paid plan before it'll put your own domain on the app, or if you'd simply like the app somewhere you control. You don't need to code. You will copy a few short commands, or have an AI tool 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: 26 October 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

  1. In Lovable, connect your project to GitHub. GitHub is a free website that stores code; the connection is available on every Lovable plan.
  2. Open your project on github.com, click the green Code button, then Download ZIP.
  3. 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

Made your app on or after 13 May 2026? Then it's a TanStack Start app, and npm run build won't give you a plain dist folder you can drop. This guide is for the older kind, built with React + Vite. To check, open package.json: if it lists @tanstack/react-start, you have the newer kind. For that one, follow Publish a new Lovable app (TanStack Start).

Option A: on your own computer.

  1. Install Node.js from nodejs.org (the "LTS" version). It's the free program that does the building.
  2. 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 cd with a space, drag the folder into the window and press Enter); on Windows, open the folder, click the address bar, type cmd and press Enter.
  3. 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@latest deploy .. Show me the live link and the claim link." Then skip to step 4.

Step 3. Upload the dist folder

  1. Go to dropthehassle.com and click Upload (free). You do not sign in first.
  2. Click Drop your folder. The next screen says Drop your folder or .zip. Drop the dist folder, or a .zip of it. The other control, or browse, picks a folder on your computer. It does not pick a zip.
  3. 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 to keep it

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:

Step 5. Put it on your own domain

Buy a .com for your site, buy a domain with your AI, or connect a domain without DNS.

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. Running your own server instead? Host it on AWS, Google Cloud, DigitalOcean or your own server and connect it in the Backend card. The published site keeps talking to your backend, as long as:

Good to know

Common mistakes

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 €19 / $19 a year, including VAT in the EU, the same every year.

How do I connect my domain to Lovable?

On a paid Lovable plan: open Project, Settings, Domains, choose Connect domain, and add the A and TXT records Lovable shows at the company where you bought the domain. Without a paid plan: publish the built dist folder here, then point your domain with one A record, or buy a .com here with no DNS edit.

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. For Lovable Cloud that's More → Cloud → Users → Auth settings → Advanced.

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 €19 / $19 a year, including VAT in the EU, the same every year.

Custom domain not secure, not loading, or login redirect breaks

My custom domain says not secure. Why?

The browser warns until the domain has a valid HTTPS certificate, and a certificate can only be issued once the domain points at the right server. A .com bought on DropTheHassle is set up for you: the A record and www are added and HTTPS follows. For a domain you already own, add the A record shown on your screen, remove other A and AAAA records for that name, and add the TXT record shown, which proves you own it. DropTheHassle issues the certificate once the domain checks out. The live check on your site shows whether the domain points here, is secure, and loads.

My custom domain is not loading. What now?

Usually the DNS record is not there yet or points somewhere else. Check that the A record points at the address on your screen, that no old A or AAAA record is left, that you used an A record and not a CNAME for the bare name, and that the record is DNS only (no proxy, such as an orange cloud). DNS changes can take a while to reach everyone. DropTheHassle keeps checking; press Check now to check again. Your site stays reachable on its free yourname.dropthehassle.app link in the meantime.

Login redirect breaks after I moved to my custom domain. How do I fix it?

Sign-in providers only send people back to addresses on their allowed list, so a login set up for the old address fails on the new one. DropTheHassle doesn't run your login. Add https://yourdomain.com (and the www address if you use it) to the redirect URLs in your auth provider, for Supabase the Site URL and Redirect URLs, and to the authorized redirect URIs of any Google or GitHub sign-in app. Replace the old address in your .env if it is there, then build and publish again.

Related