PHP 8.2 reaches end of life on December 31, 2026. That gives sites running on it just under three months of security patches before free updates stop. We're writing this now because the last two weeks of December are a bad time to be rushing a server level change, and most of our clients are on WordPress or Joomla, where the PHP version is often set once and forgotten.
If you don't know what version your site runs on, that's probably where this article is most useful. We'll walk through what the end of life date changes, what WordPress and Joomla need right now, what tends to break when you upgrade, and a short plan to get it done before the holidays.
What's Happening on December 31, 2026
PHP is the programming language that runs most of the web, including WordPress and Joomla. The PHP project releases a new major version each November, and each version gets about four years of support: two years of bug fixes, then two years of security patches only. After that, the version is done.
PHP 8.2 came out in December 2022. It stopped getting bug fixes on December 31, 2024, and has been in security-only mode since. On December 31, 2026, that stops too. The last release at time of writing was 8.2.34 on September 22, 2026, and there may be one or two more before year end.
After that date, any new security hole found in PHP 8.2 doesn't get patched by anyone official. Your site still runs. It just runs on a version attackers have a growing list of ways to break. You can see every PHP version's dates on the official PHP supported versions page.
Where WordPress & Joomla Stand
WordPress is more permissive about PHP than Joomla is. Its official recommendation sits at PHP 7.4 or higher, and the WordPress Hosting Handbook pushes developers toward PHP 8.2 or 8.3. In practice, running anything below PHP 8.0 in 2026 means a lot of plugin and theme shops have stopped testing against your version. If something breaks, you're often on your own.
Joomla is stricter. Joomla 5 asks for a minimum of PHP 8.1 and Joomla 6 requires PHP 8.3, with 8.4 recommended. Joomla 6 launched on October 14, 2025, and Joomla 4 reached end of life the same day. If you're still on Joomla 4, you're already past due for two upgrades.
What we'd recommend to a client in October 2026 is PHP 8.3 or 8.4. Both are actively supported, both are mature enough that the plugins have caught up, and 8.4 keeps getting security patches all the way through December 2028. 8.3 gets you to December 2027.
Jumping straight to 8.5 is fine too, but it's new enough that we'd want to test more carefully before putting a client site on it.
What Usually Breaks
Most PHP upgrades on a well maintained WordPress or Joomla site go through without issue. The ones that bite us tend to have one of these problems:
- An abandoned plugin or extension that hasn't been updated in two or three years (these sometimes work fine on newer PHP and sometimes throw fatal errors). There's no reliable way to tell without testing.
- Custom code written for an older build, usually a few hundred lines in a child theme or a custom module, using functions or syntax PHP has since deprecated.
- A commercial plugin on an expired license. Ie - the current version supports PHP 8.3, but the client's copy is three years old and the license lapsed in 2024.
- Older eCommerce stacks, where payment or shipping addons were never updated past PHP 8.0 and the vendor is AWOL.
None of these are hard to find on staging. They ARE painful to find on a live site the day before year end, though.
A Plan For Q4 2026
If you want to do this calmly, you still have time. Here's roughly what we'd do if the site were ours.
Right now, check what PHP version the site runs on. In WordPress, go to Tools, then Site Health, Info, Server. In Joomla, it's on the System dashboard under System Information. Write down the number, along with your WordPress or Joomla version and the hosting provider. If you're already on 8.3 or 8.4, you're done for this cycle. Come back in about a year for 8.3's deadline.
In October, take an inventory of plugins and extensions. For each one, note the last update date and the highest PHP version it's been tested against. Anything untouched since 2023 goes on a short list to replace or remove. If the site runs any custom code, get a developer to run it through a PHP compatibility checker. There are free scanners for both WordPress and Joomla that will flag most of the deprecated calls automatically.
In November, clone the site to staging, switch staging to PHP 8.3 or 8.4, and work through the error log. Fix what breaks. Test the forms, the checkout, the admin screens and anything running on a cron job. Give it a week of real use before trusting it on live.
Early December, run the upgrade on production during a quiet window, with a known-good backup ready to restore. Keep staging around for another couple of weeks in case something odd surfaces after the switch.
Leave the last two weeks of December alone. That's holiday coverage, change freezes and family time. If you work backwards from December 31, you've built in a buffer.
Not sure what PHP version your site runs on?
We'll check your site, tell you what version you're on, flag anything that could break on PHP 8.3 or 8.4, and give you a plan to use.
About Your Host
Some hosts upgrade PHP for you automatically. Some don't touch it until you ask. A few will quietly move you to a new version in January and then help you clean up the mess. Ask your host, in writing, what they plan to do with PHP 8.2 sites after December 31.
If your host doesn't offer PHP 8.3 or 8.4 at all in 2026, that's a bigger conversation than we're covering here. We've helped clients move hosts for less, and we'd rather have that conversation in October than in a panic. If you're not sure where to start, our our team runs this kind of upgrade for clients every month, and we're happy to look at your site before you commit to a plan.
None of this is urgent in the "drop everything" sense. It's urgent in the "put it on the calendar before November" sense. The sites that get caught out at year end are almost always the ones where nobody checked what version they were on until something suddenly stopped working.
