How to proxy with Cloudflare
You can use Cloudflare with Framer to enable reverse proxying—ideal for advanced use cases like traffic management, custom routing, and compliance with infrastructure policies.
Reverse proxying places a service—like Cloudflare—between your site and visitors. This setup enables:
Integration with internal infrastructure (e.g. firewalls or routing rules)
Compliance with advanced logging or regulatory requirements
Control over CDN, caching, or geographic traffic management
Reverse proxying is only recommended for users with specific infrastructure or policy needs, as Framer already handles many of these capabilities natively.
Note: Reverse proxying is available on Scale and Enterprise plans.
Set up your Framer site
To start, open your Framer project and navigate to Site Settings → Domains. Add a free Framer subdomain to your site, such as example.framer.website
.

Next, scroll to the bottom of the Domains section to set a canonical URL. In the “Advanced” input, enter your custom domain (for example, example.com
) and publish your site.

Configure your domain in Cloudflare
Log into Cloudflare and add your custom domain—for example, example.com
.

Next, go to your DNS settings and point either the root (@
) or a subdomain like app.example.com
to a dummy A
record such as 192.0.2.1
.

Create a Cloudflare Worker
In the Cloudflare dashboard, navigate to Workers & Pages and select Create to set up a new Worker. Then, assign a route to your Worker—something like example.com/*
—so it can handle all incoming traffic.

Use the following code in your Worker to forward requests to your Framer subdomain. Replace the example URL with your actual Framer domain:
Verify your setup
Ensure your Worker is assigned to the correct domain route.
Wait a few minutes for changes to propagate.
Use developer tools or an HTTP header inspector to confirm that traffic is routed through Cloudflare.
If you encounter any issues or need further assistance, feel free to contact Framer’s support team through our contact page.