Webflow vs WordPress.com

Both of these appeal to people who dislike being locked in, and they offer different escapes. Webflow gives you the code. WordPress.com gives you a file the largest publishing ecosystem in the world can read.

Two roads to owning the output

Webflow exports the code and you can take it elsewhere. WordPress.com exports content in a file another WordPress site will read, and because WordPress is the software a great many websites already run on, there is somewhere obvious for that file to go.

Those are not equivalent. Webflow's export gives you markup and no system around it; WordPress.com's gives you a system and no design. Which is more useful depends on whether the thing you would hate to lose is the layout or the archive.

Webflow scores 5 for design against WordPress.com's 3, with any hand-buildable layout reachable and Collections generating pages from a shape defined once. WordPress.com has plugins from the cheapest paid plan, which is a different kind of extensibility and a much larger catalogue.

What competence costs upfront

Webflow scores 2 for ease and WordPress.com scores 3, and neither is a drag-and-drop builder. Webflow competence takes weeks rather than an afternoon. WordPress.com has more concepts to learn than a drag-and-drop builder — themes, plugins, settings in more than one place — but the learning is spread out rather than front-loaded.

The bills differ in shape. Webflow's site plans, workspace plans and add-ons stack into one total that the entry price does not predict. WordPress.com's advertised entry rate lasts twelve months and then renews at roughly two and a half times as much.

Neither has much support to lean on: Webflow scores 3 for support and WordPress.com scores 2. Both have a free plan, and both expect you to find the answer yourself.

Which should you choose?

Choose Webflow if a designer is doing the work, the layout is the reason this site exists, and taking the markup with you is the escape you care about.

Choose WordPress.com if the writing is the point, you want plugins and a very large ecosystem behind you, and you would rather spend the design budget on something else. Diarise the renewal.