Glossary
What is Headless CMS?
A headless CMS is a content management system that stores and delivers content through an API only, with no built-in front-end templating — the content is fetched and rendered by whatever separate application (a Next.js site, a mobile app) a developer builds to display it.
A traditional CMS like classic WordPress couples content storage with a specific front-end rendering system — the templates live inside the same platform as the content. A headless CMS (Strapi, Contentful, Sanity) deliberately separates the two: editors manage content through the CMS's admin interface, but the actual website or app is a separate codebase that requests that content over an API and decides how to display it.
The practical benefit is flexibility of the front end — a team can build a fast, modern framework (Next.js, for instance) for the actual site, without being constrained by a CMS's built-in theming system, and the same content can feed a website, a mobile app, and other surfaces from one source without duplicating it in each.
The tradeoff is that a headless setup requires more custom front-end engineering than a traditional all-in-one CMS, since there's no default theme to fall back on — it's the right call when performance, design flexibility, or multi-channel content delivery matter enough to justify that extra build work, and often overkill for a simple site that a traditional CMS would serve just as well.