Skip to content

React CMS: an SDK for developers, or a page builder for editors

Every React CMS fetches content into components. The real choice is who arranges the page. With most, developers build layouts and editors fill fields; with 15 of the 48 here, editors compose pages from your own React components on a visual canvas. Choose the editing model first, then the SDK.

Reviewed by Eugene SuslovFacts read November 2026No affiliate links

48
platforms that support React
33
ship an official React package
15
let editors build pages from your components
15
offer only a plain API client

Two kinds of CMS for a React site

A headless react cms sends content as JSON and leaves rendering to you, so any of them works with React. What separates them is the package and the editing model. Some ship only a JavaScript client; others ship React components for rich text, images and live preview; a few let editors place your components on the page themselves.

That last group changes who owns the layout. In a field-based react js cms, a developer decides that the landing page has a hero, three features and a form. In a page builder, the developer defines those components once and the marketing team assembles pages from them, within whatever limits the components allow.

Every React CMS we review

48 platforms whose docs or packages cover React. Each card links to a full review with pricing, hosting and limits.

Showing 8 of 48 platforms

Payload

Featured

Best for Next.js teams who want to own the database

A MIT-licensed CMS that installs into your Next.js app rather than sitting beside it. Config is TypeScript, the admin panel is generated from it, and the database is yours.

  • Runs inside your Next.js app, same repo and same deploy
  • Postgres, MongoDB or SQLite, your instance
  • Admin UI generated from a TypeScript config
  • Next.js
  • React
  • Vue / Nuxt
  • TypeScript / Next.js
FreeCloud or self-hosted · Open source

Best for structured content at scale

The structured-content platform behind a large share of serious Next.js marketing sites. You build the editing Studio as React code in your own repository; Sanity hosts the content and serves it over GROQ.

  • GROQ query language, plus a GraphQL API you deploy per dataset
  • Studio is React code in your repo, not a hosted form builder
  • Image CDN with on-the-fly transforms and hotspot cropping
  • Next.js
  • React
  • Vue / Nuxt
  • TypeScript / React (Studio)
$0Managed SaaS · Proprietary

Best for enterprise governance

The enterprise default, and a Salesforce company since September 2026. Mature APIs, serious governance and localisation, EU data residency, and a pricing model that jumps from free to $300 a month with nothing in between.

  • Content Delivery, Preview, Management and GraphQL APIs
  • Environments and environment aliases for safe schema changes
  • Deep localisation and role-based governance
  • Next.js
  • React
  • Vue / Nuxt
  • Hosted SaaS
$0Managed SaaS · Proprietary

Best visual editing

The visual editor everyone else copies, wrapped around a component-based content model. Metered on seats, traffic, API calls, locales and AI credits, with a published 97% uptime figure on the self-serve tiers.

  • Real visual editing against your own live front end
  • Content Delivery and Management APIs, plus GraphQL on Premium and Elite
  • Image Service with on-the-fly transformation
  • Next.js
  • React
  • Vue / Nuxt
  • Hosted SaaS
$0Managed SaaS · Proprietary

Best known open source option

The best-known open-source headless CMS, self-hostable and Node-based. The MIT grant is narrower than everyone assumes: having a Strapi Cloud account is one of the things that voids it.

  • Self-hostable Node.js CMS with an admin panel non-developers can use
  • Auto-generated REST and GraphQL APIs from your content types
  • Role-based permissions and a plugin ecosystem
  • Next.js
  • React
  • Vue / Nuxt
  • JavaScript / Node.js
FreeManaged SaaS · Open source

Best for an existing SQL database

Wraps any existing SQL database in a REST and GraphQL API plus an admin app. Not open source, but free and fully permissive for organisations under $5m revenue and 50 staff.

  • Points at an existing SQL database rather than owning one
  • REST, GraphQL and realtime APIs generated from your schema
  • Flows for automation, and a vendor MCP server
  • Next.js
  • React
  • Vue / Nuxt
  • TypeScript / Node.js
FreeManaged SaaS · Source available

Best for publishing and newsletters

A publishing platform with memberships and newsletters built in, MIT licensed and genuinely self-hostable. Excellent at articles, deliberately narrow at everything else.

  • Content API and Admin API over a real publishing model
  • Memberships, paid subscriptions and email newsletters in core
  • MIT licensed, self-host with no vendor limits
  • Next.js
  • React
  • Vue / Nuxt
  • JavaScript / Node.js
FreeManaged SaaS · Open source

Best pay-for-what-you-use pricing

A GraphQL-first hosted CMS with an imgix-backed asset pipeline and the most granular pricing here. Ten separate meters, each with a published add-on rate.

  • GraphQL Content Delivery API with responsive image variants
  • Real-time Updates API for live edit overlays
  • Asset API backed by imgix transformations
  • Next.js
  • React
  • Vue / Nuxt
  • Hosted SaaS
€0Managed SaaS · Proprietary

Check the React package and the editing model

Tick what you need; each platform shows its React package where it has one.

What should the CMS give your React team and your editors?

20of 48 have it

PlatformOfficial React package33Editors compose pages from your components20Visual editing20Live preview or better33Open source22Self-hostable26
Payload
Sanity
Contentful
Storyblok
Prismic
Builder.io
Contentstack
Webiny
ButterCMS
Plasmic
Agility CMS
CloudCannon

Read from each vendor's docs and npm packages, 2026-11-20. "Not documented" means the vendor's docs do not show it.

Visual page builders for React

Editors place your components on the page; your code keeps the rules.

15 platforms
PlatformReact package
Sanity@sanity/visual-editing
Contentful@contentful/live-preview
Storyblok@storyblok/react
Builder.io@builder.io/sdk-react
Contentstack@contentstack/live-preview-utils
Webiny@webiny/website-builder-react
Plasmic@plasmicapp/loader-react
Agility CMS@agility/nextjs
CloudCannon@cloudcannon/editable-regions
dotCMS@dotcms/react
Magnolia@magnolia/react-editor
Bloomreach Content@bloomreach/react-sdk
Enonic XP@enonic/react-components
React Bricksreact-bricks
Scrivitoscrivito

Platforms whose docs show editors composing pages from registered React components with visual editing, 2026-11-20.

They work in two ways. Most add a builder to a content platform: a block or section field holds your components, and the editor sees the page while arranging it. Builder.io, Plasmic and React Bricks start from the other end: the page builder is the product, and building a site as a cms with react components is the whole point.

Under the canvas, the content model is usually a page holding an ordered list of blocks, each block a registered component with its own fields. That model is what you migrate if you ever leave, so keep block names and fields close to your components' props rather than to one vendor's conventions.

Either way, the work moves to the component library. Every prop an editor can change is one a developer has to allow for, so plan the components and their limits before you invite editors in.

Guardrails are the part teams underestimate. A builder that lets editors set any color, spacing or font size produces pages that drift from the design system within months. The better setups expose a few named variants per component and nothing else. Some vendors charge for the restriction itself: Plasmic keeps its guardrail editor role on the Scale plan.

Official React packages, platform by platform

The package name to install, and how far its editing goes.

33 platformsOfficial React packages and what they edit20 of 33support visual editing inside your React app
PlatformReact packageEditing in your app
Payload@payloadcms/live-preview-reactLive preview
Sanity@sanity/visual-editingVisual editing
Contentful@contentful/live-previewVisual editing
Storyblok@storyblok/reactVisual editing
Directus@directus/visual-editingVisual editing
DatoCMSreact-datocmsVisual editing
Hygraph@hygraph/preview-sdkVisual editing
Prismic@prismicio/reactLive preview
Builder.io@builder.io/sdk-reactVisual editing
TinaCMStinacmsVisual editing
Contentstack@contentstack/live-preview-utilsVisual editing
Decap CMSdecap-cms-appLive preview
Kontent.ai@kontent-ai/smart-linkLive preview
Keystone@keystone-6/document-rendererContent only
Webiny@webiny/website-builder-reactVisual editing
Cosmic@cosmicjs/rich-textLive preview
Caisy@caisy/live-preview-reactLive preview
Plasmic@plasmicapp/loader-reactVisual editing
Crystallize@crystallize/reactjs-componentsLive preview
Agility CMS@agility/nextjsVisual editing
CloudCannon@cloudcannon/editable-regionsVisual editing
dotCMS@dotcms/reactVisual editing
Magnolia@magnolia/react-editorVisual editing
Bloomreach Content@bloomreach/react-sdkVisual editing
Enonic XP@enonic/react-componentsVisual editing
sensenet@sensenet/controls-reactContent only
AlineaalineaLive preview
Contember@contember/interfaceContent only
React Bricksreact-bricksVisual editing
Flotiqflotiq-components-reactLive preview
Prepr CMS@preprio/toolkitVisual editing
Zesty.io@zesty-io/react-autolayoutContent only
ScrivitoscrivitoVisual editing

From npm and each vendor's docs, 2026-11-20. Some packages are named for Next.js but export React components.

Where the React app runs

The CMS rarely talks to bare React; it talks to the framework around it.

Many React sites run on Next.js, and 40 of the 48 platforms here ship a Next.js package or starter, against 33 with a React package. If your app is on Next.js, check App Router, draft mode and revalidation on our Next.js page, since that is where integrations differ most.

Outside Next.js, a React package is what carries the integration. On Vite or React Router you fetch on the client or in loaders, and live preview needs the vendor's package to listen for edits. On Astro, React components run as islands inside Astro pages, and 9 of these platforms ship an Astro loader as well.

Open source options with a React package

When the code and the content should both stay yours.

11 open source platforms ship an official React package: Payload, TinaCMS, Decap CMS, Keystone, Webiny, Plasmic, Magnolia, Enonic XP, sensenet, Alinea and Contember. You host them, so the license fee disappears and the server, database and upgrades become yours. A react js cms you run yourself also keeps content in your own database, which some clients require.

Read the license before building a product on one. Our open source headless CMS page reads each license from the repository and lists what the free edition holds back.

What a React headless CMS package actually gives you

An official package saves real work; a plain client means writing it yourself.

33 platforms ship an official React package. In a react headless cms the package typically renders rich text into components, resolves image URLs and wires up live preview, the three jobs teams otherwise rebuild for every project. 15 platforms offer no React package, only a JavaScript or HTTP client, which is fine for simple sites and a week of work for preview.

Preview depth varies too. 13 platforms, Payload, Strapi, Prismic, Decap CMS, Kontent.ai, Craft CMS, Cosmic, Caisy, Wagtail, Crystallize, Amplience, Alinea and Flotiq, document live preview: the page updates as the editor types, but editing happens in a form beside it. Visual editing goes further and lets the editor click the text on the page. For a cms for react apps with a design system, that difference decides how often a developer gets asked to change a page.

How to choose the best CMS for React

Four checks, in the order they usually rule platforms out.

  1. 01Decide who owns the layoutDevelopers, or editors working from your components. That splits the list in two.
  2. 02Check the packageAn official React package for rich text and preview saves days; the checklist shows which have one.
  3. 03Match the frameworkOn Next.js, our Next.js page checks App Router and draft mode support.
  4. 04Price the editorsPage builders often bill per editor seat. Count the people who will build pages.

The best headless CMS for React is the one whose editing model matches the people who will use it daily. A headless cms react developers like but editors avoid ends up with developers making every change.

Headless CMS for React, answered

  • Which React CMS lets editors build pages from my own components?
    Sanity, Contentful, Storyblok, Builder.io, Contentstack, Webiny, Plasmic, Agility CMS, CloudCannon, dotCMS, Magnolia, Bloomreach Content, Enonic XP, React Bricks and Scrivito document editors composing pages from registered React components, with visual editing. The components stay in your codebase; editors arrange and fill them.
  • Do React Bricks editors drag and drop blocks?
    The React Bricks docs describe adding, removing and reordering blocks with move up and move down controls, and editing text and images inline on the page. They do not describe drag and drop.
  • Does a headless CMS need an official React package?
    No. Any headless CMS returns JSON a React app can render. An official package saves the work of rendering rich text, handling images and wiring live preview, which is where most of the integration time goes.
  • Can a React page builder CMS work with Next.js?
    Yes. Most page builders here document a Next.js setup, since that is where most React sites run. Check App Router support on the [Next.js page](/headless-cms/nextjs) before you commit.
  • Which React CMS platforms are open source?
    Payload, TinaCMS, Decap CMS, Keystone, Webiny, Plasmic, Magnolia, Enonic XP, sensenet, Alinea and Contember are open source and ship an official React package. Several more are open source with only a plain API client; the checklist above shows both.
  • Does Builder.io work with React components?
    Yes. Builder.io's `@builder.io/sdk-react` package renders its content in a React app, and you can register your own components so editors place them on its visual canvas.
  • Does React Bricks work with Astro?
    Yes. The `react-bricks` package includes an Astro integration that runs with `@astrojs/react`, and React Bricks publishes an Astro starter alongside its Next.js one.
  • Is Plasmic a CMS or a page builder?
    Both. Plasmic is a visual page builder whose canvas uses your registered React components, with a built-in CMS for structured content. It loads into React through `@plasmicapp/loader-react`.

Picking the provider is the easy half.

busyless runs content and search as a system: we choose the data sources and tools, build the pipelines on top, and measure what they feed. If that is the part you are missing, talk to us.

Ask an assistant about this page

ChatGPTClaudePerplexity

For scripts and agents

Markdownllms.txt

MCP server: https://busyless.space/api/mcp

An independent comparison. No provider pays to be listed or to rank higher, outbound links carry nofollow, and we earn nothing if you sign up. Prices and terms were read from each vendor's own pages in November 2026 and change without notice.

Missing, or out of date?

Every entry here was read off the company's own website and dated, so some of it will have moved since. Corrections are free and so is being added. There is no fee, no sponsored position, and nothing that money moves up this page.