Payload vs Contentful

Contentful and Payload both store structured content and deliver it to a front end. The difference is everything around that. Contentful is a SaaS platform: the vendor hosts it, you configure content types in a web interface and pay per plan. Payload is an open-source CMS written in TypeScript: it installs inside your Next.js application, the content model is code, and the content sits in your own database.

If you are a large organisation with several brands or markets, a procurement process, strict roles and workflows, and a need for an uptime commitment from a vendor, choose Contentful. It is mature, governed and widely known by integrators.

If developers own the site, you want the content model reviewed in pull requests, the data in your own database and region, and no fee per user, locale or API call, choose Payload. It is also the better base when the site will grow into an application, because the CMS and the app share one code base.

The deciding question is whether you want to buy a platform or own one.

Payload is an open-source CMS and application framework written in TypeScript, published under the MIT licence. Since version 3 it installs directly inside a Next.js application. You describe collections, fields, access rules and hooks in code, and Payload generates the admin panel, a REST API, a GraphQL API and a Local API that your pages call without any network hop. Content is stored in PostgreSQL, MongoDB or SQLite.

Figma acquired Payload in June 2025, and the project remains open source and free. Version 3 is the stable release (3.93 in November 2026), and Payload 4.0 has been in beta since October 2026. You host it where you want: Vercel, a Node.js server, a container on a European cloud. An Enterprise offer (SSO, visual editing, dedicated support) is available on quote. The trade-off: someone technical has to deploy, update and watch the application.

Contentful is a hosted headless CMS. Content lives in spaces, each with its own content types, environments and entries. Editors work in Contentful’s web app; developers read content through the Content Delivery API, drafts through the Preview API, or through a GraphQL API generated from the content model. Content types are created in the web interface, or scripted with migration tools.

The company positions Contentful as a full content platform, with Personalization, a visual page-building canvas called Studio and AI Actions sold on top of its Enterprise plan. Its strengths are maturity, governance, a large partner ecosystem and an uptime commitment. Its weak spot is pricing: the free tier has hard caps, and the next step is a significant monthly fee.

Ten criteria we look at on every headless CMS project. The last column says which one has the edge, from our experience on client work and on our own site.

In Contentful, a content type is created in the web app: you add fields, set validations and link types together by clicking. A product owner can follow and even adjust the model, and environments let you test a change before it reaches production. Each Starter Space on the free and Lite plans comes with 25 content types, 2 environments and 10,000 records, which is enough for a marketing site and tight for a large catalogue.

In Payload, the schema is TypeScript in your repository. Collections, fields, relations, blocks, conditional logic, validation and access rules are code, reviewed in a pull request, typed end to end and rolled back like any other change. Database migrations are generated from the schema. There is no limit on types or records other than your database. Our own site runs on 21 Payload collections, from pages and articles to tools, comparisons and redirects.

If non-developers need to shape the model themselves, Contentful is friendlier. If the model is complex and evolves with the code, Payload is easier to keep consistent.

Contentful’s web app is polished and familiar to many content teams: entries, references, scheduled publishing, comments and tasks, with apps from its marketplace to extend it. Studio adds a visual canvas for assembling pages from components, sold on top of the Enterprise plan.

Payload generates an admin panel from your schema: lists, forms, drafts, versions and restore, scheduled publishing, a rich text editor built on Lexical, live preview of the real page, and roles down to the field. Because the admin is React, developers can add custom fields, dashboards or tools inside it. Editors see exactly the fields their content needs, nothing more.

Both are comfortable for editors. Contentful has more ready-made collaboration features out of the box; Payload is easier to shape around how your team actually works.

Contentful runs the platform for you: infrastructure, scaling, backups, security patches and an uptime commitment on higher plans. You do not choose the server, and your content sits in the vendor’s cloud under its data processing agreement. For many companies that is exactly what they want: nothing to run.

Payload runs wherever you deploy it. You choose the host and the database region, in Europe if needed, and the content never leaves infrastructure you control. Our own site runs on Vercel with a PostgreSQL database. For healthcare, finance, the public sector or any company with strict GDPR requirements, that choice can decide the project.

The counterpart is operations: with Payload, deployments, updates, monitoring and database backups are yours, or your agency’s.

Contentful has localisation built into the content model: each field can be translated per locale, with fallbacks. The number of locales is part of the plan, 2 on Free and 3 on Lite, with custom numbers on Enterprise. Its Enterprise spaces add locale-based publishing, localised workflows and connected spaces, designed for groups running many brands or regions from one platform. This is where Contentful is at its strongest.

Payload localises at the field level too, with a default locale and fallbacks, and the number of locales is unlimited and free. Translated slugs, hreflang and per-locale sitemaps are generated by your Next.js code. Multi-site setups are possible, with a site field and access rules, but the governance layer (who can publish what, in which market) is designed and built by your team.

For a site in two to ten languages, Payload is simpler and cheaper. For thirty markets with local teams and approval workflows, Contentful’s Enterprise tooling saves building that layer yourself.

Contentful stores and delivers content; business logic lives elsewhere, in your front end, serverless functions or other services. Its App Framework lets you extend the editor, and AI Actions automate content creation, translation and transformation on Enterprise plans.

Payload is also an application framework. Authentication, access control, hooks that run on create or update, custom endpoints and background jobs are built in, so the same project can serve a marketing site, a client area and internal tools. Because the schema and the admin are TypeScript in one repository, AI coding agents can read and change the whole system with full type safety: on our own site, that is how we shipped 113 changes in the four days after launch. Payload 4.0, in beta, adds a simpler MCP integration for AI agents.

If the CMS only feeds content to a front end, both work. If the project is heading towards an application, Payload removes a whole layer.

The right choice depends on your organisation, not on a ranking. The simple rule: if you want to buy a governed platform with a vendor behind it, Contentful; if you want to own the CMS, the code and the data, with a technical team or agency to run it, Payload.

Our Next.js agency page details how we build sites and apps on Next.js and Payload.

The two models are built differently, and that often decides the choice.

Contentful charges per plan. The Free plan includes 10 users, 2 roles, 2 locales, 100,000 API calls and 50 GB of CDN bandwidth a month, with hard caps. The Lite plan is listed at $300 a month for 20 users, 3 roles, 3 locales, 1 million API calls and 100 GB of bandwidth. Beyond that, Enterprise is quoted, and Studio, Personalization and AI Actions are sold on top. Contentful changes its grid regularly: check the pricing page before you commit.

Payload is free under the MIT licence, with no limit on users, locales, records or API calls. You pay for hosting, the database and file storage, which for a typical marketing site stays modest; Vercel Pro, for example, costs $20 per developer seat per month with $20 of usage credit included. Payload Enterprise (SSO, visual editing, dedicated support) is on quote.

The hidden line is people. Contentful saves you the operations work; Payload asks for a developer or an agency to deploy and maintain it. For custom features and apps built on Payload, we always work on quote.

Prices are official US dollar prices checked in November 2026, excluding taxes.

Teams usually move when the Contentful bill grows faster than the site, when data has to come in-house, or when the site starts needing application features. Content exports cleanly from Contentful; the model is rewritten in code and the content imported by script. If your front end already runs on Next.js, most of it is kept. Our website migration service covers the SEO side.

Our notes from running our own site on Payload and from client projects on Contentful. The full details are in our Payload and Contentful reviews.

Prices, limits and features were checked on the official pages below on 14 November 2026. Prices are official US dollar prices, excluding taxes; Contentful’s page may show euros to visitors in Europe.