What Is a Headless CMS?
How a headless CMS separates content from presentation
A headless CMS is a content management system that stores and manages content but does not provide the website front end that displays it. Instead, content is delivered through an API, usually as structured data such as JSON, so any application can present it.
A traditional CMS combines the back end, where content is edited and stored, with the front end, the templates and themes that display it. A headless CMS keeps only the back end. The content stays the same, but the presentation is up to developers, who can build it with any framework or language. Headless is one of several categories; see the overview of types of CMS.
How a headless CMS delivers content
Editors write and organize content in the CMS admin area, often using structured fields rather than free-form pages. Each item is stored with its fields, such as a title, body text, author and image. When a website or app needs the content, it sends a request to the API, usually REST or GraphQL, two common API styles, and receives the data in return.
The front end then turns that data into pages. Many teams use a static site generator to build pages in advance, while others render pages on request. Either way, the same content can feed several channels, such as a website, a mobile app, a digital screen or an email template. This approach is common in Jamstack sites.
Advantages and trade-offs of going headless
The main advantages are flexibility and reuse. Front-end teams can choose modern tools, and the same content can serve several channels without being copied. Headless setups can also deliver fast pages when combined with static generation and a content delivery network (CDN), which serves files from servers close to visitors.
The trade-offs are real. A headless CMS needs a separate front end to be built and maintained, which adds moving parts. Features that ship with traditional systems, such as built-in themes, page templates and many plugins, must be rebuilt or replaced. Previews, redirects and search engine settings also need extra work. Teams with a small budget or a simple brochure site often find a traditional CMS easier to run.
Example: a magazine that publishes to a website and an app
A magazine stores each article once in a headless CMS. Its website, a mobile app and a newsletter all request the same article through the API. When an editor fixes a typo, every channel shows the correction after the next build or refresh, depending on how each channel is set up, with no duplicate work.
For a team with one simple website and no plans for other channels, a traditional CMS is usually more practical.
Frequently asked questions
Is a headless CMS the same as a decoupled CMS?
They are closely related. A headless CMS is a kind of decoupled CMS that has no built-in front end. A decoupled CMS separates the back end from the front end but may still include its own templates, which can be used or ignored. In everyday use, the terms are often treated as the same.
Is WordPress a headless CMS?
WordPress can be used as a headless CMS because its REST API exposes content to other applications. By default, though, it is a traditional CMS, with themes that render pages on the same server. Using WordPress headlessly means building and hosting a separate front end.
Is a headless CMS harder for editors to use?
It can be. Editors may need to understand fields and content models rather than working directly on a page. Live previews are not always available unless the team sets them up, so editors may publish without seeing the final layout. Good training and a well-planned preview workflow reduce this problem.