To export a CMS-based Webflow project as a static site, you must convert dynamic content into static HTML since CMS functionality relies on Webflow’s hosting.
1. Understand the Limitation of CMS Export
- Webflow CMS content cannot be exported dynamically; it only works when hosted on Webflow’s platform.
- Exporting the site will only include static pages and CMS Collection pages that were generated at the time of export.
2. Prepare Your CMS Items
- Publish your site first to make sure all CMS pages and Collection lists are updated and indexed.
- If your CMS pages are paginated or filtered using JavaScript, only the currently visible content will be exported as static HTML.
3. Convert CMS Content Into Static Content
- Manually create static pages or bind CMS content to Collection Pages that are accessible as individual pages.
- Only fully rendered Collection Pages and Collection Lists on static pages will be included during export as static HTML.
4. Export the Code
- Go to your Webflow Designer.
- Click the Export Code icon (top right, arrow pointing out of a box).
- Click Prepare ZIP to generate your site files.
- Download the resulting ZIP file, which will include:
- HTML files
- CSS and JavaScript assets
- Images stored in the site
- Any dynamic CMS content not rendered directly on a page will be lost.
5. Manually Handle CMS-Dependent Features
- Features like form submissions, search, and filtering will not function after export, unless you rebuild them using external JS libraries or APIs.
- To retain form functionality, integrate third-party tools like Formspree or Netlify Forms.
Summary
To export a Webflow CMS site as a static site, make sure all CMS content is rendered on pages at export time. Webflow will only export what is visible/rendered—no dynamic CMS logic. Download the ZIP, and manually replace or rebuild dynamic functionality with static or third-party solutions.