Drupal's CMS Market Share Falls 82% Since 2015

Measured against websites with an identifiable content management system, Drupal's market share fell from 5.1% in January 2015 to 0.9% by 11 November 2026, according to W3Techs. That represents an approximately 82% relative decline over eleven years. The figures establish a sustained loss of market share, but not an equivalent reduction in Drupal installations, customers or organisations.

The wider CMS industry has not followed the same trajectory. Research from HTTP Archive shows that CMS adoption has increased even as established platforms such as Drupal and Joomla have lost ground. Meanwhile, artificial intelligence is changing how websites are built, raising questions about the value of traditional content management systems. Drupal's position brings these developments together: a platform with a shrinking share of the wider web, continued use in complex environments and a strategy intended to restore adoption.

The CMS Market Is Changing, Not Disappearing

AI coding agents, static-site frameworks and hosted website builders have made it easier to create websites without a conventional CMS. Yet the 2025 HTTP Archive Web Almanac found that identifiable CMS adoption increased from 42% of sampled desktop pages in 2021 to 55% in 2025. Mobile adoption rose from 43% to 54% over the same period. The findings challenge the suggestion that content management systems are disappearing from the web.

Instead, the market is becoming more fragmented. According to W3Techs, Joomla's share of websites with a detected CMS fell from 8.6% in January 2015 to 1.6% in November 2026. WordPress moved from 60.7% to 58.0% over the same period, although its share rose during the intervening years. Shopify increased from 0.7% to 7.9%, while Wix grew from 0.3% to 6.2%. These changes show the expansion of managed commerce and website-building platforms, but do not establish that customers leaving older systems migrated directly to them.

AI Is Changing What Developers Need From a CMS

The changing economics of website development became visible in December 2025 when software engineer Lee Robinson described moving Cursor's website from a headless CMS to Markdown and source code. Robinson reported completing the migration in three days using AI coding agents, compared with an initial estimate of one to two weeks. AI model usage cost approximately $260, excluding engineering time and other expenses. For his team, the change reduced the complexity of managing website content through a separate system.

Knut Melvær, Principal Developer Marketing Manager at Sanity, the platform Cursor had used, challenged the broader implications. He acknowledged the complexity of headless CMS integrations but argued that replacing a CMS with GitHub and custom tools does not eliminate responsibilities such as permissions, asset management and editorial workflows. Their disagreement illustrates a larger industry question: when AI makes website creation easier, which content-management functions still require a dedicated platform?

Other industry figures are considering the same question. In the published abstract of research dated 12 May 2026, Gartner analysts Irina Guseva and Mike Lowndes argued that agent-driven systems are challenging traditional web content management and headless architectures. WordPress co-founder Matt Mullenweg argued in February 2026 that AI could make basic functionality easier to recreate while leaving reliability, integrations and long-term maintenance valuable. These are interpretations of where the industry is heading, not evidence that traditional CMS platforms have already become unnecessary.

What Drupal's Market Share Actually Tells Us

Drupal's decline predates the recent expansion of AI coding tools. Its share of the identified CMS market fell from 5.1% in January 2015 to 3.0% in January 2020, 1.3% in January 2025 and 0.9% in November 2026. Its share of all websites surveyed by W3Techs also declined, from 2.0% in January 2015 to 0.6% in November 2026. Both measures show a long-term downward trend, although they use different denominators.

Drupal remains considerably more prominent among highly visited websites than its overall market share suggests. W3Techs' traffic-ranking data shows that its presence varies across website segments rather than increasing consistently with website popularity. The distribution suggests different patterns of adoption across traffic levels, although this snapshot cannot establish whether Drupal's position among major websites is improving over time.

Legacy installations add another complication. Drupal 7 reached end of life on 5 January 2025, but retiring an older website does not necessarily mean abandoning Drupal. Organisations may upgrade, migrate to another CMS, consolidate several sites or discontinue them. Aggregate market-share statistics cannot distinguish these outcomes.

Drupal.org's usage statistics offer a different perspective. Installations reporting Drupal 8 or newer increased from 469,925 in the week beginning 2 November 2025 to 527,443 in the week beginning 1 November 2026, a rise of approximately 12.2%. These figures depend on installations contacting Drupal.org's update infrastructure and can include development environments while excluding sites that do not report usage. They are not a count of new production websites, and weekly totals can fluctuate substantially.

Drupal's external market share can therefore decline while reported installations of newer versions increase. The figures measure different populations and should not be treated as contradictory. This distinction is central to understanding the extent of Drupal's decline and the limitations of the available evidence.

Leadership and Maintainers Confront Commercial Pressure

The Drupal Association has acknowledged concerns beyond website counts. In remarks published on 28 October 2026, interim CEO Tiffany Farriss said the Drupal Business Survey showed declining average agency deal sizes and negative sales pipeline expectations for the first time in the survey's history. She also identified weak visibility among potential customers, arguing that Drupal performs well when organisations include it in their evaluations. That assessment reflects the Association's interpretation of its survey, not an independently established explanation for the market-share decline.

Drupal founder Dries Buytaert raised a similar concern in his 7 October 2026 account of the State of Drupal. He argued that the platform's capabilities had advanced faster than its public reputation and described an AI agent evaluating Drupal without recognising newer offerings such as Drupal CMS and Site Templates. The example illustrates a possible discovery problem but does not establish that inaccurate AI recommendations are widespread.

Financial disclosures reveal additional pressure. The Association's 2025 audited financial overview reported a combined operating shortfall of approximately $1.15 million across 2024 and 2025, following a restatement of earlier accounts to correct the timing of membership revenue recognition. Unrestricted cash reserves had fallen by around 60% since the end of 2022 to approximately $960,000. The Association said it remained a going concern and that its services were not in immediate danger, while acknowledging the need for a more sustainable funding model.

Maintainers face related operational pressures. Drupal core release manager Jess (xjm) is among those seeking additional sponsored contribution time, according to Drupal's public sponsorship information. The Drupal AI Security Initiative has also reported increased vulnerability-disclosure activity associated with AI-assisted discovery, while a 2 November 2026 advisory announced a reduction in the overlapping security-support window for standard core minor versions beginning in 2027. These developments demonstrate the demands of sustaining Drupal, although they cannot be attributed directly to declining adoption.

Farriss connected these concerns in her October remarks, emphasising that free software continues to depend on funded infrastructure, security coordination and the work of contributors.

Developers and Customers Are Making Different Choices

Community discussions reveal differing experiences of Drupal's market position. A 2026 discussion on r/drupal included concerns about employment opportunities, project complexity and the cost of maintaining Drupal expertise. Other participants described continuing institutional demand and improvements in newer development tools. These accounts reveal disagreements among users but cannot establish wider employment or adoption trends.

A 2026 Acquia-commissioned survey conducted by Coleman Parkes among 575 developers in the United States, United Kingdom and France provides broader context. Security ranked among the three most important CMS-selection criteria for 56% of respondents, followed by performance and scalability at 49% and AI readiness at 40%. The findings describe stated preferences rather than actual platform-switching behaviour, and the survey was commissioned by a company with commercial interests in Drupal. Nevertheless, they indicate that developers consider several factors beyond familiarity or reputation.

Customer migrations illustrate both sides of Drupal's position. The University of California, San Francisco migrated nearly 1,000 websites from Drupal 7 to Drupal 10 between spring 2025 and spring 2026. Arizona State University announced on 20 April 2026 that WordPress would no longer be an approved Web Services platform, identifying Webspark/Drupal and Acquia as its supported direction. The university's announcement described a policy and migration programme, not a completed migration of every affected website.

Other organisations have moved away. An Illustrate Digital case study describes Board International's migration from Drupal 7 to WordPress, citing developer dependence for routine content changes and difficulties with multilingual editorial workflows. The agency-authored account is not an independent comparative study, but it illustrates how editorial usability can influence CMS selection. Together, these examples show why organisations may reach different decisions about platforms serving complex content needs.

Can Drupal's Strategy Change the Trend?

Drupal's proposed response is outlined in its Drupal CMS product strategy, revised in June 2026. The project aims to improve agency and developer productivity through AI-assisted workflows, reusable Site Templates and simpler configuration. It also seeks to maintain Drupal's enterprise position while regaining mid-market projects with total budgets of approximately $30,000 to $120,000. The strategy targets June 2028 for achieving its broader objectives.

The technical direction separates Drupal Core as an extensible framework from Drupal CMS as a more immediately usable product. During The Case for Drupal CMS session at DrupalCon Rotterdam on 29 September 2026, Drupal CMS product lead Pamela Barone and Drupal core product manager Lauri Timmanee discussed how Recipes, Drupal Canvas and Site Templates could reduce the work required to launch websites. These changes address concerns about complexity, but improved capabilities do not automatically demonstrate growth in commercial adoption.

Early adoption signals remain difficult to interpret. Drupal.org recorded an increase in installations reporting Drupal CMS Helper from 2,103 in the week beginning 2 November 2025 to 8,038 in the week beginning 1 November 2026. The module can also be used outside Drupal CMS, and reporting installations cannot be equated with new production websites. The Association has explored privacy-conscious telemetry to improve its understanding of Drupal usage, but publicly available figures have not established how many new production customers Drupal CMS has attracted.

Buytaert has argued in his essay on AI and CMS unbundling that easier content creation increases the importance of governance, permissions and reliable content management in complex organisations. That interpretation aligns with Drupal's strategic emphasis on structured content and professional development. Whether those strengths will attract enough customers to reverse the decline remains an open question.

Drupal's shrinking market share, the Association's commercial pressures and its continued presence in complex web environments are not mutually exclusive findings. They describe different aspects of a platform adapting to changes in website development and software purchasing. The available evidence establishes the extent of Drupal's decline more clearly than it establishes the success of its response.