Webflow CMS export to dashboard
Read your Webflow collection like a content inventory.
Export a collection from the Webflow CMS, drop the CSV here, and it becomes a content inventory instead of a wall of text. Draft and Archived items are filtered out of the published counts, comma-joined multi-reference fields are split back into individual tags, and the three date columns are read as dates so you can see publishing cadence rather than guessing at it.
Prefer the full explorer? Open the app, or start from the generic dashboard builder.
You are exporting a collection, not a site
The most common misunderstanding about Webflow CMS exports is scope. There is no button that gives you the whole site. You export one collection at a time, so Blog Posts comes out as one file, Authors as another, Case Studies as a third, and the relationships between them survive only as reference fields full of names or slugs. If your mental model is a database dump, adjust it: this is closer to exporting one table and hoping the foreign keys still read.
The second thing to know is that the export does not care about publish state. Drafts are in there. Archived items are in there. Both look exactly like live content except for a boolean in a column near the end. Any count of published posts that skips those two columns is wrong, usually by more than people expect, because most sites accumulate a quiet pile of half-written drafts. This page reads Draft and Archived first and splits the collection before it counts anything.
How to export from Webflow
- Open the CMS panel in the Designer or Editor In the Webflow project, open the CMS section from the left sidebar. You will see your collections listed: Blog Posts, Authors, Categories and whatever else the site defines.
- Pick one collection Click into the collection you want. The export applies to that collection only, so decide up front whether you need the posts, the authors, or both as two separate files.
- Use Export to CSV The control is in the collection settings menu at the top of the item list. Depending on your plan and role this may be limited, since CMS export is not available on every site plan.
- Open the file and check the quoting Rich text fields come out as HTML. Confirm those fields are wrapped in quotes before you feed the file to anything strict, because unquoted HTML with commas in it will wreck the column alignment.
- Drop it on this page Collection, Author and Category become group-by chips, the date columns become a timeline, and the draft and archived split appears in the summary strip.
If you plan to re-import edited rows back into Webflow, keep the Slug column exactly as exported. Webflow matches on slug, and a changed slug creates a duplicate item instead of updating the existing one.
Try with sample Webflow data (the same columns, 92 rows, no upload needed).
What the dashboard shows
Every panel below is built from a column that is actually in the export, named the way Webflow names it.
- Publishing cadence. Published On as a timeline, so a blog that claimed to be weekly and was actually monthly has nowhere to hide.
- Draft, archived and live. Three counts side by side. The draft pile is usually the most interesting number in the file and the one nobody tracks.
- Author output. Author ranked by published items, with the option to weight by read time rather than by count.
- Category and tag spread. Multi-reference tags split on the comma, so a post tagged with three things counts once in each rather than once in a joined string.
- Created against published lag. The gap between Created On and Published On, which tells you how long content really sits in review.
- Read time distribution. Read Time as a histogram, which is a decent proxy for depth and quickly shows whether the long pieces are the featured ones.
Name,Slug,Collection,Author,Category,Published On,Created On,Updated On,Archived,Draft,Featured,Read Time (min),Summary,TagsWebflow CMS export details worth knowing
- One collection per export. There is no whole-site export. Related collections come out as separate files, and the links between them survive only as text in a reference field.
- Drafts and archived items are included. Both look like ordinary rows. Two boolean columns are the only difference, and forgetting them inflates every published-content metric you compute.
- Multi-reference fields are comma-joined. Three tags arrive as one string with commas inside it. If the field is not quoted properly, that string also breaks your column count.
- Rich text exports as HTML. Paragraph tags, links and the occasional embed, all inside one cell. A naive line-by-line reader that ignores quoting will explode on the first article that contains a comma or a newline.
- Dates follow the site display format. Not ISO. Whatever format the collection is configured to display is what lands in the file, so day-first and month-first sites produce different-looking exports of identical data.
- Re-import matches on Slug. Edit a slug in your spreadsheet and Webflow treats the row as a new item on import. That is how sites end up with two copies of the same article and a broken canonical.
A Webflow export is a snapshot of one collection with its publish state attached, nothing more and nothing less. Treat it that way, split the drafts out early, and it becomes the content audit that most sites never get around to running.
Frequently asked questions
Can I export my whole Webflow site as CSV?
Not in one file. CMS export works per collection, so a site with posts, authors and categories gives you three separate downloads, and static Designer pages are not part of the CMS at all so they are not included anywhere. If you want a joined view, export each collection and match them on the reference fields, which usually carry the item name or slug rather than an id.
Why does my published post count look too high?
Because drafts and archived items are in the export and look identical to live content apart from two boolean columns. Most sites carry a surprising number of abandoned drafts, and archived items stay in the collection rather than being deleted. Filter on Draft equals false and Archived equals false to get the genuinely live set. This page splits the three groups automatically and shows each count.
How do I handle the rich text HTML in the export?
Leave it quoted and read it as a single value. Webflow writes the full HTML of a rich text field into one cell, including tags, links and any embed markup, and that content routinely contains commas and line breaks. A parser that respects RFC 4180 quoting handles it fine. A quick split on commas does not, and you get rows with wildly different column counts.
Why are my tags all in one column?
Multi-reference fields export as a single comma-joined string, since CSV has no notion of a list. Three categories on one post become one value with two commas in it. The dashboard splits those back apart so each tag counts individually, which is the only way a category breakdown makes sense. Without splitting, every unique combination becomes its own fake category.
Can I edit the CSV and import it back?
Yes, with one rule: do not touch the Slug column. Webflow matches incoming rows against existing items by slug, so an edited slug creates a brand new item rather than updating the one you meant. Keep slugs intact, edit whatever else you like, and check the field mapping screen carefully on import since Webflow will not always guess it right.
Do my unpublished drafts get uploaded anywhere?
No. The file is read inside your browser tab and the dashboard is drawn from memory. Unpublished drafts are exactly the sort of content you would not want passing through a stranger's server, which is a good part of why this page has no server component. Close the tab and nothing about your content remains.
Related tools
Audit a content collection in about ten seconds
92 CMS items with drafts and archived posts mixed in, comma-joined tags, HTML summaries and three date columns in the site's display format.
Open the sample Webflow dashboard