Connect your Cloudflare domain to Webflow - Webflow help

Learn how to point your Cloudflare domain to Webflow and connect it to your Webflow site.
Some DNS providers limit the configurations they provide, such as only accepting a single A record, or not supporting SSL on the root domain. For more flexibility, you can point your custom domain to a third-party DNS provider, like Cloudflare.
Before you get started
Create an account with Cloudflare and add your site. If you already manage your custom domain with Cloudflare, you can Quick connect your domain to point your Cloudflare domain to Webflow and set your DNS records automatically.
How to point your Cloudflare domain to Webflow with the www subdomain as the default
As of April 2025, Webflow is updating DNS records. There are two possible sets of DNS records for your site, and they may differ from site to site. Go to Site settings > Publishing > Production to confirm the correct records for your site.
- If your site hasn’t yet been migrated to Cloudflare, set all DNS records in Cloudflare to DNS Only (disable the proxy).
- Once migrated, you can enable the proxy to use Cloudflare features using Orange-to-Orange (O2O).
To connect your Cloudflare custom domain and set the www subdomain as the default:
- Direct NS records from your domain registrar to your Cloudflare account
- Go to Site settings > Publishing > Production (copy the correct DNS records)
- Create a CNAME record with the name
wwwand set the target as shown in Site settings (e.g.proxy-ssl.webflow.comorcdn.webflow.com) - Set proxy status to DNS only
- Set TTL to auto
- Create an A record with the hostname
@and target as shown (e.g.75.2.70.75or198.202.211.1) - If a second A record is shown, add it (e.g.
99.83.190.102) - Set proxy status on A record(s) to DNS Only
- Set TTL on A record(s) to auto
Then, in Webflow:
- Open Site settings > Publishing > Production
- Click Add a custom domain
- Choose Manually add domain
- Enter the domain you want to connect (e.g. yourdomain.com)
- Set the www subdomain (e.g. www.yourdomain.com) as the default domain
- Publish your site
How to point your Cloudflare domain to Webflow with the root domain as the default
As of April 2025, Webflow is updating DNS records. There are two possible sets of DNS records for your site, and they may differ from site to site. Go to Site settings > Publishing > Production to confirm the correct records for your site.
- If your site hasn’t yet been migrated to Cloudflare, set all DNS records in Cloudflare to DNS Only (disable the proxy).
- Once migrated, you can enable the proxy to use Cloudflare features using Orange-to-Orange (O2O).
Steps:
- Direct NS records from your domain registrar to your Cloudflare account
- Go to Site settings > Publishing > Production (copy the correct DNS records)
- Add a CNAME record with the name
www, target as shown in Site settings (e.g.proxy-ssl.webflow.comorcdn.webflow.com) - Set proxy status to DNS only
- Set TTL to auto
- Delete any A records set on the root domain
- Add a CNAME record with the name
@, using the value from Site settings - Set proxy status to DNS only
- Set TTL to auto
Then, in Webflow:
- Open Site settings > Publishing > Production
- Click Add a custom domain
- Choose Manually add domain
- Enter the domain to connect (e.g. yourdomain.com)
- Set the root domain (e.g. yourdomain.com) as the default domain
- Publish your site
FAQ and troubleshooting tips
I added my DNS records in Cloudflare but my domain isn’t available yet. What’s going on?
DNS changes can take up to 48 hours to fully propagate in all geolocations (typically a few hours). Use a tool like whatsmydns to check propagation. If your DNS records are correct and your domain still isn’t available after 2 days, contact Webflow support.
Help! There’s a “525 Handshake Error” from Cloudflare on my domain.
If your site hasn’t been migrated to Cloudflare, this error can occur if the Cloudflare proxy (orange cloud) is enabled. To fix it, set your DNS records to DNS Only by clicking the orange cloud.
- If you must use the Cloudflare proxy before migration, temporarily toggle the proxy off to allow SSL renewal, then back on. This is not recommended as a long-term solution.
Additional resources:
If your domain uses Cloudflare’s Zone Hold feature, SSL certificate generation may fail during connection or migration. Release the Zone Hold in your Cloudflare account before proceeding. After SSL certificate generation, you can safely re-enable Zone Hold.