CMS comparison 2024: The most popular content management systems

Numerous content management solutions by major project communities are available open source. These are referred to as open source software. With open source CMS, the system and the program code are freely accessible, and the source code can, in principle, be viewed by anyone. Users are allowed to make changes, improvements, and extensions, and to adapt the CMS to individual requirements.

The opposite of open source software is proprietary software. Here, the CMS is developed by a particular company and distributed as a commercial project. The use of proprietary management systems is usually associated with the acquisition of a paid license. The source code is not available to users.

Open source software, on the other hand, is often available without licensing costs. Such solutions are therefore particularly attractive for companies from an economic standpoint. In terms of technological developments, established open source CMS systems are no worse than the proprietary solutions. High-level developer communities are behind some of the most famous projects, such as WordPress or TYPO3. Extensive documentation and a transparent development process also ensure that software errors and security gaps are resolved promptly.

But how high is the share of open source applications in the global market in comparison to proprietary solutions for website operation?

The open source systems like WordPress, TYPO3, Joomla!, Drupal,  Contao, and Neos are currently the most popular standard solutions for professional website operation. But every system is of course not equally suited to every individual purpose. Here, we put together the main functions, application types, and system requirements of different content management systems. Our pro and con tables should help you make your decision.

Facts

• More than 58,000 extensions and a huge range of free design templates
• ‘Five-minute installation’ via Wizard
• Search engine friendly URLs
• Publishing and management tools for mobile solutions

System requirements for WordPress 5.6

• Webserver: Every server with PHP and MySQL/MariaDB support (recommended: Apache or NGINX)
• Middleware: PHP 7.4 or higher
• Database: MySQL 5.6 or higher, MariaDB 10.1 or higher
• Other recommendations: HTTPS support

The software’s large user community benefits from an enormous selection of themes, plugins, and widgets. But critics say that the system is not only too complex, but also confusing and awkward to use. WordPress shares the same problems as all successful software developments: Due to its high circulation, it’s a popular target for hackers. Because of that, users have to update their WordPress software fairly regularly with security updates. These updates come out quickly after security incidents but aren’t always compatible with all the extensions that are required for effective use of the software. As a result, software updates can be associated with considerable administrative effort, especially in the case of large projects.

Because of its low-effort, basic installation, WordPress is good for small and simply structured websites. Especially for bloggers, who want to provide their visitors with frequently changing content in attractive layouts, WordPress is an effective CMS with an intuitive web interface. As the complexity of the online project increases, though, the user-friendliness of the software significantly decreases. Large enterprise projects can theoretically be implemented too, but in such a case, the greater number of functions is inevitably accompanied by an increase in administrative effort.

If you’re striving for stable website operation, WordPress places high demands on the server as your visitor traffic increases. Users who are trying to develop complex multi-domain projects with a multilingual focus should choose a CMS like TYPO3 instead of WordPress for their purpose.

.

Interested in the leading CMS program? You can find further information on the popular blogging software in our WordPress basics article.

Facts

• Currently over 6,000 available extensions
• Object-based content management
• Community support through forums

System requirements for Joomla! 3.x

• Webserver: Apache HTTP Server 2.0 (2.4 recommended) with mod_mysql, mod_xml, and mod_zlib, NGINX 1.0 (1.8 or higher is recommended), MS IIS 7
• Middleware: PHP 5.3.10 (7.3 or higher recommended)
• Database: MySQl 5.1 with InnoDB support (5.5.3 or higher recommended), MS SQL server 10.50.1600.1 (10.50.1600.1 or higher recommended), PostgreSQL 8.3.18 (9.1 or higher recommended)

Joomla! is the development of the open source CMS Mambo. The system is particularly popular in the USA, and is characterised by a completely object-oriented software design based on a stand-alone MVC framework. This allows Joomla! users to write their own extensions and share these with the community, if they want to, using the Joomla! extensions directory, where extensions can easily be installed via the backend. Templates can be created with Joomla! modules, by combining predefined content elements.

Joomla! divides extensions into plugins, components, modules, templates and languages. These can be used in the backend as well as the frontend, which is sometimes irritating to users. The rights management and approval processes are occasionally seen as lacking for larger projects. Extensions help – but are not always available for free.

Deeper insight into the function spectrum of the user-friendly open source CMS is provided by our Joomla! basics article.

Facts

• Very flexible, modular layout
• Slim basic installation with more than 46,000 extension modules
• Focus on social publishing and community projects
• More than 1100 distributions as a complete solution for typical applications

System requirements for Drupal 9

• Webserver: Apache 2.4.7 or higher, NGINX 0.7.x or higher, MS IIS, or any other webserver with PHP support
• Middleware: PHP 7.3 or higher
• Database: MySQL 5.7.8 or higher, MariaDB 10.3.7, Percona server 5.7.8 or higher, PostgreSQL 10 or higher (with PDO), SQLite 3.26 or higher

The CMS Drupal offers extensive opportunities for customisation with its modular layout. Users who know exactly what they need can spare themselves the manual compilation of software components. For many scenarios, pre-configured distributions based on the Drupal framework are available.

With its focus on social publishing, Drupal is particularly suited for small and medium-sized community projects. The large spectrum of extensions makes it possible to implement company portals with complex multi-domain structures. But the administration of a CMS core with comprehensive extensions requires expertise and instinct. If the basic functions of the software aren’t sufficient, then additional modules will have to be installed manually via FTP. This can be a complex process. Updating extensions is sometimes difficult, as these are not always compatible with the backend.

The central application of Drupal is the layout of social publishing and community platforms. The CMS boasts a flexible, modular system for highly dynamic platforms based on user-generated content.

See our basics of Drupal basics article for more information and tips.

Facts

• Enterprise content management system
• Huge range of functions
• Extensive integrated rights management
• Simple integration of other systems such as CRM or ERP solutions

System requirements for TYPO3 CMS 10 LTS

• Webserver: Apache (recommended), MS IIS, NGINX, Caddy Server
• Middleware: PHP 7.2 or higher
• Database: MySQL 5.5 or higher, MariaDB 10.2, MS SQL Server,  PostgreSQL, SQLite
• Hardware: At least 256 MB RAM
• Other recommendations: GraphicsMagick or ImageMagick; GDlib; Freetype; ylib; If using an Apache server: mod_gzip, mod_deflate, mod_rewrite; PHP cache (for example APCu, PHP accelerator, OPcache, or Zend Accelerator); individual extensions may require additional software

TYPO3 offers a large community, which provides quick and easy help for beginners with technical problems or questions. There are also numerous professional providers who specialise in TYPO3 support and provide agency services to business users.

Professional use of the high-performance CMS requires expert knowledge. With this, even complex site structures with multilingual content can be soundly implemented. The considerable range of functions ensures professional rights management at the enterprise level and provides interfaces for classic business applications, such as CRM and ERP systems. On the other hand, critics point to the long training period required and comparatively high administration effort.

The giant spectrum of functions offered by TYPO3 makes it possible to implement any kind of online project. But this comes at a considerable expense for installation, configuration, and maintenance. The prominence and good reputation of the software contribute to its use by comparatively small websites. In this case, users are usually expending much more effort than they need to. If the entire spectrum of functions offered by the enterprise CMS isn’t required, then website operators would generally be better served by a modular software with slim basic installation. For complex projects run by experienced IT specialists, though, TYPO3 is the optimal foundation for a successful online presence.

If TYPO3 is used for large and complex projects, the installation should take place within the framework of a hosting package. Find further information about TYPO3, as well as a detailed description of the considerable range of functions, in our basics of TYPO3 article.

Facts

• User-friendly CMS with large range of functions
• More than 1,400 available extensions
• Multilingual backend
• Online demo
• 2-factor authentication (from Contao 4.6)

System requirements for Contao 4.9 Long Term Support (LTS)

• Webserver: Apache, NGINX or IIS with PHP and MySQL support
• Middleware: PHP 7.4 or higher
• Database: MySQL 8.0 or higher
• Other recommendations: To benefit from a full range of functions, the following PHP extensions are necessary: DOM, PCRE, Intl, PDO, ZLIB, JSON, Curl, Mbstring, GD

The software’s basic configuration already has a comprehensive range of functions that can be flexibly adapted to individual needs with more than 1,900 available extensions. The CMS system also offers an integrated theme manager. This makes it possible to individually configure the design and layout of a website based on Contao with the help of pre-designed modules. In addition, website owners are offered professional themes for various application types and industries via the Contao website. These themes must usually be purchased, though.

The software is known for its high-security standards. The LTS version of the CMS comes with a four-year guarantee. During this period, the LTS version receives error corrections and security updates, but no new features. The LTS version is stable and recommended for active websites.

In addition, there is a developing version, provided with bug fixes and security updates for half a year and contains new features that are not included in the LTS version and will only be included in the next LTS version. This version is recommended for everyone who wants to test new features.

An online demo, as well as extensive documentation material, enable a quick introduction to website creation. Server compatibility can be ensured by Contao Check.

The flexible CMS is suitable for websites of all sizes. The software provides users with a powerful system architecture, which can be adapted to the various requirements of the professional website operation using extensions. Intranet solutions, e-commerce platforms, corporate portals, or microsites, for example, can all be put into action and no wish is left unanswered – even when it comes to search engine optimisation and web analysis.

Only multi-level workflows can’t be implemented with Contao in the standard configuration.

Further information and a detailed description of the underlying page structure of the CMS is provided in our Contao basics article.

Facts

• • Open source enterprise content management system
  • True WYSIWYG editor (inline editing)
  • Search engine friendly URLs
  • Publishing and management tools for mobile solutions
  • Planned expandability to connect other systems such as shop, CRM, or ERP solutions

System requirements Neos CMS 7.x:

• Web server: Apache, NGINX#
• Middleware: PHP >= 7.3.0 (PHP CLI must have the same version for development)

• PHP modules: mbstring, tokenizer, xml, pdo_mysql, imagick, or gmagick
• PHP functions: exec(), shell_exec(), escapeshellcmd() and escapeshellarg()
• Database: Officially supported: MySQL > 5.7.7, MariaDB > 10.2.2 and PostgreSQL > 9.4
• Optional: Oracle, Microsoft SQL Server, SAP Sybase SQL Anywhere, SQLite, Drizzle
• Hardware: at least 256 MB RAM
• Further recommendations: Individual extensions may require additional software

‘Content’s first choice’ is not only the motto, but what Neos strives to achieve in their day to day. Right from the start, Neos was designed to be especially user-friendly. The focus is on so-called inline editing: a real WYSIWYG editor. In contrast to other, classic content management systems, editors no longer have to fill out dozens of form fields for headings, titles, etc. to get a rough preview of the new content via the preview button. Instead, they edit the content directly in the layout of the later page.

The same applies to different display formats such as a tablet, smartphone, or the display of Google search results. Users can easily switch back and forth between views without having to leave the page. This allows content to be quickly and easily optimised for different channels.

Another special feature is the so-called ‘Content Dimensions’. The highlight here is that editors can create any number of versions of content for different target groups. The content is not only available in different languages, but also for different target groups (gender, culture, country, region, etc.) Marketing campaigns can thus be controlled in a targeted manner. The maintenance of large quantities of multi-sites in a Neos system is also part of the standard repertoire.

New content in companies often goes through several review and approval processes from creation to publication. Using user and group workspaces, supported by flexible rights management, Neos easily integrates into existing processes.

Despite its focus on content, Neos is not ‘just’ a CMS. Neos was developed for integration and extensibility. It is a powerful CMS that comes with an equally powerful PHP framework called Flow. Developers can design Neos the way they need to use it. The community calls Neos a ‘Content Application Platform’. This should make it clear that the strengths of the CMS are in addition to classic websites, by allowing the user to create complex projects. The integration of third-party software, connection to external systems (ERP, CRM, etc.), shop integrations, and so on are all achievable with Neos. Existing extensions can be easily installed via Composer (e.g., Google Analytics, IBM Watson, Elasticsearch, etc.).

Nothing stands in the way of individual extensions either. Neos 4.0 introduced the Assets API. This enabled direct access to external media resources (Google Drive, Dropbox, OwnCloud, etc.). You can also effortlessly use photo services such as Fotolia or Unsplash to edit your images, without having to leave the page.

There are hardly any limits to the expandability of Neos. For example, the ‘Neos Award 2018’ went to a project that exports a publisher’s online content directly from Neos to a printable InDesign template - including special markups for prepress. This eliminates the need to enter and check content twice.

After the recently completed revision of the user interface in React, the developers are currently working on the integration of machine learning or the reimplementation of the Neos Content Repository with CQRS and EventSourcing. The latter makes Neos particularly interesting for banks, insurance companies, and public authorities, as it saves various content revisions safely from later changes.

While other CMS rely on premade themes to make the design as easy as possible for beginners, Craft assumes that professionals would rather write their HTML and CSS code themselves. This approach means that the entire system is very tidy. The code of the website stays neat and the structure of the stored files is also logically organised: Instead of using chronologically ordered folders, Craft users specify rules for which file type belongs in which directory.

Craft also has a clear backend where content editors can easily find their way around and get new articles online. There have also been individual plugins developed for the sleek CMS that extend its range of functions. That the CMS was developed for professional developers is reflected in the pricing: If you’re only creating a website for yourself, you can get a free license. But if you want to develop websites for other users, you’ll have to purchase a license.

Grav places a high value on speed, but doesn’t disregard the aesthetic aspect. On the official website, you can find both the installation data (a small ZIP archive) as well as over 100 themes that can be used to customise the design. You can also extend the functionality with more than 350 plugins, with which you can set up the backend for administration work, for example. If you don’t want to assemble all settings and extensions yourself, you can also use a skeleton: A preconfigured package that already contains sample websites.

Like with Grav, for Kirby it’s sufficient that users only upload the few files of the starter kit to the server (Apache 2, NGINX, LiteSpeed, Caddy). Only PHP needs to be available for this. In principle, it’s also not necessary to have an admin interface with a WYSIWYG editor. You can simply create the content with a text editor and then load it to the server in the correct folder, or use the Kirby panel – a simple, clear backend.

Since the CMS does without a backend, and therefore also without a corresponding WYSIWYG editor, Pico isn’t suitable for handing over content creation to an editorial team. Developers, on the other hand, will find the work much easier since there aren’t any settings hidden away in complex databases. All configurations are in their own text file. This makes the flat file CMS very suitable for small projects. Pico and its range of functions can also be extended with various available themes and plugins.

The original development started with a Dutch marketing company that created a CMS with Bolt for creating websites for their customers. By now, the open source project is also supported by others. But Bolt is still aimed at web developers – both for the initial creation of the website as well as the additional configuration. Bolt does have a clear backend in which editors can create content. But work with the CMS is not as intuitive and simplified as to be expected from WordPress, for example.

The first obstacle on the way to implementing a CMS-supported online project is the installation of the chosen software solution. The more complex the system, the more costly the installation and upkeep. Joomla! and WordPress compensate by using a wizard, which drastically reduces the time required for installation. Small web projects can be put online in a matter of minutes. Drupal also offers users a slim basic installation process. But many functions require additional modules, which can only be installed with difficulty via FTP.

The installation of the self-contained enterprise content management system TYPO3 is also complex. It’s primarily intended for users who want to implement large online projects, such as company portals or e-commerce platforms. Website operators should have an established knowledge of the software installation, configuration, and administration.

All open source solutions in our CMS comparison are based on the PHP programing language. TYPO3 users should also have knowledge of the database language SQL and the client script language JavaScript. Website operators who want to create or customise their own templates will need PHP knowledge to use Joomla!, WordPress, Drupal, and Contao. Users of TYPO3 will have to learn its own template language, TypoScript.

Expandability through extensions, plugins, widgets, or modules is available in all content management systems presented here. Multiple functions can only be used based on extensions. The comparison table shows which features are supported natively and which require additional installation.

Website operators rely on CMS systems to facilitate the creation and publication of online content. A good CMS offers functionalities that enable their users to create and manage website content without programming knowledge. Central selection criteria include an intuitive WYSIWYG editor with preview functions and spellchecker, import capabilities for non-textual elements like videos, interactive flash animations, audio content, as well as a search function with full-text search.

To provide website visitors with navigation to relevant content, the CMS should also have an available tagging system with which the content can be organised according to meaningful keywords.

If news publishing is the focus, the CMS should support blogging functionalities that enable the promotion of new content over web feeds and provide available reader feedback channels, such as a guestbook or comment function. Users who want to implement international projects should ensure that content can be made available in several languages.

High-value content is key to a successful website. Here, search engine optimization plays an increasingly important role. Website operators who want to conquer a top spot in the search engine rankings also need to fulfill certain technical requirements. These concern the URL structure of an online project, the design of meta-information, and the orientation of the layout on mobile devices.

All of the open source solutions in our CMS comparison offer users the possibility to rewrite parameterized URLs in a “talking” URL scheme that can be interpreted by both human users and search engines. Not every CMS natively supports this function without extensions.

An essential influence on search engine rankings is meta-information, like the title and description of a webpage. These are displayed to users together with the URL as a snippet in the search result and serve as a teaser animating the user to click. All presented open source systems offer users the opportunity to manually create individual meta-information for the subpage of online projects.

The rising number of mobile views has changed the demands that users put on internet presentations. Operators who still base the layout of their website exclusively on desktop users lose potential visitors and will find a decline in search engine rankings. The implementation of new online projects should make the issue of mobile-friendly presentation a priority. In principle, CMS systems counteract users by strictly separating content and presentation. For all presented solutions, you’ll find templates which automatically adjust the display size to different user devices in the scope of responsive designs. But be warned: They’re not all available for free.

Service and support are deciding factors for the selection of a CMS. Small and medium-sized enterprises can’t afford to pay for the services of professional agencies in the conception, implementation, and maintenance of the web presence.

Crucial for safe operation is whether or not the open source CMS has the necessary information available, as well as resources in the form of themes, plugins, and regular updates. In our CMS comparison, we concentrate exclusively on systems that have a large user and developer community and provide users with all necessary information for secure deployment in a detailed project documentation. All projects offer public release plans, regular software updates, and a transparent security protocol.