How to export your Webflow site, and what the ZIP leaves behind
Webflow does give you your code — on Workspace plans, not Site plans. Here is the keyboard shortcut, what is actually in the folder, and the seven things that stop working the moment the site is not on Webflow's servers.
Webflow is one of the few big builders that will hand you your site as files. That is worth saying plainly, because most will not. What catches people out is not whether the export exists — it is which plan it sits behind, and how much of the site stops working once it is a folder.
This is the short version, checked against Webflow's own help centre in September 2026.
It is a Workspace plan feature, not a Site plan one
Webflow's docs put it in one line: code export is only available on Workspace plans, and Site plans do not include it.
That is the part worth knowing before you need it rather than after. Paying for a Site plan every month does not buy you the right to walk away with the thing you built. If having the files matters to you, check which plan you are on today, not on the afternoon you decide to move.
How to actually do it
- Open the site in Webflow.
- Main menu (the W in the top-left corner) → Code export, or press Shift + E.
- Optional: press Cmd + O on a Mac or Ctrl + O on Windows and a Minify HTML checkbox appears.
- Prepare ZIP, then download it.
You cannot export part of a site. Every exportable piece goes in every time.
What is in the folder
An .html file for every page — including the Collection template pages, which come out empty. A css folder with three stylesheets: your own styles, webflow.css for the layout system and its components, and normalize.css. A js folder. An images folder with everything from the Assets panel.
No attribution is required. You can host it anywhere.
What is not in the folder
This is the list people find out about later:
- CMS content and functionality. Collection lists render their empty state. Collection pages show nothing bound to a field.
- Ecommerce. Products and checkout are a service, not markup.
- User Accounts. Users and access groups do not travel.
- Forms. Submission processing does not work on exported sites, and neither does reCAPTCHA. Webflow names GDPR as the reason.
- Site search.
- Password protection. Any page that was protected is not protected any more once exported. Worth reading twice if you have used it for a client preview.
- Localised content. Only the primary locale comes out.
- Code components.
CMS Collections, Ecommerce Collections and User Accounts can be exported separately as CSV. That is a backup of the data, not a working site — you still need something to render it.
The part that bites a month later
The js folder is not optional decoration. Navbars, sliders, tabs, forms and every interaction you built run on it. Delete it to "clean up" and the page still looks right in a screenshot and does nothing when a person touches it.
You will also notice w- in front of a lot of class names. That is deliberate on Webflow's side — it keeps their component classes from colliding with other frameworks. It is harmless. It is also a permanent fingerprint in the markup of a site that is no longer theirs.
Build where the files are yours on day one. No export flow and no plan tier in front of it. DragGo writes plain HTML and CSS you already own. DragGo vs Webflow.
So who is the export really for?
It is a genuine backup, and it is a genuine handover to a client. It is a straight answer to "can I take this with me".
What it is not is a migration button. If the site's value is in a CMS, a shop or a member area, the export gives you the shell and the CSVs, and you rebuild the moving parts on whatever comes next. Plan for that job rather than discovering it.
The question worth asking of any builder before you start, not at the end: when I leave, what do I leave with? The builders that hand over clean HTML answer it differently from the ones that will not export at all.
DragGo's answer is that the files are yours from the first save — the editor writes static HTML and CSS with no runtime to keep paying for, and publishing is the same folder going live.