WordPress PHP Version: Which One to Use and How to Upgrade Safely

Your WordPress site runs on PHP, and the PHP version your host uses decides how fast your site is, how secure it is, and whether your plugins keep working. Many sites still run on a version that stopped getting security fixes years ago, simply because nobody checked.

This guide covers which PHP version WordPress needs in 2026, how to check yours, how to upgrade safely, and what to do if something breaks.

Which PHP version does WordPress need in 2026?#

According to the official WordPress requirements page:

• Recommended: PHP 8.3 or greater.
• Minimum: PHP 7.4. WordPress 7.0, released in May 2026, raised the minimum from 7.2 to 7.4 and dropped support for PHP 7.2 and 7.3.
• Supported up to: PHP 8.5, which the core team confirmed as fully supported in 2026.

The minimum is not a target. PHP 7.4 has been end of life since November 2022, which means no more security fixes. WordPress still runs on it only so that old servers do not break overnight.

PHP versions and their support status#

If your site is on PHP 8.2, it stops getting security fixes at the end of this year. That makes November a good time to move to 8.3 or 8.4.

How to check your PHP version#

In WordPress#

1. Go to Tools > Site Health > Info.
2. Open the Server section.
3. Look at PHP version.

Site Health also shows a warning on the Status tab when your PHP version is outdated. Our WordPress Site Health guide explains the other checks on that screen.

In your hosting panel#

Most hosts show the PHP version in cPanel (Select PHP Version or MultiPHP Manager), Plesk (PHP Settings) or their own dashboard. This is also where you change it.

With WP-CLI#

Run wp --info and look for the PHP version line.

Why upgrading PHP is worth it#

• Security. Old PHP versions no longer get security fixes. A flaw found tomorrow will never be patched.
• Speed. Each PHP 8 release is faster than PHP 7.4. Pages generate faster, which helps visitors and Core Web Vitals, especially on sites without full-page caching.
• Compatibility. Plugin and theme developers drop support for old PHP versions over time. Staying on an old version eventually blocks you from updating them, and outdated plugins are the main way WordPress sites get hacked. See our guide to WordPress vulnerabilities.

How to upgrade PHP safely#

Most PHP upgrades go fine. The ones that do not usually fail because of one old plugin or a custom theme. This routine catches that before visitors do.

1. Back up the site#

Take a full backup of files and database, stored off the server. Our WordPress backup guide covers how.

2. Update WordPress, plugins and themes first#

Newer versions of plugins are far more likely to support newer PHP. Update everything, then remove plugins you do not use. See how to update WordPress.

3. Check plugin compatibility#

On WordPress.org, each plugin page shows a Requires PHP value, and the changelog often mentions PHP 8 fixes. Be careful with plugins that have not been updated in over a year: they are the most common cause of PHP upgrade errors.

4. Test on staging#

Change the PHP version on a staging copy first. Click through the homepage, a few posts, forms, checkout if you sell online, and the admin screens you use most. Turn on debug logging (WP_DEBUG_LOG) and read wp-content/debug.log for warnings.

5. Upgrade one step at a time on live#

If you are far behind, for example on 7.4, consider moving to 8.1 or 8.2 first on staging, fixing anything that breaks, and then going to 8.3. Jumping several versions at once makes it harder to tell which change broke what.

6. Check the live site right after#

Load your key pages, submit a form, test checkout, and log into wp-admin. Then keep an eye on the site for the next few days, since some errors only appear on pages or actions you did not test.

What to do if something breaks after a PHP upgrade#

The most common symptoms are:

• "There has been a critical error on this website." WordPress caught a fatal PHP error. Check the email WordPress sends to the admin address, and see our guide to the WordPress critical error.
• A blank white page. See WordPress white screen of death.
• A 500 error. See 500 internal server error.
• One feature stops working, such as a form, a slider or a payment button, while the rest of the site looks fine. This is the hardest one to notice because nothing looks broken.

The quick fix is to switch PHP back to the previous version in your hosting panel. That takes a minute and gets the site working again. Then find the plugin or theme that caused it, usually from the error log, and update, replace or remove it before trying again.

Monitor the site after you change PHP#

A PHP upgrade can break a single page or button without taking the whole site down, and uptime monitors will not notice. MyKavo checks your important pages against an approved baseline and alerts you when a page starts returning errors, a checkout or signup button disappears, or the layout changes. If you run WordPress, the free MyKavo plugin also tells you which plugin, theme, core or PHP change happened right before the problem.

Frequently asked questions#