Wagtail vs Drupal for publishers: Python editors or PHP structure?

The short version

Pick Wagtail if your team writes Python. It is a BSD-licensed content management system built on Django. You add it to a Django project, define page types in Python and write the templates, and editors get a tailored admin with workflows, scheduled publishing with expiry and revision comparison, according to the vendor’s features page.

Pick Drupal if your publication treats content as structured data: many content types, several desks with different permissions, several languages or an API consumer. Core includes Content Moderation, multilingual modules and JSON:API. The price is a heavier build, with SEO helpers and scheduling coming from contributed modules.

The deciding trade-off is stack and scope. Wagtail is a focused editorial layer on a Python framework. Drupal is a bigger platform with more in core and more to configure. Our profiles for Wagtail and Drupal go further. Everything here rests on vendor documentation, not our own install, and we name no news publisher as a user of either.

At a glance

Editorial workflow

Wagtail’s features page lists customisable workflows that control who can moderate, review and publish, scheduled publishing with expiry dates, and built-in revision comparison. Page permissions attach to pages and cascade down the page tree. The permission types are add, edit, publish, bulk delete and lock/unlock. Users without publish permission can submit changes for moderation. A group with edit rights on a section gets them on everything beneath it, which maps naturally to desks.

Drupal’s core Content Moderation module expands the unpublished and published states into workflows made of states such as Draft, Published and Archived and the transitions between them. A published version can stay live while a working copy is reviewed, and enabling the module creates a default Editorial workflow. The User Guide covers users, roles and permissions, so a desk-by-desk model is configuration.

Scheduling differs. In Wagtail it is on the features list. In Drupal it comes from the contributed Scheduler module, which lets editors schedule content, media, commerce products and taxonomy terms for publishing and unpublishing. We have not verified how Scheduler interacts with moderation states, so test that pairing.

Both can cover a newsroom’s daily needs. Drupal’s states and transitions are more explicit; Wagtail’s page-tree permissions are simpler to reason about. For approval chains beyond either default, check your own process.

Search, structured data and feeds

Neither system is complete out of the box. Wagtail’s sitemap module builds on Django’s sitemap framework and, once enabled, adds all published pages to sitemap.xml. The optional redirects app creates permanent redirects automatically when pages are moved or slugs change, and has an import command for bulk redirects, which helps migrations. We did not verify structured data, news sitemaps or RSS in the pages we opened.

Drupal asks more of you. Pathauto generates URL aliases from patterns, Metatag provides titles, canonical URLs, descriptions, Open Graph and Twitter Cards, and Simple XML Sitemap generates multilingual sitemaps with hreflang and image support and supports IndexNow. Schema.org and JSON-LD come from a separate Schema.org Metatag module, according to the Metatag page. We did not verify Drupal feed behaviour.

Either way, titles, canonical tags and JSON-LD depend on the build and modules. Follow Google’s documentation, and use the feature checklist to test output.

Hosting, performance and security

Wagtail runs as a Django application. Its documentation says it is currently compatible with Django 5.2, 6.0 and 6.1, and installs Pillow, which needs system libraries. We did not confirm supported Python versions or databases from the pages we opened. The 7.4 series is marked LTS, which gives a slower upgrade path.

Drupal 11.x requires PHP 8.3.0 or later. It supports MariaDB, MySQL, PostgreSQL and SQLite, runs on Apache, Nginx and other web servers, and recommends Linux for hosting, with Windows supported only for development. Composer is needed for installation and updates. The releases page shows Drupal 10.6.x receiving security support only until December 2026, so older branches have a deadline.

We have no performance or security benchmarks for either. Caching and CDN choices sit with your developers or host. See our self-hosted guide.

Cost of ownership

Neither has a licence fee. Wagtail’s licence is BSD-3-Clause, which permits use in open and closed projects. Drupal.org says Drupal is distributed under the GNU GPL with no licensing fees, and the Drupal Association is the non-profit supporting the project.

The spend is in people: a developer to model content, build templates, configure roles and workflows and apply updates. We did not find a vendor-run hosted Wagtail service in the pages we opened and quote no hosted price. We have not verified public prices for Drupal hosts or agencies and give no figures.

Update effort differs in shape. Wagtail upgrades follow Django’s, and Drupal updates run through Composer. Whoever owns that routine matters more than any feature list. See the cost guide and licensing guide.

Migrating between them

We did not find an official Wagtail-to-Drupal or Drupal-to-Wagtail migration tool in the documentation we opened, and we have not verified Drupal’s migration documentation. Content moves between a Django model and Drupal entities through a developer-written importer.

One piece is documented on the Wagtail side: the redirects app has an import command for bulk redirects, so a URL map from an old site can be loaded in one go. Both systems expose content over an API, Drupal’s JSON:API in core and Wagtail’s v2 API read-only, which gives a route to extract content if you script it. Test the full URL map before launch.

Which should you choose?

• Python developers, custom page types, a clean editor experience: Wagtail.
• PHP or Drupal-experienced agency, many content types and roles: Drupal.
• Many languages with separate control of interface, configuration and content translation: Drupal; Wagtail keeps a page tree per locale and adds third-party tooling for richer workflows.
• Desk-level permissions with simple scheduling: Wagtail.
• Headless with a stable, core API today: Drupal; Wagtail’s write API is a preview.
• No developer on staff: neither. See the CMS directory.

For a Drupal comparison against a .NET system, read Umbraco vs Drupal. The comparison hub lists the rest, and the demo page explains how to trial a system.