If a client no longer wants to use Webflow CMS but still wants to retain the content and design, you can access and preserve the site without rebuilding everything by exporting and/or archiving the content and site code.
1. Export Static HTML from Webflow
- Go to Webflow Designer, click the Export Code icon (arrow pointing out of a box in the top right).
- Webflow will generate a ZIP file of the HTML, CSS, JS, and images for all static pages.
- Note: CMS content is not exported unless you manually place it into static pages.
2. Convert CMS Content into Static Pages (Optional but Required for Content Preservation)
- Create Collection Templates that list all CMS content in a visible format.
- Manually copy CMS collection pages or generate list pages that show all important CMS data.
- Publish the site and then export the pages, which now contain rendered CMS content.
3. Export CMS Content via CSV
- Go to CMS Collections in Webflow Designer.
- Click the setting icon next to the collection and select Export to download the full collection as a CSV file.
- This can be imported into a different system (e.g., WordPress, Notion, Airtable).
4. Use Webflow API (Advanced Option)
- If you need to extract large amounts of structured CMS content, use the Webflow CMS API.
- Requires generating an API token and using external tools (like Postman or a custom script) to request collection data.
- Useful if there's too much to manually export or if you need more control.
5. Host Exported Files Elsewhere
- Use services like Netlify, Vercel, or traditional web hosts to deploy the static site you exported from Webflow.
- Upload the ZIP contents and serve it as a non-CMS, static website.
Summary
To make a Webflow CMS site function without CMS features, export static HTML pages (after visually embedding CMS content), download CSV files of collections for future use, and optionally use the Webflow API to programmatically access CMS data. This avoids rebuilding the site from scratch while preserving both layout and content.