Code export · Webflow
Webflow code export gives you the front end, not the product
Export policy checked on September 2026
What comes out
What Webflow actually exports.
Webflow genuinely offers a code export — this isn't a platform that traps you. The important nuance is scope: it exports the static front end beautifully, and it leaves every dynamic, server-backed feature behind.
Static HTML / CSS / JS
A ZIP with one HTML file per static page, your styles plus Webflow's base stylesheet, a /js folder and all assets.
Working interactions
Animations and interactions export as functioning client-side JavaScript (webflow.js) — the motion comes with you.
Host it anywhere
Webflow's own wording: export your HTML, CSS, JavaScript and assets and "host it anywhere you like." Requires a paid Workspace plan.
DevLink for components
A separate feature exports individual Webflow components to React, for teams pulling pieces into an existing app.
How the export works: Use the Code Export panel in the Designer to download the ZIP (paid Workspace plan required — the free Starter tier doesn't export; verify the exact current tier on Webflow's plans page). For React, DevLink exports selected components rather than the whole site.
The gap
What the export does not include.
The export is front-end only, and the gaps line up exactly with anything that made the site more than a set of pages. If your Webflow project is a marketing site, this barely matters. If it's a CMS-driven or transactional site, the export leaves the important half behind.
CMS collections and content
Your CMS collections and their content don't come out. Pages that were dynamically generated from a collection have to be rebuilt against a new data source — the export gives you the template, not the database or the content behind it.
BlockerSources: [1]Memberships and e-commerce
User Accounts / Memberships and the e-commerce backend — product database, cart, checkout — are hosted Webflow features that stay on Webflow. An exported store is a shopfront with no till.
BlockerSources: [1]Form handling
Forms render in the exported HTML, but Webflow was handling the submissions. Once exported, every form needs a new backend endpoint to actually receive and store what people send.
MajorSources: [1]Interactions JS is "keep running", not "extend"
The exported interactions work, but they're Webflow's generated, minified webflow.js — fine to serve as-is, awkward to hand to a developer to modify. It's output, not source you'd build on.
Minor
The real question
Is the exported code maintainable?
Webflow export:Mixed
It depends entirely on what your Webflow site is. As a static marketing site, the export is clean and maintainable — standard HTML/CSS/JS with readable class names that a developer can host and lightly maintain without fuss. As a CMS-driven or transactional site, "maintainable" is the wrong frame, because the half that mattered (content, accounts, commerce, forms) didn't export at all and has to be rebuilt against a real backend. So the front end is portable; the product, if there was one, is a rebuild with the export as its visual starting point.
Your options
What to do with the export.
Three honest routes. The right one depends on how far the app has to go and who is going to own the code once it gets there.
- 01
Export and self-host the marketing site
Take the ZIP, host it on your own infrastructure, and you're done. No rebuild needed.
- Right when it's a static marketing or brochure site with no CMS-driven or transactional features.
- Wrong when the site depends on CMS content, memberships or checkout.
- 02
Keep Webflow for marketing, build the app in code
Leave the marketing site on Webflow (or exported), and build the actual application — the part with data, accounts and logic — as owned code.
- Right when you're really running two things: a site and an app that outgrew a site builder.
- 03
Rebuild the dynamic site around a real backend
Use the exported front end as the design, and rebuild the CMS, accounts and commerce against a database and backend you own.
- Right when the CMS or store is central and you need to own the content and transactions, not just the pages.
The Webflow export, feature by feature: what travels and what stays
Webflow's export is easy to misjudge because the honest answer is "it depends what you built." Here's the split, cleanly. Travels with you: static pages, styles, assets, and working interaction JavaScript. Stays on Webflow: CMS collections and content, User Accounts and memberships, the entire e-commerce backend, and form-submission handling. The rule of thumb: anything that reads from or writes to a database was a hosted Webflow service, and hosted services don't export. That's why an exported marketing site is finished and an exported app is a front end waiting for a backend.
- Static pages
- Export
- Interactions
- Export
- CMS content
- Stays
- Commerce / accounts
- Stays
Sources: [1]
FAQ
Questions people actually ask.
- Do I need a paid plan to export Webflow code?
- Yes. Code export requires a paid Workspace plan — the free Starter tier doesn't include it. Webflow has moved this gate before, so confirm the exact current tier on its plans page before relying on it, but expect it to be a paid feature.
- Does the export include my CMS content?
- No. CMS collections and their content stay on Webflow. Any page that was generated dynamically from a collection exports as a static template with no data behind it — you'd rebuild those against a new content source. The export is your front end, not your database.
- Are interactions and animations included in the export?
- Yes. Interactions export as working client-side JavaScript (webflow.js), so the motion comes across. The caveat is that it's generated, minified code — great to serve as-is, but not source a developer would comfortably extend.
- Can I host an exported Webflow site elsewhere?
- Yes — that's the point of the export. Webflow's own docs say you can host the exported HTML, CSS, JS and assets anywhere. Just remember what didn't come with it: if the site relied on CMS, memberships, commerce or forms, those need a new home too.
Every builder, one table
Code export across the hub, at a glance.
The same status table on every export page. “Exports” means real, usable source comes out; “partial” means a major layer is missing; “none” means no source export at all. The nuance is on each page.
| Platform | Code export | What you get |
|---|---|---|
| Lovable | Exports code | React repo via GitHub |
| Base44 | Partial export | Front end; backend locked |
| WebflowThis page | Partial export | Front end only, no CMS |
| FlutterFlow | Exports code | Dart / Flutter source |
| Framer | No code export | Host-only, no export |
| Bolt.new | Exports code | Project files / GitHub |
| Bubble | No code export | No source export |
| Replit | Exports code | Full code, you own it |
| Softr | No code export | No code (data only) |
| Glide | No code export | No code (data only) |
| Adalo | No code export | No source export |
| Retool | Partial export | Self-host, not source |
| Xano | Partial export | API portable, no export |
Sources
Every claim, traced to a primary source.
The numbered references in the body link here. We cite vendor docs, pricing pages, changelogs and named reporting — dated where the document is dated, so the page can be re-audited each quarter.
- [01]How do I export my Webflow site code?
Webflow Help Centerhelp.webflow.com
- [02]Export components with DevLink Export
Webflow Help Centerhelp.webflow.com
Own the Webflow app outright?
We’ll map the route to code you actually own.
Book a call with Jackson, our Growth Partner — he’ll walk your export or app, the gaps that matter, and a fixed-price plan to get it production-ready, live on your screen. Or get an instant estimate first.
Or see fixed-price migration packages and how we work.