You switched PHP on your hosting, and the site went down with a white screen. Sound familiar? Since 2020, thousands of WordPress site owners have been through this scenario as hosts began mass-disabling PHP 7.4 while the plugin ecosystem hadn't yet caught up with version 8.

Now it's mid-2026, and the landscape has changed dramatically. The WordPress Core team officially removed the "beta compatibility" label for all PHP 8.x versions, from 8.0 to 8.5. The minimum recommended version has risen to PHP 8.3, and WordPress 6.9 and 7.0 fully support PHP 8.5. If your site still runs on 7.4 or 8.0, you're losing not only security but also the noticeable performance gains that newer language versions provide.

Let's break it down without fluff: which PHP versions are current for WordPress today, why "beta" is a thing of the past, and how to update without breaking a single plugin.

💡 Quick overview:

• The minimum recommended PHP version for WordPress in 2026 is 8.3, and WP 6.9 fully supports PHP 8.5 (source)
• The "beta compatibility" label was officially removed in May 2026; all PHP 8.x versions now have full support
• Safe update plan: backup → staging copy → plugin check → update → verification
• PHP 7.4, 8.0, and 8.1 no longer receive security patches; continuing to use them is risky

How WordPress arrived at full PHP 8 support

The journey took almost six years. WordPress 5.6, released in December 2020, became the first version with declared PHP 8.0 compatibility. But the team immediately designated the status as "beta," and for good reason. The core worked, but the ecosystem of tens of thousands of plugins and themes remained unpredictable. The create_function() function, removed in PHP 8.0, was used in more than 5,500 plugins at that time, according to Wordfence estimates.

The key shift happened in 2023 when WordPress adopted quantitative criteria for removing the beta label: it remained in place until usage of a specific PHP version exceeded 10% on the corresponding WordPress version. By spring 2026, the number and severity of incompatibility reports had dropped so much that the label was removed entirely, retroactively for all PHP 8.x versions.

Today the situation is clear-cut: WordPress 6.4 and newer fully support PHP 8.3, versions 6.8+ support PHP 8.4, and 6.9 and 7.0 support PHP 8.5. No more "beta" or "with exceptions."

Which PHP versions work with WordPress in 2026

The official WordPress requirements page defines three support levels. Here's the current picture as of June 2026:

Important note: PHP 8.2 reaches EOL on December 31, 2026. If your host offers "PHP 8.2" as the maximum, in six months you'll be left without security updates. Demand 8.3 or 8.4.

Why you should update right now

Three reasons that justify an hour of system administrator work.

Security. PHP 7.4 hasn't received patches since November 2022 (four years without protection). Any vulnerability discovered after that date remains an open door on your server. PHP 8.0 has been unsupported since November 2023. According to W3Techs data from June 2026, about 15% of WordPress sites still run on PHP versions without security support. That's hundreds of thousands of potentially vulnerable installations.

Performance. PHP 8.0 introduced the JIT compiler, and versions 8.1-8.4 brought a cascade of opcode optimizations, preloading, and typing improvements. In practice, moving from 7.4 to 8.3 delivers a 30-50% speed increase on a typical WordPress site without any code changes, according to benchmark measurements. For WooCommerce stores with hundreds of products, the difference is even more noticeable: lower page generation time means higher conversion.

Compatibility. Plugin developers are already testing on PHP 8.3 and 8.4 as their minimum versions. New releases of popular plugins may simply not run on PHP 7.4, leaving you without functionality updates on top of missing security patches.

What breaks when updating PHP and how to check

The main source of problems is removed functions. PHP 8.0 cut several dozen deprecated calls, including create_function(), each(), and money_format(). PHP 8.1 tightened typing: passing null to a non-nullable parameter became a fatal error instead of a warning. PHP 8.2 continued cleaning up dynamic properties, and 8.4 finally removed E_STRICT.

Practical takeaway: if your plugin or theme hasn't been updated since 2020-2021, the risk of incompatibility is high. But there are diagnostic tools.

First, the iron rule: create a backup before any actions. Then there are two paths for verification.

Path one: PHP Compatibility Checker. Install the plugin of the same name from the WordPress.org directory. It scans the code of your active theme and plugins and shows incompatible calls with the file and line number. It's not perfect (it can't see runtime problems), but in five minutes it gives you a map of the minefield.

Path two: staging copy. Create a copy of your site on a subdomain using your host's tool or a plugin like WP Staging. Switch PHP to the target version and go through all key pages: homepage, products, cart, forms, admin panel. Whatever breaks, fix or replace.

How to safely update PHP: step-by-step plan

A sequence of actions proven on dozens of sites. Each step takes minutes but saves hours of recovery.

Step 1: full backup. Files and database. Not "the host's auto-backup from last week," but a manual backup right now. Most hosts provide a button in the control panel. As a fallback, the UpdraftPlus plugin: five minutes to install and run.

Step 2: update WordPress, your theme, and all plugins to the latest versions. Fresh releases are most likely to already account for new PHP version specifics. If a plugin is abandoned and hasn't been updated in over a year, decide whether you need it before switching to the new PHP. A replacement can be found almost always.

Step 3: create a staging copy. Switch PHP on it to the target version (8.3 or 8.4) and test the site. Go through all critical pages. Fifteen minutes of testing now versus hours of emergency recovery later.

Step 4: on the production site, switch PHP in the hosting panel. Usually this is the "PHP Settings" or "Select PHP Version" section in cPanel / DirectAdmin / ISPmanager. After switching, open the site in incognito mode and check: homepage, an internal page, contact form, admin panel.

Step 5: enable logs for 48 hours. Add to wp-config.php:

1
define( 'WP_DEBUG', true );
2
define( 'WP_DEBUG_LOG', true );
3
define( 'WP_DEBUG_DISPLAY', false );

The wp-content/debug.log file will show errors that didn't appear during surface-level checking. After two days, if the log is empty or contains only notices, disable debug mode and work in peace. If there are fatal errors, you know which plugin is at fault and can replace it precisely.

⁉️🤔 Frequently asked questions

Do I need to update PHP if my site works fine?

Yes, and the longer you delay, the higher the risk. Versions without security support don't receive patches. Your host may force-disable PHP 7.4 at any moment, and the site will simply stop opening (you'll learn about it from visitors). Over four years without patches (since November 2022), an impressive list of known vulnerabilities has accumulated that nobody is fixing on PHP 7.4.

Which PHP should I choose: 8.3 or 8.4?

If your host offers both, go with 8.4. It's faster and will receive patches until December 2028. PHP 8.3 is the minimum recommended option if 8.4 isn't available. The performance difference between them is noticeable under typical WordPress workloads, so there's good reason to go higher.

What should I do if the site shows a white screen after updating PHP?

Enable WP_DEBUG (step 5 above); the log will show the exact error and file. In the vast majority of cases, the problem is one outdated plugin. Disable plugins via FTP: rename the /wp-content/plugins/ folder to /plugins-off/, and the site will come back to life. Then enable plugins one by one to find the culprit and replace it with a current alternative.

Does WordPress update PHP automatically?

No. PHP is server software configured at the hosting level. WordPress can only recommend a version through Site Health in the admin panel, but the actual switch is done by you or the hosting support team.

Can I skip the update and stay on PHP 7.4?

Technically yes, until your host force-disables the old version. But since November 2022, this version hasn't received security fixes. Every month without updating is like playing Russian roulette: you don't know which vulnerability has already been found and is being exploited.

PHP and WordPress in 2026: what to install and when to update

The short verdict: PHP 8.4 for most sites, PHP 8.3 as the absolute minimum. Moving from 7.4 not only closes security holes four years old but also delivers a noticeable speed boost, according to measurements, from 30% on a regular site to 50% on a heavily loaded WooCommerce store.

The main rule: don't skip the backup and staging testing step. Ten minutes for a copy saves hours of recovering a crashed site. Check plugins before updating PHP, not after, and the process will go without surprises.

If your host still doesn't offer PHP 8.3, that's reason to seriously consider switching hosts. In 2026, support for current PHP versions is a basic hygiene requirement, not a competitive advantage.