Export Webflow CMS

The phrase “export the CMS” gets used three different ways:

1. Just the rendered HTML.What a site crawler gets: the published page for each CMS item. Useful for rehosting the static site, useless if you're rebuilding on a framework.
2. The raw CSV the Webflow Designer offers. One CSV per collection, no rich text formatting, no asset URLs, references as item IDs. Hard to use in any modern stack.
3. Structured content the way an SSG expects it. One folder per collection. One file per item, with YAML front-matter and a rich-text body. Assets downloaded with relative paths. References as slugs. This is what Webflow Export produces.

/
  blog-posts/
    the-case-against-cms.md
    the-case-against-cms.mdx
    the-case-against-cms.json
    shipping-faster.md
    ...
  authors/
    alex-thomas.md
    sam-kerr.md
    ...
  categories/
    engineering.md
    growth.md
  assets/
    cover-the-case-against-cms.jpg
    cover-shipping-faster.jpg
    author-alex-thomas.jpg
    inline-1-shipping-faster.png
  cms.json     # combined index of all collections

cms.jsonis a convenience index — every collection and item in one file, useful if you're feeding the content into something that reads JSON instead of crawling a directory.

• Drafts and archived items. Off by default — only published items are exported. Toggle the option during scan to include them.
• Slug collisions. If two items in the same collection have the same slug (rare, but possible after manual edits), the second is suffixed with -2 and a warning shows in the scan report.
• Very large rich-text fields. Webflow has a 10k character limit per rich-text field; we handle the full range. Tables, code blocks, and nested lists round-trip through the HTML → Markdown conversion.
• References to deleted items. If an item is referenced by a field but no longer exists, the reference is dropped and a note appears in the export log.
• Custom field plugins. Anything that produces a standard Webflow field type exports normally. Truly custom plugin data (rare) might need manual handling — open a ticket via contactand we'll look at the specific case.