What is a CMS (content management system)?
Last updated: 08-10-2026
A CMS (content management system) is software that lets people create, edit, organise and publish digital content, such as web pages, images and documents, without writing code. CMS stands for content management system. Editors work in a user-friendly interface, while the system handles storage, permissions and delivery to a website or other channels.
If you've ever updated a page on a website without asking a developer, you've used a CMS. Most CMSs today are web content management systems (WCMS): they manage the content of websites. Many can also deliver content to apps, screens and other digital channels.
In short:
- What it does: create, read, update and delete content (often shortened to CRUD) through an editing interface
- Who uses it: editors, marketers and developers, each with their own permissions
- Why it matters: routine content changes don't need a developer, and the website's code and content are kept separate
How does a CMS work?
A web CMS has two parts:
- Content management application (CMA): the editing interface, often called the backend or backoffice. Editors create, edit and publish content here without touching code.
- Content delivery application (CDA): the part that turns stored content into what visitors see. It typically uses content types, templates and stylesheets.
Keeping the two apart is the core idea of a CMS. Developers build the structure and templates once; editors can then update content on their own, as often as they need.
CMS vs WCM: what's the difference?
The terms are often used interchangeably. Strictly speaking:
- A CMS manages any kind of digital content.
- A WCM (web content management system) is a CMS focused on web content.
Every WCM is a CMS, but not every CMS is a WCM. In practice, nearly every modern CMS also works as a WCM, so the distinction is mostly about labelling.
Types of content management systems
| Type | How content is delivered | Typical fit |
|---|---|---|
| Traditional (coupled) CMS | The CMS stores content and renders the website using its own templates | Websites where one team owns content and presentation |
| Headless CMS | Content is delivered through APIs; the frontend is built separately | Multiple channels (web, apps, devices) or a JavaScript frontend |
| Hybrid / decoupled CMS | Renders pages itself and exposes content through APIs | Teams that want templates for the website and APIs for other channels |
| SaaS website builder | Hosted all-in-one tool with built-in hosting and templates | Small sites that value speed over flexibility |
CMSs also differ on two other axes:
- Open source vs proprietary: whether the source code can be viewed, changed and shared (see open source vs proprietary CMS below).
- Technology stack: the language and framework the CMS is built on, for example PHP, .NET (C#) or JavaScript/Node.js. This matters for developers and for how the CMS fits with your existing systems, but is mostly invisible to editors.
CMS examples
There are many content management systems. These well-known examples are grouped by type. Some fit more than one group: Umbraco, for example, is open source, can run headless through its Content Delivery API, and is used for enterprise web content management, so it appears three times.
Open source CMS
- WordPress: PHP, GPL licence; websites and blogs
- Drupal: PHP, GPL licence; used for complex, structured sites
- Joomla: PHP, GPL licence; general-purpose websites
- Umbraco: .NET (C#), MIT licence; editor-friendly, used from small sites to enterprise platforms
Umbraco doesn't use PHP, so PHP runtime vulnerabilities don't affect Umbraco CMS or Umbraco Cloud. Read more in Umbraco is .NET, not PHP.
Headless and API-first CMS
- Umbraco: built-in Content Delivery API, so it can run fully headless or alongside normal page rendering
- Strapi: open-core (MIT-licensed community edition), Node.js
- Contentful: SaaS, API-first
- Sanity: hosted content platform with an open source editing studio
Enterprise CMS and DXP
- Umbraco: enterprise web content management on .NET; open source, with headless and composable options through APIs
- Adobe Experience Manager, Sitecore, Optimizely: commercial platforms that bundle a CMS with marketing tools such as personalisation and analytics
SaaS website builders and commerce platforms with content features
- Wix, Squarespace, Webflow: hosted website builders
- Shopify: commerce platform with built-in content pages
The "best" example depends on your needs. A blog, a multilingual corporate site and a large webshop need very different things. See how to choose a CMS below.
Features of a CMS
Editing and publishing. A visual editing interface, content types, media library, drafts, scheduling and preview.
Users, roles and governance. Role-based permissions (for example administrator, editor, writer) control who can create, edit and publish. Give administrator access only to people who understand the CMS and its setup.
Version history. View and roll back earlier versions of a page, with a record of who changed what.
Multilingual support. Manage all languages in one system, ideally with language variants of the same page, so translations stay connected. In Umbraco, see language variants in the documentation.
SEO features. Editable page titles and meta descriptions, friendly URLs, XML sitemaps and structured data (schema markup). Basic SEO is usually built in; advanced features may need extensions. Read our SEO-friendly CMS blog series.
Integrations and APIs. Connect the CMS to other systems, such as CRM, commerce, search, analytics or marketing automation. Open source CMSs can usually be extended freely; proprietary systems may limit what you can change.
Ecommerce. Some CMSs include commerce; many add it through integrations or extensions, so product data can sit alongside content.
Analytics, personalisation and A/B testing. Measure how content performs, tailor content to different visitors, and test variations of headlines, images and calls to action. These are built in, or added through extensions or integrations. In Umbraco, they're available through Umbraco Engage, including A/B testing.
CMS vs DXP
A digital experience platform (DXP) combines content management with tools for personalisation, analytics, testing, commerce and customer data, aiming to manage the whole digital customer experience.
- Choose a CMS when the core need is managing and publishing content, and you can add other tools as needed.
- Consider a DXP, or a composable stack built around a CMS, when you need several of those capabilities working together across channels.
Many teams now build a composable DXP: a CMS at the centre, connected to best-of-breed tools through APIs. Read more: What is a DXP? and Composable DXP.
Read the full comparison: CMS vs DXP: what's the difference?
Pros and cons of a CMS
A note on bias: we make an open source CMS, Umbraco. We've tried to keep this balanced.
Pros
Faster start: core features, starter kits and templates are ready to use.
Content and code are separate: editors publish without HTML or CSS knowledge.
Faster updates: simple changes don't need a developer; developers reuse built-in functionality.
Version control: earlier versions can be restored.
Controlled access: permissions reduce accidental mistakes.
Support and resources: popular CMSs have documentation, communities and experienced developers. Commercial support is often available.
Cons
Limits on flexibility: a mainstream CMS can't fit every requirement. Open source systems can be modified, but heavy customisation takes effort.
Security exposure: widely used systems can be a bigger target, and third-party extensions add risk. Keep the CMS updated, use two-factor authentication, and only install extensions you've checked.
Design constraints: templates and starter kits can limit design. Check how much control you have over the frontend before you commit.
Open source vs proprietary CMS
- Open source CMS: the source code is publicly available and can be used, changed and shared under its licence. It's usually free to use, with a community contributing improvements. Licences vary (common ones include GPL and MIT), so check what each licence allows. Read more about open source.
- Proprietary CMS: built and owned by one company. You can't change or redistribute the source code beyond the licence terms. You typically get vendor support and a more fixed feature set.
What CMS is a website using?
You can often find out with a quick check:
- Use an online detector. Tools such as WhatCMS.org and BuiltWith compare a site against known CMS signatures.
- Use a browser extension. Extensions such as Wappalyzer show the CMS and other technologies as you browse.
- Check the source code. Look at image and file paths, script names and HTML comments for CMS-specific patterns.
If nothing is detected, the site may be custom-built, heavily customised, or headless, where the CMS sits behind an API and leaves few traces in the page.
How to choose a CMS
Start with your business goals, not a feature list. Involve editors, developers and marketing early, turn your needs into a weighted scorecard, and test three or four options hands-on with your own content before you decide. You can use our CMS scorecard template to weigh the options.
For the full step-by-step process, with advice from four Umbraco partner agencies and Umbraco's product team, read our guide How to choose the right CMS or download the white paper How to choose the right CMS for your organization.
White paper: How to choose the right CMS for your organization
A strategic guide to CMS selection.
Umbraco CMS
Umbraco is an open source CMS built on .NET, developed by Umbraco HQ together with a global community. You can download and install it for free, and use it to build:
- websites
- online stores
- intranets
- headless solutions
Ways to get started:
- Self-host: download Umbraco CMS for free.
- Umbraco Cloud: managed hosting with a free 14-day trial, no credit card required. Start a trial.
- Find a partner: let us help you find an Umbraco partner.
- Try it first: explore the sandbox demo.
Can Umbraco be used headless? Yes. Umbraco CMS includes a built-in Content Delivery API, which you enable in your project. You can then use Umbraco as a traditional CMS, fully headless, or a mix of both. When your frontend needs data from more systems than the CMS, Umbraco Compose, a standalone data orchestration platform, brings data from multiple sources into one delivery layer and serves it through GraphQL.
Looking for a CMS for a larger organisation? Read about Umbraco as an enterprise CMS.
Why use Umbraco?
If you want full control of your website, then you need a truly flexible CMS. With Umbraco you can make your website look, feel and work exactly like you want it to.
What is Umbraco?
Umbraco is an open source .NET content management system that is free to install, set up and host yourself. You can also let us take care of the hosting on Umbraco Cloud.
How do I get started?
You can try out Umbraco by taking a free 14-day Cloud trial. No credit card is required.
Frequently asked questions about CMS
- What does CMS stand for?
- What is a CMS used for?
- What is an example of a CMS?
- Should I use a CMS?
- What is a headless CMS?
- What is the best CMS for websites?
- What is the easiest CMS to use?
- How many content management systems are there?
- What is an open source CMS?
- What is a proprietary CMS?
- How to choose a content management system?
What does CMS stand for?
CMS stands for content management system: software for creating, managing and publishing digital content without coding.
What is a CMS used for?
A CMS is used to build and run websites and to manage their content: pages, articles, product information, images and documents. Many CMSs also deliver content to apps, digital screens and other channels.
What is an example of a CMS?
Well-known examples include:
- WordPress, Drupal and Umbraco (open source)
- Contentful, Strapi and Umbraco (headless)
- Adobe Experience Manager, Sitecore and Umbraco (enterprise)
Should I use a CMS?
If more than one person updates your website, or content changes often, a CMS is usually faster and safer than editing code. Building from scratch only makes sense for very specific needs and comes with much more development work.
What is a headless CMS?
A headless CMS stores and manages content but has no built-in presentation layer. Content is delivered through APIs to any frontend. Read more about headless CMS.
What is the best CMS for websites?
There's no single best CMS. The right choice depends on:
- your requirements
- your team's skills
- your existing technology
- your budget
Use a weighted scorecard and test three or four options.
What is the easiest CMS to use?
It depends on who is using it:
- Editors should look at the editing experience: how quickly they can create and update a page.
- Developers should look at the language and framework, how easy it is to extend and integrate, and the quality of documentation and support.
How many content management systems are there?
Nobody knows exactly. Many systems are little known, forks of other systems or custom builds, which makes them hard to count. Wikipedia's list of content management systems alone names about 170.
What is an open source CMS?
An open source CMS has publicly available source code that you can use, modify and share under its licence. Most are free to use and are improved by a community of contributors.
What is a proprietary CMS?
A proprietary CMS is owned by one company. You license it but can't change or redistribute its source code beyond the licence terms.
How to choose a content management system?
List your must-haves and nice-to-haves, weight them in a scorecard, shortlist three or four options of different types, test them hands-on with free versions, trials or demos, and check the ecosystem: documentation, community, partners and long-term support. Read our step-by-step guide: How to choose the right CMS.