Headless WordPress in practice
“Headless” here means using only the WordPress admin and serving the public site through the WordPress REST API instead of the traditional theme layer. The question is how much of the WordPress world actually works that way.
Evidence of demand
Usage exists, and one data point is telling: the gatsby-source-wordpress plugin, which pulls content from the WordPress REST API and caches it as GraphQL for React-powered Gatsby sites, had been downloaded 59k times in the month of writing and 851k times overall. Every one of those installs is a headless WordPress deployment by definition, and that figure covers a single site-building technology — not the companies and products built around the same idea.
Why teams choose it
The commonly cited justification is architectural: decoupling the back end from the front end so each can evolve independently. That argument weakens over time. Swapping WordPress for another CMS is not obviously easier in a headless setup, and the scenario of driving a website plus a native reading app plus an internet-connected billboard from one WordPress API is not a use case gaining visible traction.
More often, the pull is developer experience. Teams like React, component-based construction, fast page transitions, Jamstack-style hosting with previews, hot module reloading, Prettier and JSX. Compared with authoring PHP templates, manually refreshing the browser and maintaining a hand-rolled build process, that is an attractive trade. Frontity targets the same React + WordPress pairing, and Vue/Nuxt approaches have been documented as well.
Static output is a second motivation: pre-generated HTML can be served entirely from a CDN, with no PHP or database adding a process ahead of rendering.
Will it overtake traditional theming?
No. It could gain ground if WordPress itself championed headless architecture with guidance, training and documentation that eased adoption, but none of that is the case, so the approach remains niche to some degree.
Hosting vendors nonetheless treat it seriously. WP Engine’s Atlas appears to be a dashboard for spinning up sites with code-as-config, potentially addressing a known pain point of headless setups: two sites to operate, one running WordPress and one running the front end that consumes its APIs. Deploy-from-Git-commits is appealing and table stakes for modern hosting.
Static generators as a headless variant
Services that build a static version of a WordPress site belong in the same bucket, since they consume WordPress APIs to produce those files just as Gatsby would.
- Strattic provisions a WordPress site treated as staging; you work there and use its publish system to push a static copy to production. The appeal is keeping the WordPress way of doing things. A custom block or plugin such as a carousel emits HTML, CSS and JavaScript together, and that output breaks if you merely fetch post content from an API and drop it onto a page — you would have to extract the assets or reimplement the component client-side. With Strattic the assets remain on the static site. Because there is no PHP, though, form integrations were hand-built, and search, comments and similar features rely on client-side Algolia, Disqus and equivalents.
- Shifter follows a similar admin-then-publish model and spins the WordPress site down when idle, which follows from the output being static and no PHP/MySQL server needing to run. It also offers a headless-only WordPress setup that presumably stays running for external API consumption.
The audience problem
Discussion of headless WordPress is largely developer-facing, while WordPress’s market is dominated by non-developers who administer sites through the plugin and theme ecosystem. That population is far larger than the developer one, and that alone will keep headless WordPress a relatively niche concept for some time.



