Can you export Webflow code on the free plan?

No. The free Starter Workspace has no export, and upgrading your Site plan doesn't add it. Every paid Workspace tier does, including Growth at $49/mo.

Does Webflow export include CMS content?

Not as working content. Each Collection exports to CSV separately, and once you've cancelled you lose Designer and Editor access, so run those exports before the plan lapses.

Can you export a Webflow site to React?

Not directly. You get static HTML with w- prefixed classes and none of Webflow's code components, so you're rebuilding components from the markup.

Will my forms still work after export?

No, and that's deliberate for GDPR reasons. The markup and styling come through intact, so you keep the fields and point the submit action at Formspree, Netlify Forms or your own endpoint.

What happens to password-protected pages?

They export as ordinary pages, readable by anyone with the URL once the files land on a public host. Put the new gate in place before you point a domain at the folder.

Is exported Webflow code good enough for production?

Yes, the markup is clean enough to ship on any static host as it stands. It's a snapshot though, so budget for a developer every time the site needs to change.

How to Export Webflow Code (Without Breaking Your Site)

September 17, 20266 minutes

Exporting a Webflow project is not as straightforward as it seems, especially if you have a blog or use its CMS features.

Key Takeaways

Webflow code export needs a paid Workspace plan, from $16/mo, and a Site plan won't do it no matter what you pay for hosting.
You get HTML, CSS, JavaScript, fonts, and images, and you don't get the CMS, forms, site search, ecommerce, memberships, or localized pages.
Collection Lists come out as empty states and Collection template pages generate nothing, so a 200-post blog exports as zero posts.
Webflow export fits static marketing sites and client handoffs. For a CMS-driven site it's the first step of a rebuild rather than a migration.

You build a sleek Webflow website and click export. You like the design, but don’t want it to live inside Webflow. Fair.

You drop the export file into Vercel, load the homepage, and it looks perfect. Then you open the blog, and realize the export didn’t work how you wanted it to.

The export button does exactly what it says, but "your site's code" means something narrower to Webflow than it does to you. Webflow publishes the list of what stops working after export, and it's longer than the list of what survives, so read it before you cancel anything.

What you get from Webflow export code

The Webflow HTML export is a ZIP with one static HTML file per page, your CSS, your JavaScript including Webflow.js, plus image and font assets. Responsive breakpoints, media queries, flexbox and grid all survive, and animations keep running because they're client-side.

Hit Shift + E, or open the "..." menu and choose "export code". Webflow prefixes its own classes with "w-" so they don't collide with other frameworks, which matters later if you're planning a Webflow export to react rebuild.

You can't pick and choose either, because every exportable part of the site comes down every time.

Webflow export needs a Workspace plan, not a Site plan

Code export sits on paid Workspace plans, not Site plans, and the two bill separately, which is why someone paying $39/mo for Premium hosting still finds the option greyed out.

The free Starter Workspace has no export at all. Core at $19/mo for in-house teams, Freelancer at $16/mo and Agency at $35/mo all include it. If you only need the files once, buy a month of Freelancer and cancel, the cheapest legitimate way to export Webflow code .

What breaks after a Webflow code export

Every row in this table comes straight from Webflow's own documentation, accurate as of September 2026, so there's no argument about it.

Feature	After export
CMS Collections	Lists render the empty state, Collection pages show no bound content
Forms	Display fine, accept input, submit nowhere
Site search	Stops completely
Ecommerce	Product lists, cart and checkout become dead markup
Memberships	Login breaks, and gated pages go public
Localisation	Only your primary locale exports
301 redirects	Gone
Sitemap and RSS	Not generated

Two of those deserve more than a table row.

The gated pages row is the security problem. Password-protected pages stop being protected the moment you export, and on a public static host that means a gated pricing page or client portal is live to anyone with the URL.

The forms one is deliberate. Webflow disables site search and forms, including file upload and reCAPTCHA, on exported sites to stay GDPR compliant, so no, it isn't a bug you can patch, and you're rebuilding form handling either way.

Spoiler alert, the design was never the hard part.

How to export a Webflow site without losing your CMS content

There are two ways to get your content out, and they solve different problems.

Export the data. CMS Collections, Ecommerce Collections and User Accounts each export to CSV from the Collections panel, one export per Collection, no bulk option. You get the content, with none of the pages that displayed it.

Unbind, then export. Clone the site first, because this process is destructive, then run Finsweet's Unbind CMS tool on the top-level Body element of every page so elements detach from their Collection fields and render as static markup, and export the clone. Export is a Workspace feature, so working from a clone costs you nothing extra.

That gets you a frozen snapshot, where your 200 blog posts exist as HTML and nobody can publish a new one without opening a code editor.

Before you click export, work through this list.

Write down every form and where submissions currently land
List your password-protected pages and decide what replaces the gate
Export every Collection to CSV
Save your 301 redirect table out of Webflow settings
Pick a form handler now (Formspree, Netlify Forms, your own endpoint)
Strip .html extensions with an .htaccess file if you want URL parity, and you do

When Webflow to code is the right move, and when it isn't

Webflow exports work for static marketing sites, landing pages, portfolios and client handoffs where the client just wants the files, because the output is clean and hosting is cheap. It doesn't work for sites where a non-developer publishes content, which in practice is most sites worth building in Webflow in the first place.

The question isn't whether you can get the code out, it's who updates the site next Tuesday. Exported Webflow output is static HTML with no editing layer attached, so you've swapped a subscription for a developer dependency. That trade is fine if you have developers, and a problem if you chose a visual builder because you don't.

If you're exporting to own the codebase rather than rent it, the rebuild target matters more than the export. Fimo lets you bring your own code and AI stack, from Astro to Next.js to TanStack, and then it lets non-developers edit and publish from the repository itself without filing a deploy ticket, which is the gap the ZIP file leaves behind, so decide where you're landing before you leave.

Getting off Webflow without losing the site

The export button gives you your design back, but the CMS, the forms and the redirects that made it a working website don't come with it.

The cleanest way out of Webflow in 2026?

Give your export file to Claude Code or Codex. Ask it to scan your Webflow sites blog and CMS-linked components and re-create your site. Now you have your site back, in totality.

The only thing missing now is a CMS to help you edit and expand your site, and a bunch of AI agents that will work 24/7 to optimize your site, fix issues, update content, and more. All of that is now a few clicks away thanks to Fimo, which works in tandem with Claude Code, Codex, Cursor, and many other AI coding agents to turn website code into autonomous websites.

Try Fimo for free.