Webflow's export gives you static HTML for your current pages. It does not give you your CMS content, your forms, or your Interactions. Here's the honest breakdown.
Key takeaways
- Webflow's export gives you static HTML/CSS/JS for your current pages – genuinely yours, but only a snapshot.
- CMS content, native forms and Interactions do not survive a static export; they only exist inside Webflow's own platform.
- "You can export" and "you can leave with everything that makes the site work" are different claims – most sites past a few pages need more than the export covers.
Webflow's own marketing says you can export your site and "own your code." That is true in a narrow, technical sense, and it is worth knowing exactly how narrow before it becomes the plan you were counting on.
What "export" actually gives you
The export produces static HTML, CSS and JavaScript for your pages as they render right now. That is genuinely useful and genuinely yours. It is also where the export stops.
What it does not give you
- CMS content. Anything living in a Collection – blog posts, products, team members, locations – is not part of the static export. It exists only inside Webflow's database, reachable only through Webflow's own CMS API while you keep paying for the plan that includes it.
- Forms. Webflow's native form handling does not travel with an export; every form needs a new backend wired up wherever the exported files end up hosted.
- Interactions and CMS-bound logic. Effects that depend on Webflow's runtime, or content dynamically pulled from a Collection at render time, do not survive the export intact.
So what do you actually own?
A snapshot of the parts of your site that do not change – which is a real, usable asset for a small marketing site with no CMS, and the exact reason our Static Export package exists at a fixed $490. It is a much smaller asset for anything that leans on Webflow's CMS, forms or Interactions, which is most sites past a handful of pages.
The honest read on lock-in
Webflow is not unusual here – most page builders keep your content one layer removed from a plain file you can walk away with. The difference worth knowing before you build on it is that "you can export" and "you can leave with everything that makes the site work" are not the same claim, and only one of them is the one Webflow states plainly.
See what each migration path actually recovers, or tell us what your site depends on and we'll tell you what an export would and wouldn't carry over.