Exporting a Webflow site to static HTML is genuinely doable yourself. Here's the real step-by-step, including everything it breaks along the way.
Key takeaways
- Static export only works cleanly if your site doesn't rely on Webflow's CMS – any Collection-driven content is left behind.
- Forms and redirects do not survive the export; both need to be rebuilt manually on the new host.
- The export itself is quick; rebuilding working forms and a correct redirect map is where most of the real work is.
If your Webflow site does not use the CMS, exporting it to static HTML is a real, doable option – and one you can attempt yourself before deciding whether to pay someone to do it properly. Here is the actual flow, gaps included.
1. Confirm you don't need the CMS
Static export only works cleanly for sites with no active Collections, or ones you're prepared to lose. If any page pulls in CMS content dynamically, that content will not be part of the exported files – check this first, because it changes which package makes sense before you start.
2. Run the export
From your Webflow project settings, the export produces a ZIP of every published page as static HTML, plus your CSS and JavaScript assets. This requires a paid site plan – Webflow does not allow exporting from the free tier.
3. Fix what the export breaks
- Forms. Webflow's native form submission does not work outside Webflow's own hosting. Every form on the exported site needs a new endpoint – a form backend, a serverless function, or a third-party service.
- Redirects. Any 301s configured in Webflow's dashboard live there, not in the export. You need to rebuild that redirect map manually on the new host, or existing inbound links and search rankings take the hit.
- Relative paths and CMS-bound links. Internal links sometimes reference Webflow's own URL structure; broken links after a move are the most common self-inflicted SEO issue in a DIY export.
4. Host it somewhere
Static files can go almost anywhere – Netlify, Cloudflare Pages, S3, a plain Apache server. None of them will restore what the export dropped in step 3; hosting is the easy part.
Where this is worth paying for instead
The export itself takes minutes. Rebuilding working forms, a correct redirect map and catching broken internal links properly is where a DIY export quietly turns into a multi-day debugging project. Our Static Export package ($490, 2–3 business days) does exactly steps 2 through 4 for you, redirects and all, and is priced for sites that don't need the CMS at all.
See what's included in Static Export, or send us your site and we'll tell you what the export would break.