To use Cloudflare with Webflow and optimize/proxy all content—including images and assets from Webflow’s CDN—you’ll need to configure Cloudflare as a reverse proxy with full caching and performance settings.
yourdomain.com
) under Project Settings > Hosting in Webflow.Webflow assets (like images, CSS, JS) are served from assets.website-files.com
, which is outside your domain and not proxied by default.
To proxy all assets, including Webflow’s static files, you need to set up Cloudflare Workers (see next step).
For your domain (yourdomain.com/*
), create or modify Cache Rules instead of older “Page Rules”.
Suggested cache settings:
Cache Level: Cache Everything
Edge Cache TTL: 1 month (adjust per needs)
Origin Cache Control: Respect origin (or ignore, if needed)
Webflow uses https://assets.website-files.com
for static sites.
Use a Cloudflare Worker to fetch and cache these assets through your domain (e.g., cdn.yourdomain.com
proxies them).
This allows full control of caching, HTTP response headers, and route-specific optimization.
Worker Tasks:
Intercept requests to cdn.yourdomain.com
Rewrite and fetch from https://assets.website-files.com
Apply custom caching rules
Serve assets via Cloudflare from your own subdomain
www
with Always Use HTTPSnon-www
to www
or vice versa to avoid duplicate content.To fully optimize a Webflow site with Cloudflare, point your domain to Cloudflare, proxy traffic (orange cloud), and use Cloudflare Workers to cache and serve Webflow-hosted assets. Set aggressive cache rules for improved performance while using Cloudflare’s optimization tools like image compression and minification.