tools.ceo

Headless CMS vs WordPress: which editing setup should you pick?

Sanity, Payload, Storyblok and Contentful against the WordPress editor, judged by the people who will use them every week.

Custom code vs WordPressUpdated October 28, 20264 min readBy tools.ceo editorial

Tablet showing a wireframe being sketched
Photo: Unsplash

The short answer

A headless CMS stores structured content and hands it to a custom front end, so editors get a clean interface and the public site stays fast and secure. WordPress keeps editing and display in one system, which is simpler to start but couples your content to a theme. Choose headless when content is reused across a site, app or emails, or when the front end is custom-coded.

  • Headless separates content from design, so a redesign does not mean re-entering content.
  • Editors fill structured fields instead of free-form pages, which keeps the layout consistent.
  • WordPress can also run headless, but you then maintain WordPress and a front end.
  • Check pricing per seat and per API call on any hosted CMS.

Headless CMS vs WordPress at a glance

What mattersHeadless CMSWordPress
Content modelStructured fields you definePosts, pages and blocks
Front endAny framework or appPHP theme
Editor experienceClean forms with live previewFamiliar block editor
RedesignsContent carries over untouchedOften tied to theme blocks
Self-hostingPayload and Strapi can be self-hostedSelf-hosted by default

The shortlist

Sanity

Flexible structured content with real-time collaboration

Hosted content platform with a customisable editing studio.

Payload

Open-source CMS that lives inside a Next.js app

Self-hostable, TypeScript-first, with admin and API generated from your schema.

Storyblok

Visual editing for marketing teams

Headless CMS with a live visual editor and component-based content.

Who edits, and how often

Start with the people. A marketing lead who updates three service pages a month needs a short, clear form. A content team publishing ten posts a week needs drafts, scheduling and roles. Every headless CMS listed here handles both, but the editing screens feel different, so trial them with the actual editors.

Structured content pays off later

In a headless CMS a service is a record with a title, summary, photo and price fields. That record can feed the website, a quote tool and an email at once. In WordPress the same service is usually a page of blocks, which is harder to reuse.

The options worth testing

Sanity is flexible and developer-friendly with real-time collaboration. Payload is open source, runs inside a Next.js app and can be self-hosted. Storyblok has a strong visual editor. Contentful suits larger organisations with many content types. Strapi is open source and self-hostable. Sources: Sanity, Payload, Storyblok, Contentful

Security angle

A headless CMS admin is not on your public domain, and the public site can be static. Attackers who find your website find files, not a login page. Hosted CMS providers also handle patching of the admin for you.

Our verdict

Pick a headless CMS when you are building a custom front end or want content to outlive the next redesign. Stay with WordPress if your team is happy in its editor and the site is mostly posts.

Questions people ask

Is a headless CMS harder for editors?

Usually not. Editors see named fields and a preview. The setup is the developer’s job.

Does headless help SEO?

Indirectly. It pairs with fast front ends and structured metadata fields, which help search performance.

Which headless CMS is cheapest?

Self-hosted open-source options such as Payload or Strapi have no licence fee, but you pay for hosting and upkeep.

No affiliate links on this page at publication. Product names link to official sites so you can check current pricing. How we work.

Keep reading.

New guides, about once a fortnight.

Websites, security and AI for people who pay for the software. One email when something is worth your time, nothing else.

Free. Unsubscribe from any email.