How to set up domain mapping in Bubble

In the Bubble editor, go to Settings in the left sidebar, then click the Domain / email tab. In the Domain section, enter your custom domain (like www.yourapp.com or app.yourapp.com). Click Add domain. Bubble will display the DNS records you need to configure at your registrar. Copy these values — you will need them in the next step. For a root domain (yourapp.com without www), Bubble provides A record IP addresses. For a subdomain (www.yourapp.com or app.yourapp.com), Bubble provides a CNAME target.

Log in to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) and navigate to DNS settings for your domain. For a subdomain like www.yourapp.com: add a CNAME record with Host set to 'www' and Value set to the CNAME target Bubble provided. For a root domain (yourapp.com): add the A records Bubble provided, each pointing to the specified IP address. If you want both root and www to work, set up the root domain A records and add a CNAME for www pointing to the root domain. Set TTL to the lowest available value (300 seconds) to speed up propagation.

DNS changes can take 15 minutes to 48 hours to propagate worldwide, though most resolve within 1-2 hours. Go back to Bubble's Settings → Domain tab and click Check DNS or refresh the page. Bubble will indicate whether it can see your DNS records. You can also verify independently using a tool like dnschecker.org — enter your domain and check that the A or CNAME records point to the correct values. If propagation is slow, try flushing your local DNS cache or testing from a different network.

Once DNS is verified, Bubble automatically provisions an SSL certificate for your custom domain using Let's Encrypt. This can take a few minutes to a few hours. Check by visiting your domain in a browser — you should see the padlock icon indicating HTTPS is active. If you see SSL errors like ERR_CERT_INVALID or SSL_ERROR_BAD_CERT_DOMAIN, wait 30 minutes and try again. If the error persists, check that you do not have Cloudflare proxy mode (orange cloud) enabled — it can interfere with Bubble's SSL provisioning. Use DNS only mode (grey cloud) in Cloudflare.

If you use email on your domain (like hello@yourapp.com), changing DNS records can break email delivery. Before making changes, note down your existing MX records, SPF records (TXT records starting with v=spf1), DKIM records, and any other email-related DNS entries. After adding Bubble's DNS records, verify that your MX and email TXT records are still intact. If your registrar requires you to replace existing records, make sure to add the email records back alongside the new Bubble records. Test email delivery by sending and receiving a test message.

If you want yourapp.com to redirect to www.yourapp.com (or the reverse), you need to configure this at the DNS or registrar level since Bubble does not handle automatic redirects between root and www. Most registrars offer URL forwarding or redirect features. Set up a 301 (permanent) redirect from the non-primary version to the primary one. If using Cloudflare, create a Page Rule that redirects yourapp.com/* to https://www.yourapp.com/$1 with a 301 status. This ensures users always land on the correct version and search engines do not see duplicate content.