Sanity vs Contentful vs Payload: picking a headless CMS
Payload for self-hosted, code-first Next.js sites; Sanity for a hosted, flexible editor with a generous free tier; Contentful for large, governed teams.
By Sohail Hussain21 November 20266 min read
For most company websites built in Next.js, pick Payload if you want the CMS inside your own codebase, self-hosted, with no per-seat fees; pick Sanity if you want a hosted CMS with a very flexible editor, real-time collaboration and a free tier that covers many small sites; pick Contentful if you are a larger organisation with many editors, locales and approval rules, and the budget for an enterprise product.
All three are good. The differences are in where the content lives, who controls the content model, and how the price grows as your team and content grow.
How are Sanity, Contentful and Payload different?
Sanity stores your content in its hosted database, the Content Lake. The editing interface, Sanity Studio, is an open-source React application your developer configures in code: content types, fields, validation and custom inputs are all defined in TypeScript or JavaScript. You query content with GROQ, Sanity's query language, or GraphQL.
Contentful is a hosted SaaS product end to end. Content types are usually defined in its web interface, though they can be scripted. Its strengths are governance: roles, environments, locales, workflows and the kind of audit trail large organisations ask for. You query content through REST or GraphQL APIs.
Payload is an open-source, MIT-licensed CMS that installs into a Next.js application. The admin panel, the API and your website can run as one app. Content types are TypeScript config files in your repository. You choose the database (Postgres, MongoDB or SQLite) and host it wherever Node.js runs. Figma acquired the company behind Payload in 2025, and the project remains open source.
We set these up for clients as part of our website design and development work, alongside plain WordPress where that is the better fit. If you are still deciding whether to go headless at all, read headless CMS vs WordPress first.
How do they compare side by side?
| Sanity | Contentful | Payload | |
|---|---|---|---|
| Hosting | Content hosted by Sanity; Studio hosted by Sanity or you | Fully hosted SaaS | Self-hosted, inside your Next.js app |
| Licence | Studio open source; Content Lake proprietary | Proprietary | Open source (MIT) |
| Content model defined in | Code | Web interface, or scripts | Code |
| Query API | GROQ, GraphQL | REST, GraphQL | REST, GraphQL, local API in Next.js |
| Collaboration | Real-time co-editing | Workflows, roles, comments | Versions, drafts, access control in code |
| Localisation | Field- or document-level, configured in code | Built-in locales, limited by plan | Built-in, configured in code |
| Free tier (as of October 2026) | 20 seats, 10,000 documents | 10 users, 10,000 records, 2 locales | No licence cost; pay for hosting |
| First paid step (as of October 2026) | $15 per seat a month | $300 a month | Hosting and database only |
| Best for | Flexible content, small to mid teams | Large teams, many locales, governance | Developer-led sites, data you host yourself |
Prices change often. Check Sanity's pricing and Contentful's pricing for current limits, and Payload's documentation for hosting requirements.
When is Sanity the right pick?
Your content model is unusual or will change. Because the Studio is code, a developer can build exactly the editing screens your content needs: a product configurator's options, a timeline, a map field. Changing the model later is a code change, reviewed like any other.
Several people edit at once. Sanity's real-time collaboration lets editors work on the same document without overwriting each other, which helps marketing teams in launch weeks.
You want hosting handled and a free start. As of October 2026, Sanity's free plan includes 20 seats, 10,000 documents and two public datasets. A typical company site with a blog, case studies and team pages fits inside it. The Growth plan, at $15 per seat a month, adds private datasets and higher limits.
The cost to watch is seats. A company with 30 occasional editors pays for 30 seats on Growth, even if most log in twice a year.
When is Contentful the right pick?
You have many editors, regions and approval steps. Contentful's roles, environments and workflow features suit a marketing department publishing in several countries with legal review.
Non-developers will manage the content model. Content types can be changed in the web interface, so a content team can add a field without a code release. That is a strength for large teams and a risk for small ones, where unplanned changes break the front end.
The budget is enterprise-sized. As of October 2026, the free plan covers 10 users, 2 locales and 10,000 records. The first paid plan, Lite, is $300 a month, with larger spaces as paid add-ons. For a single company website that does not need the governance, this is hard to justify.
When is Payload the right pick?
You want one codebase and no CMS vendor. The admin, API and site live in one Next.js app, deploy together and share types. There is no third-party service whose pricing can change under you.
Your content must stay on your infrastructure. Data sits in your own database, in the region you choose. For clients with data residency requirements, or content that is not public, this settles the question.
You want to avoid per-seat pricing. Payload has no seat or document fees. A site with 50 editors costs the same as one with two.
The cost is responsibility. You host the database, back it up and keep Payload updated with the rest of the app. If nobody will do that, a hosted CMS is safer. Our website hosting cost calculator estimates the hosting side from your traffic.
What about Strapi, Storyblok and WordPress?
Strapi is the other well-known open-source, self-hosted option. It runs as a separate Node.js service rather than inside your Next.js app, which suits teams that want the CMS and the site deployed independently.
Storyblok is a hosted CMS built around a visual editor, where editors see the page while they edit. If your marketing team insists on arranging page sections visually, put it on the shortlist.
WordPress can act as a headless CMS too, using its built-in REST API or a GraphQL plugin. It makes sense when your team already knows WordPress or has years of content in it; headless WordPress with Next.js explains how.
How should you choose?
- Where must the content live? On your own servers: Payload or Strapi. Hosted is fine: any of them.
- Who will change the content model? Developers, through code review: Sanity or Payload. A content team, without releases: Contentful.
- How many editors, and how will that grow? Many occasional editors push towards Payload, which has no seat fees.
- What is the yearly budget for the CMS alone? Zero to a few hundred dollars: Payload or Sanity. Several thousand: Contentful becomes reasonable.
- How will editors preview drafts? Ask for a demo of preview on your own content before signing.
For how the CMS fits into the larger decision between WordPress and a custom build, read WordPress vs custom website. For the setup on the Next.js side, see how to add a CMS to a Next.js site.
Was this guide useful?