Flint logo
Back to docs
Publishing

Webflow Setup

How to connect Flint to your Webflow site using Cloudflare Workers for folder on main domain forwarding.

Overview

Webflow does not natively support folder on main domain routing to external origins. To serve Flint pages in a folder on your main Webflow domain (e.g. acme.com/lp/), you need an external reverse proxy. The recommended approach is Cloudflare Workers (free tier works).

Note: You do not need direct CDN-level access to your Webflow site to use Flint. The reverse proxy sits in front of your domain and routes only the Flint subpath — all other traffic passes through to Webflow as normal.

  • •Your Webflow site continues to serve your main website.
  • •Cloudflare sits in front of your domain and routes traffic.
  • •A Cloudflare Worker intercepts requests to your Flint folder on main domain and proxies them to your Flint-hosted subdomain.
  • •All other traffic passes through to Webflow normally.

Since Webflow itself now runs on Cloudflare infrastructure, this is called an Orange-to-Orange (O2O) setup.

Prerequisites

  • •A Cloudflare account (free tier is sufficient)
  • •Your domain DNS must be managed through Cloudflare (DNS records set to Proxied/orange cloud)
  • •Your Flint subdomain (contact the Flint team if you do not know this value)
  • •A paid Webflow account with a custom domain connected

Setup Steps

There are two supported approaches for setting up the reverse proxy between your Webflow domain and Flint. Choose the option that best fits your infrastructure.

Option 1: Cloudflare Worker (Recommended)

For full instructions on setting up the Cloudflare Worker rewrite, see the Cloudflare setup guide.

Option 2: Webflow Cloud Reverse Proxy

Webflow provides an official subdirectory reverse proxy example that can be deployed directly to Webflow Cloud, without needing Cloudflare.

  • •What it is: A lightweight Next.js-based reverse proxy deployable to Webflow Cloud via OpenNext.
  • •How it works: Proxies requests from a subdirectory path (e.g., yourdomain.com/lp/) to your Flint subdomain — all within the Webflow ecosystem.
  • •Requirements: Node.js 18+ and some technical setup on your side.
  • •Benefit: Stays entirely within the Webflow ecosystem — no external proxy service needed.

Refer to the GitHub repository for setup instructions and configuration details.

Important Notes

  • •Webflow does not configure or support third-party reverse proxies. The Cloudflare Worker approach is self-managed.
  • •Webflow offers a managed reverse proxy service for Enterprise plan customers, but the Cloudflare approach gives you more control and works on any Webflow plan.
  • •If you're evaluating CMS options and haven't fully committed to Webflow, Flint can also host your entire website — eliminating the need for a reverse proxy setup. Contact the Flint team to learn more.