PHP 8.2 support ends in December. Now what?
WordPress is written in PHP, and your site runs on whichever PHP version your server has installed. Like all software, each PHP version is only supported for a set time. On 31 December 2026, PHP 8.2 reaches the end of its security support. After that, when a vulnerability is found in it, no fix will come.
If your site runs on PHP 8.2 or anything older, now is the time to plan the upgrade, not January.
How PHP support works
Under PHP’s current policy, each release gets two years of active support, with bug and security fixes, followed by two more years of security fixes only. Then it reaches end of life. Here’s where recent versions stand:
| Version | Security fixes until |
|---|---|
| PHP 7.4 | Ended November 2022 |
| PHP 8.0 | Ended November 2023 |
| PHP 8.1 | Ended 31 December 2025 |
| PHP 8.2 | 31 December 2026 |
| PHP 8.3 | 31 December 2027 |
| PHP 8.4 | 31 December 2028 |
| PHP 8.5 | 31 December 2029 |
The official dates are on php.net’s supported versions page.
Some hosts and Linux distributions keep patching older versions themselves, so it’s worth asking yours. Don’t rely on it, though. Many don’t, and plugin authors stop supporting old versions either way.
Why it matters, even if nothing’s broken
- Security. Vulnerabilities found in an end-of-life version stay open. The site can be fine today and exposed next month.
- Plugins move on. Plugin and theme authors raise the minimum PHP version they support over time. Stay on an old version and eventually you can’t install their updates, including their security fixes.
- Speed. Newer PHP versions generally run WordPress faster, without changing a line of your site’s code. It’s often the first step in speeding up a site.
- Hosts force the issue. Many hosts upgrade old versions automatically, or charge extra to keep them. An upgrade you didn’t plan is the kind that breaks things on a Saturday.
Which version are you on?
In WordPress, go to Tools → Site Health → Info and open the Server section, which lists the PHP version. Your hosting control panel shows it too, and usually lets you change it.
If you use the command line, be careful with php -v. It shows the version the command line uses, which isn’t always the one serving your website. Site Health shows the one that counts.
Upgrading without breaking anything
Most sites move from PHP 8.1 or 8.2 to 8.3 or 8.4 without trouble. The ones that break usually have an old theme, an abandoned plugin, or custom code written years ago. Here’s the order we do it in:
-
Update everything else first. WordPress, the theme and every plugin, on the current PHP version. Many compatibility fixes are sitting in updates that haven’t been installed yet.
-
Make a staging copy of the site on the same kind of server, and switch only the staging copy to the new PHP version.
-
Turn on error logging on staging, so warnings are written to a log file instead of hidden:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); -
Click through everything that matters: the homepage, forms, search, logins, the checkout with a test payment, and the admin screens your editors use. Then read
wp-content/debug.log. -
Fix or replace what breaks. A “deprecated” notice is a warning about the future. A fatal error needs fixing now, by updating the plugin, replacing it or correcting the custom code.
-
Switch the live site at a quiet time, straight after a fresh backup, and keep the old PHP version available so you can switch back quickly.
-
Watch the error log for a few days afterwards. Some code only runs on a schedule, like a nightly import or a monthly invoice run.
Which version to aim for? The newest one that all your plugins support. For most WordPress sites today, that means PHP 8.3 or 8.4, which get security fixes until the end of 2027 and 2028.
When the upgrade reveals a bigger problem
Sometimes testing shows the theme itself can’t run on any supported version, and fixing it would mean rewriting most of it. That’s a sign it’s time to think about what comes next, and rebuild or tune-up? can help with that decision. In the meantime, don’t leave the site as it is: ask your host about extended security support for the old version, and put a firewall in front of the site.
PHP upgrades, tested on staging before they reach your live site, are part of our server management work.