A Clean Webflow-to-Static-HTML Workflow for Moving Off-Platform

Converting a Webflow site to static HTML is one of the cleanest migrations in the no-code world. Webflow's published output is already close to hand-written HTML — the tricky part is handling the pieces that assume Webflow's backend is still in the loop.

Two paths, one output

You have two options to get a static HTML bundle of a Webflow site: Webflow's native Site-plan export, or a third-party capture like SitedIn. Both produce a folder of HTML and CSS; the differences are what's inside and what's missing.

Webflow's native export

Requires a paid Site plan on the project
Includes interactions, compiled to JS — good fidelity for motion work
Does not include CMS Collections — dynamic pages come through as empty templates
Does not include e-commerce products

SitedIn capture

No Site plan required — reads any published Webflow URL
Captures CMS-rendered pages because it sees the rendered page, not the template
Interactions: captured as-is (the compiled JS already baked into the published page comes with)
Free for a single page, paid for multi-page sites

After the export — what to rewire

Forms

Webflow Forms POST to webflow.com. Before you deploy the exported site, change the action attribute on each form element to your own handler. Formspree, Netlify Forms, Cloudflare Workers with a KV store — all work.

CMS

If your site reads from Webflow CMS at runtime via API, that stops working when you leave. Two options: freeze the content at export time (SitedIn's full-site capture does this), or re-implement the CMS on your own stack (Sanity, Contentful, or a headless WordPress all integrate cleanly with a static front-end).

E-commerce

Webflow Ecommerce checkout is Webflow-hosted. Swap it for Snipcart, Shopify Lite embedded, or Stripe Checkout with a serverless order handler.

Hosting the output

The exported folder works on any static host. Cloudflare Pages and Netlify both deploy from a Git repo on push. For faster iteration, drag the folder onto Netlify's deploy page and you have a URL in 30 seconds.

When to stay on Webflow

If the CMS is the product — blogs, team-editable pages, visual updates — Webflow's editor is hard to beat for non-technical users. The export is for archival, hand-off, or migration, not as a day-to-day workflow.