Orange-to-Orange ( O2O )

About O2O

Webflow now supports O2O, aka Orange-to-Orange, in its DNS configurations.

This means 2025 is the first time that Webflow has an officially supported DNS configuration for reverse proxies and other Cloudflare services.

And this is a big deal.

Why do you want this?

Cloudflare add a wealth of free services to hosted sites;

• Advanced redirects
• Workers, for reverse proxy configurations
• Workers, for API configurations
• Page rules
• Caching
• R2 object store
• KV store
• D1 Sqllite
• ZeroTrust, for high security of site sections

And starting with Pro plans ( $30/mo ), you can add many more;

• Firewall (WAF) and analytics ( paid plans )
• Cache analytics ( paid plans )

Use Cases

• Reverse proxy for page customization
• Hosting of specialized large assets like background videos, PDF files, etc.
• Advanced redirects for complex site migrations. Supports full regex patterns
• Visibility into where traffic is coming from
• Country-blocking or restrictions for certain pages
• Advanced securing of site pages
• Possibly, caching to mitigate Webflow bandwidth overages

Setup Notes

You need;

• A Cloudflare account ( free )
• Your DNS migrated into that Cloudflare account ( free )

See Webflow's domain onboarding overview for Cloudflare.

DNS Configuration

The O2O configuration is very clean;

• CNAME @ cdn.webflow.com Proxied (orange cloud enabled)

• CNAME www cdn.webflow.com Proxied (orange cloud enabled)

That's it.

Webflow's Dashboard

Note that Webflow may show configuration warnings when you're using an O2O setup.

‍When the Cloudflare proxy is enabled, your domain may still show “Update needed” in Site settings > Publishing > Production. This is expected, as the proxy hides your DNS records from Webflow’s verification check. If your site is published and loading correctly, no action is needed.

‍

‍