The CMS gap in Webflow's export
Webflow's code export is great for hand-off, but it's limited to what's in the Designer: collection list and collection template pages don't include your CMS items, and ecommerce isn't exported. If your site is built on the CMS — a blog, a portfolio, a directory — the export alone won't give you a working copy.
A crawler doesn't care how a page was built. It follows links on the published site, so every CMS item that has a URL is saved as its own HTML file, with the assets it uses.
When a static Webflow copy makes sense
- Self-hosting for compliance, data-residency or client-handover requirements.
- Archiving a campaign or microsite before you retire a site plan.
- Performance — serving the bundle from your own CDN with your own caching rules.
Keep designing and publishing in Webflow; re-run the conversion (or schedule it on a paid plan) whenever content changes.
What needs a backend
Webflow forms, Ecommerce, Memberships/Users and site search are served by Webflow. Map forms to a form service or your own endpoint with form-action mapping; move commerce and gated content to a dedicated service. Interactions built with Webflow's JavaScript are bundled with the page, but preview the ZIP before switching DNS.
How to do it with Static Converter
- 1Publish your Webflow siteUse your custom domain or the
webflow.iostaging URL. - 2Add the URL and choose a full crawlA full crawl follows collection lists into every CMS item.
- 3Optimize and map formsEnable WebP and minification; point forms at your new endpoint.
- 4Download and hostDeploy the ZIP to any static host and point your domain.