Observations of Webflow as a WordPress Developer in 2026

For over a score now, I’ve beaten the war drums for WordPress. I’ve built roughly 50 websites using it — job boards, small business sites, university portals, a website for a monk church, sites for art exhibitions, and a handful that were pulling close to a million monthly users. I’ve also built a few that, in hindsight, probably should never have been squeezed into WordPress at all. But that’s a story for another post.

My job as a developer isn’t to “build a site in WordPress.” It’s to create a website for a client that helps them meet their clients’ needs online. That distinction matters more than it sounds. So over the last two years, I’ve taken on some Webflow work – helping clients maintain existing sites and launching new ones from scratch. So after a few case studies, here’s where I’m at:

What I like about Webflow

Breakpoints – If you’ve spent any time fighting with responsive layouts in WordPress — stacking Gutenberg blocks, wrestling with a page builder’s mobile overrides, or writing media query patches in a child theme — Webflow’s approach feels like breathing fresh air. You’re working visually at every viewport from the start. What you see is genuinely what you get, and the feedback loop between design decision and real-world result is tight in a way that WordPress, for all its strengths, has never quite matched.

Components – The component model is the other thing. Webflow calls them Components, which maps neatly to how designers and modern front-end developers already think. You build a card, a nav, a hero block — and you reuse it with overrides rather than copying and praying everything stays in sync. In WordPress, we kinda have this in Patterns, but there’s Synced Patterns and unsigned, and block templates. The lines between all 3 can be confusing, and is slightly adjusting with every major update.

CSS Sidebar – The CSS tab on the right sidebar has nearly everything you’d need for doing a visual layout. Box Diagram, Font styles, colors, Flex Layouts; It’s all there on one screen and fairly easy to scan. And you can add custom rules which are basically random CSS rules that don’t fit into normal groups. Gutenberg style settings for blocks aren’t terrible, but the learning curve doesn’t feel as shallow, and the flex-align, item-align, flex options aren’t as user friendly as Webflows.

What I still think WordPress does better.

Here’s where I’ll probably lose a few Webflow enthusiasts, but I think the gap is real: WordPress is a significantly better platform for managing content.

Media Library – The Media Library alone is something Webflow has refused to change. In WordPress, a client’s entire asset library — images, PDFs, documents, videos — lives in one organized, searchable place. You can edit images, swap out a file sitewide, and give editors a familiar, structured environment to work in. Webflow’s asset management is locked into the page builder. Have a blog post and need a featured image? gotta upload a new one, can’t use one already used on the site. You can cheese this by maybe setting up a URL/link field but it’s still not as smooth as WP’s Media Library.

Custom Post Types – WordPress’s custom post types and taxonomies give you a real content model. Events, team members, case studies, resources, locations — you can build content structures that mirror how a business actually organizes its information, and then surface that content flexibly across the site. Webflow’s CMS Collections are manageable, and I truly think the visually hooking fields into layout is something WP could take a page out of, but once a client’s content needs get complex, the seams start to show.

Core Blocks – I’m shocked that Webflow doesn’t have a native dialogue block. You can clone someone else’s easily, or make one yourself, but for god sake we have native HTML5 <dialog> elements, we shouldn’t he having to craft something like that from scratch. I know WP only just got these added like a year or 3 ago, but the amount of Gutenberg blocks that use HTML5 block syntax is under appreciated.

Ecosystem – This is where I think the comparison isn’t even close yet. WooCommerce, Gravity Forms, membership plugins, LMS platforms, booking systems, CRM integrations — the WordPress plugin ecosystem is two decades deep and battle-tested across millions of sites. Webflow can handle some of this through third-party embeds and integrations, but if a client needs e-commerce operation, a members-only portal, or a lead-generation workflow with conditional logic, WordPress gives you more to work with and more control over how it all fits together.

The honest summary

Webflow is an exceptional tool for building a visually precise, design-led website. If the primary goal is a beautiful, fast marketing site and the content needs are relatively straightforward, it’s a genuinely compelling choice — especially if you’re working closely with a designer.

But WordPress is still the better platform for running a content-heavy or business-logic-heavy website. The question I ask myself now before recommending either one is simple: what does this client actually need to do, day in and day out, once the site is live? If the answer involves managing a library of content, running business operations through the site, or building out custom workflows — WordPress is still where I point them.

The right tool for the job.