Is Joomla! dead? The rise and fall of Joomla!

At its January 2017 peak, Joomla! ran 3.4% of every website on the internet. Today it runs 1.2%. People have been writing the obituary since 2012 — so instead of another opinion, here are twenty years of data: W3Techs, Google Trends and BuiltWith, mapped against every major release from 1.0 to 6.x. The answer is more interesting than yes or no.

Peak share of all websites
3.4%
Jan 2017 · W3Techs
Share today
1.2%
Aug 2026 · W3Techs
Share of the CMS market
1.7%
was 11.0% in 2010 · W3Techs
Search interest vs 2009 peak
2/100
Aug 2026 · Google Trends

The whole arc in one line

Google search interest in “joomla”, worldwide, from the month the project was born to this month, indexed to its all-time peak. The peak is March 2009 — under Joomla! 1.5, before 2.5 or 3.0 ever shipped. Attention started leaving during the 1.6/1.7 whiplash of 2011, half a decade before actual usage peaked.

Yearly averages of monthly data. 2005 covers September–December; 2026 covers January–August.

Google search interest in Joomla!, 2005 to 2026Line chart of yearly average search interest, indexed to the March 2009 peak of 100. Interest rises from 18 in 2005 to 94 in 2009, then falls almost continuously to 2 by 2021 and stays there through 2026. Markers show each major Joomla! release.0255075100200520082011201420172020202320261.01.51.6 / 1.72.53.x4.x5.x6.0Mar 2009: all-time peak2005: 18.5 / 1002006: 47.8 / 1002007: 71.5 / 1002008: 82.7 / 1002009: 93.7 / 1002010: 86.3 / 1002011: 77 / 1002012: 58.4 / 1002013: 43.4 / 1002014: 29.3 / 1002015: 20.3 / 1002016: 13.9 / 1002017: 9.2 / 1002018: 5.8 / 1002019: 4.2 / 1002020: 3.2 / 1002021: 2 / 1002022: 2.3 / 1002023: 2 / 1002024: 1.9 / 1002025: 1.9 / 1002026: 2.3 / 100

What each release gained — and lost

The measure changes with the era, because the instruments do: W3Techs’ survey begins in 2011, so the first two releases are read through search interest (indexed to the 2009 peak = 100) and everything after through share of all websites. Each entry shows the reading when the release shipped and when it was superseded, on January-1 snapshots.

  1. 1.0Sep 2005 → Jan 2008Search interest 0 → 81

    The fork that worked

    Seventeen days after the entire Mambo core team walked out of Miro and formed Open Source Matters, Joomla! 1.0 shipped — a rebranded Mambo 4.5.2.3. The gamble held: the community followed the developers, not the trademark. Joomla! won Packt’s Open Source CMS Award in 2006 and its PHP category in 2007, and search interest went from zero to 81% of its eventual all-time peak before 1.5 even shipped.

  2. 1.5Jan 2008 → Jan 2011Interest 81 → 100 → 77

    The golden age

    The first real Joomla! — a new MVC framework, not Mambo’s bones. Under 1.5 Joomla! hit its all-time search-interest peak (March 2009) and became the default answer to “I need a serious site and WordPress is just a blog tool.” This is the release every later release gets measured against.

  3. 1.6 / 1.7Jan / Jul 2011 → Feb 2012Interest 77 → 58

    The whiplash

    Two majors in six months, each supported for barely seven. 1.6 landed three years after 1.5 with a breaking ACL rewrite; 1.7 followed in July on a new short-cycle policy. Extension developers had to chase three incompatible targets in one year, and agencies learned to wait. The first sustained interest decline starts exactly here — while WordPress 3.0 was consolidating. Installed share still inched up, 2.6% to 2.8%: bases move slower than sentiment.

  4. 2.5Jan 2012 → Dec 2014Share 2.8% → 3.2%

    The stabiliser

    The apology for 2011: a long-term-support release that gave site owners three quiet years, and Joomla! passed 30 million downloads in March 2012. Here the two curves split cleanly for the first time — share of all websites rose from 2.8% to 3.2% while search interest halved, 58 to 29. The sites kept coming; the conversation had already moved.

  5. 3.xSep 2012 → Aug 2023Share 3.2% → 3.4% → 2.2%

    The eleven-year release

    Bootstrap in core, mobile-first, and genuinely good — Joomla!’s share of all websites climbed to its all-time measured peak of 3.4% in January 2017, holding the #2 CMS spot ahead of Drupal as late as 2020. Then the platform went quiet. Joomla! 4 was promised “before the end of 2018” and arrived in August 2021. In that gap Shopify passed Joomla! (2020), then Wix and Squarespace (2021). The web didn’t leave Joomla! for another CMS era — it left during a release that outlived its own roadmap by three years.

  6. 4.xAug 2021 → Oct 2025Share 2.2% → 1.7%

    Three years late

    Shipped on Joomla!’s 16th birthday, the same day as 3.10 — a modern core, accessible backend, web services API. Technically the release 3.x had needed since 2018; commercially it arrived after the audience had made other plans, and migration friction from 3.x did the rest. Share fell from 2.2% at the start of its launch year to 1.7% by the January after 5.0 took over.

  7. 5.xOct 2023 → currentShare 1.7% → 1.6%

    Cadence restored

    Exactly on schedule, two years after 4.0 — the first major release in a decade to land on the date the roadmap named. Dark-mode admin, modern PHP, painless upgrade from 4. The curve nearly flattens here: one tenth of a point across its two Januaries as flagship, against half a point lost across 4.x’s. Predictability wins back trust slower than it was lost — but the bleeding slowed.

  8. 6.0Oct 2025 → currentShare 1.3% → 1.2%

    On time, again

    Released 14 October 2025, again to the day, alongside 5.4. 6.1 followed on schedule in April 2026; 6.2 is dated for October. The headline share keeps drifting — 1.3% to 1.2% this year — but 7.3% of all Joomla! installs are already on 6.x within ten months, and BuiltWith ranked Joomla! the #2 fastest-growing open-source CMS of the last 90 days. Two release trains have now run on time. That has not been true since 2012.

Share of the actual web

W3Techs surveys the top ten million websites every January 1. For a full decade Joomla! ran between 2.6% and 3.4% of the entire web and held second place among all CMSes — still #2 as late as 2020. Then three platforms went past in eighteen months: Shopify during 2020, Wix and Squarespace during 2021 — precisely the years the web spent waiting for Joomla! 4, promised for 2018 and shipped in August 2021.

The all-time peak is 3.4% of all websites in January 2017. The August 2026 reading is 1.2%. Note the shape: the drop is not a slide from 2011 — it is a plateau, a four-year wait, and a step down.

Joomla! share of all websites, W3Techs, 2015 to 2026Line chart. Joomla! runs 3.3 to 3.4 percent of all websites from 2015 to 2017, then declines every year to 1.2 percent by August 2026. Markers show the Joomla! 4.0, 5.0 and 6.0 releases and the points where Shopify, Wix and Squarespace overtook Joomla!0%1%2%3%4%201120132015201720192021202320251.6 / 1.72.53.x4.x5.x6.0Jan 2017: 3.4% — the peakShopify passesWix & Squarespace passJan 2011: 2.6% of all websitesJan 2012: 2.8% of all websitesJan 2013: 2.8% of all websitesJan 2014: 3.2% of all websitesJan 2015: 3.3% of all websitesJan 2016: 3.3% of all websitesJan 2017: 3.4% of all websitesJan 2018: 3.2% of all websitesJan 2019: 3% of all websitesJan 2020: 2.6% of all websitesJan 2021: 2.2% of all websitesJan 2022: 1.7% of all websitesJan 2023: 1.8% of all websitesJan 2024: 1.7% of all websitesJan 2025: 1.6% of all websitesJan 2026: 1.3% of all websitesAug 2026: 1.2% of all websites

The front door, against WordPress’s

Estimated visit counts to joomla.org are too volatile to chart honestly, so we measured its search footprint instead: the keywords joomla.org ranks for in Google, normalised against wordpress.org in the same DataForSEO database. In late 2020, joomla.org ranked for 11 keywords for every 100 wordpress.org ranked for. The 2026 reading is 3.7.

Note the middle of the curve: a real relative recovery through 2024 — the Joomla! 5 era — before search visibility compressed sharply for both projects’ sites in 2025–26 and Joomla!’s share of the shrinking pie fell to its lowest reading.

joomla.org search footprint relative to wordpress.org, 2020 to 2026Line chart of keywords joomla.org ranks for per 100 keywords wordpress.org ranks for in Google, yearly averages: 11 in late 2020, falling to 4.4 by 2022, recovering to 8 in 2024, then declining to 3.7 in 2026. Markers show the Joomla! 4.0, 5.0 and 6.0 releases.048122021202220232024202520264.x5.x6.02020 (Oct–Dec): 11 keywords per 100 of WordPress's2021 (full year): 6.8 keywords per 100 of WordPress's2022 (full year): 4.4 keywords per 100 of WordPress's2023 (full year): 4.8 keywords per 100 of WordPress's2024 (full year): 8 keywords per 100 of WordPress's2025 (full year): 5.4 keywords per 100 of WordPress's2026 (Jan–Aug): 3.7 keywords per 100 of WordPress's

What’s actually left

Percentages hide the absolute scale, so here is BuiltWith’s live count. For every Joomla! site running today, roughly 4.8 sites ran Joomla! once and left. WordPress runs about fifty times as many live sites; inside the web’s top 10,000 properties the gap narrows to twenty-fold — Joomla!’s remaining base skews institutional.

The sharper problem is what the survivors run: 53.1% are still on Joomla! 3, unsupported since August 2023 — and with 4.x past its October 2025 cutoff, 72.1% of the live Joomla! web receives no security updates at all. Against that, the counter-signal: BuiltWith ranked Joomla! the second fastest-growing open-source CMS of the last 90 days, with 8,796 new sites in 30 days. The base is smaller. It is not dying — it is consolidating around people who chose it on purpose.

Live Joomla! websites
755,424
Sites that used Joomla! historically
3,598,905
In the top 1M websites
7,855
In the top 10k websites
93
New sites in 30 days
8,796

What the surviving sites run

Joomla! installs by major version, August 2026Stacked bar. Joomla! 3 accounts for 53.1 percent of installs, Joomla! 5 for 20.7, Joomla! 4 for 8.8, Joomla! 6 for 7.3, Joomla! 2 for 5.9 and Joomla! 1 for 4.3. Versions 1 through 4 — 72.1 percent of installs — are out of security support.Joomla! 1.x: 4.3% of installs1.x4.3%Joomla! 2.x: 5.9% of installs2.x5.9%Joomla! 3.x: 53.1% of installs3.x53.1%Joomla! 4.x: 8.8% of installs4.x8.8%Joomla! 5.x: 20.7% of installs5.x20.7%Joomla! 6.x: 7.3% of installs6.x7.3%Out of security support — 72.1%Supported — 28.0%

Share of Joomla! installs by major version · W3Techs, 19 August 2026

Why it actually declined

Everything above is measurement. This part is not. It is what we watched from inside the ecosystem — fourteen years building and selling Joomla! products, two decades in this market — and where we could put a document or a number behind the claim, we have.

None of it is about the code. Joomla!’s code has usually been good. It is about how the project treated the people who bet businesses on it.

And none of it is hindsight. Joomla!’s own magazine published a piece called The Fall of Joomla! in June 2016 — a decade ago — naming several of these out loud. Nothing on that list got fixed.

  1. Two major versions, twice the bill

    Until Joomla! 3, the project ran short-term and long-term releases in parallel and expected the ecosystem to carry both. From 2008 to 2014 an extension vendor was shipping for 1.5 and 2.5, or 2.5 and 3.x, at the same time: two codebases, two test matrices, two support queues, one revenue stream. Nobody at the top ever priced that for us.

    STS releases were supported seven months, LTS twenty-seven — and the project’s own policy said the first STS after an LTS “introduces fundamentally new features and changes that break compatibility with the previous LTS.” The model was abandoned in April 2014, after the shops that could not afford it had already left.

  2. Shiny object syndrome

    MooTools while the rest of the web standardised on jQuery. Then jQuery and Bootstrap 2 baked into 3.0. Then Bootstrap 5 swapped into Joomla! 4 while Joomla! 4 was already in beta, after years of betas built on Bootstrap 4. Every switch had a defensible engineering argument and not one of them had a migration budget for the people downstream.

    The official 3.0 FAQ conceded “components and templates will need the most work.” A conflict report over MooTools and jQuery colliding was filed on release day itself. Akeeba, one of the largest vendors, described tracking Joomla! 4 through twelve alphas, seven betas and five release candidates as “obscene amounts of work due to the constant changes.”

  3. Developers were always second-class citizens

    The Joomla! Extensions Directory was the distribution channel — the one place a small shop could be found. It has been purged, replatformed onto new URLs, and rebuilt again, and each time the vendors who had spent years earning rankings and reviews restarted from zero. It used to send real traffic. Now it collects dust.

    4,425 listings were purged in March 2013. The whole directory was replatformed in December 2014 onto a new URL scheme. Listings went from 9,559 in mid-2012 to 4,855 today. In 2024 reviews disappeared from listings for more than six months with the bug report sitting open. A fourth rebuild has been in progress since 2022.

  4. It never decided who it was for

    WordPress went after marketers. Drupal went after enterprise developers. Joomla! sat between them and called it balance. For twenty years the pitch has been “more powerful than WordPress, easier than Drupal,” which tells a buyer you are the best at nothing. And the people who actually choose the CMS were never developers — they are the marketers who have to live in the admin every day. Joomla! never courted them, so they never came, and they were the ones doing the recommending.

    John Hooley made this argument in Joomla!’s own magazine in June 2016: positioning as a “middle” solution “communicates nothing to your audience except that you are not the best at anything,” and “unlike developers, marketers loved Wordpress and loathed Joomla!” Ten years on, the positioning has not changed.

  5. No one was ever actually in charge

    WordPress has had Matt Mullenweg since 2003. Drupal has Dries Buytaert. Laravel has Taylor Otwell. Joomla! has had more than ten presidents since 2005, most of whom used the platform to build a personal profile and moved on. You cannot run a twenty-year platform on two-year terms and call the result a strategy.

    As of March 2026 the presidency of Open Source Matters is vacant, and a Joomla! co-founder published a piece in the project’s own magazine titled “Who Will Stand Up? The Next President of Open Source Matters.” The mechanism was named in that same magazine back in 2016: “some contributors have treated the project as their personal Game of Thrones and through Machiavellian tactics have driven out other contributors who disagreed with their vision for Joomla!”

  6. The money went to travel, not to the product

    This one is not our opinion — it is in the foundation’s own published accounts. For years the majority of every dollar raised in Joomla!’s name went on flights, hotels and conferences, and not one of those years carries a line item for building the software. And if you ran a profitable business on Joomla!, partnering with the foundation was a wall rather than a door.

    Travel plus conferences and meetings were 70.4% of all expenses in 2016 and 76.3% across the eighteen months to June 2018. Neither period lists a development expense at all. In 2021 the board disclosed $37,149 spent outside its own financial policy — $23,497 of it by the sitting president, whose conduct the board recorded as “unacceptable behaviour from an officer.” Income fell from $436,543 in 2016 to $66,182 in 2023–24. Meanwhile the 2008 trademark rules refused any extension name beginning with “Joomla!” and licensed the name only to GPL extensions.

  7. They never built the local scene

    WordPress built an institution to carry local events — money, contracts and legal liability held centrally so an organiser in Dhaka or Bologna only has to organise. Joomla! wrote a charter that pushed all of it back onto volunteers, then cut the little it did fund. Communities do not appear because a project recognises them. They appear because someone underwrites the room.

    Joomla!’s events charter makes local organisers “solely responsible for all actions and liabilities,” caps event funding at $500 and requires seed money to be repaid. JoomlaDays peaked at 36 events in 2014; WordCamps ran 115 in 2016 and 142 in 2019. In 2018 Joomla! cancelled its own World Conference and the programme that helped volunteers travel to events.

  8. And the roadmap was always a rumour

    This is the one you can see in every chart on this page. Agencies do not need a platform to be fast. They need it to be predictable, because they sign contracts against it. For a decade Joomla! could not tell anyone what was shipping or when — and a vendor who cannot answer that question loses the deal to one who can.

    Joomla! 4 was promised “before the end of 2018” and arrived in August 2021. Shopify, Wix and Squarespace all passed Joomla! inside that window.

Our read, after fourteen years in this market

The data doesn’t say Joomla! lost to WordPress. It says Joomla! lost to its own release calendar. Both sustained declines start at a cadence failure, not a competitor’s launch: search interest breaks at the 1.6/1.7 whiplash of 2011, and market share breaks inside the three-year silence between the 2018 promise of Joomla! 4 and its 2021 delivery — the exact window in which Shopify, Wix and Squarespace walked past. Communities forgive slow software. They don’t forgive unpredictable software.

That diagnosis cuts both ways. Since 2023 the project has shipped two major releases on the day the roadmap named — 5.0 and 6.0 — with 6.2 already dated for October. The install base still declines about a tenth of a point a year, but the cause of the last decade’s losses is, for the first time since 2012, actually fixed.

And it may not matter, because the ground moved again. The web is being rebuilt around AI, and Joomla! is not in that conversation: as of August 2026 AI support in Joomla! is a proof of concept that has not been merged — Joomla!’s own magazine describes the MCP work as needing “cleanup, proper installation scripts, and automated tests” — while 6.1 shipped a workflow editor and a captcha. Fixing the release calendar was the right answer to the last decade. It is the wrong answer to this one.

So here is our honest read: Joomla! is not dead, but it is dying, and on the current trajectory the interesting question is no longer market share — it is how many years the long tail has left. We have built on this platform since 2012, through every release on this page, and we would rather say that plainly than sell anyone a story. If you run client sites on Joomla!, 4.x lost security support in October 2025 and that is the problem to solve this quarter.

The questions everyone asks

Is Joomla! dead in 2026?

Not dead. Dying. 755,424 sites still run it and new ones still appear, but it has gone from 3.4% of the web to 1.2%, three platforms have passed it, and 72.1% of what survives gets no security updates. A platform can take a long time to die. This one has started.

Will AI finish it off?

That is our bet, and it is the part nobody in the community wants to hear. The web is being rebuilt around AI and Joomla! has not adapted at all: as of August 2026 its AI work is an unmerged proof of concept its own magazine says still needs “cleanup, proper installation scripts, and automated tests,” while 6.1 shipped a workflow editor and a captcha. When the tools that build websites become the ones that choose the platform, being absent from that conversation is going to hurt — badly, and faster than the curves on this page suggest.

What is Joomla!’s market share?

1.2% of all websites and 1.7% of the CMS market as of August 2026, per W3Techs — down from peaks of 3.4% and 11%. It was the web’s #2 CMS as recently as 2020. Compare the platforms in our Joomla! vs WordPress breakdown.

Should I still use Joomla! in 2026?

If you already run it: yes, and get off 3 and 4 now — that is a security problem, not a preference. If you are choosing a platform from scratch, we sell Joomla! products and we will still tell you the truth: pick it for a specific reason — multilingual core, granular ACL, an existing team — not because you expect the ecosystem around it to grow. Start with migrating off Joomla! 3.

Methodology & sources

All figures collected 19 August 2026. The sources measure different things and disagree by design; we never mix them in one chart.

  • W3Techs — share of all websites, surveyed each January 1: historical CMS survey and Joomla! detail page. The live table starts in 2015; 2011–2014 come from archived captures of the same page and carry their own survey dates.
  • Google Trends — worldwide interest in “joomla”, indexed so March 2009 = 100, charted as yearly averages. It measures attention, not installations.
  • BuiltWith — live-site counts from BuiltWith Trends. Its crawl reaches further into the long tail than W3Techs’ traffic-ranked sample, so the two never reconcile: cite one, never an average.
  • DataForSEO — keywords each root domain ranks for in Google’s US results, October 2020 – August 2026, charted as joomla.org per 100 of wordpress.org. Only the ratio is publishable: wordpress.org’s own raw count falls 94% over the window, so the raw series measure the database, not traffic.
  • “Why it actually declined” — the arguments are ours; the figures are primary. Joomla!’s release-cycle documentation, its 2013 directory purge and 2014 replatform announcements, archived listing counts, the events charter and 2018–19 budget, WordPress’s WordCamp counts, and Open Source Matters’ published accounts plus its board’s May 2021 post on expenses outside financial policy. Expense percentages are ours, computed from those line items.
  • AI status — the unmerged proof of concept and the work it still needs are described in Joomla!’s own magazine, 19 February 2026.
  • Release dates — Joomla! announcements and the version history on Wikipedia: 1.0 Sep 2005, 1.5 Jan 2008, 1.6 Jan 2011, 1.7 Jul 2011, 2.5 Jan 2012, 3.0 Sep 2012, 4.0 Aug 2021, 5.0 Oct 2023, 6.0 Oct 2025, 6.1 Apr 2026.

Citing this page: journalists and researchers may reuse the figures and charts with attribution and a link back. Something off? Tell us — we’ll correct it and credit you.