How to Add Custom Domains in Bubble.io

You’ve built your app on Bubble.io. It works. It looks great. But there’s one thing holding it back — it’s still running on a yourapp.bubbleapps.io URL.

That’s a problem.

75% of people judge a business’s credibility based on its web presence. A subdomain from a no-code builder signals “I’m just testing this.” A custom domain signals “I mean business.” The gap between the two is not just aesthetic — it directly affects trust, conversions, and how seriously people take what you’ve built.

The good news? Adding a custom domain in Bubble.io takes less than 30 minutes if you know what you’re doing. This guide walks you through every step — from purchasing your domain to verifying SSL — so you can stop looking like a side project and start showing up like a serious product.

Why a Custom Domain Changes Everything

Before jumping into the how-to, let’s be clear about what’s at stake.

94% of first impressions are design-related, and your URL is part of that first impression. When someone sees yourbrand.com versus yourbrand.bubbleapps.io, two completely different trust signals fire in their brain. One says “established.” The other says “not ready yet.”

Beyond perception, there are practical reasons to make the switch:

• SEO performance: Search engines index custom domains more favorably. Your branded URL builds domain authority over time — something a Bubble subdomain never will.
• Email deliverability: If you’re sending emails from your app, a branded domain improves deliverability rates significantly. Emails from free subdomains are 10x more likely to land in spam compared to those sent from a custom domain.
• Brand consistency: Every touchpoint — ads, social, business cards, emails — should point to the same place. A custom domain makes that possible.
• SSL and security: 85% of online shoppers abandon a site that isn’t HTTPS-secured. Bubble issues an SSL certificate automatically once your custom domain is connected, which keeps your users safe and your conversion rates intact.

Over 3 million people have built on Bubble.io. The ones who are serious have already made this switch. Here’s how you do it.

What You Need Before You Start

Getting this right the first time means having everything ready before you touch a single setting. Here’s your pre-flight checklist:

A paid Bubble.io plan — Custom domains are not available on the free plan. You need at least the Starter plan to connect your own domain. Check Bubble’s current pricing page to find the tier that fits your needs.

A registered domain name — You’ll need to own the domain you want to connect. If you don’t have one yet, register it through providers like Namecheap, GoDaddy, Cloudflare, or Google Domains. .com domains typically run $10–$15 per year.

Access to your domain registrar’s DNS settings — You’ll be adding DNS records (specifically a CNAME record) to point your domain to Bubble. Make sure you have login access to wherever your domain is managed.

Your Bubble app published — Your app needs to be in a published state before the custom domain will work correctly.

Once you have all four in place, you’re ready to connect.

How to Add a Custom Domain in Bubble.io

Upgrade Your Plan

Log into your Bubble.io account and go to Settings → Plans. Upgrade to a paid plan if you haven’t already. Once upgraded, the domain settings will unlock inside your app’s dashboard.

Open Your App’s Domain Settings

Inside your Bubble editor, click on the Settings tab in the left sidebar, then click Domain / email. This is where all custom domain configuration lives.

You’ll see a field labeled “Domain name”. This is where you’ll enter the custom domain you want to use.

Enter Your Custom Domain

Type your domain in the field. You can use:

• A root domain: yourbrand.com
• A subdomain: app.yourbrand.com

For most apps, using a subdomain like app.yourbrand.com is recommended — it gives you flexibility to keep a marketing site on the root domain while running your app on the subdomain.

Click “Add domain” once entered.

Configure Your DNS Records

This is the most critical step — and the one where most people get stuck.

After you add your domain in Bubble, you’ll see a set of DNS records you need to add to your registrar. Here’s what Bubble gives you and what to do with each.

The CNAME Record

Bubble will provide a CNAME record that looks something like this:

• Type: CNAME
• Host / Name: www (or app if you’re using a subdomain)
• Value / Points to: yourdomain.bubbleapps.io
• TTL: 3600 (or “Automatic”)

Log into your domain registrar, navigate to the DNS Management or DNS Settings section, and add this CNAME record exactly as shown.

For root domains (yourbrand.com), most registrars don’t support CNAME records at the root level. In this case, you have two options:

• Use an ANAME or ALIAS record (if your registrar supports it) pointing to Bubble’s target
• Switch your DNS management to Cloudflare, which supports this through their CNAME flattening feature

Cloudflare’s free plan handles this seamlessly and is worth the 10-minute migration if your registrar doesn’t support root CNAME or ALIAS records.

Propagation Time

Once you save your DNS records, there’s a waiting period. DNS changes can take anywhere from a few minutes to 48 hours to propagate globally, though most updates resolve within 1–4 hours.

You can check propagation status using tools like whatsmydns.net — paste your domain and select CNAME to see if the record has spread across servers worldwide.

Verify and Activate Your Domain in Bubble

Once your DNS records are live and propagating, go back to Bubble’s Settings → Domain / email page.

Click “Check DNS configuration” or the equivalent verification button. Bubble will run a check to confirm your DNS records are pointing correctly.

If everything is set up right, you’ll see a green confirmation. Your domain is now connected.

If the check fails, don’t panic — DNS propagation is often still in progress. Wait 30 minutes and try again. If it’s been more than 24 hours and it still fails, double-check that your CNAME record has no typos and that there are no conflicting A records on the same hostname.

Enable SSL on Your Custom Domain

Here’s the best part: Bubble handles SSL automatically.

Once your domain verification passes, Bubble issues and manages your SSL certificate through Let’s Encrypt. Your app will automatically be accessible via https:// with no extra steps required on your end.

This matters because:

• Google Chrome marks non-HTTPS sites as “Not Secure” — a warning that drives 90% of users away immediately
• SSL is a confirmed Google ranking signal, giving HTTPS sites a small but real SEO advantage
• Payment processors like Stripe require HTTPS to function

You don’t need to buy a separate SSL certificate or configure anything. Bubble does it for you. Give it 10–15 minutes after your domain verifies to activate.

Set Your Domain as the Default in Bubble

After your custom domain is verified and SSL is active, make sure Bubble is serving your app on the right URL.

In Settings → Domain / email, look for the option to set your custom domain as the primary domain. This ensures that:

• Traffic to your .bubbleapps.io URL automatically redirects to your custom domain
• All internal links and app URLs use your branded domain
• Users don’t accidentally bookmark the Bubble subdomain

This redirect is handled server-side and requires no extra configuration from you — just toggle it on.

Troubleshooting Common Issues

Even with the right steps, you might run into a few roadblocks. Here’s how to handle the most common ones.

DNS check keeps failing after 24+ hours

Open your registrar’s DNS management and verify:

• The CNAME record host is exactly right (no extra dots, no spaces)
• There are no conflicting A records on the same hostname
• TTL is set to 3600 or lower

SSL certificate not activating

SSL requires your DNS to be fully propagated first. If your domain just passed the DNS check, give SSL an additional 15–30 minutes. If it still hasn’t activated after an hour, try removing and re-adding the domain in Bubble settings.

App loads but shows a security warning

This usually means a mixed content issue — your app is loading some resources over HTTP instead of HTTPS. Check your Bubble app for any hardcoded http:// URLs in API calls, image URLs, or external scripts and update them to https://.

Root domain not resolving

If yourbrand.com isn’t loading but www.yourbrand.com works, you likely need an ANAME/ALIAS record at the root. Switch DNS management to Cloudflare — their CNAME flattening feature solves this for free.

Bubble subdomain still appearing in some places

Make sure you’ve set your custom domain as the primary in Bubble settings and enabled the redirect. Also clear your browser cache and try an incognito window to rule out a local caching issue.

How Long Does the Full Process Take?

Here’s a realistic timeline:

The only thing you can’t control is DNS propagation speed — that depends on your registrar and global DNS infrastructure. Most setups are fully live within a few hours.

Conclusion

Adding a custom domain to your Bubble.io app is one of the highest-leverage moves you can make as a builder. For roughly $10–$15 per year and 20 minutes of setup time, you remove one of the biggest credibility barriers standing between your app and the people who need it.

The steps are straightforward: upgrade your plan, enter your domain in Bubble’s settings, add a CNAME record at your registrar, wait for propagation, and let Bubble handle SSL automatically. That’s it.

The one thing a custom domain can’t do by itself is bring qualified people to your app. It creates the conditions for trust — but trust needs traffic to matter. If you’re ready to build the outbound system that fills your pipeline with the right people, Salesso handles that end-to-end. Targeting, campaign design, and scaling — built around your specific offer and audience.

Start with the domain. Then build the pipeline.