How to put your Lovable or Bolt app on your own domain

To put a Lovable or Bolt app on your own domain, you need a paid plan, a published project and access to your domain's DNS settings. You add the domain in the tool's domain settings, create the DNS records it shows you, wait for the HTTPS certificate, and then update your login redirect URLs and email settings so everything uses the new address. The domain part usually takes minutes of work plus some waiting; the login and email part is where most apps break.

This guide covers both, with the exact steps for Lovable and Bolt and notes for v0, Replit and Cursor projects.

What is DNS, and which records matter?

DNS is the system that tells the internet which server answers for your domain name. You manage it wherever your domain's nameservers point: usually the registrar where you bought it (GoDaddy, Namecheap, Squarespace and so on) or a service like Cloudflare.

You'll only deal with a handful of record types:

What should you do before you start?

1. Check your plan. Custom domains need a paid plan on both Lovable and Bolt.
2. Publish the project. Lovable lets you connect before publishing, but the domain only serves your app once it's published. Bolt only shows the option for published projects.
3. Find where your DNS lives. Log in to your registrar and look for DNS or nameserver settings. If the nameservers point to Cloudflare, you edit the records there.
4. Take a screenshot of your current records. If something goes wrong, you can put them back.

How do you connect a domain in Lovable?

Based on Lovable's documentation:

1. Go to Project → Settings → Domains and click Connect domain.
2. Enter the domain (yourapp.com) or a subdomain (app.yourapp.com) and choose which one it is.
3. Choose how to set up DNS. The automatic option (through a service called Entri) logs in to supported providers and creates the records for you. The manual option shows you the records to create yourself.
4. For manual setup, create:
   • An A record for @ (the root) or your subdomain, pointing to the IP Lovable shows you.
   • A TXT record with the host _lovable (or _lovable.app for a subdomain called app) and the lovable_verify=… value Lovable gives you.
5. Remove any AAAA records on that name, and if you have CAA records, make sure they allow the certificate authorities Lovable lists.
6. Click Done and wait for the status to change to Live.

Lovable says most changes finish within a few hours, and DNS can take up to 72 hours. When you connect a root domain, Lovable redirects www to it by default.

If you use Cloudflare's proxy (the orange cloud), keep the record set to DNS only while Lovable verifies it, or use Lovable's advanced option for proxies, which gives you a CNAME instead.

About redirects: if you connect several domains, the primary one serves the app and the others redirect to it with a temporary (302) redirect. Lovable doesn't offer permanent (301) redirects between project domains.

How do you connect a domain in Bolt?

Based on Bolt's documentation:

1. Publish the project first.
2. Open the project settings, go to Domains & Hosting and choose the option to connect a domain you own.
3. Bolt shows you the DNS records to add. Create them at your registrar exactly as shown.
4. If you're connecting a subdomain such as app.yourcompany.com, complete the verification step Bolt asks for. Root domains don't need it.
5. Wait, then check the Status column in Domains & Hosting.

Bolt says most domains connect within a few hours and some take up to 24. It will warn you if the domain is already connected to another project or in use on Netlify. You can also buy a domain through Bolt, and a domain bought inside a project is linked right away.

If you later move from a paid hosting plan to the free one, Bolt stops publishing to your custom domain.

What about v0, Replit and Cursor projects?

• v0 deploys to Vercel, so you add the domain in the Vercel project's domain settings and create the records Vercel shows.
• Replit lets you link a custom domain to a deployment and gives you the records to create. Its docs note that after linking a domain you may need to republish so the app knows about the new address.
• Cursor doesn't host anything. You connect the domain wherever you deploy (Vercel, Netlify, Render, Cloudflare and so on).

Our guide on moving a vibe-coded app from preview to production covers those hosts in more detail.

Why does login break after switching domains?

This is the most common problem after a domain change. Sign-in works on the old address and fails, or sends people back to the old address, on the new one.

The reason is that your auth provider only sends users to addresses on an approved list. In Supabase, that list lives under Authentication → URL Configuration:

1. Set the Site URL to your new main address, exactly as people will use it (with or without www, but consistent).
2. Add the new domain to Redirect URLs. Keep the old one while you test, then decide whether to remove it.

If your Lovable app runs on Lovable Cloud, Lovable adds the domain to the auth settings automatically once it's Live. If it doesn't work, check the Cloud auth settings. If you use your own Supabase project, you add it yourself.

Google sign-in needs one more step if you use your own Google credentials: check the authorized origins and redirect URLs in Google Cloud Console and add your new domain where it's needed.

Which emails still point to the old address?

Two kinds of email are affected.

• Login emails (confirmation, password reset, magic links). Their links are built from the Site URL, so updating it fixes most of them. Check your email templates for any old address typed in by hand.
• Emails sent from your domain. Supabase's built-in email service is meant for testing. For a real launch, connect your own SMTP provider and authenticate your domain with SPF, DKIM and DMARC records. Those are more DNS records, so add them carefully next to your existing MX records.

What else still uses the old address?

Search your project for the old address (the lovable.app address, or whatever default address your tool gave you) and check:

1. Stripe success and cancel URLs, and any webhook endpoint that lives on the app's domain.
2. Links written directly into the code or into the database.
3. The page's canonical and social preview tags.
4. Analytics and Google Search Console, which treat a new domain as a new site.

A five-minute check after the switch

In a private window, on your phone and your computer:

1. The app loads on the new domain with the padlock (HTTPS).
2. www and the root both end up on your main address.
3. You can sign up with a new email, confirm it and log in.
4. Password reset sends a link to the new domain.
5. A test payment, if you take payments, returns to the new domain and gives access.

Quick answers

How long does it take? The setup is a few minutes. DNS changes often take effect within a few hours, and can take up to 72 hours on Lovable or 24 on Bolt.

Will my old address stop working? Not necessarily. Check what your tool does with it, and keep it in your auth redirect list until you've tested the new one.

Should I buy the domain through Lovable or Bolt? It's simpler, since the records are set for you. Buying from a registrar gives you more control if you'll use the domain for email or other sites too.

Domain connected, but something still breaks?

That's usually auth, email or a payment URL, and it's a quick fix once someone finds it. Run the free App Health Check on your new domain, see how we fix Lovable apps and Bolt apps, or tell us what's failing.