Headless CMS vs WordPress: what changes, and is it worth it?

A headless CMS stores content and a separate front end shows it; WordPress does both. When headless is worth the extra cost, and when plain WordPress wins.

By Sohail Hussain21 November 20265 min read

A headless CMS stores and manages your content and hands it to a separate front end through an API; the website visitors see is built on its own, usually in a framework like Next.js. Traditional WordPress does both jobs in one system: the same installation stores the content and renders the pages with a theme. Headless is worth it when you want a fast custom front end, content reused across a site, an app and other channels, or a site that is more than pages. It is not worth it for a standard company site whose marketing team builds its own pages with a page builder, or when the budget is tight.

The word "headless" puts people off, but the idea is simple: the "head" is the part visitors see. Remove it from the CMS, and the CMS becomes a content database with a good editor attached.

What does "headless" mean in practice?

On a traditional WordPress site, an editor writes a page, presses publish, and WordPress shows it to visitors using the theme. Everything happens in one system on one server.

On a headless site, the editor writes the page in the CMS and presses publish, exactly as before. The CMS stores it and makes it available through an API. A separate front end, which a developer has built, fetches that content and turns it into pages. If the front end is Next.js, it usually pre-renders the pages and regenerates the changed ones a few seconds after publishing.

For your team, the editing screen looks similar. For your visitors, the site is faster and has no admin panel on the same server. For your developer, the site is two systems instead of one.

The headless CMS can be a purpose-built product such as Sanity, Contentful or Payload, or WordPress itself, which has had a built-in REST API since version 4.7. We build both kinds as part of our website design and development work, and plain WordPress when that is the better fit.

How do traditional WordPress, headless WordPress and a headless CMS compare?

Traditional WordPressHeadless WordPressHeadless CMS (Sanity, Payload, Contentful)
Who renders pagesWordPress themeSeparate front end, e.g. Next.jsSeparate front end, e.g. Next.js
Editing experienceNative, with live layout editingFamiliar WordPress editor; layout set by developerPurpose-built editor; layout set by developer
Preview of draftsBuilt inNeeds setupNeeds setup; some include visual preview tools
Plugins for visitor-facing featuresWorkDo not work; rebuilt in the front endNot applicable
SpeedDepends on theme, plugins and cachingFast by defaultFast by default
Security surfaceAdmin and plugins on the public siteAdmin can sit on a private addressNo admin on the public site
Systems to maintainOneTwoOne or two, depending on hosting
Launch cost compared with a theme buildBaselineHigherHigher

What do you gain by going headless?

Speed. The front end serves pre-rendered pages from a CDN, with only the code each page needs. A headless site passes Core Web Vitals with far less tuning than a typical theme-based WordPress site.

Security. The public site has no login page, no plugins and no database connection to attack. The CMS can sit on a separate address, behind a login or restricted to your office network.

Design and features without limits from a theme. The front end is written for your site. Calculators, filtered listings, client areas, bilingual layouts and integrations are ordinary code instead of plugin workarounds.

Content you can reuse. The same case study can appear on the website, in a mobile app, in a sales deck generator or on a partner portal, because it is structured data rather than a page layout.

A cleaner editing model. Editors fill in fields, such as title, summary, client, industry and results, instead of arranging blocks. The site stays consistent no matter who publishes.

What do you give up?

Visitor-facing plugins. Page builders, sliders, form plugins, the front-end output of SEO plugins, related posts, cookie banners: none of these work headless. Each is rebuilt in the front end. If your WordPress site leans on a dozen such plugins, that is a dozen features to rebuild and budget for.

Layout freedom for editors. On traditional WordPress with a page builder, a marketer can design a new landing page alone. On a headless site, they assemble pages from sections a developer built. New kinds of section need a developer.

Simple preview. Seeing an unpublished change in context takes setup on every headless build. Next.js handles this with Draft Mode, but someone has to wire it to the CMS and test it.

One bill and one login. You now host a CMS and a front end, often with two providers, and publishing depends on the two talking to each other.

The widest pool of developers. Anyone can maintain a WordPress theme. A headless site needs a developer who knows the front-end framework as well as the CMS.

Is headless WordPress a good middle ground?

Sometimes. If your team already knows WordPress, has years of content in it, and relies on admin-side plugins such as Advanced Custom Fields or editorial workflow tools, keeping WordPress as the editor and adding a Next.js front end avoids retraining and content migration. We explain the setup in headless WordPress with Next.js.

The catch is that you keep WordPress's maintenance. Core and plugins still need updating, and the admin still needs protecting, even if it is no longer on the public domain. You also pay for the front end. For a new site with no WordPress history, a purpose-built headless CMS is usually simpler; Sanity vs Contentful vs Payload compares the three we see most.

Which should you choose?

Stay on traditional WordPress if:

  • your marketing team builds landing pages themselves and wants to keep doing so;
  • the site depends on visitor-facing plugins you would rather not rebuild;
  • the budget is close to a theme build, with little left over for a front end;
  • there is no strong speed, security or feature reason to change.

Go headless if:

  • speed matters to revenue or rankings, and tuning WordPress has hit its limits;
  • the site has features beyond pages and forms;
  • the content will appear in more than one place, such as a site and an app;
  • you want editors working in structured fields so the site stays consistent.

Price both before deciding. A headless build typically costs more to launch than a theme-based one, and our website cost calculator shows how page count and features move the range. For the broader business case, including five-year running costs, read WordPress vs custom website.

Was this guide useful?

Questions

Frequently asked.

Is headless WordPress the same as a headless CMS?

It is one kind. Headless WordPress means using WordPress only for editing and storing content, and building the visible site separately, usually in Next.js. Purpose-built headless systems such as Sanity, Contentful and Payload were designed for this from the start, so they have no theme layer to switch off.

Do WordPress plugins work on a headless site?

Only the ones that work inside the admin or on the content itself, such as custom fields, editorial workflow and user roles. Plugins that change what visitors see, including page builders, sliders, form plugins and the front-end output of SEO plugins, do nothing on a headless site. Each of those features is rebuilt in the front end.

Is a headless site more expensive?

Usually, at launch. You are building a front end and setting up a CMS, preview and publishing hooks, which typically adds a third or more to the cost of a theme-based WordPress build. Running costs can be lower, because there are fewer plugins to update and the front end needs little maintenance.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.