PHP 8.2 end of life: what it means for your WordPress site

PHP is the language WordPress runs on, and each PHP version only gets security fixes for a limited time. PHP 8.2 reaches end of life on 31 December 2026. After that, security problems found in PHP 8.2 itself are no longer fixed, whatever version of WordPress you run on top of it.

Many WordPress sites moved to PHP 8.2 a couple of years ago and have not changed since, so a lot of sites are affected. Here is what to do, in order.

Which PHP versions are supported?

WordPress itself recommends PHP 8.4 or 8.5 for new installations. WordPress 7 still runs on PHP versions as old as 7.4, but that is a compatibility floor, not a recommendation: running an unsupported PHP version is a risk WordPress cannot fix for you.

1. Check which PHP version your site uses

In your WordPress admin, go to Tools → Site Health → Info, open the Server section and look for PHP version.

You can also see it in your hosting control panel, or run our free site check, which shows it when your server makes it public.

If you are on 8.3 or newer, you have at least a year. If you are on 8.2 or older, read on.

2. Decide which version to move to

For most sites the best target today is PHP 8.4. It is what WordPress recommends, it has security fixes until the end of 2028, and most well-maintained plugins and themes support it.

If an important plugin or your theme is not ready for 8.4 yet, PHP 8.3 is a sound stepping stone: it is supported until the end of 2027.

3. Bring WordPress, plugins and theme up to date first

Most PHP upgrade problems come from old plugins and themes, not from WordPress itself. Before touching PHP:

• Update WordPress core to the latest release.
• Update every plugin and your theme.
• Delete plugins you no longer use, rather than just deactivating them.
• Look for plugins that have not been updated in over a year. These are the ones most likely to break, and the ones to replace.

Do this on a staging copy if your host offers one. Many do, often as a one-click option.

4. Switch PHP on a staging copy

On your staging site, change the PHP version in your hosting panel. On cPanel hosts this is usually under MultiPHP Manager or Select PHP Version. Then test the parts of the site that matter:

• The homepage and your most visited pages
• Contact and enquiry forms, including that the emails arrive
• Checkout and payments, if you have a shop
• Logging in and editing a page in the admin
• Anything built by a page builder, slider or booking plugin

Also turn on WordPress debug logging on staging and check the log for warnings and fatal errors after clicking around.

5. Fix what breaks

The usual fixes are:

• A plugin breaks: update it, or replace it with a maintained alternative.
• The theme breaks: update it. If it is a custom or abandoned theme, the incompatible code needs fixing, which is usually a small job.
• Custom code in functions.php breaks: older PHP code often uses features that newer PHP has removed. These are normally quick fixes once the error log points to them.

6. Switch the live site

When staging runs cleanly:

1. Take a full backup of files and database.
2. Switch the live site to the new PHP version at a quiet time.
3. Check the homepage, forms and checkout straight away.
4. Watch the error log for the next day.

If anything goes wrong, most hosts let you switch the PHP version back in seconds. That is your rollback.

What if my host switches PHP for me?

Some hosts move every site to a newer PHP version automatically when the old one reaches end of life. That is good for security, but it happens on their timetable, not yours. If your site has an old plugin or theme, it can break on the day. Doing the upgrade yourself, before the deadline, means you choose when it happens and you have tested it first.

Want it done for you?

We check your plugins, theme and custom code for problems, fix them on a staging copy, then switch PHP on the live site with a backup and a rollback ready. One fixed price, agreed before we start. See PHP upgrade, or start with a free site check.