Applies to Joomla 6.x, 7.0-dev · Joomla 8 roadmap as published by the Joomla project As of November 2026

Joomla 8 has no release date, no alpha and no code branch yet. What exists is the "Joomla 8 roadmap": a feature list that came out of a strategy sprint in September 2025, was approved by the Joomla Production Department and published on the developer site in February 2026. Many items are still open for volunteers. The roadmap page files every item under Joomla 6.x or 7.x, so much of it could arrive before 8.0. Joomla's release cycle places major versions in October of odd years and names 2029 in its own example, which would put Joomla 8 in October 2029 – a planned cycle, not an announced date. The roadmap facts below come from the project's own pages and pull requests, and every feature on it is proposed, not decided.

Joomla 8 at a glance

QuestionAnswer (November 2026)
Is Joomla 8 announced?As a plan, yes. As a release, no: there is no 8.0 milestone and no 8.x branch on GitHub.
When could it come out?October 2029, if the published two-year cycle holds. No one has announced that date.
Where is the roadmap?The Feature Roadmap on developer.joomla.org, in two sections: Joomla 6.x and Joomla 7.x.
What comes first?Joomla 7.0. Its GitHub milestone is due 11 October 2027.
Can I help?Yes. An online sprint on 4–5 December 2026 works on the open roadmap items.

Where the "Joomla 8 roadmap" comes from

It is not a feature list for the 8.0 release alone. In June 2025 the Joomla Production Department wrote in the Community Magazine that the project had a release cycle and plenty of new features, but no mid- and long-term plan. It called a sprint to write one. The steps since then:

  • June 2025: the sprint is announced for 4–7 September 2025 in Germany, with 10 to 15 people from different areas.
  • August 2025: the community is asked for ideas that would take Joomla forward over the next four years – with the condition that whoever proposes a feature also helps build, test, manage or fund it.
  • September 2025: the sprint ranks the ideas on four criteria: competitive advantage, benefit for Joomla's audience, ease of implementation and backward-compatibility risk. Ratings from the community, collected during the sprint, count in the result.
  • 28 February 2026: the feature list goes public on developer.joomla.org, each item approved by the Production Department. The announcement says plainly that it is a living pipeline, not a fixed roadmap.
  • July 2026: some items are covered by the Sovereign Tech Fund accessibility project; the roadmap links them to its milestones.
  • 20 October 2026: Benjamin Trenkle, who leads the Joomla Maintenance Team, writes that some features are already implemented and announces an online sprint for 4–5 December 2026.

So "Joomla 8" names the planning effort and its horizon. The features themselves land in whichever release is ready for them.

What is on the roadmap

The Feature Roadmap page says that all dates are tentative and that the list is not final. Here is what it held on 16 November 2026, with the status the project gives each item. Most items have a person in charge; eight have none yet.

Joomla 6.x: the groundwork (14 items)

The project calls these the highest priority. Both merged items already ship: the proof-of-work captcha (plg_captcha_powcaptcha, a captcha with no external service and no API key) since Joomla 6.1, through PR #46514, and the unified link and media dialogs in TinyMCE since Joomla 6.2, through PR #48138 and PR #48043.

StatusItems
Merged and shippingBuilt-in proof-of-work captcha (6.1); link and media dialogs in the editor (6.2)
Ready for testingModule assignment with inheritance (PR #47570); redirects for renamed, removed or unpublished items (PR #46807) – both open against 6.3, not merged
In progressMCP servers so AI tools can work with Joomla (with accessibility in mind); a much larger user manual
In planningWCAG 2.2 AA compliance; whether and how to integrate an AI framework
Looking for volunteersContent versioning with drafts, extended to categories, modules and menu items; documentation for the web services; developer documentation; better machine-to-machine web services; configurable authoring forms; a new sample dataset

Joomla 7.x: bigger features and breaking changes (12 items)

This section is for features that need more effort or that break backward compatibility, which Joomla only allows in a major version. None of them is merged yet.

StatusItems
In progressAutomated workflows: content workflows combined with the task scheduler, e.g. feature an article on a date (open PR #48480 against 6.3, not merged); an Ajax backend, so list actions like unpublish work without a page reload (open PR #47463 against 6.3, not merged)
In planningA rate limiting framework that core and extensions can use, e.g. against login brute force; filtering items by custom field values, in menu items or as user filters, front end and back end
Looking for volunteersFramework-agnostic templates and design system; a new default template for each major version; several sites in one Joomla installation; a site-wide content-language filter for translators on the front end; the same language filter in the backend; UI presets per user role; less repetitive default code for extensions; one consistent API for categories, tags and custom fields

The default template item is the only one that names Joomla 8 directly: the goal is a fresh default template for each major release, "e.g. Joomla 8", as a visual update of the current core template rather than a rewrite.

Joomla 8 release date: what the release cycle says

Joomla's Software Release Cycle, in the official manual, sets a major version every two years, planned for October of an odd year – the manual's own examples are 2025, 2027 and 2029 – with four minor releases in between. The last minor, x.4, is a bridge release with no new features: you can only update to the next major from it. After x.4.0 comes out, the series gets bug fixes for one year and security fixes for two.

VersionReleased / plannedSupport
Joomla 5October 2023Security fixes only since October 2026; end of life 12 October 2027
Joomla 6October 2025 (6.2 in October 2026)Expected end of life October 2029: two years after 6.4.0, due with Joomla 7
Joomla 7GitHub milestone due 11 October 2027–
Joomla 8October 2029 by the cycle; not announced–

The Joomla 5 dates follow from the same rule (5.4.0 came out in October 2025); endoflife.date lists the same ones. The Joomla 7 date comes from the milestone on GitHub, the Joomla 8 line only from the cycle. The cycle has held since Joomla 4 switched to it (5.0 in 2023, 6.0 in 2025), but dates in a volunteer project depend on people, and the roadmap page says so itself. One consequence is already clear: Joomla 6's end of life and the planned Joomla 8 date fall in the same month, so sites on Joomla 6 need to be on Joomla 7 by October 2029.

You can check the state of the repository yourself. On 16 November 2026 the development branches were these, and none of them is an 8.x branch:

# joomla-cms development branches, 16 Nov 2026
git ls-remote --heads https://github.com/joomla/joomla-cms.git | cut -f2 | grep -- '-dev$'
# refs/heads/5.4-dev
# refs/heads/6.2-dev
# refs/heads/6.3-dev
# refs/heads/7.0-dev

What it means for you now

If you run Joomla sites

  • Nothing to test for 8.0 yet. Plan around Joomla 6's end of life instead.
  • Joomla 5 is the deadline that matters first: it gets security fixes only since October 2026 and reaches end of life on 12 October 2027, around when Joomla 7 is due. Sites still on Joomla 3, 4 or 5 should be on Joomla 6 well before then.
  • Stay on the latest Joomla 6 minor. Only the newest minor of a series is supported, and the route to 7 – and later to 8 – goes through the x.4 bridge releases.
  • Watch Joomla 6.3. Module assignment with inheritance and redirects for renamed items are ready for testing against 6.3. Since 6.4 is a bridge release without new features, a 6.x item that misses 6.3 can only arrive in Joomla 7.x or later.

If you build extensions or templates

  • Clean up for Joomla 7 first. Joomla 7 removes many APIs that were deprecated for 7.0, and its Backward Compatibility 7 plugin is installed disabled – code that still leans on the old APIs will break there long before Joomla 8 matters. Our posts on replacing Factory getters and testing against 7.0-dev cover how.
  • Watch the items that touch your code: the Ajax backend (actions in list views), one consistent API for categories, tags and custom fields, filtering by custom fields (if you built your own field filters) and the rate limiting framework (if you protect forms yourself).
  • Template developers: Cassiopeia and Atum are built on Bootstrap 5 today. A framework-agnostic design system and a new default template per major would change what "the core look" means for overrides – still looking for volunteers, so nothing to adapt to yet, but worth following.
  • Help shape it. Most items are looking for volunteers. If a feature touches your product, working on its pull request lets you test it against your code before it is merged.

How to follow it or take part

  • Online sprint, Friday–Saturday 4–5 December 2026. Implementation, testing and code review on the remaining roadmap items. Features already covered by the Sovereign Tech Fund programme are out of scope. To join, contact Sigrid Gramlinger by email or on Mattermost; the article says participants get the task list and meeting details.
  • The Feature Roadmap on developer.joomla.org lists the status of each item and, for most, a person in charge. Contact that person for a feature you want to work on.
  • GitHub: new ideas go in as feature requests; the 7.0.0 milestone shows what is lined up for Joomla 7.

For the release in between, start at our Joomla 7 hub: where Joomla 7 stands and the Joomla 7 upgrade checklist.

Sources

Getting your site ready for what comes next

A site on the current Joomla 6 minor with maintained extensions needs only the routine bridge-release steps to reach 7, and later 8. If your site is still on Joomla 3, 4 or 5, or depends on extensions nobody updates any more, our Joomla migration service moves it to Joomla 6: we audit every extension, template override and piece of custom code first, run the move on a staging copy and keep your URLs or redirect them. For extension authors who want their code checked against 7.0-dev, see custom extension development.