How to Export Your Webflow Blog

Webflow has no WordPress export. What it gives you is a CSV file for each CMS Collection, with your posts' rich text as HTML and their images as links to files Webflow hosts. WordPress can't import that file on its own, so you need an import plugin, a developer, or a migration tool such as Blog Porter.

We checked every claim about Webflow and WordPress below on 13 November 2026, on their own websites or by looking at live Webflow blogs. Moving your whole site, not just the blog? Start with how to migrate Webflow to WordPress.

The short answer

• A handful of posts: copy and paste them. It costs nothing.
• A spreadsheet-style backup: Webflow's CSV export. It's quick, but the images still live on Webflow.
• A developer and a custom destination: Webflow's Data API.
• Dozens or hundreds of posts going into WordPress: Blog Porter. It imports the posts with formatting, slugs and images.

What Webflow gives you

The CSV export. Webflow lets you export any CMS Collection as a CSV file, to back it up or move it to another platform:

1. Open the CMS panel.
2. Click the name of your blog Collection, often called Blog posts.
3. Click Export.

You can also select a few items and export just those. Two details catch people out. The file includes archived items, and on a site with more than one language it only includes items from the locale you're viewing.

The code export. Webflow can export your site's HTML, CSS and JavaScript, but only on paid Workspace plans, and CMS content isn't included. Your Collection pages come out as empty templates, so this doesn't export your blog.

The RSS feed. You can turn on an RSS feed for a Collection. Each item carries a title, an image and a description that Webflow describes as a short summary. It's made for readers and newsletters, not for moving full posts.

What's in the CSV file

Webflow's help page explains how each kind of field is exported:

• Rich text (your post body) comes out as HTML.
• Images and files come out as links to files Webflow hosts.
• Reference fields, such as a post's author or category, come out as plain text.
• Multi-reference fields come out as a comma-separated list of text.
• Most other fields come out as plain text or URLs.

The file also has an Item ID column, which Webflow uses to match rows when you import a file back into Webflow. WordPress has no use for it.

Rich text fields can also hold code embeds and component instances, such as a call to action or a form. Webflow's help pages don't say how these come out in the CSV, so open a post that uses one and check its HTML in the file.

Map the CSV columns to WordPress

Every Collection has a Name and a Slug field. The rest depends on how you set up yours. A typical blog Collection maps like this:

An import plugin such as WP All Import lets you map each column to a WordPress field. Anything you don't map, such as option or switch fields, is left behind.

Where the CSV route breaks

WordPress can't read it. The importers listed in WordPress's import documentation cover Blogger, LiveJournal, Movable Type, RSS, Tumblr and WordPress files. The only CSV importers it mentions come with WooCommerce, for products and tax rates. For posts, you need a plugin such as WP All Import, which imports CSV files into posts. Its free version doesn't import images into your media gallery. That's a Pro feature.

The images stay on Webflow. Webflow says image URLs in the export point back to the site you exported from. If you delete that site, those links break, including images inside rich text. On every Webflow blog we looked at, post images loaded from cdn.prod.website-files.com. After a CSV import, each one has to be downloaded into WordPress and its link replaced.

Categories and authors arrive as text. WordPress categories, tags and authors are separate records, so you map these columns to them in your import plugin, or set them by hand.

Archived posts are mixed in. Filter them out of the spreadsheet before you import, unless you want them back.

Dates need choosing. Webflow keeps a Created On, Updated On and Published On date for each item, and your Collection may have its own date field as well. Decide which column becomes the WordPress publish date, and check that it's in your file.

The CSV route can work for a small, simple blog if you don't mind fixing images and categories afterwards. For a larger blog, the image work alone takes longer than the import.

Option 2: copy and paste

Open each post on your live Webflow site, copy it, and paste it into a new WordPress post. It's free and slow. For every post you fix the formatting, add the images again, and set the date, slug, category and tags by hand. Our estimate is 10 to 15 minutes per post, so 50 posts take roughly 8 to 12 hours.

Images pasted this way can keep loading from Webflow. In the WordPress editor, select each image and use Upload to Media Library in the block toolbar. WordPress warns that a linked image may stop displaying if the original file is moved or deleted.

Option 3: Webflow's Data API, for developers

Webflow's API can list a Collection's items, up to 100 per request, with a token that has the CMS:read scope. According to Webflow's field type reference, rich text comes back as HTML, images as objects with a URL, and reference fields as 24-character item IDs. Option fields come back as option IDs.

So you look up every referenced item to get its name, download every image, and write each post into WordPress yourself. It can reach every item, but it's a small software project, not an export.

Option 4: Blog Porter

Blog Porter is a WordPress plugin. You install it on your WordPress site and enter the public page that lists your posts, such as yoursite.com/blog. It collects the post links on that page, follows Webflow's Next button through a paginated list, and imports each post it finds.

It imports:

• the post title and the main rich text field, with formatting
• the original slug
• the featured image, from the page's Open Graph image or structured data
• available inline and featured images, downloaded into your WordPress Media Library, with a retry for any that fail
• the publish date, author and tags, when your post template includes article structured data (JSON-LD)
• each post page's meta description, saved where Yoast SEO, Rank Math or SEOPress read it

The analysis is free. It lists the posts it found and shows the exact price before you pay: $0.20 per post, with a minimum of 5 posts, paid once. A 50-post blog costs $10. The import runs in resumable batches inside WordPress.

Check four things before you run it:

1. Your listing page links to your posts. Blog Porter collects the post links under the address you enter, such as /blog/post-name. If your posts live under their own Collection path, such as /blog-posts/post-name or /post/post-name, it reads the links in the page's Collection list instead. Keep your Webflow URLs in WordPress explains how Webflow builds these addresses.
2. The list shows every post. A Collection list shows up to 100 items unless pagination is on, and a display limit or filter shows fewer. A list that loads more posts with a script, such as a "load more" button, only shows Blog Porter its first batch.
3. Your posts are published and public. Blog Porter can't read drafts, archived items, or pages behind a password.
4. Your template has a publish date Blog Porter can read. Blog Porter reads the date from article structured data or, without it, from a date shown on the post page in an element whose class name includes date. If it finds neither, posts are dated the day you import them. You can add it first: on a paid plan, Webflow lets you add schema markup to a Collection page and bind it to your Collection fields.

Blog Porter imports a post's category when the post page links to the category page. It doesn't import other reference fields or custom fields, so check your categories in WordPress after the import.

What none of these moves

These routes are about blog posts. Plan for the rest of your Webflow site separately:

• Pages, design and interactions. You rebuild these with a WordPress theme and plugins.
• Forms and code embeds. Blog Porter removes forms and scripts from post content, so check any post that used an embed.
• Redirects. None of these routes creates them. Keep your Webflow URLs in WordPress shows how to keep old links working.

Before you cancel Webflow

Keep your Webflow site published until every post is in WordPress with the right slug and date, no post still loads images from website-files.com, and your URLs or redirects work. Webflow says deleting the site breaks its hosted images, and Blog Porter can only read posts that are still public. How to migrate Webflow to WordPress lists every step in order, from hosting to DNS.

Move your Webflow blog into WordPress

Install Blog Porter in WordPress, enter your blog listing page, and the free analysis shows the posts it found and the exact price. Start with Install the Blog Porter plugin, or read more about moving from Webflow to WordPress.