What this workflow gives you
A deployed static version of your captured Webflow pages in your own Cloudflare account. Cloudflare serves the captured files, while Webflow-hosted forms, checkout and CMS publishing remain separate. Inspect interaction scripts and form destinations on the pages.dev preview before moving the domain. A working page layout alone does not establish that a customer can submit or buy.
- Input
- Published Webflow URL
- Output
- Static HTML and reachable assets
- Your account
- Cloudflare Pages
From HTML export to a live site
- 01
Convert and review the public pages
Open the Webflow HTML converter and use a published URL you own or are authorized to convert. Review the capture report and preview before proceeding. Inventory public CMS item pages as well as landing pages. Compare the capture report with that inventory: a static article can be present even though the Webflow collection and future publishing workflow have not moved.
- 02
Prepare the static folder
Keep index.html, page files and their referenced assets together. For a downloaded ZIP, extract the files first and locate the folder containing index.html. Do not upload a Next.js source folder or accidentally place the site inside an extra nesting folder.
- 03
Connect your own Cloudflare account
From the saved site in FNJ, use Deploy with token and choose Cloudflare. Enter a Cloudflare token with Pages: Edit permission for the account you intend to use directly in FNJ. Follow the dashboard result to the deployment URL. You can also deploy your extracted HTML independently using Wrangler.
- 04
Test on the preview URL
Visit a CMS item URL directly on Cloudflare, test its navigation, then submit a test form through the intended replacement service. Open important nested pages directly and refresh them. Inspect failed asset requests and follow each form or purchase action to its real destination before treating a successful upload as a usable website.
- 05
Connect the final domain
Add your domain through the Cloudflare Pages project's custom-domain settings and follow its DNS instructions. Confirm the domain is active and serves the reviewed version. Keep important paths; configure redirects for changed URLs and check canonical tags on the final address.
Deploy the downloaded folder with Wrangler
If you use the command line instead of FNJ's deploy action, sign in to your own Cloudflare account. The following example uses webflow-site as a project name and ./site as the extracted folder containing index.html; replace both with your own values.
npx wrangler login
npx wrangler pages project create webflow-site
npx wrangler pages deploy ./site --project-name=webflow-siteWrangler uploads the static directory, not the ZIP. Choose Direct Upload or Git integration when setting up the Pages project; Direct Upload projects cannot later switch to Git integration without creating a new project.
Checks specific to Webflow
- Open each captured CMS item URL and confirm its content is present; collection data will not update automatically.
- Submit a test form and complete a test checkout on the new host before moving your domain.
- Check interactions and animations with the original Webflow site closed; external Webflow scripts may still be required.
Webflow to Cloudflare Pages: questions
- Can I host a Webflow site on Cloudflare without moving the builder account?
- You can host the reviewed static HTML output. Cloudflare serves the captured files, while Webflow-hosted forms, checkout and CMS publishing remain separate. Inspect interaction scripts and form destinations on the pages.dev preview before moving the domain. A working page layout alone does not establish that a customer can submit or buy. A builder account, database or editing workspace is not part of that deployment.
- Does this workflow need a Next.js build?
- No. This page covers an exported HTML bundle with a top-level index.html. Upload the static files. A Next.js source project needs its own build and deployment setup; do not upload application source as if it were prebuilt HTML.
- What should I test before switching my Webflow domain?
- Visit a CMS item URL directly on Cloudflare, test its navigation, then submit a test form through the intended replacement service. Also test direct visits to nested URLs, mobile layouts and any changed redirects on the final domain.
- Does FNJ host this site or manage the Cloudflare bill?
- The deployment uses your Cloudflare account. You control hosting settings and any charges under its current plan. FNJ's conversion access and the hosting provider's terms are separate; check each before purchasing.
Continue with the right setup
Converting requires a signed-in FNJ account and current conversion access. Review FNJ pricing for purchase terms. For help using your own agent, follow the deployment guide and prompt library.
Cloudflare: upload a static site