Joomla 6.2.0 “Mwezi” is the latest Joomla release, published on 13 October 2026. It is a minor release on the Joomla 6 line, so a 6.1 site updates in place, and a Joomla 5.4 site can upgrade straight to 6.2. 6.2 brings TinyMCE upgrades, more control over article images, new Login module options, security flags for extension updates, and XOAuth2 for email. Joomla 5.4.10, released the same day, is the last bugfix release for Joomla 5. This guide covers what 6.2 adds, what 6.x changed from 5.x, and how to upgrade safely.
Joomla 6.0 shipped in October 2025 and 6.1 followed. 6.2.0 is now the version to run (download 6.2.0, Joomla 6.2 announcement). The project says 6.2 is the result of more than 130 pull requests from volunteers. The next patch, 6.2.1, is planned for 24 November 2026.
Did the 6.2 update fail or break something? The checksum or JSON error, “not compatible” warnings, the language switcher and override notices are covered in Joomla 6.2 update problems.
If you need a managed path from 3.x, 4.x, or 5.x onto 6.2, use Infyways Joomla Upgrade services.
What you will learn
- Where Joomla 6.x stands after the 6.2.0 release on 13 October 2026
- What Joomla 6.2 shipped, checked against the official release notes
- The 6.2 release timeline and the planned 6.2.x patch dates
- How 6.x differs from 5.x and 4.x
- A practical upgrade checklist for site owners and developers
- When to call in Joomla upgrade or support help
Official schedule source: Joomla Project Roadmap.
What’s new in Joomla 6.2?
Joomla 6.2 is a feature release focused on content editing, site-builder options and safer updates. It does not change the architecture. The main changes, from the Joomla 6.2 announcement and the 6.2.0 changelog:
| Area | What changed in 6.2 | Why it matters |
|---|---|---|
| TinyMCE editor | Image and media buttons open the Joomla Media Manager. A unified link selector modal serves the article, contact and menu buttons. Native Read More button. TinyMCE follows Joomla’s text filter by default. TinyMCE updated and untranslated toolbar-builder buttons fixed | Fewer clicks for editors. HTML follows your Global Configuration filters instead of TinyMCE’s own allowed elements, so test custom markup |
| Articles and categories | Separate CSS class fields for an intro or full-text image and its surrounding figure. Subcategory images in category lists and blogs (content, contacts, newsfeeds). Fix for categories that looked empty when their articles were scheduled for the future | More styling control without overrides |
| Modules | Login module options to hide the “Forgot your password?” and “Forgot your username?” links. Submenu toggling fixed for deeper levels in the standard menu layout | Removes two common reasons for template overrides |
| Administrator | Fancy Select search results show their group name (useful for module positions). Redesigned backend Help page | Faster admin work |
| Installation and updates | More precise web installer errors. Developers can flag an extension release as a security update (severity None to Critical). Flagged updates are highlighted in System → Update → Extensions and on the dashboard quick icon | You can see which extension updates are security fixes |
| Generic XOAuth2 for SMTP authentication: Joomla stores a refresh token from the mail provider instead of the account password | Relevant for Microsoft 365 and Google Workspace mail | |
| Developers | Reorganised JavaScript and CSS asset build pipeline. Also in the changelog: an Enum form field, a language fallback chain, the option to prefer the highest-severity update, and clearer SVG upload errors | Extension developers should rebuild and retest assets |
Article preview without a frontend login is not in 6.2.0. It was added during the betas and then reverted (pull request #48325). Do not plan around it.
Joomla 6.2 release timeline
| Milestone | Date | Status |
|---|---|---|
| Alpha 1 to 3 | 26 May to 21 July 2026 | Done |
| Beta 1 (feature freeze) | 18 August 2026 | Done |
| Beta 2 and Beta 3 | 1 and 15 September 2026 | Done |
| Release Candidate | 29 September 2026 | Done |
| 6.2.0 stable | 13 October 2026 | Released, latest |
| 6.2.1 | 24 November 2026 | Planned |
| 6.2.2 to 6.2.4 | 5 January, 16 February, 30 March 2027 | Planned |
Planned dates can change with volunteer availability (Joomla roadmap). Release managers for 6.2: Viviana Menzel and Martin Kopp.
Production rule: run Joomla 6.2.0 on live sites once your extensions are verified on staging. If an extension you depend on is not ready, stay on 6.1.4, the newest 6.1 release, while you wait, and keep it patched. Test on a staging copy first. launch.joomla.org is fine for quick experiments.
Joomla 5.4 after 13 October 2026: 5.4.10 was the last bugfix release for Joomla 5. Security fixes for 5.4 continue until 12 October 2027. The project calls 5.4 to 6.2 an upgrade, not a migration: most extensions work with the Behaviour – Backward Compatibility 6 plugin enabled.
Upgrade notes for 6.2
Read the official Joomla 6.1 to 6.2 upgrade notes and the 6.2.0 changelog before you upgrade. Developers should note the deprecations retargeted to Joomla 7, the deprecated CMS Crypt package, and the rebuilt asset pipeline.
What Joomla 6.x already changed vs 5.x and 4.x
Joomla 6.0 was the architectural jump. 6.1 and 6.2 are incremental on that base.
| Area | Joomla 4.x | Joomla 5.x | Joomla 6.x |
|---|---|---|---|
| Focus | Bootstrap 5 admin, accessibility | Modern PHP, compatibility plugin era | Framework cleanup, new packages, stricter future path |
| PHP | 7.2+ era evolving to 8.x | PHP 8+ focus | PHP 8.3.0 minimum, 8.4 recommended |
| Extensions | Many older extensions still ran | Compat plugin smoothed upgrades | Test every extension; compat is a bridge, not a forever plan |
| APIs | Mixed legacy | Deprecations increasing | Renderer, Console, Preload, DB/HTTP modernization |
| Support clock | Ended | 5.4 bugfix ended 13 Oct 2026 (5.4.10) | 6.2.0 current; bugfix to 17 Oct 2028 |
Core 6.0 themes that still matter for upgrades: stronger database patterns, HTTP / cryptography modernization, console tooling, preload helpers, and the compatibility plugin for migration. Details live in Joomla 6 migration docs and the roadmap.
Joomla 4, 5 and 6 support timeline (end of life dates)
Joomla 4 is end of life. Its regular bugfix support ended on 15 October 2024 and security fixes ended in October 2025, so a Joomla 4 site no longer receives patches. Move it to 5.4 and then to Joomla 6.
| Version | Released | Bugfix support ends | Security support ends |
|---|---|---|---|
| Joomla 3.10 | August 2021 | Ended | 17 August 2023 (end of life) |
| Joomla 4.4 | October 2023 | 15 October 2024 | October 2025 (end of life) |
| Joomla 5.4 | 14 October 2025 | 13 October 2026 | 12 October 2027 |
| Joomla 6.x | 14 October 2025 | 17 October 2028 | 16 October 2029 |
What Joomla 4 introduced (still in 6)
Many features people still call “new” arrived in Joomla 4: the Atum administrator and Cassiopeia front-end templates, the Web Asset Manager, the rebuilt Media Manager, Workflows, Web Services API, two-factor authentication and a cleaner routing system. Joomla 5 and 6 kept these and removed the legacy layers around them. Dates from the Joomla roadmap; upgrade steps in How to upgrade Joomla 3 to Joomla 6.
How do I upgrade to Joomla 6.2?
From 6.1, it is a normal minor update in System → Update → Joomla. From 5.4, disable Behaviour – Backward Compatibility, enable Behaviour – Backward Compatibility 6, and upgrade. Older versions go through 5.4 first. The steps below apply to every path.
Why you should upgrade now
- Support calendar. Joomla 5 bug fixes ended with 5.4.10 on 13 October 2026. Security patches continue until 12 October 2027, but bug debt stacks up if you stay behind.
- Extension vendors. Good vendors already ship builds that declare Joomla 6.2. Check each vendor’s changelog before you update.
- 6.2 editor and language changes. TinyMCE filter defaults and language fallback can change what editors see. Staging catches that before clients do.
- Email security. If your SMTP runs on Microsoft 365 or Google Workspace, XOAuth2 lets you stop storing the mailbox password in Joomla.
Need hands-on help: Joomla Upgrade, ongoing Joomla support and maintenance, or hire Joomla developers. For K2 sites stuck on old stacks, pair the CMS upgrade with K2 migration services.
Step 1: Inventory and hosting check
- Export installed extensions, templates, custom overrides, and PHP version.
- Confirm hosting meets Joomla 6 PHP requirements (modern 8.x). Upgrade hosting before the CMS if needed.
- Mark every extension as: J6-ready, needs compat plugin, or replace. A Joomla 6 compatibility check with the free Migration Scanner lists the exact files and lines for each one.
- Filter the Joomla Extensions Directory by Joomla 6 where vendors list readiness.
Step 2: Stage, never upgrade live first
- Full backup (files + database).
- Clone to staging with the same PHP version you will use in production.
- From 5.x, update to the newest 5.4.x first, then upgrade the staging copy to 6.2.0.
- From 6.1.x, update the staging copy to 6.2.0 and test editors, menus and multilingual switching.
Download packages from downloads.joomla.org. Report core issues at issues.joomla.org.
Step 3: Compatibility plugin, then remove the crutches
- Enable the Joomla compatibility / BC plugin only while you patch or replace broken extensions.
- Retest logins, checkout, forms, multilingual switching, and search.
- Fix or replace templates that assume removed APIs.
- Plan to turn the compat plugin off once everything is native-ready. It is a bridge.
Upgrade notes: Joomla 6.1 to 6.2 upgrade notes. If the update itself fails, see Joomla 6.2 update problems.
Step 4: QA before production cutover
- Frontend: home, menus, articles, category blogs, media, forms.
- Admin: article edit (TinyMCE readmore/links), installer update view, language strings.
- SEO: SEF URLs, redirects, sitemaps, canonical tags.
- Performance: cache, CDN, image formats (WebP converter for Joomla).
- Security: install the current 5.4.x or 6.x security releases on whatever you run today. Do not wait for the upgrade to patch.
When staging is green, schedule production during low traffic, restore plan in hand. Infyways can run that cutover under Joomla Upgrade or white-label via outsource Joomla services.
Developer action plan for 6.2
- Test extensions on 6.2.0 now, and on 6.2.1-dev nightly builds before 6.2.1.
- Rebuild and retest any assets that depend on the core JavaScript and CSS pipeline.
- Adopt EnumField where enums already model your options.
- Re-test TinyMCE integrations after the text-filter default change.
- Watch language packs for fallback-chain behavior on incomplete translations.
- Flag security releases in your update server so 6.2 highlights them for users.
- Read the 6.1 to 6.2 upgrade notes for deprecations now targeted at Joomla 7.
Agencies maintaining many client sites: outsource Joomla services and Joomla extension development.
Key takeaways
- Latest: Joomla 6.2.0, released 13 October 2026. Next patch 6.2.1 is planned for 24 November 2026.
- 6.2 is a minor release: 6.1 updates in place, and 5.4 upgrades directly.
- Headline 6.2 changes: TinyMCE Media Manager and link picker, Read More button, article image classes, Login module options, security flags for extension updates, XOAuth2 email.
- Joomla 5 bug fixes have ended (5.4.10). Plan the move to 6.2 now.
- Upgrade on staging first. Use Infyways Joomla Upgrade if you want a managed migration.
Frequently asked questions
When was Joomla 6.2 released?
Joomla 6.2.0 was released on 13 October 2026 and is the latest version. 6.2.1 is planned for 24 November 2026 on the roadmap.
Is Joomla 6.2 safe for live sites?
Yes. 6.2.0 is a stable release. Test your extensions and template on a staging copy first, then update the live site.
What is the current stable Joomla version?
Joomla 6.2.0, released 13 October 2026, on downloads.joomla.org. For Joomla 5, the last release is 5.4.10.
How is Joomla 6.2 different from Joomla 6.0?
6.0 was the major platform jump. 6.2 is a minor release that adds TinyMCE improvements, article image and figure classes, Login module options, security flags for extension updates and XOAuth2 email, on the same architecture.
Can I upgrade from Joomla 5.4 directly to 6.2?
Yes. The project calls it an upgrade, not a migration. Disable Behaviour – Backward Compatibility, keep Behaviour – Backward Compatibility 6 enabled, and test on staging.
What should I do if the Joomla 6.2 update fails?
Check for updates again, or upload the 6.2.0 package with Upload & Update. Fixes for the common errors are in Joomla 6.2 update problems.
Will my Joomla 5 extensions work on Joomla 6?
Some will, some need the compatibility plugin, some need vendor updates. Inventory and test on staging. Replace abandonware before you cut over.
Does Joomla 5.4 still get updates?
Only security fixes. 5.4.10 (13 October 2026) was the last bugfix release, and security support runs until 12 October 2027.
How do I upgrade to Joomla 6 safely?
Backup, clone to staging, update hosting/PHP, update or replace extensions, test, then schedule production. Infyways documents and runs this under Joomla Upgrade services.
Where do I get help if the upgrade breaks?
Start with staging logs and vendor docs. For a full recovery or multi-site rollout, use Joomla support and maintenance or hire Joomla developers.