XenForo announced version 2.4 in September 2024 with a target window of Q4 2024 to Q1 2025, and the software still has not shipped.
The current release is 2.3.12, which landed in July 2026. The original target window closed in March 2025.
None of that changes the everyday workings of a XenForo board, which is why most administrators stopped watching a long time ago. The delay still matters if you are choosing software, commissioning add-on work, or budgeting a redesign around a version that keeps not arriving.
XenForo previews upcoming features in public posts, and the 2.4 run started briskly. Direct message labels appeared in early December 2024, followed by the new editor later that same month.
Chunked uploads arrived in February 2025. Featured content improvements followed within weeks, then flash message changes and progressive web app work in early April.
Then the previews stopped. The next one did not appear until February 2026, roughly eight months after a June 2025 status post and ten months after the previous feature preview.
That February burst covered custom field filtering, custom field searching and support for a new GIF provider. Useful work, certainly. Not the sort of headline that signals an imminent release.
The announcement had also promised a change of habit. Previews would come out steadily through development instead of being saved for launch, so the community could react to features early. The silence in the middle tested that promise hard.
Nothing further has appeared since late February 2026. The January 2026 patch acknowledged the situation in passing, noting that anyone expecting a 2.4 preview was getting a substantial 2.3 update instead.
The specifics explain a great deal. XenForo is moving its database layer from mysqli to PDO, adding native SQLite support for development and testing, and building a fluent query builder that works across database types.
That is plumbing rather than product. It is also the kind of change that touches every add-on doing anything unusual with the database, which makes a careless release far more expensive than a late one.
The editor rebuild sitting at the center of 2.4 added its own wait. The team chose to ship on Tiptap version 3 instead of releasing on version 2, which meant holding back until the upstream library settled.
Two details from the original announcement are worth holding onto. The Tiptap editor was first earmarked for a future 3.0 release and pulled forward into 2.4, and the team promised minimal backwards compatibility trouble on upgrade.
The same post mentioned roughly fifteen features merged or pending that had never been announced publicly. The backlog is in the communication as much as in the code.
Developer tooling absorbed effort too, including a PhpStorm plugin, built-in PHP web server support for local work, and a development console. None of it is visible to a single one of your members.
2026 alone brought 2.3.8 in January, 2.3.9 in February, 2.3.10 in March, 2.3.11 in June and 2.3.12 in July. Five releases across seven months.
None of them were token gestures. The January release carried more than eighty fixes and improvements, including a denial-of-service fix, retina thumbnail generation, and further passkey work.
XenForo also patched the older 2.2 line twice in early 2026, shipping 2.2.19 in March after 2.2.18 in February. Boards a full version behind are still receiving attention.
The public discussion has meanwhile become an artifact in its own right. The status thread alone now runs past forty pages of replies.
So the practical answer for anyone deciding today is unglamorous. Buy or upgrade on 2.3, and treat 2.4 as a free improvement whenever it turns up.
The one group that should plan differently is add-on developers and the site owners who pay them. A database layer change and a new editor together mean custom code will need reviewing, and that bill arrives whenever 2.4 does rather than on a date anyone can put in a budget.
The current release is 2.3.12, which landed in July 2026. The original target window closed in March 2025.
None of that changes the everyday workings of a XenForo board, which is why most administrators stopped watching a long time ago. The delay still matters if you are choosing software, commissioning add-on work, or budgeting a redesign around a version that keeps not arriving.
The preview trail went quiet for eight months
The timing was ambitious from the outset. XenForo 2.3.0 had shipped on July 4, 2024, and the 2.4 announcement followed barely ten weeks later, with a window that would have squeezed two feature releases into a single year.XenForo previews upcoming features in public posts, and the 2.4 run started briskly. Direct message labels appeared in early December 2024, followed by the new editor later that same month.
Chunked uploads arrived in February 2025. Featured content improvements followed within weeks, then flash message changes and progressive web app work in early April.
Then the previews stopped. The next one did not appear until February 2026, roughly eight months after a June 2025 status post and ten months after the previous feature preview.
That February burst covered custom field filtering, custom field searching and support for a new GIF provider. Useful work, certainly. Not the sort of headline that signals an imminent release.
The announcement had also promised a change of habit. Previews would come out steadily through development instead of being saved for launch, so the community could react to features early. The silence in the middle tested that promise hard.
Nothing further has appeared since late February 2026. The January 2026 patch acknowledged the situation in passing, noting that anyone expecting a 2.4 preview was getting a substantial 2.3 update instead.
The holdup sits under the hood rather than in the features
A developer status post in June 2025 was unusually direct. It said the team was working to release 2.4 as soon as possible, but that scope changes and strategic decisions had made it take longer than expected.The specifics explain a great deal. XenForo is moving its database layer from mysqli to PDO, adding native SQLite support for development and testing, and building a fluent query builder that works across database types.
That is plumbing rather than product. It is also the kind of change that touches every add-on doing anything unusual with the database, which makes a careless release far more expensive than a late one.
The editor rebuild sitting at the center of 2.4 added its own wait. The team chose to ship on Tiptap version 3 instead of releasing on version 2, which meant holding back until the upstream library settled.
Two details from the original announcement are worth holding onto. The Tiptap editor was first earmarked for a future 3.0 release and pulled forward into 2.4, and the team promised minimal backwards compatibility trouble on upgrade.
The same post mentioned roughly fifteen features merged or pending that had never been announced publicly. The backlog is in the communication as much as in the code.
Developer tooling absorbed effort too, including a PhpStorm plugin, built-in PHP web server support for local work, and a development console. None of it is visible to a single one of your members.
Waiting for XenForo 2.4 does not mean running unpatched code
This is the part that gets lost in the grumbling. The 2.3 line has kept moving steadily throughout the delay.2026 alone brought 2.3.8 in January, 2.3.9 in February, 2.3.10 in March, 2.3.11 in June and 2.3.12 in July. Five releases across seven months.
None of them were token gestures. The January release carried more than eighty fixes and improvements, including a denial-of-service fix, retina thumbnail generation, and further passkey work.
XenForo also patched the older 2.2 line twice in early 2026, shipping 2.2.19 in March after 2.2.18 in February. Boards a full version behind are still receiving attention.
The public discussion has meanwhile become an artifact in its own right. The status thread alone now runs past forty pages of replies.
So the practical answer for anyone deciding today is unglamorous. Buy or upgrade on 2.3, and treat 2.4 as a free improvement whenever it turns up.
The one group that should plan differently is add-on developers and the site owners who pay them. A database layer change and a new editor together mean custom code will need reviewing, and that bill arrives whenever 2.4 does rather than on a date anyone can put in a budget.
