Glossary
Headless CMS

Headless CMS

A headless CMS separates the back end where you manage content from the front end where that content gets displayed. That split gives developers more flexibility to push the same content to a website, an app, or anywhere else, without being locked into one specific front-end setup.

A traditional CMS couples the back end, responsible for content creation, storage, and management, with the front end, which presents that content to users. This interdependence limits flexibility when delivering content, as changes to the front presentation layer affect the back management layer. 

Headless CMS decouples both ends, allowing developers to use any front-end framework or tool to deliver and display content. Content is stored in a central repository and delivered via an Application Programming Interface (API), making it reusable across multiple platforms, devices, and applications.

See how Webflow's CMS handles content and design together in Design & manage CMS content in Webflow.

Other glossary terms

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Hmm…we couldn’t find any results. Try a different search term or reset the filter.
Reset the filter
Load more