Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/joomla/joomla-cms (opens in new tab) · github.com/WordPress/WordPress (opens in new tab)
Pick Joomla
If the site is structured: several editor groups with different view and edit rights, content in more than one language, or PostgreSQL, all in the core (~458 MB idle).
Pick WordPress
If it is a blog, brochure site or shop and you want the widest choice of themes and plugins and the easier install (~524 MB idle), accepting plugins for multilingual and fine-grained permissions.
Joomla and WordPress are the same kind of server software: PHP on a MySQL-family database, both under the GPL, both run from a Docker image beside a database container. The difference is what each treats as built in. Joomla calls itself "a Content Management System (CMS) which enables you to build websites and powerful online applications", and ships access control and a multilingual framework in the core. WordPress states its mission as to "democratize publishing", and leaves most else to a very large plugin and theme ecosystem. Our install checks put them within about 70 MB of each other at idle, so the choice is about what you will be doing after the install screen.
Joomla describes itself as "a free and open-source content management system (CMS) for publishing web content". Its user guide says "The default features of Joomla are implemented as core extensions", and that "Many more extensions are available from the Joomla! Extensions Directory (JED)". The shape that implies is a larger core, with extensions for the edges.
WordPress is "open source software" whose aim is that publishing is open to anyone: "WordPress is designed for everyone", with minimum setup and ease of use named as priorities. Its Plugin Directory calls itself "the largest directory of free and open source WordPress plugins", and the front page lists plugins that change what the product is: a page builder, an SEO suite, a shop, two-factor login. The shape is a small core that you grow with plugins.
This is the sharpest built-in difference. Joomla's user guide says "User Groups are used to divide site users into groups with different responsibilities", with nine built-in groups you can extend, and access levels decide who can view an object, starting from "Public, Guest, Registered, Special and Super Users". What users can do is a separate layer, "Action Permissions, either in Global Configuration settings or in Component settings or in Item settings", and "The default user groups are set up with parent child relationships to minimise duplication of permissions." You can make an article visible to one group and editable by another without an add-on.
WordPress's roles page says it "has six pre-defined roles", from Super Admin (multisite only) down to Subscriber, with Administrator, Editor, Author and Contributor in between. They map to capabilities such as install_themes or activate_plugins. That is plenty for a blog with a few writers. A site that needs per-category or per-item view restrictions is where Joomla's model starts to pay off and WordPress asks for a plugin.
Joomla's documentation separates "installed languages" (those the core or extensions are translated into) from "content languages" (those the site content can be written in). The Multilingual Associations component lets you "associate translations with each other", enabled by turning on the System - Language Filter plugin and setting Item Associations to Yes. It is not automatic: the guide says "the menus, articles, and other content you write still need to be translated by hand for each language", and third-party extensions need their own language files.
WordPress core has no equivalent. Its roadmap lists "Multilingual — Core implementation for Multilingual sites" as a later, long-term phase, and a 2015 make.wordpress.org/core summary of a WordCamp Europe multilingual discussion proposed that "WordPress core should not provide a translation or localisation UI and/or workflow", leaving that to plugins. For a multilingual WordPress site that means picking a plugin (Polylang and WPML are the well-known ones) and living with its data model. For a multilingual Joomla site, the structure is in the box, and you write the translations.
WordPress wins on sheer reach. The Plugin Directory's most popular listings include Elementor, Yoast SEO and WooCommerce, and the Theme Directory says it "is used by millions of WordPress users all over the world". If a feature exists as a web product, someone has probably written a WordPress plugin for it, and you can compare listings before committing.
On updates, WordPress documents that "Automatic background updates were introduced in WordPress 3.7", and its hardening guide describes /wp-content/ as the part "intended to be writable by your user account and the web server process". In a container deployment, the practical point is simpler: both projects publish official images, so updating means pulling a newer image and keeping the volume. Neither is hands-off. Each site's plugins are the real maintenance load.
Both are the same GPL family. Joomla's README says it is "distributed under the GNU General Public License version 2 or later"; WordPress is "licensed under the GPLv2", and its about page adds "GPLv2 or later". Our catalog lists both as GPL-2.0-or-later. Both are free to run, so the cost is the server and whatever commercial extensions you choose.
Requirements are close. Joomla 6's requirements page lists PHP 8.3.0 as the minimum (8.4 recommended), MySQL 8.0.13, MariaDB 10.4 or PostgreSQL 12.0 as minimums, and "Recommended PHP Memory Limit: at least 256MB". WordPress recommends "PHP version 8.3 or greater", "MariaDB version 10.11 or greater OR MySQL version 8.0 or greater" and HTTPS. One real difference: Joomla supports PostgreSQL, while WordPress's requirements page names only MySQL and MariaDB.
Both catalog pages set a documented floor of 1 GB. In our install check (GCP e2-standard-2, Ubuntu 26.04, default install snippet, measured at idle on first boot, so no content and no traffic), Joomla idled at ~458 MB of RAM and ~2.5 GB of disk (September 2026), and WordPress at ~524 MB of RAM and ~2.8 GB of disk (October 2026). Treat those as a first-boot baseline, not production load: a busy site with plugins will use more.
The snippets differ in a way that matters. Joomla's skips the browser installer with JOOMLA_ADMIN_* variables and publishes plain HTTP on 8080. Ours for WordPress pins the image, puts Caddy in front for automatic HTTPS (it needs a domain), keeps WordPress on 127.0.0.1, and creates the admin with WP-CLI so the public install screen is never left open. We rate Joomla 2 out of 5 for difficulty and WordPress 1 out of 5.
Choose Joomla if the site is structured: several editor groups with different view and edit rights, content in more than one language, or PostgreSQL as the database. You get that in the core, and in exchange you accept a smaller extension catalogue and a harder install by our rating.
Choose WordPress if the site is a blog, a brochure site or a shop, and you want the widest choice of themes, plugins and people who know the product. It is the easier one to install by our rating, and it idled at ~524 MB in our check. Plan on plugins for multilingual and fine-grained permissions.
Both installs are verified on Ubuntu 26.04; the compose files are on the Joomla and WordPress pages. A 1 GB plan is the documented floor for each, and 2 GB leaves room for the database, caching and a few plugins or extensions. Put a TLS reverse proxy in front before the site faces the internet, keep the database unpublished, take regular volume backups of both the site files and the MySQL data, and update the image on a schedule rather than when something breaks.
Joomla if you need built-in user groups with per-item permissions, a multilingual framework or PostgreSQL support; it idled at ~458 MB in our check. WordPress if you want the widest plugin and theme choice and the simplest install; it idled at ~524 MB. Both are GPL and run on PHP with MySQL.
Joomla ships the framework in the core: installed and content languages and a Multilingual Associations component, though the docs note your content still has to be translated by hand. WordPress core has no multilingual content model: its roadmap lists multilingual as a later phase, so sites rely on plugins such as Polylang or WPML.
Our catalog lists a 1 GB floor for both. On a GCP e2-standard-2 with Ubuntu 26.04, default install snippet, at first-boot idle, Joomla used ~458 MB and WordPress ~524 MB, with ~2.5 GB and ~2.8 GB of disk. That is idle with no content or traffic, not production load.
Yes. Joomla's README says it is distributed under the GNU General Public License version 2 or later, and WordPress says it is licensed under the GPLv2 or later. Both are free to run on your own server.
Paid link — we earn a commission if you shop through it.
A PHP content framework where you model structured content and languages, or the familiar block-editor CMS with the plugin ecosystem.
A publication with members and paid newsletters built in vs. the plugin-extended CMS.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.