Webflow vs Payload

If designers and marketers will build, change and publish the site themselves, choose Webflow. The Designer, the CMS and the hosting come in one subscription, and there is no server, update or backup to think about.

If the site has to do more than a builder allows (a client area, a calculator, an integration with your product or CRM), if your data must stay in Europe, or if you want the code in your own repository, choose Payload. It is an open-source CMS that lives inside a Next.js application, with the content in your own database.

The deciding question is not a feature list. It is whether someone technical, in-house or at an agency, will own the site after launch.

Webflow is a visual website platform. You design pages in the Designer, which writes clean HTML and CSS as you work, structure content in the CMS, and publish to Webflow’s own hosting with one click. Marketers edit text and publish articles without a developer, and the platform takes care of SSL, security and uptime.

The trade-off is that you work inside Webflow’s model. Hosting is Webflow’s, on its own infrastructure, and standard plans do not let you choose where the site or the CMS data are stored. Logic beyond what the platform offers goes through custom code or third-party tools. Webflow has opened up to AI with its own MCP server and an official Claude connector, and it is preparing Source by Webflow, an agentic platform still in limited preview.

Payload is an open-source CMS written in TypeScript that installs directly inside a Next.js application. You describe your content model in code (collections, fields, access rules), and Payload generates the admin panel your team uses to write, with drafts, versions and languages. The content lives in your own database, PostgreSQL or MongoDB, and the site, the CMS and the content model sit in a single repository.

Because it is open source and part of your app, you host it where you want: on Vercel, on Cloudflare Workers, or in a container on a European cloud. Figma acquired Payload in June 2025, and the project remains open source. The trade-off: there is no visual page designer. Layouts are built in code, then your team fills them from the admin panel, and someone has to deploy, update and watch the application.

Nine criteria we look at when a client hesitates between the two. The last column says which one has the edge, from our experience on both.

This is the biggest day-to-day difference. In Webflow, a designer can move a section, change a spacing or build a new landing page on the canvas and publish it the same afternoon. Marketers who only change text use the Editor and never touch the layout.

In Payload, pages are built from blocks that a developer defines once: a hero, a feature list, a testimonial, a call to action. Your team then assembles and fills them from the admin panel, with live preview, drafts and scheduled publishing. They cannot invent a new layout, but they cannot break the design either. For a team that publishes a lot, in several languages, that structure is an advantage; for a team that redesigns pages every week, it is a constraint.

Webflow hosts every site on its own infrastructure, built on Amazon Web Services with a global CDN. It is fast and reliable, but standard plans do not let you choose where your site or your CMS data are stored.

With Payload, you choose. You can deploy on Vercel with functions in a European region such as Paris, on Cloudflare, or keep the application, the database and the files with a European provider such as OVHcloud or Scaleway. For healthcare, finance, the public sector or any company with strict GDPR requirements, that choice can decide the project. The counterpart is that the database and its backups are now yours to run, or ours if we maintain the site for you.

Webflow is a subscription per site. Entry points are about $14 a month for a static site, $23 for a site with the CMS, and from $39 for the Business plan, and the bill grows with seats, languages and CMS items. Check current rates on webflow.com before deciding.

Payload itself is free and open source. You pay for hosting and the database, which depend on your host and your traffic, and for the time to maintain the application. On a small site, Webflow is often simpler and not more expensive. As content, languages and features grow, Payload usually wins, because nothing is billed per item or per locale. In both cases the subscription is the small line: the build and the ongoing work weigh much more.

On Webflow, an agent such as Claude works through the official MCP connector: it can create and edit CMS items, build pages and run bulk changes by conversation, inside what the API exposes. Some things, such as classic interactions, stay out of its reach, and you still check the result in the Designer.

On Payload, everything is code an agent can read: the content model, the access rules, the templates and the deployment. Claude can add a field, write a migration, build a new block and open a pull request that we review before it goes live. That is how we rebuilt bebranded.xyz on Payload and Next.js in November 2026, with Claude working alongside us. For teams that want agents to do real work on the site, not only edit content, the open stack goes further.

What we recommend, depending on the project in front of us.

We did it on our own site, so we plan client migrations the same way. Content can be exported from the Webflow CMS, but pages and interactions are rebuilt, not imported. The goal is a new site that looks the same on day one, keeps every URL that ranks, and is easier to grow afterwards.

Our notes from years on Webflow and from running our own site on Payload.