WordPress 21 Apr 2026 5 min read

Headless WordPress: when it pays off and when it does not

Headless WordPress, or WordPress as the backend for an app or PWA, can be the right choice but means two systems to build and maintain. How to weigh cost and value.

Kristoffer Pihlfelt

Developer and founder, Pihlfelt & Vänner

Headless WordPress pays off when the same content needs to reach several channels, such as a website and a mobile app, or when the website is part of a larger application that is being developed continuously anyway. For an ordinary business website or online store, it is usually more expensive to build and maintain without delivering matching benefits. There, a well-built traditional WordPress site on good hosting is usually the better choice.

What headless means

On a regular WordPress site, WordPress does two jobs: editors write and store content, and the same system builds the pages visitors see. In a headless setup, WordPress only does the first. What visitors see is a separate application, often built with a JavaScript framework, that fetches content from WordPress through an API – a standardised way for two systems to exchange data. WordPress has one built in, called the REST API.

The result is two systems instead of one. That is the root of both the benefits and the drawbacks.

When it pays off

  • The same content in several channels. News, product information or guides that appear on the web, in an app, on screens or in a customer portal. Editors write once in WordPress.
  • An app or PWA with WordPress as the backend. A PWA (progressive web app) is a web app that can be installed on a phone's home screen and partly work offline. If the app's content needs to be updated by editors, WordPress is a proven tool for that, while the app itself is built separately.
  • The website is part of a larger product. If you already have an application with its own interface, pulling marketing content from WordPress can make more sense than building your own editing tool.
  • You have long-term access to developers. An in-house development team or a partner who takes responsibility over time, not just for the build.

When it does not pay off

Cost

Much of what makes WordPress good value disappears. SEO plugins, forms, search, previews, page builders and many WooCommerce features rely on WordPress also rendering the pages. In a headless setup, their equivalents have to be built or connected in the separate application. The project therefore ends up closer to a web application than a website, in both price and time. For comparison, a simpler WordPress website takes 2–4 weeks, while larger web applications take 2–6 months.

Two systems to maintain

WordPress still needs updating and securing. The separate application has its own dependencies that also need updating, and often its own hosting. Two systems mean two things that can break and higher ongoing costs for maintenance and hosting.

The editor experience

Editors often lose what they value most in WordPress: seeing how a page will look before publishing, and building new pages themselves with blocks. Previews can be solved, but it takes extra development. New page types and layouts usually require a developer.

Performance

Headless is often promoted as faster. It can be, but a traditional WordPress site with good hosting, caching and a lightweight theme is fast too. Headless is not automatically faster, and a poorly built application can end up slower than what it replaced.

Dependence on developers

Far more people can take over a regular WordPress site than a custom headless build. That makes you more dependent on whoever built it and can make switching suppliers more expensive.

The technical side in brief

You do not need the details, but a few things are useful to know when talking to a supplier. The built-in WordPress API gives access to posts and pages, but in practice developers often need to build custom endpoints – their own entry points into the API that deliver exactly the data the app or website needs, and nothing more. On top of that, decisions are needed on login if some content should be protected, on how content is cached so it loads quickly, and on how search engines will be able to read the pages.

The middle ground that is often enough

It does not have to be either-or. A common approach is to keep the website as a traditional WordPress site while an app pulls selected content from the same WordPress installation through the API. Editors keep their way of working, the website keeps its plugins and the app gets its content.

If the app is mostly custom business logic rather than content – bookings, accounts, calculations – it is often better to build it as a separate application, for example in Laravel, and let WordPress handle the editorial side.

Our recommendation

Choose headless if your content genuinely needs to reach several channels, if you are building an app or PWA where editors update the content, or if the website is part of a product under continuous development. Choose traditional WordPress if what you need is a business website or online store that your editors can run themselves. If you are unsure, we are happy to help you weigh cost against benefit, and to build the integration when it is needed. Read more about our API development.

Share: