Webflow export code: the ZIP, and what stays on Webflow.
Webflow will hand you a ZIP of HTML, CSS, JavaScript and images, on a paid Workspace plan, with no attribution required. The list of what the ZIP does not carry is the part to read before you tell a client they own their site.
A real ZIP. Now read the second list.
Of the three builders, Webflow gives the straight answer. The ZIP holds an .html file for every page, three CSS files, a JS folder and an images folder with everything uploaded to the Assets panel, and the help centre says you can host it anywhere and edit it. Code export belongs to paid Workspace plans; a Site plan alone does not include it.
The second list is longer. Not in the export: CMS content, so Collection lists and pages come up empty; User Accounts; Ecommerce; any locale but the primary; password protection; and forms and site search, which the article says stop for GDPR. Hand edits “may break some Webflow components”. The data has its own doors: Collections export to CSV, rich text as HTML, images and files as Webflow-hosted URLs that die with the site; form submissions export to CSV per form, uploads as URLs that go when the submissions are deleted.
- HTML and CSS of your pages
- A ZIP, on paid Workspace plansPASS
- Images and files
- Assets in the ZIP; CMS images as Webflow URLs
- Form submissions
- CSV per form; processing stops on export
- Blog and collection content
- CSV per Collection; empty in the pages
- The Designer and components
- Stays. Hand edits “may break” components
- Search, accounts, password protection
- Stops working at exportFAIL
- Your domain
- Yours already. Webflow is not a registrarPASS
Read from Webflow’s help centre on 3 September 2026. The links are at the foot of the page.
What you actually send the client. A ZIP with the middle missing.
Here the conversation starts well and then turns. You send the ZIP. The client’s new developer opens it and finds the blog empty, the team page empty, the contact form posting nowhere and the search box inert. You send the CSVs. They ask where the images in the CSVs are hosted. You explain that they are on Webflow, on the site you were about to cancel.
None of this is hidden. It sits on one help-centre page, under a heading about what your exported files don’t include. The trouble is the sentence the client heard first, from you: Webflow exports code. It does. The site was never only code. Set beside the other two, the ZIP is still the straight answer: Wix documents no site export at all, and Squarespace exports one .xml file shaped for WordPress.
The CODES test names the seam. Data asks whether your records live in your database or someone else’s. On Webflow they live in a Collection until you export it, and the images stay behind after you do. The markup is yours to keep; the records are yours to fetch, one CSV at a time, before the plan ends.
The ZIP is a site with the middle taken out. Say so before you send it.
Rebuild it as a folder of files. All of it, this time.
Webflow’s export is already most of the way to the owned stack: static pages, styles, scripts and assets in a folder. What the stack adds is the middle Webflow keeps — the content as files in the same repository, a form endpoint you run, and a build step that fills every Collection page before it ships. Static files on hosting with a free tier, behind a strict content-security policy, making zero third-party requests at runtime.
Keep the domain. There is nothing to transfer: the help centre says Webflow is not a registrar, so the domain already sits with whoever sold it — or with IONOS, if the client bought it through Webflow. Point its DNS at the new host and the address on the client’s invoices does not change.
Move the content while the old site is still published. Export each Collection to CSV, then download the images and files the CSV points at, because those URLs die with the site. Export the form submissions and save the uploads the same way. The rich text arrives as HTML, which a static build takes as it is.
Then run the release gate before anything ships. A banned phrase, a dead link, a claim nobody can source: the build fails and nothing goes out. The CODES test tells you where to build; the gate keeps what you built worth handing over.
The export is a snapshot. The folder is the site.
Every claim above, dated and linked.
Sources
- Code export on paid Workspace plans, not Site plans; the ZIP’s contents; what is not included; forms, search and password protection on exported sites; editing the exporthelp.webflow.comAccessed 3 September 2026
- Collection export to CSV; rich text as HTML; images and files as Webflow-hosted URLs that break if the site is deletedhelp.webflow.comAccessed 3 September 2026
- Form submissions: CSV per form; uploads as URLs; no processing on exported sites; deleting submissions deletes the fileshelp.webflow.comAccessed 3 September 2026
- Collecting form submissions on an exported site: a third-party form service, or a custom form actionhelp.webflow.comAccessed 3 September 2026
- Webflow is not a domain registrar; domains bought through Webflow come from IONOS; any domain connects by DNShelp.webflow.comAccessed 3 September 2026
Read the sharpest chapter first. It costs an email.
We’ll send the build-gate chapter in full: the checks, the code, and the reasoning. Read it. If it doesn’t change how you think about shipping client sites, you’ve lost ten minutes and kept a working release gate.
That did not send. Check the address and try again.