Webflow moved us onto Cloudflare in 2025 and then left all our heavy stuff (images, CSS, JS, fonts) sitting on their CDN.
So yes, we get O2O, WAF and the orange cloud — but:
-
No Cloudflare Image Transformations on Webflow assets by default
-
No unified caching on your own domain
-
OG/social images that aren’t exactly social‑friendly
-
Extra CORS weirdness if you try to get clever
We’ve been wrestling with that for years, each time a change comes we adapt, and now we’ve shipped a Cloudflare Worker that:
-
Proxies all Webflow CDN assets (images, CSS, JS, fonts, icons) through your domain
-
Uses Cloudflare Image Transformations to auto‑convert to AVIF/WebP with configurable quality
-
Caches originals + transformed versions at the edge with long TTLs
-
Treats OG/Twitter images differently so social previews don’t break
-
Plays nicely with the new O2O setup (no more hacky cassette apps or weird asset subdomains)
If you care about squeezing extra performance out of Webflow’s new Cloudflare hosting, I wrote up a full how‑to plus the complete Worker script.
Webflow on the Edge: The 2026 Cloudflare Asset Proxy and Optimisation Guide
https://www.milkmoonstudio.com/post/optimize-webflow-with-cloudflare-images-assets-caching-in-2026