Webflow vs Payload

Webflow and Payload answer different questions. Webflow is a visual website platform: designers build pages on a canvas, the CMS holds structured content in Collections, and Webflow hosts the result, with forms and site search built into paid plans and localization available as an add-on. Payload is an open-source content backend written in TypeScript. It gives you the content model, an admin panel, APIs and access control, and the website itself is a separate frontend that developers build, usually in Next.js, in the same project.

So the fair comparison is Webflow against Payload plus a frontend and a place to host it. This page compares Webflow’s current plans, as restructured in May 2026, with Payload 3. For the mechanics of a move, see the Webflow to Payload migration guide. This comparison is about choosing between them.

The short decision

Stay on Webflow when the site is mainly a marketing surface, the people who change it think in layouts, and the content fits its limits. Webflow bundles the hosting, forms and site search, so a team without developers can run the whole site from it. Its code components and Webflow Cloud also let developers add React components and small applications without leaving the platform.

Choose Payload when the content has outgrown the website. That usually means items that reference each other in several ways, content that a product app or partner portal also reads, or rules about who can edit what that belong in code. Payload fits teams that already have developers, or that work with a delivery partner, because the frontend’s templates and components are theirs to build, even when they start from Payload’s website template. The application can run on infrastructure the team manages, through Payload’s Vercel and Cloudflare templates, or on hosting from Payload under an enterprise agreement.

Where the boundary sits

Webflow is several products in one. The Designer is the page builder, the CMS stores Collection items, hosting serves the site, and features such as forms, site search, Localize, Optimize for testing and Analyze for analytics sit on the same platform, several of them as paid add-ons. Changing a page and publishing it happen in one tool.

Payload covers the content layer: the model, the admin, the APIs and access control. A headless CMS like Payload stores content and serves it through APIs, while a separate frontend renders the pages. Payload 3 installs into a Next.js application, so the admin, the APIs and the site can share one codebase, but the frontend is still code your team writes: page templates, components, styles, the form UI, the search UI and the SEO metadata. Payload’s Local API lets that frontend read content directly on the server, without an HTTP call.

Who owns design and content

In Webflow, design and content live in the same tool, and roles decide who can do what. Seats are bought per person, and each seat carries a role: designers take full seats, while marketers and content editors take limited seats. The Marketer role builds and edits pages from existing components, the Content editor role updates text, images and Collection items, and up to 100 reviewers can comment for free. The legacy Editor was retired on 4 August 2026, and Webflow moved its users to free client seats or limited seats.

In Payload, developers decide what a page can contain. They define block types, such as a hero, a feature grid or a quote, and editors compose pages from those blocks in the admin and check them in Live Preview, which renders the draft through your own frontend. A new kind of section is a code change that goes through review. Payload lists a Visual Editor for its enterprise tier as coming soon; treat it as roadmap until it ships.

The practical question is how often the site needs a layout nobody has built before. Reshaping landing pages every week goes faster on Webflow’s canvas. Payload’s block library pays off when pages follow a known set of patterns and the risk sits in the content.

Content model and plan limits

Webflow’s CMS is configured in the Designer. Since the May 2026 plan change, the Premium Site plan includes 20,000 CMS items and 40 Collections, and the Team plan’s site includes 100 Collections; existing sites move to the new plans at their renewal. The July 2024 update set the limit at 60 fields and 10 references per Collection. On a page, a Collection list shows up to 100 items unless pagination is on, and a page can hold 40 Collection lists, 10 of them nested.

A typical marketing site stays well inside those limits. A data-heavy site meets them sooner: an integrations directory that references categories, partners, plans, regions and related entries uses half of the ten references before anyone asks for a new relationship, and a page meant to show several hundred items at once needs pagination or several lists.

Payload defines collections and fields in TypeScript. Relationship fields connect collections, a join field shows the relationship from the other side, and access control can restrict a collection, a document or a single field. Payload sets no platform limit on the number of items; the database and hosting you choose set the practical ceiling. The schema changes through pull requests, so a new field is reviewed and deployed like any other code change.

Components and page building

Webflow components carry properties, so a designer can reuse a card or a section and change its content per instance. On Premium, code components bring React components written in a codebase into the Designer, where designers and marketers configure them through props. DevLink Export works the other way, exporting Webflow components for use in a React project.

In Payload, a blocks field holds the page structure as data, and the frontend maps each block type to a React component in your repository. The component library, its styles and its accessibility are code your team owns and tests. That takes more work to set up, and the result is a library the team can test and reuse across its own applications.

Localization, forms and search

Webflow’s Localize is an add-on priced by the number of added locales. Its pricing lists Localize Essential from $9 a month per added locale, for up to three added locales, covering CMS and static-page localization, localized SEO and AI translation, and Localize Advanced from $29 a month per added locale, for up to ten, adding localized assets and URLs and automatic visitor routing. The Team plan includes Localize. Forms are built in, with unlimited submissions on paid Site plans and file upload on Premium, and Premium includes site search.

Payload localizes at the field level in core: you declare the locales, mark the fields that vary and set fallback, and one document holds every language. Publishing a document’s locales independently depends on a feature Payload labels experimental and in beta. The Form Builder plugin lets editors build forms, stores submissions in your database and can send emails, while your frontend renders the form. The search plugin indexes chosen fields into a search collection. In each case the routing, the form UI and the search UI are frontend work.

Hosting, APIs and custom code

Webflow hosts every published site. Premium includes 50 GB of bandwidth, and add-ons extend it up to 2.5 TB. The Data API reads and writes CMS items, pages, forms and assets; its rate-limit reference still names the plans from before May 2026, with 60 requests a minute on Starter and Basic, 120 on the former CMS and Business plans, and custom limits on Enterprise. An app that reads Webflow content at volume needs caching or webhooks. Webflow Cloud deploys Next.js and Astro apps from GitHub, either on a path of an existing Webflow site or on their own domain, with usage limits that depend on the plan.

Payload generates REST and GraphQL APIs from the config, and server code in the same application uses the Local API. Hooks, custom endpoints and custom admin components are TypeScript in the same codebase. The get-started page offers three ways to run it: self-hosted on any Node.js host, deployed from the Vercel or Cloudflare templates, or hosted by Payload under an enterprise agreement. Whoever hosts it, the database, backups and monitoring need an owner: your team, a delivery partner or Payload.

Cost inputs

On Webflow, each site has a Site plan. Since May 2026, Basic is $15 a month billed yearly or $25 monthly, without the CMS, and Premium is $25 a month billed yearly or $39 monthly. Seats are bought per person, and Localize, extra bandwidth, Optimize (from $299 a month) and Analyze (from $9 a month) are separate add-ons. The Team plan is $2,500 a month on an annual contract and includes a site with 100 Collections, ten seats, Localize and publishing workflows. Enterprise is priced by quote.

Payload’s core is MIT-licensed and charges no licence or seat fee. Its costs are hosting, the database and file storage, email delivery, building the frontend and maintaining the application, plus any enterprise agreement for support, SSO or hosting. Price both over the same period for the same number of editors, languages, environments and traffic, and include the frontend build on the Payload side and the design work on both.

Export, migration and exit

Webflow’s code export requires a paid Workspace plan and produces HTML, CSS, JavaScript and assets. It leaves out CMS content, forms processing, site search, password protection, code components and every locale except the primary one. Collection content exports as CSV, one Collection and one locale at a time, with references as plain text, rich text as HTML and images as Webflow-hosted URLs that break if the site is deleted. Neither export recreates Webflow’s features elsewhere: Collection-bound templates, forms, search and localization have to be rebuilt.

Leaving Payload looks different. The content is in a database you control and the schema is in your repository, so nothing is locked behind an export button. The work is rebuilding the content model, admin and access rules in whatever comes next; our guide to migrating off Payload covers that direction.

When staying on Webflow is the better call

Stay on Webflow when the site is design-led, the content fits comfortably inside the Premium limits, and the team wants to change layouts without a development cycle. Webflow’s hosting, forms, search and Localize cover a typical marketing site, and the MCP server lets AI agents work on the site through its APIs. If the site needs one application feature, Webflow Cloud or a code component may cover it without moving the whole site.

WAYF builds Webflow sites for this case, and we recommend Webflow when a full code build would cost more than it returns.

What a move to Payload rebuilds

A move re-implements what Webflow does beyond storing content. Plan for the design system and page templates; the Collection-bound pages and lists; interactions and animations; form handling and notifications; site search; localized routes and hreflang; SEO metadata, sitemaps and redirects for every indexed URL; replacements for Optimize and Analyze if the team uses them; and moving assets off Webflow’s CDN.

The migration guide walks through the content model, the import and the cutover, and the Webflow migration page covers what running the move with WAYF involves.

Two decision scenarios

Both scenarios are illustrative. They are not client projects.

A design-led brochure site. A B2B services firm runs a 30-page site on Webflow Premium. Two designers own the layouts, three marketers publish, a blog of about 150 posts and a case-study Collection make up the CMS, English and German run through Localize Essential, and form submissions go to the sales team. The recommendation is to stay. The site uses a fraction of the Premium limits, the marketers build pages from components without waiting for anyone, and the forms and search are in the plan while the existing Localize add-on covers the two locales. A Payload build would add a frontend to design, code and host, and the firm would gain nothing it currently needs. The review point is the day the content has to appear somewhere other than the website.

A content and product site that outgrew the builder. A software company’s site has grown into documentation, a changelog, an integrations directory of 1,800 entries linked to categories, partners and plans, and pricing data that its Next.js product app also displays. It publishes in six languages, and its engineering team already maintains the app. Payload fits. The directory becomes collections with relationship fields and access rules for partner-submitted entries, the app and the site read the same content, and six languages sit inside each document with fallback. The move rebuilds the frontend, forms, search and redirects, and hosting can run with the app, through a delivery partner or with Payload. A split is also possible: keep the marketing pages on Webflow and move the directory and pricing into Payload. That keeps two systems in the stack, so price it against a full move.

A short evaluation checklist

Run these with your own site before choosing:

• Inventory. Count the Collections, the items in each and the references per Collection, and compare them with 20,000 items and 40 Collections on Premium.
• Who changes what. List who changes layouts, who edits content and how often, and how many full and limited seats that means.
• Reuse. Note every place the content appears outside the website, and how it gets there today.
• Languages. Count the locales, decide whether URLs are localized, and name who approves each translation.
• Features in use. List forms and where submissions go, site search, password-protected pages, interactions, Optimize, Analyze and any Webflow Cloud apps. Each needs an equivalent after a move.
• API traffic. Estimate the requests a minute your integrations need, against Webflow’s 60 or 120.
• Exit test. Run a code export and a CSV export of your largest Collection, and list what is missing.
• Cost. Put the Webflow plan, seats and add-ons beside Payload’s hosting, the frontend build and maintenance, over the same period.

A note on our position

WAYF is an official Payload partner and top contributor, so we have an interest in this comparison. We are also a certified Framer partner, and Framer competes with Webflow. We build Webflow sites as well, when they are the right fit. We recommend staying on Webflow when the site is a design-led marketing surface inside its plan limits.

If you choose Payload, WAYF’s Payload development service covers the build. For a move from Webflow, plan the replatforming around the content, forms and redirects that need to move.