Exporting a Webflow site you don't own the Workspace for: what a 62-post CMS looks like from the outside

When you publish a Webflow site, it becomes static HTML with CMS marks scattered throughout. We conducted an export on 31 October 2026 of the public site marketing.flowbase.co, and the resulting files revealed a wealth of information. There were 62 posts, 21 pages, 577 images (weighing in at approximately 94 MB), and more than 229 additional CMS items that were not posts.

The HTML code included data-wf-site, data-wf-collection, and data-wf-item-slug, marking every Webflow page, CMS items, and their respective slugs. However, the sitemap did not explicitly indicate which collection served as the blog. We established a rule to name the blog collection as blog/posts/articles/news, or use the largest collection as the default if no such naming convention was present.

Some posts had just one date, while others had none. Consequently, only the sitemap's lastmod (last publish date, not first) was retained for those posts. The body of the HTML element stood as the largest, with -p-500 resized image copies mapping back to their original files. Similarly, a newsletter block was repeated on 16 pages, each with its own set of images.

Short sections containing forms were omitted from the final export. What a visitor can't see through their own view includes categories/authors/tags (all CMS references), forms, e-commerce, memberships, code embeds, layout, and drafts. For a comprehensive guide on this process, visit https://decamp.app/notes/webflow-cms-export.