There is no Joomla 6.8 release. The headline you may have encountered is inaccurate. As of June 2026, the latest stable version of Joomla is 6.1.1, released on May 26, 2026, with its predecessor 6.1.0 arriving on April 14, 2026.
If you’ve seen claims about a 6.8 release with 12 new features, you’re looking at outdated information, speculation, or mislabeled content—none of which reflect the current state of the Joomla project. The confusion likely stems from mixing up version numbers or conflating multiple release cycles. Joomla’s actual current roadmap shows 6.2 in early alpha development, scheduled for October 2026, but no 6.8 appears anywhere on the official project timeline. It’s important to verify Joomla release information against the official Joomla.org announcements and GitHub releases, especially when making upgrade decisions for production sites.
Table of Contents
- What Version of Joomla Is Actually Current?
- The Actual Joomla 6.1 Features (Not 12, But 5 Key Ones)
- How These Features Improve Workflows for Developers and Site Managers
- Joomla’s Roadmap: What’s Next After 6.1?
- Should You Upgrade to Joomla 6.1 Right Now?
- Visual Workflow Editor in Action
- The Proof-of-Work CAPTCHA Advantage
What Version of Joomla Is Actually Current?
Joomla 6.1.1 is the latest stable release available to download and install today. This version includes security fixes and bugfixes on top of the 6.1.0 foundation released six weeks earlier. The version numbering follows a major.minor.patch structure: Joomla 6 is the major version (the flagship release from 2023), while 6.1 and 6.1.1 are incremental updates that refine and stabilize the codebase.
The previous major version, Joomla 5, entered long-term support (LTS) status in late 2024, meaning it still receives security updates but no new features. If you’re running an older installation of Joomla 4 or earlier, you are no longer receiving security patches and should plan an upgrade. Many shared hosting providers and managed Joomla services have already begun migrating sites from Joomla 4 to 6 to reduce support burden and improve security posture, so checking your current version is a practical first step before undertaking any major work.
The Actual Joomla 6.1 Features (Not 12, But 5 Key Ones)
Joomla 6.1 introduced five significant features, not twelve. The first is a Visual Workflow Editor—an interactive, drag-and-drop interface for designing content pipelines and editorial workflows. Instead of manually configuring state transitions in configuration files, editors can now visually map out how articles move from draft to review to publication, making content governance more transparent and less error-prone. The second is a Proof-of-Work CAPTCHA system designed for privacy and accessibility. Unlike Google reCAPTCHA, which tracks users and requires third-party JavaScript, Joomla’s implementation solves a mathematical puzzle on the client side without sending data to external services.
This appeals to sites concerned with GDPR compliance or visitor tracking, though it does require slightly more client-side processing power and may feel slower on older devices. The third feature is Media Custom Fields, which extends custom field support beyond images to include audio, video, and document files—useful for media-rich sites like podcasts, educational platforms, or documentation hubs. The fourth addition is Module Versioning, extending the full version history and rollback capability that previously existed only for articles to apply now to modules as well. This means you can revert a sidebar module or navigation change to a previous state without losing work, similar to how Git commits work. The fifth major improvement is performance-focused: on-demand plugin loading for PHP 8.4+, which means Joomla only loads plugin code when needed rather than loading everything on every page request, reducing memory footprint and improving response times on resource-constrained servers.
How These Features Improve Workflows for Developers and Site Managers
The Visual Workflow Editor directly addresses a pain point in large organizations where multiple people handle content creation, review, and publication. Previously, a Joomla site manager had to document the workflow externally and ask developers to code state transitions. Now, a non-technical manager can build and modify the workflow in the admin interface, reducing the feedback loop and eliminating miscommunications between editorial and technical teams.
A news organization with 15 contributors, 3 section editors, and 1 legal reviewer can now visually define that path in minutes, not days. Module Versioning prevents the common mistake of making a quick sidebar module edit without documenting it, then having to reverse-engineer what changed after the homepage looks different. A developer working on a redesign can experiment freely, knowing every iteration is tracked and any change can be rolled back with one click. The on-demand plugin loading on PHP 8.4+ is particularly valuable for agencies managing dozens of Joomla sites: if you run 50 small business sites on shared hosting, each with 20 installed plugins but only 5 active, the memory savings compound across all sites on a single server, reducing resource contention and lowering the hosting bill.
Joomla’s Roadmap: What’s Next After 6.1?
Joomla 6.2 is currently in alpha development, with the first alpha release already available for testing. The planned release date is October 2026, roughly four months from now. After 6.2, the roadmap extends into 2027, but no details on specific features for 6.3 or beyond have been publicly committed. The project maintains a published roadmap at developer.joomla.org/roadmap, which is the authoritative source for planning future upgrades.
For site owners deciding whether to upgrade from Joomla 5 or 4 to Joomla 6.1, the timeline matters. If you’re comfortable staying on Joomla 5 long-term support, you’ll continue receiving security patches through at least 2025. However, as more third-party extensions (templates, plugins, components) add Joomla 6-only features, you may find yourself unable to use newer extensions without upgrading. The typical migration path is to test Joomla 6.1 on a staging server, verify that all your critical extensions are compatible, then schedule a production upgrade during a maintenance window—not immediately, but not so far in the future that you fall too far behind.
Should You Upgrade to Joomla 6.1 Right Now?
The answer depends on your extension compatibility and risk tolerance. Joomla 6 simplified and modernized the core significantly, which means some older extensions built for Joomla 4 do not work on Joomla 6 without updates from the developer. Before upgrading a live site, audit your installed components, modules, and plugins against the Joomla Extension Directory (JED) to check their Joomla 6 support status. If a critical extension lacks a Joomla 6 compatible version and the developer is unresponsive, upgrading is off the table until you find an alternative or the extension is updated.
A second consideration is testing thoroughly on staging. The Visual Workflow Editor, while powerful, adds new configuration state to your database. If you’ve heavily customized your site’s content workflow through plugins or templates, upgrading to 6.1 and enabling the new workflow editor could introduce unexpected behavior if your customizations conflict with the new editor’s state management. Test the entire editorial process, including multi-user workflows, content transitions, and any custom approval plugins, before taking the site live on 6.1.
Visual Workflow Editor in Action
Imagine a professional services firm that publishes case studies. Currently, the workflow is: author writes, submits to internal email; manager reviews, comments in email; legal team reviews the document; once approved, a administrator manually publishes the article. With Joomla 6.1’s Visual Workflow Editor, the site manager creates a workflow with states: Draft → Manager Review → Legal Review → Published.
The author creates an article and sets it to “Draft.” The workflow automatically notifies the manager. Once the manager transitions it to “Manager Review,” the legal team’s group is notified and sees it in their Joomla admin dashboard. No email forwarding, no manual status tracking, no confusion about whose turn it is. The entire pipeline is visible in one diagram, and any team member can see where an article is stuck.
The Proof-of-Work CAPTCHA Advantage
Joomla’s native Proof-of-Work CAPTCHA computes a lightweight mathematical puzzle in the browser and submits proof that work was done, without revealing anything to third parties. A contact form submission includes proof of work, but no tracking pixel, no IP logging, and no data sent to Google.
For GDPR-compliant sites and visitors in regions with strict privacy laws, this is a material difference from reCAPTCHA. The tradeoff is that very old browsers (Internet Explorer 11 and older) or devices with slow JavaScript engines may take 2–5 seconds longer to submit a form, whereas reCAPTCHA is instant on modern browsers. The security level is comparable for most use cases—it stops automated bulk submissions without incurring the privacy cost of centralized bot detection.
