How to Export a Webflow Site: Static Code, CMS Data, and Backups

Webflow gives you three separable artifacts. The first is a static ZIP containing HTML, CSS, JS, images, and fonts — the visual output of your site at the moment of export. The second is CMS collection data, exported as CSV files, one per collection. The third is a full site backup, which is Webflow-internal and only useful for restoring inside Webflow. For any migration — to WordPress, to another static host, to a custom stack — you need the first two and can ignore the third.

Open Project Settings from the site's Designer, go to the Export tab, and confirm that code export is available. If it says the feature requires an upgrade, upgrade the site plan (or ask the workspace owner to). Once available, click Export Code to trigger the download. The ZIP typically arrives within 30 seconds for a small site and up to a couple of minutes for larger sites.

For each CMS collection your site uses, open the collection in the Designer, click Settings, and export the collection as CSV. Repeat for every collection. Save the CSVs in a folder next to your static ZIP — you'll re-import them into your destination platform's CMS after migration. Categories, tags, and reference fields are preserved as columns; multi-reference fields are comma-separated inside a cell.

Unzip and you'll see a folder structure that mirrors your Webflow pages: `index.html` for the homepage, one HTML file per static page, a `css/` folder with the compiled stylesheet, a `js/` folder with the interactions bundle, `images/` for all uploaded images, `fonts/` for custom fonts. Every internal link is relative, so the site works when opened as a folder or served from any static host without additional configuration.

For WordPress migrations, drop the ZIP into the AI to Wordpress uploader. The static-html pipeline detects the Webflow output structure, extracts the shared header and footer into `header.php` and `footer.php`, generates a `page.php` template per HTML file, packages the CSS and JS into the theme, and mirrors images and fonts into the theme's assets directory. Total time: under two minutes for most sites.

For each Webflow CMS collection, use WP All Import (or the built-in Tools → Import → CSV) to bring the CSV into a matching WordPress custom post type. Field mapping is manual the first time and takes about ten minutes per collection. Once mapped, re-imports (for subsequent Webflow exports) are one-click. Blog posts typically map to the built-in Posts CPT; other collections map to newly-created custom post types.

Exported forms have no submission endpoint. In WordPress, install Contact Form 7 or WPForms, create a form that matches your exported markup, and replace the exported form's `<form>` tag with the plugin's shortcode. Alternatively, keep the exported HTML and point its `action` attribute at admin-ajax.php or a REST endpoint you register in a mu-plugin. Both approaches take under an hour for a typical site with two or three forms.

If you don't want WordPress, the exported ZIP is deployable to any static host: Netlify, Vercel, Cloudflare Pages, GitHub Pages, a $2 shared hosting account. Just upload and point DNS. Static hosting is cheap and fast but leaves you without a CMS — for editorial teams that matters, which is often why the WordPress route is more common.

Export whenever the design has meaningfully changed. Store each export in a dated folder so you can compare versions if a bug appears after re-migration. If you're on a serious cadence (weekly exports), automate: Webflow has a Data API that can trigger exports programmatically, and CI can drop the resulting ZIP into your migration pipeline. Most teams don't need this level of automation, but it's available if the scale demands it.