Updated September 2026 · Written and maintained by the Progression Agency strategy team
A traditional CMS such as WordPress stores content and renders the website; a headless CMS stores content and serves it through an API to whatever front end you build. This guide explains what a headless CMS is, how headless WordPress works, the trade-offs in editing, performance, security, cost and hiring, the main headless platforms, and a decision rule for whether a business website should go headless.
On this page · 9 sections
The short answerStay with a traditional CMS (WordPress, Webflow, Squarespace) when marketers must edit and publish independently, when the site is a marketing site with standard features, and when budget is limited. Go headless (Sanity, Contentful, Storyblok, Strapi, Payload, or headless WordPress with a Next.js or Astro front end) when content must feed several channels, when the front end must be fully custom and very fast, when security and scale matter, or when the site is really a product. Headless costs more to build and needs developers to change layouts; it pays off for larger, multi-channel or performance-critical sites.
Comparisons are based on each project’s official documentation as linked in the text. Progression Agency builds with all of the technologies compared and has no affiliate relationship with any of them.
What is a headless CMS?
A headless CMS is a content management system without a presentation layer (the head). Editors create structured content in an admin interface; the CMS exposes it through a REST or GraphQL API; developers build the website, app or other channel that fetches and renders it. Because the front end is separate, the same content can feed a website, a mobile app, a kiosk or a voice assistant, and the front end can be built in any framework and hosted anywhere. See web development frameworks.
What is a traditional (monolithic) CMS?
A traditional CMS combines content storage, editing and rendering in one application: WordPress, Drupal, Joomla, and hosted builders such as Webflow, Squarespace and Wix. Themes and plugins control how content appears, editors see the page as they build it, and the whole thing is hosted as one system. WordPress alone runs about 43% of all websites according to W3Techs.
| Traditional CMS | Headless CMS | |
|---|---|---|
| Rendering | CMS renders pages (themes, templates) | Separate front end (Next.js, Astro, Nuxt, app) renders via API |
| Editing experience | Visual, page-based, previews built in | Structured fields; preview needs setup |
| Who changes layouts | Marketers (themes, page builders) | Developers |
| Channels | Website first; APIs possible | Any channel from one content source |
| Performance | Depends on host, caching and theme | Typically excellent (static or edge-rendered front end) |
| Security | CMS is public-facing; plugins add risk | CMS admin can be private; front end is static or isolated |
| Hosting | One host (managed WordPress etc.) | CMS host plus front-end host |
| Build cost | Lower | Higher (custom front end) |
| Ongoing cost | Hosting, maintenance, plugins | CMS subscription plus hosting, developer time for changes |
| Best for | Marketing sites, blogs, small business | Multi-channel, custom, high-traffic, product-like sites |
Headless WordPress
WordPress can be used headless: editors keep the familiar admin, and a Next.js or Astro front end reads content through the REST API or WPGraphQL. It keeps WordPress’s editing, plugins for content types and a huge talent pool while gaining a fast, secure, custom front end. The costs are two systems to host, previews and page-builder plugins that no longer work as expected, and developers needed for any layout change. It suits organizations invested in WordPress content with a large or performance-critical site. WordPress’s REST API is documented at developer.wordpress.org.
The main headless CMS platforms
| Platform | Type | Known for | Consider when |
|---|---|---|---|
| Sanity | Hosted, real-time | Customizable studio, GROQ queries, real-time collaboration | Developer-led teams, complex content models |
| Contentful | Hosted | Enterprise features, integrations, governance | Larger organizations |
| Storyblok | Hosted | Visual editor with component previews | Marketers who want visual editing with headless |
| Strapi | Open source, self-hosted or cloud | Node.js, customizable, own your data | Teams wanting self-hosting |
| Payload | Open source, Next.js-native | TypeScript, runs inside Next.js | Next.js products |
| Hygraph | Hosted | GraphQL-first | API-heavy projects |
| Headless WordPress | Self-hosted or managed | Familiar editing, plugins | Existing WordPress content |
| Directus | Open source | Database-first, any SQL database | Data-heavy applications |
Headless CMS vs WordPress: the practical comparison
For a company site with a marketing team that edits weekly, WordPress on managed hosting is faster to build, cheaper to run and lets marketers change pages without developers. For a site that must be very fast, feed an app, handle high traffic, or present a fully custom design, headless (including headless WordPress) wins on performance, security and flexibility, at a higher build cost and with developers in the loop for structural changes. Visual-editing headless platforms such as Storyblok narrow the editing gap. See WordPress alternatives and best CMS platforms.
Headless website development: what it involves
Content modeling (defining types and fields), CMS setup, a front end in Next.js or Astro that fetches content and renders pages statically or on demand, previews for editors, webhooks that rebuild or revalidate pages on publish, image handling, search, forms and analytics, and hosting for both halves. See Astro vs Next.js and custom website development.
Cost comparison
| Traditional WordPress site | Headless site | |
|---|---|---|
| Build (business site, 20-50 pages) | $8,000-$40,000 | $25,000-$100,000 |
| CMS licensing | $0 (open source) plus plugins | $0-$1,000+ per month depending on platform and seats |
| Hosting | $20-$300 per month | $20-$500 per month (CMS + front end) |
| Layout changes | Marketer, hours | Developer, days |
| Content changes | Marketer | Marketer |
When to go headless: a decision rule
- Go headless if content feeds more than the website (app, partner sites, digital signage).
- Go headless if the site must be fully custom and among the fastest in its category.
- Go headless if the CMS must be kept off the public internet for security.
- Go headless if the site is a product with logged-in features built in Next.js anyway.
- Stay traditional if marketers must build pages independently, if the budget is under about $25,000, or if the site is a standard marketing site.
How Progression Agency builds both
We build WordPress sites for content-led marketing teams and headless sites (Sanity, Storyblok, Payload or headless WordPress with Next.js or Astro) when performance, channels or product features require it. The recommendation is written with costs for both paths. See WordPress development and Next.js development.
Deciding between WordPress and headless?
Tell us who edits the site, where content must appear and what it must do; we will recommend the CMS and front end with costs for both routes.
Getting found in search
AI, AEO and what is changing
Paid media and lead generation
Websites and design
Choosing and working with an agency
Software and app development
Web development, platforms and hosting
- React vs Vue vs Angular
- Svelte vs React
- Astro vs Next.js
- Next.js vs React
- Web development frameworks
- What is a tech stack
- SSR vs CSR vs SSG
- React Native vs Flutter
- Vercel vs Netlify
- Cloudflare vs AWS
- AWS vs Azure vs Google Cloud
- Web hosting types compared
- Hosting for React and Next.js
- SaaS hosting
- WordPress hosting guide
- Backend hosting options
- Website hosting for small business
- WordPress alternatives
- Best CMS platforms
- Webflow vs WordPress
- Wix vs Webflow
- Framer vs Webflow
- Shopify vs WooCommerce
- Custom software vs off-the-shelf
- Website development cost
- Monolith vs microservices
- Custom website development services
- React development company
- Next.js development company
- WordPress development company
- Webflow development agency
- Front-end development company
- WordPress maintenance services
- Ecommerce website redesign services
- Website migration services
- DevOps services
- Cloud migration services
- Website speed optimization services
- Website security services
Social, content and brand
By industry and by situation
Frequently asked questions
What is a headless CMS?
What is the difference between a headless and a traditional CMS?
Is WordPress a headless CMS?
Is headless CMS better than WordPress?
What are examples of headless CMS platforms?
Is a headless CMS good for SEO?
Is a headless CMS more secure?
Is a headless CMS more expensive?
Can marketers edit a headless site?
What is a headless website?
What is JAMstack?
What front end should I use with a headless CMS?
Can I migrate from WordPress to a headless CMS?
How long does a headless site take to build?
Which does Progression Agency recommend?
Planning a website or web app?We design, build, deploy and host custom websites, React and Next.js applications and WordPress sites, with a written scope first.
Get a free marketing proposal
Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.