Compare
What is the best headless CMS for Next.js?
Short answer
Sanity is the headless content management system (CMS) Deploi picks for most Next.js builds, because its next-sanity package ships Draft Mode, Visual Editing and live updates in one dependency (Sanity Docs, October 2026). Payload is the better pick when the CMS must run inside your Next.js app on your own database (Payload Docs, October 2026).
- Sanity's Next.js toolkit
- next-sanity: client, live updates, Visual EditingOne package with the Sanity client, defineLive for the Live Content API, Draft Mode helpers and an optional embedded Studio routeSource: Sanity Docs (Sanity and Next.js)
- Next.js 16 request spike
- Fixed in next-sanity v13, 21 May 2026On next-sanity v12 with SanityLive, Sanity saw an average 4x request increase after upgrading to Next.js 16Source: Sanity Docs (Next.js 16 and SanityLive: avoiding request overages)
- Payload hosting model
- Installs in your Next.js /app folderMIT licensed; runs on MongoDB, Postgres or SQLite; supports only listed Next.js ranges, such as 16.2.6 and laterSources: Payload (Installation, MIT License (GitHub repository))
- Entry paid plans, monthly
- Sanity $15 a seat, Storyblok $99, Contentful $300Sanity Growth per seat; Storyblok Growth with 5 seats billed monthly; Contentful Lite with 20 users; Payload is free to self-hostSources: Sanity (Plans that scale with you); Storyblok (Pricing); Contentful (Pricing); Payload (README (GitHub repository))
Deploi’s call
Start with Sanity for a Next.js build unless the CMS has to live inside the app. Then pick Payload, and accept that your team now runs the database, the upgrades and the admin panel.
PickPick Sanity when
- Content feeds more than one Next.js site or channel, so you would rather read it from a hosted backend than from inside one app.
- Editors need click-to-edit previews and live updates on the App Router without running a CMS server of their own.
- Developers want TypeScript types generated from the schema and from each GROQ (Graph-Relational Object Queries) query.
- You can pin next-sanity to v13 or later before running its SanityLive component on Next.js 16.
AlternativePick another content management system (CMS) when
- Payload: the CMS must live inside the Next.js app, on your own database and hosting.
- Storyblok: marketers assemble pages from components in a visual editor and the 5 seats included on its Growth plan fit your team, as of October 2026 (Storyblok pricing).
- Contentful: the company is standardizing on Salesforce and an enterprise contract already covers it, as of October 2026.
Which headless CMSs work best with Next.js in October 2026?
Sanity fits most Next.js builds, and Payload, Contentful and Storyblok each fit one narrower case. All four headless content management systems (CMSs) document first-party Next.js tooling (Sanity Docs, Payload Docs, Contentful Docs, Storyblok Docs, October 2026). The table uses only each vendor's own pages.
| Criterion | Sanity | Payload | Contentful | Storyblok |
|---|---|---|---|---|
| Next.js package | next-sanity, with Server Components and the App Router data cache | Installs in the /app folder | @contentful/vercel-nextjs-toolkit route handlers | @storyblok/react with an rsc import |
| Preview and click-to-edit | Draft Mode plus Visual Editing overlays | Live Preview in an iframe | Live Preview with inspector mode | Visual Editor opens the clicked block |
| TypeScript types | TypeGen from schema and GROQ queries | payload generate:types | Types from its command-line tool and libraries | storyblok types generate |
| Hosting model | Hosted Content Lake | Self-hosted with your database | Vendor-run, uptime guarantee up to 99.99% on Enterprise | Vendor-run, 97% uptime service-level agreement (SLA) on Growth |
| Fit | Our pick for most builds | CMS inside the app | Salesforce estates | Marketer-built pages |
The shortlist leaves Strapi out because Payload covers the self-hosted, open-source case more closely.
What should a Next.js team look for in a CMS?
A Next.js team choosing a content management system (CMS) should check five things before features: App Router and caching support, draft preview with click-to-edit, live updates, generated TypeScript types, and the hosting model. The fifth decides the most, because it sets who runs upgrades and who pays for traffic.
- App Router and caching. next-sanity exports work with Server Components, the App Router data cache and Draft Mode (Sanity Docs, October 2026).
- Preview. Contentful activates Draft Mode through a route handler (Contentful Docs, October 2026); Storyblok needs the draft version and a preview access token (Storyblok Docs, October 2026).
- Live updates. Live updates cost requests. Sanity measured an average 4x request increase, and 7 to 10x or more on marketing and docs sites with many segments, when next-sanity v12 with SanityLive met Next.js 16; next-sanity v13 fixes it (Sanity Docs, October 2026).
- Types. All four generate TypeScript types, from a schema, a config or a command-line interface (CLI).
- Hosting. Payload ties your CMS to your Next.js version: its installation page lists supported Next.js ranges and warns that not all 15 and 16 releases are compatible (Payload Docs, October 2026).
Why is Sanity our pick for most Next.js builds?
Sanity is our pick because one package, next-sanity, covers the client, live updates, click-to-edit previews and an embedded Studio route, while content stays in a hosted backend you don't deploy. The package delivers live updates through the Live Content API (application programming interface) and typed GROQ (Graph-Relational Object Queries) queries, and what next-sanity gives a Next.js team lists every export (Sanity Docs, October 2026). Sanity TypeGen generates types from Studio schemas and from the results of GROQ queries (Sanity TypeGen, October 2026). The Live Content API is available on all plans, including Free (Live Content API docs, October 2026).
The Sanity and Next.js integration guide covers setup. Two reasons beat the feature list:
- No second deployment. Content lives in a hosted backend, so a second site, an app or an AI assistant can read the same dataset without sharing a Next.js codebase. Payload and Contentful can also serve other channels through their own APIs.
- Editors get previews early. Visual Editing for marketing teams works with the App Router, and live updates through the Live Content API refresh pages without manual cache busting.
When is Payload, Contentful or Storyblok the better pick?
Payload, Contentful and Storyblok each win one condition that Sanity doesn't meet as well. Our view of these three rests on their own pages and documentation, so each condition comes from them. Payload wins when the content management system (CMS) must live in your codebase: it describes itself as "the Next.js fullstack framework", an open-source TypeScript codebase you own and deploy anywhere (Payload Docs, October 2026). Storyblok wins when marketers build pages from components: clicking a component in its Visual Editor opens that block, and field changes render in real time (Storyblok Docs, October 2026).
Contentful is Deploi's pick inside Salesforce estates. Salesforce says it completed the purchase of Contentful on 1 September 2026 and will integrate it across Customer 360 (Salesforce release, October 2026), and Contentful's Live Preview shows edits in the same page as the entry editor (Contentful Docs, October 2026).
The head-to-heads go deeper: Sanity against Payload, Sanity against Contentful and Sanity against Storyblok.
What does each option cost to run?
Payload costs nothing to license, while Sanity, Storyblok and Contentful charge monthly for hosted plans; the cheapest paid tier depends on how many editors you have. Sanity Growth is $15 per seat a month, billed monthly (Sanity pricing, October 2026). Storyblok Growth is $99 a month with 5 seats, or $90.75 a month billed annually (Storyblok pricing, October 2026). Contentful Lite is $300 a month for up to 20 users (Contentful pricing, October 2026). Payload calls itself "completely free and open-source" (Payload on GitHub, October 2026), so its cost is your hosting and database.
| Plan cost | Sanity Growth | Storyblok Growth | Contentful Lite | Payload |
|---|---|---|---|---|
| Free tier | Free plan, 20 seats | Starter, 1 seat, up to 2 | Free plan, 10 users | Free, open-source license |
| 5 editors a month | $75 | $99 | $300 | $0 plus hosting |
| 10 editors a month | $150 | $174 | $300 | $0 plus hosting |
| Seat ceiling on the plan | 50 seats | 10 seats | 20 users | Not applicable |
On busy sites, usage quotas can move the total more than seats do (Deploi's judgment), so model requests and bandwidth as well as seats.
Deploi’s point of view
- Where we disagree
- Most best-CMS lists rank by features and ignore where the content lives. That's the deciding question for a Next.js team. Payload is part of your app, so a Next.js upgrade is also a CMS upgrade, and Payload's own docs warn that not all Next.js 15 and 16 releases are compatible. Sanity, Contentful and Storyblok are hosted services, so the risk moves to request quotas and preview wiring instead. The second mistake is treating live updates as free: Sanity documents an average 4x request increase when next-sanity v12 meets Next.js 16.
- What we’ve seen
- deploi.ca's Shopify sections run on an older Next.js release with the Pages Router and next-sanity in production, not the App Router. Pages rebuild through incremental static regeneration, and the FAQ section has a signed revalidation endpoint built for a Sanity webhook. The FAQ Hub with AI Chatbot template, which Martin Dejnicki published on Sanity Exchange, runs Next.js 16.0.7, also on the Pages Router. Our App Router verdict, including the Live Content API and Visual Editing, rests on Sanity's documentation.
- Where we would push back
- A team that picks a hosted CMS for a site with two editors and no preview needs is paying for features it won't use. For a brochure site that changes monthly, Markdown in the repository or the cheapest plan of any option here is enough.
- What we'd tell you to do first
- Write down who edits, how often, and whether content leaves the website. Those three answers pick between Sanity, Payload and Storyblok faster than any feature table.
When this answer changes
- next-sanity ships a major version that changes defineLive or SanityLive cache behavior
- Payload changes the Next.js version ranges it supports, or its free license terms
- Sanity, Storyblok or Contentful change the price or seat limits of their entry paid plans
- Next.js changes prefetch or caching defaults in a new major version
- Contentful's Next.js toolkit or Live Preview SDK changes under Salesforce ownership
Sources
Every source opened and checked on 25 October 2026.
- Sanity Docs, Sanity and Next.js
- Sanity Docs, Next.js 16 and SanityLive: avoiding request overages
- Sanity, Plans that scale with you
- Sanity, Sanity for Startups
- Sanity Docs, Sanity TypeGen
- Sanity Docs, Live Content API
- Payload, What is Payload?
- Payload, Installation
- Payload, Live Preview
- Payload, Generating TypeScript Interfaces
- Payload, README (GitHub repository)
- Payload, MIT License (GitHub repository)
- Contentful, Pricing
- Contentful, Setting up a route handler to activate Draft Mode
- Contentful, Live preview
- Contentful, Get started (developer documentation)
- Storyblok, Pricing
- Storyblok, Integrate Next.js with Storyblok
- Storyblok, Visual Preview in Next.js
- Storyblok, types generate
- Salesforce, Salesforce press release