WordPress PHP Versions: Requirements, How to Check and How to Upgrade Safely

WordPress is written in PHP, so the PHP version your server runs affects your site's security, compatibility and speed. It is also one of the most neglected settings on business websites, because it lives in the hosting account rather than the WordPress dashboard.

As of October 2026, WordPress needs PHP 7.4 or later. That minimum was raised in WordPress 7.0 (20 May 2026), which dropped support for PHP 7.2 and 7.3. The official recommendation is PHP 8.3 or greater, and WordPress 7.1 is documented as fully compatible with PHP 7.4 through 8.5.

The catch is that "WordPress supports it" is not the same as "it is safe." PHP 7.4, 8.0 and 8.1 no longer receive security fixes from the PHP project, and WordPress supports them only for backward compatibility. Your plugins and theme also have to support the version you choose.

This guide covers the current requirements, how to check your version, how to test compatibility and how to upgrade without breaking your site.

Current WordPress PHP requirements

WordPress publishes two different numbers, and they are often confused.

• Minimum: the oldest PHP version WordPress will run on. According to the WordPress 7.1 hosting handbook page, the minimum is PHP 7.4, with MySQL 5.5.5 or MariaDB 5.5.5. WordPress 7.0 "raised the minimum PHP version from 7.2.24 to 7.4."
• Recommended: what WordPress.org suggests you actually run. The requirements page recommends PHP 8.3 or greater, MySQL 8.0 or greater (or MariaDB 10.11 or greater) and HTTPS support. The hosting handbook goes further and recommends PHP 8.4.x or 8.5.x for new installs.

Two common misunderstandings to avoid. First, WordPress 7.0 did not raise the MySQL minimum to 8.0; 5.5.5 is still the minimum and 8.0 is only recommended. Second, PHP 8.x is no longer labelled "beta support." In May 2026 the core team clarified that WordPress 6.9 and 7.0 fully support PHP 8.5 and retired the beta label.

Sites stuck on PHP 7.2 or 7.3 cannot update to WordPress 7.x. According to the core team's January 2026 announcement, they remain on the 6.9 branch. Only the newest branch officially receives security updates; fixes are backported to older branches as a courtesy when possible.

PHP version support status

The PHP project supports each version for about four years: two years of active support with bug fixes, then two years of security fixes only. The table combines the PHP project's supported versions page with WordPress's compatibility notes, as of October 2026.

If your site is on PHP 8.2, plan an upgrade now: its security support ends on 31 December 2026.

Why old PHP is a risk

• No security patches. Once a PHP version reaches end of life, newly found vulnerabilities in PHP itself are not fixed by the PHP project. Some hosts backport fixes, but you depend entirely on them.
• You get stuck on old WordPress. Every time WordPress raises its minimum, sites below it stop receiving new versions.
• Plugins move on. Plugin authors list a "Requires PHP" value on WordPress.org, and many now require newer versions. When an update needs a newer PHP than your server has, WordPress shows that it "does not work with your version of PHP" and will not install it, so you can end up stuck on an old, vulnerable plugin version. Plugins accounted for 91% of the 11,334 new WordPress ecosystem vulnerabilities Patchstack counted in 2025.
• Performance. Newer PHP versions include engine improvements. The size of the gain depends on the site, so test rather than expect a specific number.

Our WordPress security guide explains how PHP fits with the rest of your security setup.

How to check your PHP version

1. In the WordPress dashboard, go to Tools > Site Health.
2. Open the Info tab and expand Server. The PHP version is listed there.
3. The Status tab also flags an outdated PHP version as a recommended improvement.

WordPress.org's Update PHP page says that if you see PHP 8.3 or higher, no update is needed. You can also see the version in your hosting control panel, or with php -v over SSH, though the command-line PHP can differ from the version serving your website.

How to test compatibility before upgrading

PHP upgrades rarely break WordPress core. They break old plugins, old themes and custom code. Test before switching live:

1. Update everything first. WordPress.org's advice is to update WordPress, plugins and themes before changing PHP. Current versions are far more likely to support new PHP.
2. Check each plugin's "Requires PHP" and last-updated date on WordPress.org. A plugin not updated in years is the most likely problem.
3. Clone the site to staging and switch staging to the new PHP version. See our staging sites guide.
4. Turn on logging on staging with WP_DEBUG and WP_DEBUG_LOG, then click through the site: home page, forms, search, login, checkout and admin screens. Read the log for errors, warnings and deprecation notices.
5. Fix or replace anything that fails. Contact the developer, update custom code, or switch to a maintained alternative.

Static scanning tools can help, but use them with care. WordPress.org's Update PHP page mentions the PHP Compatibility Checker plugin. As of October 2026 its directory listing shows it tested only up to WordPress 6.4, so treat its results as a hint, not a verdict, and rely on real testing on staging. A quick alternative for a single plugin is to try it in WordPress Playground, which lets you choose the PHP version.

How to upgrade PHP

PHP runs on the server, so you change it through your host, not inside WordPress:

• Control panel: most hosts have a PHP version selector in cPanel, Plesk or their own dashboard.
• Managed WordPress hosts usually have a per-site PHP setting, and many upgrade PHP for you on a schedule, with notice.
• VPS or dedicated servers: you or your sysadmin install the new PHP version and switch the web server to it, including the extensions WordPress needs.
• No option available? Ask your host. If they cannot offer a supported PHP version, that is a strong reason to move. Our WordPress hosting types guide explains the options.

Treat a PHP change like any other platform upgrade, following the same discipline as version upgrades for CMS themes and plugins. Before switching live, take a full backup. Our WordPress backups guide explains what to include.

What to do if the upgrade breaks something

• Switch back. The quickest fix is to set PHP back to the previous version in your control panel. WordPress.org recommends this, or asking your host or a developer for help.
• Read the error. A "critical error" message usually comes with an email to the admin that names the failing plugin or theme, plus a recovery mode link. Our troubleshooting guide covers this.
• Isolate the cause on staging by deactivating plugins one at a time.
• Do not stay on the old version forever. Treat the rollback as temporary and fix the incompatible component.

PHP settings that matter besides the version

The version is not the only PHP setting that affects WordPress:

• Memory limit: WordPress tries to raise PHP memory to 40MB for single sites and 64MB for multisite by default, set with WP_MEMORY_LIMIT. Large sites, page builders and WooCommerce often need more, which your host's PHP limit must allow.
• Max execution time and upload size: these affect imports, backups and large media uploads.
• Extensions: WordPress relies on PHP extensions such as those for MySQL, image processing and encryption. Site Health lists missing recommended modules.
• OPcache: caches compiled PHP and is normally enabled by good hosts.

Conclusion

As of October 2026, WordPress requires PHP 7.4 or later, recommends 8.3 or greater, and fully supports up to 8.5. Because PHP 7.4 through 8.1 are end of life and 8.2's security support ends this year, most sites should be on 8.3 or newer. Check Site Health, update your plugins, test on staging, then switch. More guides live in our WordPress hub, and eSEOspace handles PHP upgrades as part of its website maintenance services.

Frequently asked questions