Can you add a custom domain to a Lovable app?
Yes, on a paid Lovable plan: publish the project, open Project → Settings → Domains, add the domain, and create the A record (185.158.133.1) and the TXT verification record it shows at your registrar. On the free plan new domains cannot be connected and the app stays on its lovable.app address, so the other route is to export the app to GitHub, host it elsewhere and attach the domain there. Hosting the export on Hostwares takes the domain on the site's Domains tab, with the certificate issued once DNS resolves, and you keep editing in Lovable.
Step by step
- 1
Decide where the domain should point
If you are on a paid Lovable plan and happy with Lovable hosting, use route A. If you want a flat price, your own environment variables, or a host that is not tied to your Lovable subscription, use route B: the app's code is yours and runs on any host.
Both routes can run at once. Lovable keeps publishing to its lovable.app address while the domain points wherever you choose.
- 2
Route A: connect the domain inside Lovable
Publish the project first. Then open Project → Settings → Domains and add your domain. For a root domain Lovable shows an A record pointing at 185.158.133.1 plus a TXT verification record at _lovable (value starting lovable_verify=); for a subdomain, or when the domain sits behind a proxy such as Cloudflare, it shows a CNAME to your project's lovable.app address instead. Create those at your registrar, wait for the status to turn Live, then set the domain as primary.
A paid plan is required to connect a new domain; a domain already connected keeps working after a downgrade. The www subdomain is not added for you, so add it separately if you want both.
Records Lovable asks for (root domain)
A @ 185.158.133.1 TXT _lovable lovable_verify=<value shown in Settings → Domains> - 3
Route B: export to GitHub and deploy the repository
In Lovable, connect the project to GitHub; Lovable creates the repository and keeps it in sync. In Hostwares, go to Dashboard → Deployments → New, pick that repository and a pack. The Vite build is detected and the build and start commands are filled in. Payment comes first: the order creates an invoice and the build starts once it is paid.
Or from a terminal
hw ask "deploy my Lovable repo as my-app" - 4
Route B: attach the domain on the Domains tab
Open the site, Domains tab, enter app.example.com, and create the DNS record the tab shows at your registrar. The certificate is issued once the record resolves. From an agent the same step is the add_domain tool; from the terminal, ask hw to point the domain at the site.
If the site already had a domain, add_domain replaces it, so the tool asks before taking a live domain off.
- 5
Update the sign-in redirect and check a deep link
If the app uses Supabase Auth, add the new domain to the Site URL and Redirect URLs in your Supabase project's Auth settings, or sign-in links keep sending people to the old address. Then open a page other than the home page directly to confirm routing works on the new host.
What breaks, and the fix
- Sign-in links still point at the old address
- Add the new domain to Site URL and Redirect URLs in Supabase Auth settings.
- Deep links return 404 on the new host
- Open a non-home route directly after deploy; if it fails, check the build output is a single-page app and that the start command serves index.html for unknown paths.
What it costs
- Route A: a paid Lovable plan plus the domain from a registrar.
- Route B: a Frontend pack from $1/mo for the app; the domain itself from $11.39/yr if you register it with us, or any registrar you already use.
- If the app has a database, sign-in users or files, a dedicated Supabase pack from $5/mo.
App
$1/mo
Starter Frontend pack, 1 vCPU / 1 GB RAM / 10 GB
Database, users and files
$5/mo
Smallest dedicated Supabase pack; several projects fit on one
For comparison
- Lovable Pro (custom domains need Pro or higher): $25/mo (checked 2026-11-06, lovable.dev)
Questions
Can I add a custom domain on the free Lovable plan?+
No. Lovable's docs say custom domains are available on paid plans; a free project stays on its lovable.app address. That is why many people export the code and host it elsewhere with their own domain.
Where is the domain setting in Lovable?+
Project → Settings → Domains, after the project is published. The records to create appear there, and the domain can be set as primary once its status is Live.
Which DNS records does Lovable need?+
For a root domain, an A record to 185.158.133.1 and a TXT verification record at _lovable. For a subdomain, or a domain behind a proxy such as Cloudflare, a CNAME to your project's lovable.app address. Lovable also offers an automatic setup for common registrars.
Which DNS record does Hostwares need?+
The site's Domains tab shows the exact record for your domain; create it at your registrar and the certificate is issued once it resolves. Agents use the add_domain tool, which does the same thing.
Do I lose the Lovable editor if I host the app elsewhere?+
No. You keep editing in Lovable; the GitHub repository it maintains is what gets deployed. Only the place the app runs changes.
Can both the Lovable address and my domain stay live?+
Yes. Lovable keeps publishing to lovable.app, and your domain points wherever you decide. Switch it over when the copy on the new host looks right.
What does hosting the export cost?+
A Frontend pack from $1/mo, flat for the pack's term. A dedicated Supabase pack from $5/mo if the app has data and users. Nothing is metered.
Related
Next guides
Sources: Lovable docs: Connect a custom domain (2026-11-06) · Lovable pricing (2026-11-06) · Lovable docs: Deployment, hosting and ownership (2026-11-06)