Drupal 10 vs Drupal 11: Complete Comparison and New Features in 2026

Introduction

If your website is still running Drupal 10, 2026 is the year to make a clear upgrade plan.

Drupal 10 is not obsolete yet. The final Drupal 10 minor series, Drupal 10.6.x, continues to receive security support until December 2026. However, Drupal 10 itself reaches end of life on December 9, 2026, after which no new Drupal 10 core releases will be published.

Meanwhile, Drupal 11 has moved well beyond its original 11.0 release. As of August 18, 2026, the current feature branch is Drupal 11.4.x, and the latest stable Drupal core release is Drupal 11.4.5, released on August 6, 2026.

That distinction matters. Comparing Drupal 10 only with Drupal 11.0 misses almost two years of improvements added through Drupal 11.1, 11.2, 11.3 and 11.4.

Drupal 11.3 introduced major improvements such as native HTMX integration, a stable Navigation module, native content export and significant cache/database optimizations. Drupal 11.4 went further with fewer database lookups, Brotli asset compression, faster translation processing, a new experimental native CLI and configurable Argon2id password hashing.

This Drupal 10 vs Drupal 11 comparison explains what actually changed, which improvements matter in production, and whether Drupal 10 website owners should upgrade during 2026.

What Is Drupal 11?

Drupal 11 is the current major generation of Drupal core. Drupal 11.0.0 was released on August 2, 2024.

The transition from Drupal 10.3 to Drupal 11.0 was deliberately less disruptive than older Drupal major upgrades. Drupal.org explicitly noted that Drupal 10.3 already contained most of Drupal 11.0’s functionality. The major-version transition primarily removed deprecated code, upgraded major dependencies and raised platform requirements.

That means features commonly associated with the original Drupal 11 launch should not automatically be described as Drupal-11-exclusive.

For example, much of the functionality available at the Drupal 11.0 launch had already landed in Drupal 10.3. Drupal 11 removed backward-compatibility layers that Drupal 10 retained.

The more substantial functional divergence happened afterward, because new feature development moved to Drupal 11’s feature releases.

The current Drupal 11 line therefore combines:

the cleaner Drupal 11 foundation;
Symfony 7 and newer platform requirements;
the Drupal Recipes ecosystem;
Single Directory Components;
object-oriented hooks;
improved Workspaces;
JSON Schema generation;
AVIF support;
improved caching;
native HTMX;
stable Navigation;
native content export;
major database-query reductions;
Brotli CSS/JavaScript compression;
a native experimental Drupal CLI;
modernized password hashing options;
and numerous editor and developer-experience improvements.

Drupal 10 vs Drupal 11: Quick Comparison

Feature	Drupal 10	Drupal 11	What Changed?	Why It Matters
Current line in Aug. 2026	10.6.x	11.4.x	Drupal 10 is in maintenance phase	New development belongs on Drupal 11
Latest context	Final Drupal 10 minor	11.4.5 latest stable	11.4.5 released Aug. 6, 2026	Drupal 11 is the forward path
EOL/security horizon	Ends Dec. 9, 2026	Supported beyond Drupal 12	Drupal 11 has much longer runway	Important for long-lived sites
Minimum PHP	PHP 8.1+ for Drupal 10 generation; supported versions vary by minor	PHP 8.3 minimum for Drupal 11; 11.3 also supports PHP 8.5	New PHP baseline	Modern runtime and dependencies
Symfony	Symfony 6.x	Symfony 7.x	Major framework upgrade	Cleaner modern PHP stack
Twig	Twig 3.x	Twig 3.x	Same major Twig generation	Theme migration is less disruptive
Composer	Composer-based workflow	Composer 2.7+ baseline for Drupal 11	Modern dependency management reinforced	Safer reproducible builds
MySQL	5.7.8+	8.0+	Minimum raised	Check hosting before upgrading
MariaDB	10.3.7+	10.6+	Minimum raised	Database server may need upgrade
PostgreSQL	12+	16+	Minimum raised	Infrastructure planning required
SQLite	3.26+	3.45+	Minimum raised	Relevant to local/smaller deployments
CKEditor	CKEditor 5	CKEditor 5 with continuing enhancements	Editor evolves rather than being replaced	Easier editorial migration
JSON:API	Available	Available and performance improved	Core API remains; entity-query efficiency improves	Important for decoupled Drupal
REST	Available	Available	Modern dependency/core improvements	Existing API architectures remain viable
Views	Mature	Mature and continuously improved	No fundamental replacement	Low migration disruption
Layout Builder	Available	Available	Recipes can automate configuration	Easier repeatable site setup
Media	Available	Available	Benefits from broader entity/image improvements	Better modern media workflows
Content Moderation	Available	Available	Continues evolving with Workspaces	Enterprise publishing remains strong
Workspaces	Available	Improved	UI separated and architecture made more flexible	Better future editorial workflows
Navigation	Experimental development began before 11.3	Stable from 11.3; enabled in Standard in 11.4	Major admin UX milestone	Better administration on complex sites
HTMX	Not native in Drupal 10 core	Native from 11.3	Core-level HTMX integration	Interactive UX with less custom JS in suitable cases
SDC	Introduced before/around Drupal 11 transition	Expanded; native variants in 11.2	Component model matured	Better design-system development
Recipes	Early/experimental availability around Drupal 10.3/11.0	Substantially improved	Inputs, config actions, dependency handling and speed improved	Repeatable site features
OOP hooks	Procedural model dominant	OOP hooks introduced in 11.1 and expanded later	Modern PHP development model	Cleaner modules/themes
Content export	Contrib solutions commonly used	Native CLI export from 11.3	Core can export entities/dependencies	Better reusable content workflows
Asset compression	Aggregation/gzip workflows	Brotli support in 11.4	15–25% better compression than gzip in Drupal’s cited comparison	Potentially smaller transfers
Cache architecture	Mature	Multiple lookup/query optimizations	11.2–11.4 progressively improve cache efficiency	Better scalability
CLI	Core scripts + commonly Drush	Experimental extensible `dr` CLI added in 11.4	Native CLI direction emerging	Long-term developer tooling improvement
Password hashing	Existing secure hashing	Configurable hashing; Argon2id option in 11.4	Stronger algorithm available	Security modernization
Theme hooks	Primarily traditional files/procedural patterns	OOP theme hooks from 11.3	Modern theme architecture	Cleaner custom themes
Accessibility	Strong core commitment	Continues to receive improvements	Evolution rather than reset	Important for public-sector sites
Multilingual	Mature	Mature plus faster translation handling in 11.4	Translation processing modernized	Especially useful on large multilingual sites
Upgrade future	EOL Dec. 2026	Drupal 11.5 LTS planned alongside Drupal 12	Longer supported route	Better strategic platform choice

Drupal.org’s current requirements specify MySQL 8.0+, MariaDB 10.6+, PostgreSQL 16+ and SQLite 3.45+ for Drupal 11, versus lower minimums for Drupal 10. Drupal 11 requires PHP 8.3 as its baseline, while Drupal 11.3 added PHP 8.5 support.

Drupal 11 Release Timeline

Drupal Version	Release	Major New Features	Developer Impact	Editor/User Impact
Drupal 11.0	Aug. 2, 2024	Cleaned deprecated code, newer dependency/platform baseline	Symfony 7, PHP 8.3, removed deprecated APIs	Mostly continuity with 10.3
Drupal 11.1	Dec. 16, 2024	OOP hooks, Recipe improvements, icon API, cache improvements	Modern hook classes	Better defaults and Workspaces flexibility
Drupal 11.2	Jun. 19, 2025	JSON Schema, SDC variants, AVIF, caching improvements	Better APIs/testing/component development	Faster installation and Navigation improvements
Drupal 11.3	Dec. 17, 2025	HTMX, stable Navigation, content export, theme OOP hooks	Major frontend/backend improvements	Better admin navigation and CKEditor
Drupal 11.4	Jul. 1, 2026	Major DB/cache optimization, Brotli, CLI, Argon2id	Faster runtime and modern tooling	Faster sites and fullscreen editing

Drupal 11.0

Release date: August 2, 2024.

Drupal 11.0 was primarily a modernization release rather than a completely new CMS.

The most important changes were:

PHP 8.3 minimum;
Symfony 7;
newer dependency requirements;
removal of deprecated Drupal APIs;
removal of deprecated modules/themes;
higher database minimums;
updated Composer/platform requirements.

Drupal.org specifically explained that Drupal 10.3 and Drupal 11.0 had essentially the same public APIs and features except for limited edge cases.

This is an important SEO and technical distinction: Recipes and Single Directory Components should not simply be described as functionality that never existed in Drupal 10. They were part of the transition-era innovation and Drupal 11 became the platform on which they continued developing.

For developers, the main migration concern was deprecated custom code and dependency compatibility.

Drupal 11.1

Release date: December 16, 2024.

Drupal 11.1 was the first feature release where Drupal 11 began clearly moving beyond Drupal 10’s feature track.

Major improvements included:

Object-oriented hooks. Hooks could now be implemented using classes and PHP attributes. Instead of relying exclusively on globally named procedural functions, developers could organize hook implementations in modern PHP classes.

Recipe improvements. Recipes gained user input support and more configuration actions, including actions for blocks and Layout Builder.

Icon management API. Modules and themes gained a dedicated mechanism for defining icon packs.

Workspaces restructuring. Workspaces UI functionality was separated into the Workspaces UI module, allowing alternative user interfaces.

Render caching for forms. Forms could opt into render caching.

Better CSS/JS caching. Asset aggregation became less sensitive to library ordering, reducing unnecessary variations in aggregate files and potentially improving browser/CDN cache hit rates.

Drupal 11.1 also added full PHP 8.4 support.

Drupal 11.2

Release date: June 19, 2025.

Drupal 11.2 delivered important developer, API and performance changes.

Faster installation. Drupal.org measured site and extension installation at roughly three to four times faster than Drupal 11.1 in its demonstrated scenarios. This resulted from container-rebuild and installer optimizations.

OOP hooks became much more complete. APIs that previously still required .module implementations gained object-oriented alternatives.

JSON Schema generation. Drupal core could generate JSON Schemas for content entities, making it easier for API clients to understand expected data structures.

This is particularly useful for decoupled applications, typed API clients and validation tooling.

Single Directory Component variants. SDC gained native variants, making design-system components easier to model.

AVIF support. Drupal’s image toolkit gained AVIF capability with WebP fallback where AVIF conversion is unavailable.

Lower default CSS weight. Drupal.org reported reducing default core CSS loaded on every page from approximately 7 KB to about 1 KB.

Cache efficiency. Placeholder processing and cache-tag invalidation were optimized, reducing cache dependencies, cache lookups and round trips to persistent cache backends.

Drupal 11.2 also removed the old UI-based extension update mechanism that was not Composer-aware. Composer became the expected safe mechanism for managing extension code.

Drupal 11.3

Release date: December 17, 2025.

Drupal 11.3 was one of the most consequential Drupal 11 feature releases.

It introduced:

native HTMX integration;
stable Navigation;
major database/cache optimizations;
better CKEditor linking and lists;
native content export;
object-oriented hooks for themes;
PHP 8.5 support;
an experimental MySQLi database driver.

Drupal.org’s automated tests reported significantly fewer database/cache operations, while its release announcement described the ability to serve approximately 26–33% more requests with the same database load in tested scenarios. This should be treated as Drupal’s test result, not a guaranteed production benchmark.

Drupal 11.4

Release date: July 1, 2026.

The latest feature series takes Drupal 11’s optimization work considerably further. Drupal 11.4.5, released August 6, is the latest stable patch release as of this article’s verification date.

Drupal 11.4 adds:

approximately half as many database queries as 11.3 across Drupal’s tested request types;
just over one-third of Drupal 11.0/10.6 database and cache lookups on a completely cold cache in Drupal’s comparison;
more efficient entity listing queries;
faster Recipes;
dramatically faster translation handling;
Brotli CSS/JS aggregation;
a native experimental dr CLI;
configurable password hashing with Argon2id;
PHP attributes for controller routes;
further OOP conversion of theme/module code;
Symfony Runtime integration;
fullscreen CKEditor editing;
experimental Gin-based Default Admin theme.

Drupal 10 vs Drupal 11: Detailed Feature Comparison

The key architectural difference is not that Drupal 11 replaced Drupal’s established systems. JSON:API, REST, Views, Media, Layout Builder, Content Moderation, multilingual APIs and configuration management remain recognizable.

Instead, Drupal 11 progressively modernizes how those systems are built and executed.

PHP, Symfony and Twig

Drupal 11 raises the minimum PHP baseline to PHP 8.3 and moves from Drupal 10’s Symfony 6 generation to Symfony 7. Both Drupal 10 and Drupal 11 use Twig 3.x.

Therefore, Symfony compatibility is a meaningful custom-code consideration, while Twig does not undergo the same major-version jump.

Frontend Architecture

Single Directory Components continue Drupal’s shift toward reusable component-driven frontend architecture.

Drupal 11.2 added native SDC variants, and Drupal 11.3’s HTMX integration provides another option for interactive interfaces that do not require large amounts of application-specific JavaScript.

APIs, JSON:API and REST

JSON:API and REST remain core technologies rather than Drupal 11 replacements.

Drupal 11.2’s JSON Schema generation improves machine-readable entity definitions. Drupal 11.4 also reduces joins for entity listing queries, which Drupal.org says should particularly benefit JSON:API sites.

Configuration and Recipes

Traditional configuration management remains essential for deploying site configuration.

Recipes solve a different problem: packaging and applying reusable site capabilities. By Drupal 11.1, Recipes could accept inputs and perform more configuration actions; 11.2 improved dependency handling; and 11.4 made recipe-based installation significantly faster.

Drupal 11 Performance Improvements

Drupal 11 Performance: Is It Really Faster Than Drupal 10?

In many core-level workloads, Drupal 11.3 and especially Drupal 11.4 contain measurable optimizations that Drupal 10.6 does not have.

That does not mean every Drupal 11 site will automatically be faster than every Drupal 10 site.

Database Queries and Cache Lookups

Drupal 11.3 reduced database and cache operations by combining operations in areas such as path aliases, entity loading and rendering.

Drupal 11.4 continued this work.

Drupal.org reports that 11.4 reduces database queries by roughly half compared with 11.3 across a range of tested requests. On completely cold caches, it uses just over one-third of the database/cache lookups of Drupal 11.0 or Drupal 10.6 for equivalent requests.

Asset Compression

Drupal 11.4 supports Brotli compression for aggregated JavaScript and CSS when the PHP Brotli extension is available.

Drupal.org states that Brotli typically produces 15–25% better compression ratios than gzip in this context.

Translation Handling

Large multilingual websites may see particularly useful backend improvements.

Drupal.org tested a site containing 66 projects and 38 languages and found checking translation updates to be 87% faster in Drupal 11.4 than 11.3. That is a specific test scenario, not a promise that every multilingual site will improve by 87%.

Backend and Frontend Performance

Other improvements accumulated across the Drupal 11 series:

improved asset aggregation;
render caching for forms;
fewer cache-tag lookups;
smaller dynamic-page-cache dependencies;
lighter default core CSS;
HTMX usage in BigPipe;
faster entity loading;
more efficient entity listings;
faster Recipe installation.

Real-World Performance

A Drupal version is only one part of performance.

Actual response time and throughput also depend on:

PHP configuration;
database tuning;
Redis/Memcached usage;
CDN configuration;
contributed modules;
custom modules;
theme architecture;
external APIs;
cache-hit ratio;
authenticated versus anonymous traffic;
content complexity;
infrastructure;
traffic patterns.

So Drupal 11.4 provides a better-performing core foundation, but it cannot compensate for every application-level bottleneck.

Drupal 11 Security Improvements

Drupal 11 improves the security baseline primarily by maintaining a modern dependency stack and continuing active security support.

Modern Dependencies

Drupal 11 uses PHP 8.3+ and Symfony 7 rather than Drupal 10’s older baseline.

Running maintained dependencies matters because unsupported upstream software eventually stops receiving security fixes.

Faster Dependency Security Updates

Drupal 11.4 changed drupal/core-recommended constraints so selected dependencies such as Guzzle, Twig and Symfony Polyfills are no longer pinned as tightly to minor versions.

The purpose is to allow important dependency security fixes to be installed without necessarily waiting for another Drupal core release. Drupal.org also warns that teams should perform appropriate QA because a newly updated dependency may not yet have gone through Drupal core’s normal release testing.

Argon2id Password Hashing

Drupal 11.4 makes the password hashing algorithm configurable and adds Argon2id as an option.

Drupal 12 is expected to make Argon2id the default. Drupal 11.4 sites can adopt it earlier; existing user passwords are rehashed as users subsequently log in.

This is security hardening—not a claim that Drupal 11 is “100% secure.”

A secure Drupal deployment still requires timely updates, safe hosting, correct permissions, secure custom code, dependency monitoring and operational security.

Drupal 11.3: HTMX, Navigation and Other Major Improvements

What Does HTMX Mean for Drupal?

HTMX allows developers to trigger server requests and update portions of a page using HTML attributes instead of building every interaction with substantial custom JavaScript.

Drupal 11.3 integrates HTMX natively. Drupal.org says its implementation can support rich interfaces with up to 71% less JavaScript in relevant scenarios. Again, that figure applies to Drupal’s demonstrated use cases rather than every website.

Imagine a “Load more” interface.

A traditional implementation might require custom JavaScript to:

listen for a click;
make an AJAX/fetch request;
parse the response;
find the target DOM element;
inject new markup;
handle state/errors.

HTMX can move much of this behavior into declarative HTML while Drupal continues generating the server-side response.

It does not mean React, Vue or custom JavaScript are obsolete. Complex client-side applications may still require them. HTMX gives Drupal developers a lighter alternative for many server-driven interactions.

Stable Navigation

Drupal’s modern Navigation module became stable in Drupal 11.3.

It is designed as a more modern administrative navigation experience than the legacy Toolbar and is especially useful on sites with complex administration structures.

Drupal 11.4 subsequently enabled Navigation in the Standard administrative experience, while Toolbar remains available but is planned for removal in Drupal 12.

Better CKEditor

Drupal 11.3 added native entity-reference-based content linking in CKEditor, allowing editors to find site content through autocomplete/dropdown interfaces. List formatting options were also improved.

Native Content Export

Drupal 11.3 added a core command for exporting content entities, including referenced dependencies where requested.

This is useful for reusable demo content, recipes, testing and moving known content structures between environments.

OOP Hooks for Themes

Themes gained support for the same #[Hook()]-style architecture being adopted by modules.

For custom theme developers, this enables better-organized, class-based PHP instead of keeping every customization in traditional procedural theme files.

Drupal 11.4: What’s New in the Latest Feature Release

Drupal 11.4 is particularly relevant in 2026 because it is the current feature series.

Fewer Database and Cache Lookups

Entity-field loading has been optimized, cutting database queries significantly compared with Drupal 11.3.

Entity listing queries also use fewer table joins, which can help API-heavy sites.

Faster Recipes

Drupal.org reports recipe-based installation becoming approximately twice as fast in 11.4.

Faster Translation Processing

Locale APIs have undergone substantial modernization, including migration away from older .inc-based code toward object-oriented APIs.

Brotli Asset Compression

Aggregated CSS and JavaScript can use Brotli where ext-brotli is available, potentially transferring smaller files than gzip.

Native Drupal CLI

Drupal 11.4 introduces an experimental extensible CLI available through:

./vendor/bin/dr

Drupal.org describes this as the beginning of a transitional path where capabilities traditionally associated with Drush may gradually move into Drupal core. Drush is not suddenly obsolete, and the new CLI remains experimental.

Password Hashing

Argon2id is now available as a configurable password hashing algorithm.

Fullscreen CKEditor

CKEditor text formats can enable a FullScreen plugin, allowing editors to work with the editor across the browser viewport.

PHP Attributes

Developers can define controller routes using Symfony’s Route PHP attribute and can use Drupal’s Bundle attribute for bundle classes in appropriate cases.

Drupal 11 Developer Experience

For developers, the biggest long-term Drupal 11 improvements are architectural.

Object-oriented hooks reduce reliance on globally named procedural functions.

Single Directory Components provide a more self-contained frontend component structure.

JSON Schema generation helps decoupled developers understand entity payloads.

Native HTMX gives developers a lightweight option for server-driven interactivity.

The experimental core CLI begins moving command-line capabilities closer to Drupal itself.

PHP attributes reduce YAML/procedural boilerplate in selected APIs.

PHPUnit 11 support modernizes testing.

Symfony 7 aligns Drupal with the contemporary PHP ecosystem.

These improvements do not remove the need to understand Drupal’s entity, render, cache, service-container and configuration systems. They make those systems easier to integrate with modern PHP development practices.

Drupal 11 for Content Editors

Content editors benefit from Drupal 11 even though many of the biggest changes happen below the UI.

Notable improvements include:

stable modern Navigation;
better internal linking in CKEditor;
better list formatting;
fullscreen CKEditor in 11.4;
improved publication-status permissions;
continued Workspaces development;
faster administrative operations;
better default administration direction.

Drupal 11.4 also includes Gin in core as the experimental Default Admin theme, including dark mode. It is not yet the stable default replacement for Claro, so it should be described as experimental rather than as Drupal 11.4’s default production admin theme.

Drupal 11 for Enterprise Websites

Drupal 11 is particularly relevant to enterprise, government and high-traffic deployments because its improvements target problems that become more noticeable at scale.

These include:

fewer database queries;
fewer persistent cache operations;
stronger API tooling;
Workspaces;
Content Moderation;
multilingual capabilities;
modern dependency support;
component-based frontend architecture;
scalable JSON:API;
improved administration;
predictable Composer deployments.

Organizations should still validate every upgrade against their own architecture.

A 50-page corporate site and a multilingual government platform with millions of entities do not have the same upgrade risk.

Drupal 10 End of Life: What Happens After December 2026?

Drupal.org states that Drupal 10 reaches end of life on December 9, 2026. No new Drupal 10 releases will be made after that date.

Drupal 10.6.0 is the final Drupal 10 minor release, with the 10.6.x line serving as the final maintenance branch.

After EOL, organizations should not expect normal Drupal core security releases for Drupal 10.

For a public-facing production website, particularly an enterprise, government, healthcare, financial or high-traffic platform, remaining on an unsupported major version creates unnecessary operational and security risk.

Drupal 11.4.x receives security support until June 2027, while Drupal 11.3.x continues receiving security support until December 2026. Drupal 11 itself is planned to remain supported until Drupal 13, and Drupal.org says Drupal 11.5 is planned as an LTS release alongside Drupal 12 in December 2026, with Drupal 11 support expected through the end of 2028.

Should You Upgrade From Drupal 10 to Drupal 11?

For most actively maintained Drupal 10 websites, yes—2026 is the appropriate time to move to Drupal 11, assuming contributed and custom code is compatible.

Small Websites

Upgrade rather than carrying Drupal 10 past EOL. For simple sites with common maintained modules, the migration may be relatively straightforward.

Corporate Websites

Plan the upgrade during 2026 rather than treating December as the project start date. Allow time for QA, integrations and editorial testing.

Enterprise and Government Websites

Begin or complete the migration well before EOL. These environments typically require security review, accessibility testing, performance testing, procurement/change windows and formal rollback plans.

High-Traffic Websites

Drupal 11.3/11.4 performance improvements are attractive, but benchmark your actual application. Test anonymous and authenticated traffic, cache behavior, API traffic and database load.

Sites With Many Contributed Modules

Compatibility is the main concern. Verify every required project before changing core.

Sites With Custom Modules

Audit deprecated APIs and Symfony/PHP compatibility. Custom code that was already clean on late Drupal 10 releases is generally easier to move.

Sites With Custom Themes

Check Twig, JavaScript dependencies, custom preprocess logic and theme hooks. Consider gradually adopting SDC and OOP theme hooks rather than attempting an unnecessary full rewrite during the core upgrade.

Drupal 10 to Drupal 11 Upgrade Checklist

Update Drupal 10 to the latest supported 10.6.x patch release.
Confirm the server meets Drupal 11 requirements.
Upgrade PHP to a supported Drupal 11 version.
Confirm MySQL/MariaDB/PostgreSQL/SQLite compatibility.
Update Composer and review dependency constraints.
Audit contributed modules for Drupal 11 compatibility.
Audit contributed themes.
Scan custom modules for deprecated Drupal APIs.
Review custom code for Symfony 7 compatibility.
Review Twig templates and custom theme logic.
Check custom JavaScript and frontend dependencies.
Review removed core modules/themes and replacements.
Take verified database and file backups.
Create a production-like staging environment.
Perform the Composer upgrade on staging first.
Run database updates.
Rebuild caches.
Export and review configuration.
Run automated PHPUnit/functional tests where available.
Test login, forms, search, Views and permissions.
Test editorial workflows and Content Moderation.
Test multilingual functionality.
Test APIs and integrations.
Run accessibility checks.
Benchmark performance before and after.
Verify cron, queues and scheduled jobs.
Create and test a rollback procedure.
Schedule production deployment with monitoring.

Drupal.org notes that sites on Drupal 10.6 upgrading to Drupal 11 should target Drupal 11.3.0 or higher, making the current 11.4 series the logical destination in August 2026 rather than upgrading through obsolete Drupal 11.0-era releases.

Frequently Asked Questions

1. Is Drupal 11 better than Drupal 10?

For new development and long-term maintenance, yes. Drupal 11 has the longer support horizon, modern dependencies and feature development that Drupal 10 no longer receives. Existing Drupal 10 sites should still upgrade through a tested migration rather than changing versions without compatibility checks.

2. What is the main difference between Drupal 10 and Drupal 11?

Drupal 11 removes deprecated Drupal 10 code, raises platform requirements, uses Symfony 7 and continues receiving new feature development. Drupal 11.3 and 11.4 also contain substantial performance, HTMX, Navigation, CLI and developer-experience improvements unavailable in Drupal 10.6.

3. Is Drupal 10 still supported in 2026?

Yes, but only temporarily. Drupal 10.6.x is the final supported Drupal 10 line and Drupal 10 reaches EOL on December 9, 2026.

4. When does Drupal 10 reach end of life?

December 9, 2026. Drupal.org says no new Drupal 10 releases will be made after that date.

5. What is the latest Drupal version as of August 18, 2026?

The current Drupal 11 feature series is 11.4.x, and the latest stable patch release is Drupal 11.4.5, released August 6, 2026.

6. What is new in Drupal 11.4?

Major additions include further database/cache optimization, Brotli CSS/JS compression, faster translation processing, faster Recipes, the experimental native dr CLI, configurable Argon2id hashing, fullscreen CKEditor and expanded PHP-attribute/OOP capabilities.

7. Is Drupal 11 faster than Drupal 10?

Drupal 11.3 and 11.4 contain significant core performance optimizations. Drupal.org reports that Drupal 11.4 uses just over one-third of Drupal 11.0/10.6 database and cache lookups on completely cold-cache requests in its comparison. Real production performance still depends heavily on the individual site.

8. Are Drupal 10 modules compatible with Drupal 11?

Many maintained modules support both, but compatibility is not automatic. Modules relying on removed deprecated APIs or incompatible Composer dependencies may require updates.

Check every critical contributed and custom module before upgrading.

9. Can I upgrade Drupal 10 directly to Drupal 11?

Yes, when prerequisites are satisfied. For a current Drupal 10 site, first update to the latest supported Drupal 10.6.x release and resolve compatibility/deprecation problems. Drupal.org specifically states that sites on 10.6 upgrading to Drupal 11 must upgrade to 11.3.0 or higher.

10. Should I upgrade to Drupal 11 in 2026?

For most maintained production sites, yes. With Drupal 10 EOL approaching in December, delaying the planning phase until the deadline increases operational risk.

11. Does Drupal 11 require PHP 8.3?

Drupal 11’s minimum baseline is PHP 8.3. Drupal 11.3 additionally supports PHP 8.5. Always check the exact Drupal minor and upstream PHP support status before choosing your production runtime.

12. Does Drupal 11 use Symfony 7?

Yes. Drupal 10 uses the Symfony 6 generation while Drupal 11 uses Symfony 7.

13. Does Drupal 11 use a newer Twig major version?

No. Both Drupal 10.x and Drupal 11.x use Twig 3.x.

14. Is HTMX available in Drupal 11?

Native Drupal core HTMX integration arrived in Drupal 11.3.0. It provides a lighter approach to many server-driven interactive experiences and is also used by Drupal’s BigPipe implementation.

15. How long is Drupal 11.4 supported?

Drupal 11.4.x is scheduled to receive security support until June 2027. Drupal 11.3.x continues receiving security support until December 2026.

Final Verdict

The Drupal 10 vs Drupal 11 decision in 2026 is increasingly straightforward.

Drupal 10.6 remains a supported and viable maintenance release for organizations that need additional migration time, but it has a fixed endpoint: December 9, 2026.

Drupal 11.4 is the better destination for active development.

The strongest reasons are not simply the “Drupal 11” label. They are the improvements accumulated after Drupal 11.0: object-oriented hooks, improved Recipes, better caching, JSON Schema generation, SDC variants, AVIF support, native HTMX, stable Navigation, content export, dramatically reduced database/cache work, Brotli compression, modernized translation handling, Argon2id support and an emerging native CLI.

For organizations already on a well-maintained Drupal 10.6 site, this is also not the kind of major-version migration Drupal users may remember from much older generations. Drupal deliberately created a forward-compatible path through late Drupal 10 releases.

The right strategy is therefore not to panic about Drupal 10 EOL—but neither is it to wait until December.

Audit your dependencies, remove deprecated custom code, validate your infrastructure, upgrade on staging, test thoroughly and move to a supported Drupal 11 release while there is still comfortable time to resolve problems.

Information verified: August 18, 2026.

Sources and References

The following official Drupal.org resources were used as the primary sources for version, lifecycle, requirements and feature information:

Editorial note: Version-specific statements above are intentionally attributed to the release where Drupal.org documents them. Features already present in Drupal 10.3/10.4 have not been relabeled as Drupal-11-exclusive merely because they were highlighted around the Drupal 11 launch.