Can Webflow export Blog and CMS content along with the rest of the code when uploading through FTP?
TL;DR
- Webflow’s code export only includes static HTML, CSS, JavaScript, images, and hard-coded content.
- CMS content like blog posts and dynamic Collection Pages is not exported and must be manually converted or rebuilt using an API or a headless CMS.
Webflow cannot export CMS or Blog content when exporting code for FTP upload. Only static content and structure are included in the export.
1. What Webflow Exports
When you use Webflow’s Export Code feature, it includes:
- HTML, CSS, JavaScript, and images of static pages
- Content on those pages hard-coded at the time of export
- Structure and styling of the site as seen in the Designer
2. What Is Not Exported
The export does NOT include any CMS items, such as:
- Blog posts or dynamic collections
- CMS Collections, fields, or Collection Pages
- Editor functionality or CMS backend
3. Why CMS Content Isn’t Exportable
Webflow CMS runs on Webflow’s proprietary backend, which powers dynamic content via their own database engine. When you export your site, it becomes purely static, so there's no access to:
- Collection templates
- Dynamic filtering or sorting
- CMS binding logic
4. Workaround Options
To manually include CMS/blog content in a static export, you can:
- Convert CMS content into static pages: Copy and paste content into static pages manually before export
- Use Webflow’s API: Pull CMS data and recreate it on another platform, but this requires custom development
- Switch to a headless CMS: If self-hosting, you might recreate your CMS using tools like Sanity, Contentful, or Strapi
Summary
You cannot export CMS or blog content with Webflow’s FTP/export tool. Only static elements are included. To host a Webflow CMS site externally, you'll need to rebuild or replicate the CMS functionality outside Webflow.