In short
- A headless CMS manages content and serves it through an API. Your own code decides how it looks.
- One source of content can feed a website, an app, and other channels at once.
- It suits custom-coded sites and products with several channels. For a simple blog it is often overkill.
- Plan for content modeling, previews, and a developer for new page types.
Also called: Headless content management system, API-first CMS.
What headless means
In a traditional CMS such as WordPress, content and presentation live in one system. An editor writes a post, the theme supplies the template, and the CMS renders the finished page. That front end is the "head".
A headless CMS removes it. Editors still get an editing interface, but the CMS only stores structured content and serves it through an API, usually REST or GraphQL. Developers build the website or app separately and pull the content in. The result is a custom website or app whose design is free of any theme system, with content your team edits on its own.
How it works
One source, many channels
- Marketing websitePages built from content via the API
- Mobile appThe same content in native screens
- Web applicationHelp text, onboarding, and docs
- Other channelsKiosks, email, in-store displays
Content is stored as structured types rather than finished pages. An article might have a title, an author, a summary, a body, and a list of related products. Designing those types, called content modeling, is the first real job of a headless project. A good model makes content reusable across channels, while a poor one recreates page layouts in form fields.
When an editor publishes, the front end either fetches the new content on the next request or a webhook tells it to rebuild the affected pages.
Headless vs traditional CMS
| Question | Traditional CMS | Headless CMS |
|---|---|---|
| Who builds the pages | The CMS, from themes and templates | Your own front-end code |
| Where content goes | Mainly one website | Any site, app, or channel through the API |
| Editing experience | Visual, close to the live page | Structured fields, with previews that need setup |
| Front-end freedom | Shaped by the theme system | Any framework or design |
| Who can set it up | Often a non-developer with a theme | A developer |
| Examples | WordPress, Drupal | Contentful, Sanity, Strapi |
The line is less sharp than the table suggests. WordPress can serve content headlessly through its REST API, and several headless systems have added visual editing and live preview.
Common headless CMS options
Contentful is a hosted service where content types are defined and edited in its web app. Sanity pairs a hosted content store with Sanity Studio, an editing interface that developers configure in code. Strapi is open source, built on Node.js, and can be self-hosted or run on its own hosted cloud. Many other options exist.
When choosing, look at the editing screens your team will live in every day, how previews work, how pricing changes as seats, languages, and content grow, and how easily you can export everything if you leave. On a Choie project, the front-end code written for the client is theirs once its deliverable is paid for, while a hosted CMS stays under its vendor's own terms, so export is the part to check.
When it is worth it, and when it is overkill
Is headless right for you
Worth it
- Content feeds a site and an app
- A custom-coded site with a distinct design
- Several teams or languages share content
- Speed and front-end control matter
Probably overkill
- A blog or small brochure site
- No developer available after launch
- Editors want drag-and-drop page building
- One channel and a theme that fits
The trade-off is setup and upkeep. Someone has to build the front end, wire up previews, and add new page types in code. For a team without a developer, a site builder or WordPress with a good theme is usually the better call, and no-code vs custom code covers that choice.
Choie plans the content model and the pages it feeds together, since the people designing those pages also build them, whether they belong to the product or a launch site. Every project starts with a written scope and a fixed total. See how a project runs.
Common questions
Is WordPress a headless CMS?
Not by default, since it renders its own pages from themes. It can be used headlessly through its REST API or a GraphQL plugin, with a separate front end pulling the content.
Is a headless CMS good for SEO?
It can be, because search performance depends mostly on the front end the CMS feeds. Pages rendered on the server or built ahead of time, with good titles, metadata, and speed, do well, and headless gives developers full control over all of that.
Do editors need technical skills to use a headless CMS?
No. Editors work in a web interface with fields for each piece of content. The technical work is in setting up content types, previews, and the front end, which a developer handles. After a Choie launch, defects in the studio's own work are fixed at no charge for 30 days, and new content types after that are covered by a monthly engagement.
How much does a headless CMS cost?
Most hosted options have a free or entry tier for small projects and charge more as you add users, content, languages, or API traffic. Open-source options like Strapi can be self-hosted without a license fee but still need hosting and upkeep.