PHP 8.2 End of Life (Dec 31, 2026): What WordPress Site Owners Need to Do

PHP 8.2 stops receiving security fixes on December 31, 2026, according to the official release schedule on php.net. After that date, new security flaws found in PHP 8.2 will not be patched by the PHP project. If your WordPress site runs on 8.2, move it to PHP 8.3 (security support until December 31, 2027) or PHP 8.4 (security support until December 31, 2028). Test the switch on a staging copy of your site first, then change the live site.

This guide is for business owners who got an email from their web host or saw a warning inside WordPress and want to know what to do. You don't need to be a developer to follow it. You will need your WordPress login and your hosting account login.

What Ends on December 31, 2026?

PHP is the programming language WordPress runs on. Your web host installs a version of it on the server, and your site uses whatever version the host has set for your account. Each PHP version gets a fixed support window from the PHP project. When the window closes, that version stops getting fixes.

Here are the PHP versions that are still supported, with dates from the official PHP supported versions page:

Active Support vs. Security-Only Support

According to php.net, each PHP version is fully supported for two years after release. During that time, reported bugs and security issues are fixed in regular updates. After that, the version gets two more years of fixes for critical security issues only, released as needed. PHP 8.2 has been in that security-only stage since its active support ended on December 31, 2024. On December 31, 2026, the security fixes stop too.

PHP 8.1 and Older Are Already Unsupported

The php.net end-of-life list shows PHP 8.1 reached end of life on December 31, 2025, with 8.1.34 as its last release. PHP 8.0 and 7.4 ended earlier. If your site shows any of these versions, this guide applies to you now, not in December. The PHP project's own advice on that page is that users of these versions are “strongly urged to upgrade to a current version.”

What Happens If You Stay on PHP 8.2

Nothing visible happens on January 1. Your site keeps loading. The change shows up the next time someone finds a security flaw in PHP 8.2: the PHP project won't release a fix. Some hosts keep patching older versions themselves for a while, so ask yours.

There is a slower problem too. Each plugin can declare the minimum PHP version it needs, according to the WordPress plugin handbook. As plugin makers raise that minimum past 8.2, new versions of your plugins stop supporting your server, along with any security fixes those versions include.

If your site already shows signs of trouble, such as strange redirects, spam pages showing up in Google, or a suspension notice from your host, deal with that before you change PHP versions. Our hacked website repair service cleans the site first so you aren't upgrading an infected copy.

How Do You Check Your Site's PHP Version?

It takes about a minute. There are two places to look.

In the WordPress Dashboard

1. Log in to your WordPress admin (usually yoursite.com/wp-admin).
2. In the left menu, go to Tools → Site Health.
3. Click the Info tab.
4. Open the Server section and find the line for the PHP version.

The Status tab on the same screen may also show a warning that reads “Your site is running an outdated version of PHP, which requires an update.” The WordPress Site Health documentation files that warning under security.

In Your Hosting Control Panel

Most hosts show the PHP version in the control panel, in a section with a name like PHP Version or PHP Settings. On hosts that use cPanel, it is often under MultiPHP Manager. This is also where you will change the version later, so it is worth finding now.

One hosting account can run different PHP versions for different websites, so check the version for your specific domain. If you can't find the setting, message your host's support: “Which PHP version is my site on, and which versions can I switch to?”

Some servers also announce their PHP version publicly. Our free website security check shows it if yours does, along with outdated WordPress and plugin versions.

What Can Break When You Upgrade PHP?

WordPress itself handles current PHP versions. The WordPress.org requirements page recommends PHP 8.3 or greater. Problems almost always come from the add-ons around WordPress. The WordPress core handbook makes the same point: “WordPress is rarely used in isolation (without any theme or plugins).”

The usual suspects on an older business site:

• Plugins that haven't been updated in years. The developer stopped working on them before newer PHP versions came out.
• Paid themes or plugins with an expired license. The fix may exist, but you haven't been able to download it.
• Custom code. Changes a developer added to your theme's functions.php file or a small custom plugin, often years ago.
• Old page builders. A builder version from several years back may not run cleanly on a newer PHP version.

A break can be loud or quiet. The loud kind is a blank page or the message “There has been a critical error on this website.” The quiet kind is worse: a contact form that looks fine but never sends, or a quote calculator that stops calculating. Nobody notices until the phone stops ringing.

Why Test on a Staging Copy First

A staging site is a private copy of your website, usually on the same hosting account. You change the PHP version on the copy and click through it while your real site keeps running for customers. If the copy breaks, nothing is lost and you know exactly which plugin to deal with. Many hosts include one-click staging in the control panel. If yours doesn't, a developer can set one up.

How to Upgrade PHP on a WordPress Site, Step by Step

Pick a slow weekday morning for this, not a Friday afternoon or the week your phones are busiest. Budget a couple of hours for a simple site and more if testing turns something up.

Step 1: Take a Full Backup

Back up both the files and the database, and keep a copy somewhere other than the server itself. Your host's backup tool or a backup plugin can do this. Before you move on, make sure you know how to restore that backup. A backup you can't restore doesn't help.

Step 2: Make a Staging Copy

Create the staging site from your hosting panel or with a staging plugin. Make sure the copy is hidden from search engines so Google doesn't index a duplicate of your site.

Step 3: Update Everything on Staging

Still on PHP 8.2, update WordPress, your theme, and every plugin on the staging copy. Delete plugins you no longer use. Many PHP problems are already fixed in the latest plugin version, so this step clears out a lot of false alarms.

Step 4: Switch Staging to PHP 8.3 or 8.4

In your hosting panel, change the PHP version for the staging site only. Start with 8.4, since it is supported a year longer. If it breaks something you can't fix quickly, try 8.3.

Step 5: Test the Pages and Forms That Bring in Work

• Homepage, one page of each type (service page, city page, blog post), and your contact page.
• Submit every form and confirm the email notification actually arrives.
• Booking widgets, quote calculators, and click-to-call buttons on a phone.
• Checkout or payments, if you take them online.
• The admin side: log in, edit a page, save it, and upload an image.
• Tools → Site Health → Status, to see whether any new warnings appear.

Ask your host or developer to check the PHP error log on the staging site too. Warnings there often point to the plugin that will cause the next problem.

Step 6: Switch the Live Site and Test Again

Once staging passes, update the plugins on the live site to match, take one more backup, and change the live site's PHP version. Run the same test list again. Check your form notifications again over the next few days.

How to Roll Back

If the live site breaks after the switch, go back to the same setting in your hosting panel and choose the previous PHP version. That undoes the PHP change without touching your content. If a plugin update caused the problem instead, restore the backup from Step 1. Then go back to staging and work out what failed before trying again.

What If a Plugin Blocks the Upgrade?

Testing sometimes turns up one plugin or theme feature that won't run on the newer PHP version. You have three ways to handle it.

Replace the Plugin

Look the plugin up on WordPress.org and check the “Last updated” date. If it hasn't been touched in years, it is unlikely to get a fix. Find an actively maintained plugin that does the same job, set it up on staging, and swap it in. For simple features like a contact form or a slider, this is usually the cheapest route.

Have a Developer Patch It

If the broken piece is custom code, or a plugin your site depends on with no good replacement, a developer can update the code for the newer PHP version. Some fixes are small. Others take longer, so ask for a quote after they have seen the error log from staging.

Consider a Rebuild When Most of the Site Is Abandoned

Some older sites fail in many places at once: an outdated theme, an old page builder, and several plugins with no developer behind them. Patching all of it buys time until PHP 8.3 or 8.4 reaches its own end of life, and then the same work comes back.

A rebuild can cost less over time than repeated patching. It can be a fresh WordPress build or a different platform. Our Next.js vs WordPress comparison for local service businesses covers when each one makes sense. Either way, protect the rankings you already have by following a website migration SEO checklist so your redirects and page URLs carry over.

Frequently Asked Questions

What to Do This Week

1. Check your PHP version under Tools → Site Health → Info → Server.
2. Ask your host what they plan to do about PHP 8.2 and whether staging is included.
3. Take a full backup and confirm you can restore it.
4. Book the staging test before December, so you have time to fix or replace a plugin if one breaks.