Headless CMS
A content system that stores content and serves it to any front end through an API.
A headless CMS manages content but does not control how it is displayed. Editors write and organise content in it; developers fetch that content through an API and render it in any front end, such as a Next.js site, a mobile app or several sites at once.
The trade-off is flexibility against convenience. A headless CMS frees the design and lets one source of content feed many channels, but someone has to build and maintain the front end. Visual builders such as Framer and Webflow bundle the CMS and the front end together instead.
Key characteristics
- Separates content storage from presentation.
- Delivers content through an API to any front end.
- Suits custom-coded sites, apps and multi-channel content.
- Needs developers for the front end, unlike an all-in-one builder.
Example
A company keeps product updates in a headless CMS. The same entries appear on its Next.js marketing site, inside its app and in its help centre, each with its own design.
Frequently asked questions
What is the difference between a headless CMS and a traditional CMS?
A traditional CMS stores content and renders the pages. A headless CMS only stores and serves content; a separate front end, built by developers, renders it.
Do I need a headless CMS?
Only if content must feed several front ends or a custom-coded site. For a single marketing site, a builder with its own CMS is usually simpler.
Related terms