Contentful vs Payload
Pick Contentful when not running infrastructure is the point: a hosted admin, a vendor on the hook for uptime, and mature roles and workflow for a large editorial team. Pick Payload when the content should sit in your own database with no meter running against records, locales or API calls. For a small site a hosted plan is often cheaper once engineering time is priced in; at scale, self-hosting usually wins.
- Contentful Headless SaaS · fully managed
- Payload Self-hosted · code-first · open source
Last verified: 9 September 2026. Pricing and vendor-status claims on this page were checked at the source on that date.
WAYF is an official Payload partner and top contributor, so we have an interest in this comparison. Our full position, including when Contentful is the recommendation we give, is in “A note on our position”, further down the page.
When to pick each
Pick Contentful when
- You want a fully managed service with no infrastructure to run or patch.
- A large, non-technical editorial team needs a polished hosted admin from day one.
- Vendor SLAs, compliance certifications, and enterprise support matter more than owning the stack.
- You do not have a Node or TypeScript team to maintain a self-hosted CMS.
- A predictable plan fee is easier for you to approve than running your own infrastructure.
Pick Payload when
- You want your content in your own database, on infrastructure you control.
- Your team works in TypeScript and React and wants the content model as version-controlled code.
- Usage-based pricing that climbs with records, locales, and API calls is a concern at your scale.
- The CMS needs to live inside a Next.js app or be customised beyond what a hosted admin allows.
- Avoiding vendor lock-in is a first-order requirement.
Feature comparison
Architecture & hosting
| Feature | Contentful | Payload |
|---|---|---|
| Model | Headless SaaS, fully managed by Contentful | Self-hosted application you run |
| Source code | Proprietary | Open source (MIT) |
| Where content lives | Contentful's cloud | Your own database — Postgres or MongoDB |
| Hosting | Contentful only, and Contentful operates it | Any Node host or your own cloud, which your team then runs, patches and monitors |
Content modeling
| Feature | Contentful | Payload |
|---|---|---|
| Where the schema is defined | Web UI, or the migrations CLI | TypeScript config in your repo |
| Schema in version control | Through migration scripts, not natively | Yes — the config is the schema |
| Page-builder field | References + rich-text embeds | Blocks field, built for this |
| Relationships | Reference fields (entry links) | Relationship fields |
Developer experience
| Feature | Contentful | Payload |
|---|---|---|
| APIs | REST across separate Delivery, Preview and Management APIs, plus GraphQL | REST + GraphQL + a typed local API |
| TypeScript types | Generated with extra tooling | Generated from your config automatically |
| Local development | Runs against the hosted space | Fully local against your own database |
| AI agents & MCP | Hosted OAuth-gated server, plus an open-source server you run locally | First-party MCP plugin serving /api/mcp from your own deployment |
| Embedding in an app | Consumed over the API | Can run inside the same Next.js app |
Editor experience
| Feature | Contentful | Payload |
|---|---|---|
| Admin UI | Polished, mature, hosted for you | Customisable React admin you host |
| Roles & permissions | Mature, and gated by plan: 2 roles on Free, 3 on Lite; custom roles, SSO and SCIM provisioning are Enterprise only | Field- and collection-level access in code; SSO, publishing workflows and a system-wide audit log are licensed enterprise features with no published price |
| Preview | Built-in preview | Draft preview you wire to your frontend |
Localization & scaling
| Feature | Contentful | Payload |
|---|---|---|
| Localization | Built in, and capped by plan: 2 locales on Free, 3 on Lite, a custom number on Enterprise; localized workflows are Enterprise only | Built into core, field-level, with no cap on locales |
| Pricing model | Plan fee with capped users, roles and locales, plus API and bandwidth overages on Lite | Free and open; you pay for hosting |
| Cost at scale | Rises with seats, records, locales, API calls | Tracks your infrastructure cost |
| Vendor lock-in | Higher — proprietary and cloud-bound | Lower — open, self-hosted, exportable |
Update, 3 September 2026: Salesforce completed its acquisition of Contentful on 1 September 2026. See what the close changes.
The choice between Contentful and Payload is mostly one decision wearing two hats: do you want a managed service that someone else runs, or a platform you own and host yourself. Almost every difference below follows from that one fork. This page lays out where each side genuinely wins, then breaks the differences down feature by feature.
The core difference
Contentful is a headless content platform delivered as software-as-a-service. You model content in a hosted interface, editors work in a mature admin, and Contentful runs the infrastructure, the uptime, and the upgrades. You consume the content over an API and never think about servers.
Payload is a headless CMS you run yourself. The content model is TypeScript in your repository, the data sits in your own Postgres or MongoDB database, and the admin is a React application you deploy. It is open source, so there is no per-seat licence and no vendor between you and your content.
Neither model is better in the abstract. They differ in who carries the operational work, and in how much control that costs. Which fits depends on your team and your constraints.
Where Contentful is the stronger choice
Contentful earns its keep when not running infrastructure is the point. A marketing or editorial team without engineers to keep a CMS patched and online gets a polished, hosted admin and a vendor on the hook for uptime. Its roles, permissions, and workflow tooling are mature, and on enterprise tiers the compliance certifications and support agreements are the kind procurement teams want to see in writing.
If your organisation would rather approve a predictable plan subscription than own a deployment, and if the editorial team is large and non-technical, Contentful removes a category of work you would otherwise have to staff.
Where Payload is the stronger choice
Payload earns its keep when ownership and fit matter. Your content sits in your own database, on infrastructure you control, with no usage meter running against records, locales, or API calls. For a TypeScript and React team, the content model living as version-controlled code means schema changes go through pull requests and code review like everything else.
It also reaches places a hosted CMS cannot. Payload can run inside the same Next.js application as your frontend, share its authentication, and be extended with custom React components and server-side logic. When the CMS is part of the product rather than a separate service, that closeness is the whole point.
Pricing and total cost of ownership
The two pricing shapes are different in kind. Contentful’s cost is a subscription that grows with seats, records, locales, and API consumption, which makes it predictable to budget and steeper as usage climbs. Payload’s software is free; the cost is the infrastructure you run it on plus the engineering time to operate it, which stays roughly flat as content volume grows.
For a small site with a few editors, a hosted plan is often cheaper once you price in engineering time. For a large platform with many locales, heavy API traffic, or a lot of records, self-hosting frequently wins on total cost, and the savings compound with scale. The answer turns on your numbers.
This page weighs one destination. If the open question is whether to leave Contentful at all, or which other platform to weigh, our guide to Contentful alternatives works through that decision by motive.
The plan gates named above were rechecked at the source on 11 September 2026: user, role and locale counts, overage rates, SSO, SCIM provisioning and localized workflows against Contentful’s published pricing, SSO and publishing workflows against Payload’s enterprise page, and the system-wide audit log against Payload’s enterprise audit-log page. Neither vendor publishes a price for the enterprise tier that carries them.
A note on our position
WAYF is a Payload Partner agency and a top contributor to its open source, so we have an interest here. We pick Payload often because self-hosting, code-first modeling, and no lock-in fit how we and our clients build. When a team is better served by a managed SaaS, that is the recommendation we give, and Contentful is a strong one.
Decided on Payload? Read the Contentful-to-Payload migration guide →
Common questions
-
Is Payload better than Contentful?
Neither is better in the abstract; they suit different constraints. Contentful is delivered as software-as-a-service, so uptime, upgrades and infrastructure stay with the vendor, and the subscription scales with seats, records, locales and API calls. Payload is open source and self-hosted, so the content model lives in your repository and the data in a database you control, with the operational work coming to your team. Teams with engineers to run it, or a reason to keep content inside their own perimeter, tend toward Payload; teams without that capacity, or with a large editorial group already served by a hosted admin, tend toward Contentful.
-
How much does Contentful cost compared to Payload?
The two pricing shapes differ in kind. Contentful's cost is a subscription that grows with seats, records, locales and API consumption, which makes it predictable to budget and steeper as usage climbs. Payload's software is free; the cost is the infrastructure you run it on plus the engineering time to operate it, which stays roughly flat as content volume grows. The crossover point is where the subscription overtakes what running your own deployment costs, and it moves with locales, API volume and record count rather than with page count.
-
Is Contentful or Payload better for a large editorial team?
Contentful has the stronger case here. Its roles, permissions and workflow tooling are mature, and a marketing or editorial team without engineers to keep a CMS patched and online gets a polished hosted admin plus a vendor accountable for uptime. On enterprise tiers the compliance certifications and support agreements are the kind procurement teams want to see in writing.
-
What does the Salesforce acquisition mean for Contentful customers?
Update, 3 September 2026: Salesforce completed the acquisition on 1 September 2026 (SEC Form S-8, filed the same day). The close transferred ownership of the company. Your entitlements, prices and terms run as written until renewal or amendment, so your renewal date and your notice-to-non-renew deadline are what decide your position now.
-
Can Payload replace Contentful?
For most content estates, yes, and the work takes the shape of a migration. Payload covers the same headless job: content modelled as structured data and consumed over an API. What changes is the operating model, because the model becomes TypeScript in your repository, the data moves into a database you run, and the admin becomes a React application you deploy. The Contentful-to-Payload migration guide covers the field mapping and the pipeline.
-
Can an AI agent read and write content in Contentful or Payload?
Both offer an MCP server, and they differ in where it runs. Contentful hosts one at mcp.contentful.com/mcp, using OAuth and the MCP app's per-environment allow-list alongside each user's permissions. Its open-source local server, @contentful/mcp-server, uses a Contentful Management API personal access token; version 1.19.0 went out on 1 September 2026. Both can manage content, content models and assets. Payload ships a first-party plugin serving /api/mcp from your own deployment, with each request authorised by an API key sent as a bearer token by default, so the agent surface sits inside infrastructure you control.
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.