How do I connect a custom domain in Webflow?

Choose how to connect

A custom domain replaces or sits beside your webflow.io staging address so visitors reach your brand URL. You need a paid Site plan on the site before you connect. In Site settings > Publishing > Production you can Quick connect a domain or subdomain, buy a new domain through Webflow's partner flow, or manually add a domain and set DNS yourself.

Manual connection suits teams that already manage DNS at a registrar. Quick connect can set records automatically when your host is supported. This guide focuses on the manual path and the DNS checks that unblock publish.

Add the domain and set DNS

In Site settings > Publishing > Production:

• Click Add a custom domain, choose Manually add domain, enter yourdomain.com, then Add domain.
• That step prepares both the root domain and the www subdomain.

Then open your DNS host and create the records Webflow shows for that site. As of the current docs, a common set is:

• A record, hostname @, value 198.202.211.1
• CNAME record, hostname www, value cdn.webflow.com
• TXT record, hostname _webflow, value starting with one-time-verification= from Site settings

Copy the values from Site settings > Publishing > Production for your site. Older sites may still show two A records until Webflow finishes a DNS migration. If Publishing settings list different IPs, use those values, not a remembered list from another site.

Some hosts prefer the full root hostname instead of @, the full www hostname instead of www, or a trailing dot on CNAME targets. Remove extra A records on the root and extra CNAMEs on the same subdomain so they do not conflict with Webflow's records. Keep registrar default nameservers unless you intentionally manage DNS elsewhere.

Verify, set default, and publish

Under the domain, click Check status. When records look correct, click Verify domain and wait for the Custom domain verified message. Then open Publish, check the new domain, and publish to selected domains. Hosting transfers inside the same Workspace may skip re-verification.

If you connect more than one domain, click Make default on the preferred host (often www.yourdomain.com) so other domains redirect and you avoid duplicate-content risk. Setting the root as default without matching DNS can cause too many redirects. You can connect up to 50 custom domains on one site.

Fix status errors before go-live

If Check status fails, confirm only Webflow A and CNAME values appear for the connected hosts, wait for propagation (up to 48 hours), and clear a local browser cache when testing. Extra A records on the root or wrong CNAME targets are common blockers. After DNS is healthy and the domain is verified, publish again and open the live URL in a private window.

Example check: Domain yourdomain.com added manually, A @ to 198.202.211.1, www CNAME to cdn.webflow.com, _webflow TXT present, Check status green, Verify domain done, then Publish with only that production domain selected for the first live push.