Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/drupal/drupal (opens in new tab) · github.com/WordPress/WordPress (opens in new tab)
Pick Drupal
If the site is a content system: several structured content types, roles and permissions, Views listings or multiple languages, and someone comfortable with Composer.
Pick WordPress
If you want the quickest route to a working blog or brochure site with a block editor and plugins. Our Drupal RAM figure (~42 MB) is Drupal before its web installer runs, so it is not comparable with WordPress's installed site.
Drupal and WordPress are both GPL content management systems written in PHP, and both turn up when someone says they want to run their own website. They are aimed at different jobs. Drupal describes itself as "content management software" and the platform "many government agencies" use, and says "what sets it apart is its flexibility". WordPress says it is "the platform of choice for millions of sites across the web". One is a framework you model content in; the other is the one most people already know how to use. Our catalog also records a measurement for Drupal that needs a caveat before you compare it with anything, covered below.
Drupal pitches "versatile, structured content that dynamic web experiences need", extended by modules, themes and distributions. Its own User Guide shows what the core covers: chapters on content types, taxonomies and reference fields, on Views ("Overview of view concepts and details of common view tasks"), on user roles and permissions, and a chapter called "Making Your Site Multilingual", covering content translation and configuration translation. Drupal CMS, which the install docs describe as aimed at marketers, designers and content creators, is a separate starting point from the core download. You decide the content model: what a "Recipe" or "Event" is, which fields it has, and who can edit it.
WordPress starts from posts and pages. The block editor is the default way to write, with blocks "for paragraphs, images, headings, lists, videos, galleries, and more", and "more can be added through WordPress plugins". Upstream says the block editor replaced the classic editor in WordPress 5.0, which now needs a plugin. The WordPress About page describes it as running on PHP with a MariaDB database. If you want a blog or a brochure site, the editor is built for that.
This is the real difference. In Drupal you create content types, attach fields, build lists with Views and control who may do what with roles and permissions, all described as core topics in the User Guide. That takes more setup than writing a post, and it pays off when the site has several kinds of structured content that relate to each other. In WordPress the unit is the post or page, laid out with blocks and patterns. Custom structure is something you add through plugins and themes. Both models work; the question is whether your site is a handful of pages and posts or a content database.
Drupal's User Guide gives multilingual setup its own chapter: adding a language, configuring content translation, translating content and translating configuration. WordPress's own handbook is plain about core: "WordPress currently does not support a bilingual or multilingual blog out-of-the-box." It points to community plugins instead, and says core multilingual support is planned for the fourth and final phase of the Gutenberg project. If more than one language is a day-one requirement, Drupal does it in core; on WordPress you are choosing and maintaining a plugin.
Both are GPL. Drupal is "distributed under the terms of the GNU General Public License" with no licensing fees, and our catalog lists GPL-2.0-or-later. WordPress's licence page says its licence "is the GPLv2 (or later)", and its licence page adds a position that matters if you ever sell themes or plugins: "Derivatives of WordPress code inherit the GPL license", and "we feel strongly that plugins and themes are derivative work and thus inherit the GPL license". For a site owner, neither licence limits what you can run. There is no Enterprise edition to buy in either catalog entry.
Drupal's system requirements page lists MariaDB, MySQL, PostgreSQL and SQLite as supported databases, Apache, Nginx and other web servers, and "Linux or a similar operating system" as the recommended host. Its install docs include a Composer step: "After updating the codebase with Git, the required PHP libraries must be installed with Composer", then "Run the installer". Our snippet instead uses the Docker Official Image drupal:11-apache beside PostgreSQL 16 with volumes for modules, profiles, themes and sites; you finish in the web installer, choosing PostgreSQL and postgres as the host. The community recommends DDEV for local builds, per the install docs.
WordPress in our catalog is the official wordpress:7.1.3-apache image with MySQL 8.4, plus Caddy for automatic HTTPS and a wpcli container that creates the admin from the command line, so the public install screen is never left open. That is a longer snippet because it includes HTTPS and the admin step, and it needs a domain pointed at the server. We rate WordPress 1 out of 5 for difficulty and Drupal 2 out of 5.
Neither upstream gives a server RAM minimum. Drupal's PHP requirements set a per-process PHP memory minimum of 64MB and add that "Typically, 128 MB or 256 MB is used on production systems." Our 512 MB floor for Drupal and 1 GB for WordPress are estimates. What we measured was idle at first boot on a GCP e2-standard-2 test box (Ubuntu 26.04, Docker), default install snippet only. Drupal idled at ~42 MB of RAM and ~1.5 GB of disk (October 2026). WordPress idled at ~524 MB of RAM and ~2.8 GB of disk (October 2026).
Do not read those RAM numbers as Drupal being twelve times lighter. The two snippets stop at different points. Both figures add up every container in the snippet. Ours for Drupal starts Drupal (Apache and PHP) beside an empty PostgreSQL and ends at the web installer, which still asks you for the database, so ~42 MB is Drupal before it is installed: no tables, no content, no modules enabled. The WordPress snippet runs MySQL, Caddy and a wp core install step, so its ~524 MB describes an installed site behind a proxy. We have not measured an installed Drupal site, so we cannot say how close the two would be.
Choose Drupal if the site is a content system rather than a blog: several structured content types, roles and permissions, Views-style listings, or multiple languages, and someone on the team is comfortable with Composer and with modelling content before writing it. Expect more setup than WordPress, and treat our ~42 MB as an installer-stage figure.
Choose WordPress if you want the quickest route to a working blog or brochure site, a block editor that editors already know, and extensions through plugins and themes. Our snippet idled around ~524 MB with a configured site behind Caddy, and it is the easier of the two (1 out of 5 against 2 out of 5).
Neither has a licensing catch for a site owner, so the decision is about who edits the site and how structured the content is, not about price.
Both installs are verified on Ubuntu 26.04, with the full snippets on the Drupal and WordPress pages. Drupal's snippet publishes port 8080 over plain HTTP and ends at the web installer, so finish the installer promptly and put a TLS reverse proxy in front before the port faces the internet. WordPress's snippet already includes Caddy and creates the admin from the command line.
Drupal lists a lower minimum: 512 MB vs 1024 MB for WordPress.
Drupal if your site needs structured content types, roles and permissions, Views-style listings or several languages, and you are comfortable modelling content up front. WordPress if you want a working blog or brochure site quickly with the block editor and plugins. Both are GPL-2.0-or-later and both are verified on Ubuntu 26.04 as Docker Compose stacks with a database.
Not on the evidence we have. Drupal idled at ~42 MB of RAM and WordPress at ~524 MB on our GCP e2-standard-2 box, but our Drupal snippet ends at the web installer, which still asks for the database, while the WordPress snippet includes Caddy and a wp core install step. The figures are first-boot numbers at different stages, and we have not measured an installed Drupal site.
Neither catalog entry lists one. Drupal is "distributed under the terms of the GNU General Public License" with no licensing fees, and WordPress's licence is "the GPLv2 (or later)". WordPress's licence page also says it feels strongly that plugins and themes are derivative work and inherit the GPL.
Drupal's system requirements list MariaDB, MySQL, PostgreSQL and SQLite; our snippet uses PostgreSQL 16 and the web installer asks you to choose it. WordPress's About page says it runs on PHP with a MariaDB database; our snippet pairs the official image with MySQL 8.4.
Paid link — we earn a commission if you shop through it.
A CMS with access control and a multilingual framework in the core vs. a small core grown with the largest 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.