Now booking enterprise content platform builds for 2026. Contact us

CMS comparison Drupal vs Wagtail

Drupal vs Wagtail

Drupal is an open-source traditional CMS that you host yourself. Wagtail is an open-source traditional CMS that you host yourself. The table below sets them side by side on 28 features. They get a different status on 10.

  • Drupal Traditional · Open source · 16 of 28 built in
  • Wagtail Traditional · Open source · 18 of 28 built in

Sources checked: Drupal on 29 Sept 2026, Wagtail on 29 Sept 2026. Plans and releases can change after those dates.

WAYF is an official Payload partner and top contributor. Every platform in the table is classified by the same published definitions, and each answer lists the vendor page it came from.


Feature comparison

Built inPaid tierPlugin or add-onLimitedNot available
Drupal vs Wagtail feature comparison. Columns are the two platforms. Rows are features, grouped by area.
Platform
Drupal Traditional
Wagtail Traditional
Overview
What it is Open-source PHP CMS with fieldable content types, core JSON:API and multilingual modules. Teams self-host it or use Drupal hosting platforms.Open-source CMS built on Django. Content types are Python models, and you host it yourself on any Python stack.
Edition compared The product and release each column describes. Drupal 11 core. Drupal CMS 2 bundles core with selected contrib modules. Version 11.4.8, released 26 Sept 2026 Wagtail 8, open source Version 8.0, released 25 Aug 2026
Vendor Drupal community, supported by the Drupal Association drupal.org Wagtail core team (created by Torchbox) wagtail.org
Licence Open source GPL-2.0-or-later Open source BSD-3-Clause
Hosting Self-hosting No vendor cloud Acquia, Pantheon and other companies sell managed Drupal hosting. Self-hosting No vendor cloud The Wagtail project runs no managed hosting. Deploy it like any Django app.
Built with PHP, Symfony, TwigPython, Django
Database MySQL, MariaDB, PostgreSQL, SQLitePostgreSQL, MySQL, MariaDB, SQLite
Pricing Public list prices only. Hosting and implementation are extra everywhere. Free to start Free and open source. Hosting, support and contrib services cost extra. Free to start Free and open source. No licence fee.
Content modelling
Content model in code You define content types in files in your repository, review them like any other code and apply them from there. Imperative migration scripts alone count as limited. Built in Content types and fields export to YAML config files. Built in Page and snippet types are Django models. 2
Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. Built in Field UI in core. Not available Developers define content types in Python only.
Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. Built in Layout Builder in core. Paragraphs and Drupal Canvas are contrib. 910 Built in StreamField blocks. 2
Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. Built in Field-level content translation in core. 7 Built in Core i18n with simple_translation. The wagtail-localize package adds a translation workflow. 3
Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. Built in Image styles scale, crop and convert images. 8 Built in Renditions with resize, crop and format filters. 4
APIs and delivery
REST API A documented REST or JSON HTTP API returns content. Built in JSON:API and REST modules in core. 3 Built in Read-only v2 API. Writable v3 API in preview since 8.0. 51
GraphQL API The vendor or an official module provides a GraphQL API for content. Plugin or add-on GraphQL contrib module. Developers build the schema. 4 Plugin or add-on wagtail-grapple, maintained by Torchbox. 6
Webhooks The CMS can call an external URL when content is created, changed or published. Plugin or add-on Webhooks contrib module. Core has no outgoing webhooks. 18 Not available Django signals such as page_published. No webhook settings. 18
Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. Built in Twig themes. Built in
Editorial workflow
Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. Built in Drafts of published content need the core Content Moderation module. 5 Built in
Scheduled publishing An editor can set a future date and time for content to publish or unpublish. Plugin or add-on Scheduler contrib module. 11 Built in Go-live and expiry dates. 7
Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. Built in Revert in core. Side-by-side compare needs the Diff contrib module. Built in Editors can compare and revert revisions. 11
Preview Editors can see unpublished content rendered as it will appear on the site before publishing. Built in Preview button on the edit form. Built in 20
Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. Limited Layout Builder edits blocks on a rendered preview. Drupal Canvas is contrib. 910 Limited Preview panel beside the edit form. No click-to-edit on the page. 20
Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. Built in Workflows and Content Moderation modules in core. 5 Built in Moderation workflows with tasks assigned to groups. 8
Content releases Editors group changes across several entries and publish them together as one release. Built in Workspaces module, stable in core since 10.3. 6 Not available
Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. Not available Not available Concurrent editing notifications warn editors. No live co-editing. 12
Access and governance
Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. Built in Built in Groups with page, collection and model permissions. 9
Field-level permissions Admins can restrict access to single fields, on top of content types and entries. Plugin or add-on Field Permissions contrib module. 12 Built in Set in code with the permission argument on panels. 10
Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. Plugin or add-on OpenID Connect or SAML Authentication contrib modules. 13 Plugin or add-on django-allauth supports SAML and OpenID Connect. 19
Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. Limited Database Logging records content events by user. It caps and prunes entries. 20 Built in Site-wide history report of logged actions. 11
Platform and extensibility
Multiple sites One installation or account can manage several separate websites or brands with shared users. Plugin or add-on Domain contrib module. Core multisite shares only the codebase. 14 Built in Several sites in one installation with shared users. 9
Extensible admin UI Developers can add their own components, views or fields to the editing interface. Built in Custom field widgets, forms and admin routes. Built in Hooks, viewsets and custom panels.
Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. Built in drupal.org module directory. Built in Wagtail packages directory on wagtail.org. 17
Form builder Editors can build and publish forms and collect submissions without code. Plugin or add-on Webform contrib module. Core Contact is deprecated in 11.4. 152 Built in wagtail.contrib.forms form builder. 13
Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. Built in Limited Login for private pages is built in. Public sign-up needs a package such as django-allauth. 14
AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. Plugin or add-on AI module from the Drupal AI Initiative, bundled with Drupal CMS. 1619 Plugin or add-on Wagtail AI, an officially supported package. 15
Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. Not available Community contrib only, e.g. the MCP Server module by Lullabot and Omedia. 17 Limited Experimental wagtail-mcp package, announced September 2026. 16

Considering more platforms? Compare Drupal and Wagtail with the rest of your shortlist in the CMS comparison tool.


Where they differ

Drupal and Wagtail get a different status on 10 of the 28 features and the same status on 18. Drupal has 16 built in on its baseline edition, Wagtail has 18. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.

Built in on Drupal, a different answer on Wagtail 3

  • Content model in the UI Drupal: Built in. Wagtail: Not available.
  • Content releases Drupal: Built in. Wagtail: Not available.
  • Site member accounts Drupal: Built in. Wagtail: Limited.

Built in on Wagtail, a different answer on Drupal 5

  • Scheduled publishing Drupal: Plugin or add-on. Wagtail: Built in.
  • Field-level permissions Drupal: Plugin or add-on. Wagtail: Built in.
  • Audit log Drupal: Limited. Wagtail: Built in.
  • Multiple sites Drupal: Plugin or add-on. Wagtail: Built in.
  • Form builder Drupal: Plugin or add-on. Wagtail: Built in.

Built in on neither, with different answers 2

  • Webhooks Drupal: Plugin or add-on. Wagtail: Not available.
  • Official MCP server Drupal: Not available. Wagtail: Limited.

More comparisons

Full write-ups with worked examples and costs: Drupal vs Payload.

Open the CMS comparison tool to put up to six platforms in one table.


We're booking content platform
engagements for 2026.

Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.