Webflow or WordPress Is the Wrong Question

The platform question is downstream of a people question. Decide who on your team needs to change the site, how often, and what happens today when they try. Then decide how much developer time you are willing to keep between a marketing team and a page change. The platform follows from those answers, and the feature comparison you were about to run gets much shorter.

We spent an hour in early September with Jordan Maslyn, an ex-COLABer and current Lead Solution Architect at Webflow, in a session our team titled “Is Webflow better than WordPress?” Jordan built on Drupal and WordPress for years before moving to Webflow, including work on headless WordPress at WP Engine. To our question, he did not answer yes. He answered with the reframe titled, then spent the hour showing where each platform holds up and where it does not.

If you want the feature-by-feature comparison instead, we have written that one separately. This piece is about the decision that comes before it.

The real decision is about who changes the site

Webflow’s positioning is specific. It is built for organizations where marketers, communications staff, and content editors own the site day to day, and where an agency or in-house developer builds the design system underneath them. Jordan described the pattern he sees most often: an agency runs a three to six month engagement, ships a design system and a replatformed site, and then the client’s own team runs campaigns, landing pages, and content without filing a ticket for each one. Most agencies stay on retainer for the work that still needs them, like a net-new component or a CRM integration.

Before you sit through a single demo, answer four questions with your own team in the room:

• Which five changes does your team make most often, and who makes them today?
• When one of those changes needs a developer, how long does it wait?
• Who is allowed to publish to the live site, and who should be?
• What happens to the site if the person who knows it best leaves in six months?

Those answers narrow the field faster than any feature matrix. In our experience the pattern that points toward Webflow is a small communications team with a steady campaign calendar and no developer of their own. The pattern that points away from it is a site carrying logic: gated member portals, complex integrations, anything closer to an application than a set of pages.

Jordan was direct about that boundary. Intranets, member portals with complex logic, anything leaning on a large library of third-party plugins, and builds where requirements keep moving into custom functionality are all places where a general-purpose CMS still wins. His words, not ours: WordPress still wins on flexibility and customizability from an engineering perspective, and Drupal sits in similar territory.

COLAB can build on both, and our recommendation follows the client’s team and roadmap rather than the platform we know best.

The design system is what your team inherits

The thing a client’s team actually inherits from an agency build is not a website. It is a design system, and its structure decides whether they can maintain the site or stop trying.

Webflow’s model will read as familiar to anyone who thinks in CSS. Variables live in collections with modes, so a theme collection can carry base, inverted, and accent values while a responsive collection carries tablet and mobile values. Style selectors map to real HTML and CSS selectors. Components follow atomic principles, support slots for nesting, and expose props that lower-permission users can change per instance without touching the component definition.

The practical effect is that a marketer can change a heading level or a section’s padding through a prop while the component itself stays locked. How much you expose is a build decision, not a platform limitation. We plan that exposure deliberately, component by component, because it is the difference between a client team that publishes confidently and one that files a ticket rather than risk breaking a page. That planning spans the design work and the build together.

On the Figma handoff, Jordan was candid that the older Figma-to-Webflow plugin made promises it did not keep at scale. Variables ported cleanly. Responsive components and motion did not. What he sees working better now is pairing Figma’s MCP server with Webflow’s and having an AI assistant move variables between them. For raw HTML and CSS, Webflow has a tool called Code to Canvas that maps generated markup into Webflow’s own structure. Webflow is not rendering your HTML, it is translating it into Webflow’s own design language, so fidelity degrades as input size grows. Jordan’s advice was to work one section at a time rather than asking for a whole page in one pass.

Motion is a strength. Webflow acquired GreenSock, the company behind GSAP, in October 2024, and built a timeline interface on top of it. Teams that prefer code can still write it.

Governance is the part IT and InfoSec asks about first

Webflow’s permission model is built around roles that range from view-and-comment access through full site administration, with editing tiers in between. A content editor can fix copy and swap images but cannot add sections. A marketer can build pages and add sections, but only from existing components. Designers can create and change components. Site managers control settings and permissions.

Two capabilities matter more than the role list. Access can be scoped by locale, by CMS collection, and by individual page, so a translation team can be limited to one language and kept out of the homepage entirely. And an approval workflow can require a user to work in a page branch and submit changes for review before merging, which is a sensible default for staff new to the platform.

Here is the part to settle before anyone falls in love with the demo. Almost every governance feature above is gated by plan. Webflow’s documentation places custom roles, design approvals, granular access controls, and the site activity log on Enterprise plans and Enterprise partner accounts. Page branching and single-page publishing require Team or Enterprise Platform. A nonprofit or membership organization evaluating Webflow on a CMS or Business plan is not evaluating the governance model described in most Webflow demos.

That is a budget conversation, and it belongs in platform selection rather than in the first invoice after launch. It is also the single most useful question to ask a vendor in a demo: which plan is this screen on?

On recovery, Webflow creates a restore point automatically on every fiftieth auto-save, and users can create one manually at any time. Backups can be previewed in a separate tab before restoring, which helps when you are not certain which version you want. Paid plans keep unlimited backups. Free Starter plans can restore only the two most recent.

Jordan called version control an area where the platform could do better, and he is right. Restores are whole-site, not granular. The site activity log, available on Enterprise plans, records class, component, variable, custom code, CMS, and publish events, and it distinguishes whether a change came from a person, from Webflow AI, or from an MCP-connected tool. That last detail will matter more every quarter.

The security posture is structural rather than promotional. Webflow deploys static HTML, CSS, and JavaScript, which removes the server-side application layer that a server-rendered stack has to keep patched. Client-side risk from embedded third-party scripts remains, and custom code access is itself a permission you can withhold from the people most likely to paste something in.

Apps are a narrower surface than WordPress plugins. Webflow reviews every app submitted to its Marketplace against published guidelines before listing, and Designer Extensions operate inside the Designer rather than running arbitrary code on the live site. That is a meaningfully different risk profile from a WordPress install carrying forty plugins, each with its own update cadence and maintainer. Webflow holds SOC 2 Type 2 attestation and ISO 27001:2022 certification, both documented on its trust center.

The content model is relational, and publishing has three constraints

Webflow does not separate post types from taxonomies the way WordPress does. Everything is a collection, and relationships are built with reference and multi-reference fields, so a blog collection can point at a categories collection and a category can feature a single post. Anyone who has built with custom fields in WordPress will recognize the shape. Jordan’s own comparison: it does not reach the full extent of ACF, but it covers a good share of it. If your information architecture depends on hierarchical taxonomies, model it on paper before you commit.

Publishing supports full-site and single-page publishing, and individual CMS items can be published on their own or queued for the next site publish. Three constraints deserve attention before a content team builds a process around it.

Schema changes require a full-site publish. Webflow’s documentation is explicit: change a collection’s structure and the whole site has to go out for it to take effect. Content model work cannot ship in isolation the way a single page can.

Single-page publishing is narrower than it sounds. It carries the page’s content, design, page-level settings, and custom code, but not CMS item data and not site-level settings like fonts, redirects, or site-wide code. There is no rollback on a single-page publish, and it requires a Team or Enterprise Platform plan.

Branching is scoped to one page at a time, which limits it for a site-wide refresh, and it also requires Team or Enterprise Platform. Webflow announced a feature called Releases at its September 2026 conference intended to branch entire sites, including pages, CMS content, components, assets, and locales, with scheduled publishing for coordinated campaigns. Releases is in beta and expected later in 2026. Treat it as direction, not as something to plan a campaign around today.

What a content migration looks like on this model

If you are moving a site with real content volume, the constraints above stop being trivia and start setting your schedule.

Model the collections before you move a single item. Because everything is a collection and relationships run through reference fields, the shape of your content has to be decided up front. Retrofitting a taxonomy you skipped means a structural change, which means a full-site publish, which means the change lands everywhere at once. Teams used to adding a custom field in WordPress mid-migration will find this the sharpest adjustment.

Sequence the structural work first, then the content. Get every collection and field in place, publish the structure, then move items. Interleaving the two produces a run of full-site publishes at exactly the moment the site is least stable.

Plan URLs and redirects as their own workstream. This is true of any replatform, and it is the piece most often left until the week of launch. Map old paths to new ones while the old site is still live and you can still check your work.

Budget for the parts that do not migrate. Forms, third-party embeds, analytics, consent tooling, and anything driven by a plugin on the old site each need a decision: rebuild it, replace it with an app, or carry it in custom code. That inventory belongs in discovery, not in the final sprint.

Set honest expectations on performance and analytics

Webflow Analyze covers sessions, visitors, bounce rate, traffic sources, click events, scroll depth, and clickmaps, with an overlay showing where the average page fold sits on a given breakpoint. Two things to know. It is a paid add-on rather than something included with a site plan, and it is a page-design instrument rather than a measurement platform. It tells the person building a landing page whether the hero is too tall or the call to action sits below the fold. Webflow’s own documentation expects discrepancies with other analytics tools, so plan to run your existing stack alongside it rather than instead of it.

An audits panel flags issues like missing schema markup and skipped heading levels. Image compression to AVIF or WebP is available through a conversion tool in the Assets panel, though it is a manual step rather than something that happens on upload, and it replaces the original file.

On page speed, the platform is rarely the deciding variable. Creative work costs points. Animation, video, large imagery, and third-party scripts move a score more than the CMS underneath them does, so a number from one site tells you little about what yours will do. Set the performance budget during design and hold the conversation about what the creative is worth in load time while there is still time to change it.

Where Webflow fits, and where it does not

Webflow fits marketing sites, corporate sites, campaign microsites, and organizations whose own team wants direct control over publishing. It fits well when the design system is built carefully and the permission model is configured to match the org chart.

It is a harder fit for application-heavy builds, for teams that need more than staging and production environments, and for organizations that depend on a broad library of plugins. Custom code is handled through JavaScript bundles deployed to a CDN and referenced by the site, which works, but it is not the multi-environment developer workflow that hosted WordPress or Drupal offers.

Webflow announced Source at the same conference, a local application intended to pair a Webflow content layer with a front end built in Next.js or Astro, with governance for agent-assisted development. It is in limited research preview, so watch it rather than plan around it.

Our position is straightforward. We build on both, and the recommendation follows from your team, your governance requirements, and your roadmap. If the people who need to change your site are waiting on someone else to do it, that is the problem to solve first.

Thank you to Jordan Maslyn and the Webflow team for an hour of candid conversation. A good platform discussion with a vendor includes the limits, and this one did.

If you are weighing a platform decision, we are glad to talk it through. Let’s talk.