# What Does Webflow's Code Export Include, and Can You Host It Elsewhere?

Canonical: https://figment.so/blog/webflow-code-export

Yes. On paid Workspace plans Webflow exports real static HTML, CSS and JavaScript you can host anywhere. CMS data, ecommerce, forms, site search and localized content are not included.

**Yes. Webflow's code export gives you real, static HTML, CSS and JavaScript that you can host anywhere, with no attribution required.** It ships only on paid Workspace plans. It does not include your CMS database, ecommerce data, working forms, site search, password protection or localized content, and several of those need a separate export or a third-party replacement before you leave Webflow's hosting.

## What plan do I need to export code?

You need a paid Workspace plan, because code export is a Workspace-level feature, not a site-level one. Webflow's help center states that on paid Workspace plans you can export your site's HTML, CSS, JavaScript and assets to back up your code, provide it to a client, or host it anywhere you like, with no attribution required ([Webflow](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code)). Webflow is explicit that **Site plans do not include code export**.

To run it, open the site, go to Main menu > Code export (the "W" logo, upper left) or press Shift + E, click **Prepare ZIP**, and download the file.

## What is in the zip?

The export package contains:

- Static HTML for every page, plus CMS Collection templates (the layout, not the live database)
- CSS, including your custom styles and Webflow's base/Normalize CSS
- JavaScript needed for interactions and animations
- An images folder with everything uploaded to the site's Assets panel

Interactions and animations that run in the visitor's browser (scroll effects, hover states, click triggers, tabs, sliders, accordions) are exported as working JavaScript and keep working on the new host.

## What does the export leave out?

CMS content, User Accounts, Ecommerce content, code components and their functionality, and localized pages, elements and content are not included. Webflow's export documentation lists these exclusions ([Webflow](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code)). Two need more detail:

- **Site search and native forms stop working.** Webflow says this is to comply with GDPR: forms (including file upload and reCAPTCHA) and site search will not work on exported sites, because they depend on Webflow's backend APIs, which an exported site no longer has access to (same source). A form element still renders, but submitting it does nothing until you wire it to something else. Submissions you already collected are not in the zip either, so export them separately.
- **Localization exports only the primary locale.** If you use Webflow Localization, the exported files contain just your default-language pages and content. Every localized version is left behind and needs a separate plan.

## How do I get my CMS content out?

Export it as CSV, one Collection at a time: open the Collection in the Designer and click Export. Webflow supports CSV export for CMS Collections, Ecommerce Collections and User Accounts, including localized Collection content, so budget time to do this once per Collection ([Webflow](https://webflow.com/updates/export-content-as-a-csv)). CMS content is not in the code export because it is a live database, not a set of files.

Image and file fields export as URLs pointing back to Webflow's asset hosting, not as attached files. Download those assets separately before you cancel hosting.

## How do I host the export on another host?

Follow these steps in order:

1. **Export the code.** Main menu > Code export (or Shift + E), then download the zip.
2. **Export every CMS Collection you use, individually, as CSV.** Do this before you touch hosting. The templates in the zip are useless without the content that used to fill them.
3. **Download the media library assets you need going forward.** CSV exports only link to Webflow-hosted URLs, which stop resolving once you leave.
4. **Unzip and inspect the folder.** You will see per-page HTML files, a `css/` folder, a `js/` folder and an images folder.
5. **Pick a static host** (Netlify, Vercel, Cloudflare Pages, or a plain web server) and upload the folder as-is, or connect it through Git if you convert it to a repository first.
6. **Replace the form element with a third-party form service.** Webflow's guidance for exported sites is to point the form at a third-party provider or embed a form built with one, then republish before exporting again so the new site talks to that provider instead of Webflow ([Webflow](https://help.webflow.com/hc/en-us/articles/33961341546899-Collect-form-submissions-on-exported-sites)).
7. **Re-add reCAPTCHA yourself,** following Google's integration guide. Webflow's built-in reCAPTCHA element does not carry over to exported sites.
8. **Rebuild anything CMS-driven** as static pages or a separate headless setup, using the CSVs from step 2 as your content source.
9. **Set up redirects on the new host** for any URL that changes, especially CMS item URLs that Webflow generated. Webflow's own 301 settings stop applying once your domain points elsewhere, so the redirects have to live on the host that serves the domain. Our [redirects guide](/blog/redirects-when-changing-website-builders) covers building the map.
10. **Point your domain's DNS at the new host** once you have verified that the static export renders correctly. Keep the Webflow project live until you have confirmed the new site works end to end.

## What still will not work after I move it?

- **Site search** needs a separate implementation (a hosted search service, or a client-side index you build yourself). No toggle restores it.
- **Ecommerce** does not export as working checkout code. Only the product Collections come out, as CSV, for you to rebuild on a different commerce platform.
- **Password-protected pages become public.** Webflow states that protected pages "will no longer be protected after code export." Delete them from the exported folder, or put them behind your new host's access control, before you upload anything.
- **User Accounts** (Webflow's built-in membership feature) export as CSV data only. Webflow switched User Accounts off on all sites on January 29, 2026, so any login or membership system needs a replacement anyway. See [Can Webflow do memberships?](/blog/webflow-memberships).

## What if something goes wrong after the move?

Keep the original Webflow project and its hosting active until you have checked the exported site end to end: every page loads, every form submits somewhere real, every CMS-driven page still resolves at its old URL or redirects correctly, and images display. Exporting does not delete or disable the original site, so if a page is missing or a redirect is wrong you can still pull the missing CSV or re-export the code from the live Webflow project. Cancel Webflow hosting only after the new host has been live and verified for as long as you are comfortable with.
