Upgrades

Drupal 12: Release Date, Requirements and How to Prepare

Tiberiu Trandaburu 10 min read
Drupal 12 release in the week of 7 December 2026: how to prepare, starting with PHP 8.5

Drupal 12 is scheduled for release in the week of 7 December 2026, together with Drupal 11.5.0. It requires PHP 8.5, MariaDB 10.11 and PostgreSQL 18 or later, and it can only be installed as an update from Drupal 11.3 or later. If your site is on Drupal 11 there is no rush: Drupal 11 is supported until early December 2028, so the right move now is to get your hosting and modules ready, not to upgrade in the first week.

Key takeaways

  • Drupal 12.0.0 is planned for the week of 7 December 2026. Drupal 10 reaches end of life in the same week, on 9 December.
  • Drupal 12 needs PHP 8.5. Drupal 11.3 and 11.4 already run on PHP 8.5, so you can change PHP first and Drupal later.
  • Drupal's update system refuses to update from Drupal 11.2 or earlier. Get to 11.4 (or 11.5 once it is out) before you plan anything else.
  • Nine modules and three themes leave core, including Contact, Search, Toolbar, Claro and Olivero. Check your site against the list before the upgrade.
  • Drupal 11 is supported until early December 2028 and Drupal 12 until early December 2030. On a Drupal 10 site, go to Drupal 11 now; you cannot skip a version.

Drupal 12 release date and where the release stands

The Drupal core release schedule sets the Drupal 12.0.0 release for the week of 7 December 2026, and the end-of-life table on the same page gives 9 December 2026 as the Drupal 12 release date. Drupal 11.5.0 is released in the same window, and security support ends for Drupal 11.3.x and Drupal 10.6.x.

DateMilestoneStatus on 19 November 2026
2 September 2026Drupal 12.0.0-alpha1Released
30 September 2026Drupal 12.0.0-beta1 (platform requirements and removed extensions fixed)Released
14 October 2026Drupal 12.0.0-beta2 (includes security fixes)Released, latest Drupal 12 release
Week of 9 November 2026Drupal 12.0.0-rc1 and 11.5.0-rc1Scheduled, not yet published on drupal.org
Week of 7 December 2026Drupal 12.0.0 and 11.5.0. End of security support for 11.3.x and 10.6.xScheduled
9 December 2026Drupal 10 end of lifeScheduled

Beta and release candidate versions are for testing, not for production. The release notes for the betas say so directly: they exist so that site owners and module authors can check compatibility and upgrade paths.

If you are still on Drupal 10, Drupal 12 does not change your plan. Drupal major upgrades run in sequence, so a Drupal 10 site goes to Drupal 11 first. Our guide to Drupal 10 end of life covers that upgrade step by step.

Last checked against the Drupal core release schedule and the Drupal core releases page on drupal.org: 19 November 2026.

Drupal 12 requirements

The main change for Drupal 12 is PHP 8.5. The web server and MySQL requirements stay the same as for Drupal 11, while MariaDB and PostgreSQL move up.

ComponentDrupal 11Drupal 12
PHP8.3 or later8.5 or later
MySQL8.08.0 (no change)
MariaDB10.610.11
PostgreSQL1618 (see note below)
SQLite3.45 with json13.45 with json1 (no change)
Web serverApache 2.4.7 or nginx 1.1No change. IIS is not supported.
Composer2.7.0 or laterLatest secure release recommended (2.9.3 at the time of the announcement)
Starting point for the updateDrupal 10.3 or laterDrupal 11.3 or later; 11.4 or 11.5 recommended

A note on PostgreSQL: the platform requirements announcement and the drupal.org database requirements page list PostgreSQL 18, but the 12.0.0-beta1 release notes say PostgreSQL 19. If you run Drupal on PostgreSQL, check the final 12.0.0 release notes before you commit to a database version.

Three more changes matter for hosting and security:

  • Password hashing. Drupal 12 uses argon2id by default. If argon2 is not available on your server, the release notes explain how to switch back to bcrypt with kernel parameters.
  • Windows in production. Hosting Drupal directly on Windows in production is deprecated. The advice is to use Linux on Windows instead. Windows for local development stays supported.
  • HTTP fallback for updates. The update_fetch_with_http_fallback setting is gone. If your site cannot reach updates.drupal.org over HTTPS, fix the SSL/TLS problem on the server.

Last checked against the Drupal 12.0.0 platform requirements announcement, the drupal.org system requirements pages and the 12.0.0-beta1 release notes: 19 November 2026.

PHP 8.5 is the first thing to sort out

Change PHP before you change Drupal. According to the drupal.org PHP requirements table, Drupal 11.3 and 11.4 already support PHP 8.5, so you can move the server to PHP 8.5 on Drupal 11, test, and only then run the Drupal 12 upgrade.

PHP versionSecurity support until (php.net)Drupal 11.3 / 11.4Drupal 12.0
8.331 December 2027YesNo
8.431 December 2028YesNo
8.531 December 2029YesYes

There is a second reason to plan this now. Many Drupal 11 sites run on PHP 8.3, and PHP 8.3 security support ends on 31 December 2027, almost a year before Drupal 11 itself reaches end of life. Moving to PHP 8.5 on Drupal 11 fixes that and removes the biggest blocker for Drupal 12 in the same step.

Ask your hosting provider when PHP 8.5 is available on your plan, and test your custom code and contributed modules on it in a development copy. If your host cannot offer PHP 8.5, a hosting change will take longer than the Drupal upgrade itself.

Last checked against php.net supported versions and the drupal.org PHP requirements page: 19 November 2026.

Modules and themes removed from Drupal 12 core

Drupal 12 removes nine modules and three themes from core and moves them to contributed projects. If your site uses one of them, add the contributed version to Composer while you are still on Drupal 11, or uninstall it if nobody needs it.

Removed from coreTypeWhat to do
Ban, Contact, Field Layout, History, Search, Settings Tray, Shortcut, Telephone, ToolbarModulesRequire the contributed project before the upgrade, or uninstall if unused
ClaroAdmin themeReplaced by the new Default Admin theme, which is now stable. Claro continues as a contributed project.
Olivero, Stable 9ThemesIf your front-end theme is Olivero or is based on Stable 9, require the contributed version before the upgrade
Migrate Drupal, Migrate Drupal UIModulesRemoved with no contributed replacement. The Migrate API stays in core.
Syndicate block (RSS icon)Block pluginRemoved. Any placed Syndicate block is removed during the update.

One warning from the release notes is worth repeating: if a removed module is needed for the site to work, do not uninstall it. Uninstalling destroys its configuration and data. Require the contributed version instead, so the module keeps working after the upgrade.

Contact and Search are the two that surprise people, because many sites use the core contact forms or the core search page without thinking of them as modules. If you still migrate content from Drupal 7 with Migrate Drupal, finish that migration on Drupal 11.

To see what is enabled on your site, run:

drush pm:list --type=module --status=enabled
drush pm:list --type=theme --status=enabled

The drupal.org upgrade guide for Drupal 12 is still marked as work in progress and lists a shorter set of removed modules than the beta release notes. The list above comes from the 12.0.0-beta1 release notes, which are newer. Check the final 12.0.0 release notes before your upgrade.

What Drupal 12 changes for developers

For teams with custom code, Drupal 12 is mostly about removed deprecations and new major versions of dependencies. The release notes list these changes:

  • Code deprecated in Drupal 11 is removed, including entire deprecated modules and themes.
  • PHPUnit moves from 11.5 to 12.5, and test annotations must be converted to PHPUnit attributes.
  • Guzzle moves from 7 to 8, and htmx from 2.0 to 4.0, with backward-incompatible changes.
  • The Backbone and Underscore JavaScript libraries are removed. Custom JavaScript that uses them must bring its own copy.
  • Filenames with dangerous characters, such as shell metacharacters, are now cleaned up with underscores.

Apart from these removals, Drupal 12.0 is close to Drupal 11.5. The release notes describe 12.0.x as nearly identical to 11.5.x except for removed deprecated code and updated dependencies. That is why a Drupal 11 site with clean, current code usually has a small upgrade ahead of it.

Drupal 11 support dates: how long you can wait

You can stay on Drupal 11 until early December 2028, as long as you keep moving to supported minor versions. Each Drupal 11 minor release has its own security window, so "on Drupal 11" is only safe if you are on a supported 11.x.

VersionSecurity support
Drupal 11.3.xEnds in the week of 7 December 2026
Drupal 11.4.xUntil 21 April 2027
Drupal 11.5.xReleased in the week of 7 December 2026
Drupal 11 (major version)Until early December 2028
Drupal 12 (major version)From 9 December 2026 until early December 2030

If your site is on Drupal 11.3, update to 11.4 now and to 11.5 when it is released. That keeps you covered by security releases and puts you on the version the Drupal 12 update path expects.

Last checked against the Drupal core release schedule: 19 November 2026.

When to move to Drupal 12

Move when your contributed modules are ready, not when Drupal 12.0.0 comes out. A new major version is only as usable as the modules your site depends on, and many maintainers publish their Drupal 12 releases in the weeks and months after the core release.

Your site todayWhat to do now
Drupal 10Upgrade to Drupal 11 before or as soon as possible after 9 December 2026. Drupal 12 is not an option yet for you.
Drupal 11.2 or olderUpdate to 11.4 now. Drupal 12 cannot update a site that is on 11.2 or earlier.
Drupal 11.3 or 11.4, PHP 8.3 or 8.4Plan the move to PHP 8.5 and run Upgrade Status. Fix what it reports while you are still on Drupal 11.
Drupal 11.4 or 11.5, PHP 8.5, clean Upgrade Status reportUpgrade on a staging copy once your contributed modules have Drupal 12 releases. Test the release candidate in development before that.

In our work, the sites that upgrade quickly are the ones that never let deprecations pile up. A Drupal 11 site that gets monthly updates and fixes Upgrade Status warnings as they appear needs little work for Drupal 12. A site that has not been touched since its Drupal 11 launch has more to catch up on.

How to prepare a Drupal 11 site for Drupal 12

Do the preparation on Drupal 11, one change at a time. The order below keeps each step small and easy to test.

  1. Update to the latest Drupal 11 release. Get to 11.4 now, and to 11.5 after it is released. Update contributed modules to their latest releases at the same time.
  2. Move the server to PHP 8.5. Test on a development copy first, then change production while you are still on Drupal 11.
  3. Check the database version. MariaDB sites need 10.11 or later. PostgreSQL sites should wait for the final 12.0.0 notes to confirm 18 or 19.
  4. Run Upgrade Status with the 5.x branch. It checks your environment, contributed projects and custom code against Drupal 12. Our guide to the Drupal Upgrade Status module explains which branch to install, the Drush commands and how to read the report.
  5. Resolve the removed modules and themes. Require the contributed versions of anything you use from the list above, or uninstall what you do not use.
  6. Fix custom code. Run Drupal Rector for deprecations, then fix the rest by hand. Convert PHPUnit annotations to attributes if you have tests.
  7. Test the upgrade on a copy. When your modules are ready, run the upgrade on a staging copy of the live site:
composer require 'drupal/core-recommended:^12' 'drupal/core-composer-scaffold:^12' 'drupal/core-project-message:^12' --no-update
composer require drush/drush --no-update
composer update --dry-run
composer update
drush updatedb
drush cache:rebuild

If Composer refuses to update, composer why-not drupal/core ^12 shows which package is blocking it. That is usually a contributed module that does not have a Drupal 12 release yet.

After the upgrade, check the status report for errors about missing extensions. The release notes warn that Drush may skip warnings about missing extensions during the database update, and they only show up in the status report afterwards.

Frequently asked questions

When does Drupal 11 reach end of life?

Drupal 11 is supported until early December 2028, according to the Drupal core release schedule. The exact date will be on a core release window in that month. Individual minor versions end earlier: Drupal 11.3.x in the week of 7 December 2026 and Drupal 11.4.x on 21 April 2027.

When does Drupal 11.4 reach end of life?

Security support for Drupal 11.4.x ends on 21 April 2027. Before that date, update to Drupal 11.5, which is released in the week of 7 December 2026.

Can I download Drupal 12 now?

Yes, but only as a test release. Drupal 12 alpha and beta releases are on drupal.org and can be installed with Composer using the @beta stability flag. They are not meant for production, so use them on a development copy to test your modules and custom code.

Need help planning your Drupal 12 upgrade?

DevAtWork is a Drupal agency in Bucharest, Romania. We upgrade, migrate and maintain Drupal sites for organisations and digital agencies across Europe. If you want to know what Drupal 12 means for your site, your hosting and your timeline, see our Drupal migration and upgrade services or tell us about your site.

Sources

Tiberiu Trandaburu, Founder & CEO, DevAtWork
Written by Founder & CEO, DevAtWork

Tiberiu is the founder and CEO of DevAtWork, a Drupal agency based in Bucharest, Romania. Since 2016 he has led Drupal projects for European institutions, international brands and digital agencies, from new builds and migrations to long-term support and security. He writes about Drupal upgrades, security and running websites that last.

More about the author
Start a project

Ship your next Drupal release with us.

Senior developers, clean code, and a reply within 24 hours.