Table of Contents

PHP and WordPress in 2026: Upgrade the Runtime Without Breaking the Site

Originally published: November 26, 2020 · Last updated: August 17, 2026

The original version of this article introduced PHP 8 as something new. In 2026, that framing is obsolete. WordPress.org now recommends PHP 8.3 or greater, and WordPress 7.0 is documented as fully supporting PHP 8.5.

The practical question is no longer whether WordPress can use PHP 8. It is how to keep the site’s PHP runtime modern without discovering plugin incompatibilities on the live site.

Why PHP version matters

PHP executes WordPress on the server. Supported modern versions receive language and security improvements, while legacy versions eventually reach end of life. WordPress.org explicitly warns that old PHP versions may expose sites to security vulnerabilities.

WordPress compatibility is only one layer

A WordPress version can support a PHP release while one old plugin or theme does not. Real sites are combinations of core, extensions, custom code and hosting configuration. Test the whole stack.

Check the current environment first

Record the WordPress, PHP, theme and plugin versions before changing anything. Update supported plugins and themes, review known compatibility information and take a current backup that you know how to restore.

Test on staging when possible

Change the PHP version on a staging copy and inspect the front end, wp-admin, forms, ecommerce, scheduled tasks and integrations. Turn on appropriate logging so warnings or fatal errors can be diagnosed without exposing debug information to visitors.

Do not jump versions blindly

If a neglected site is several PHP generations behind, the fastest safe path may involve updating application code first, then changing PHP. The objective is to reach a supported modern version with a tested site, not simply select the highest number available in the hosting panel.

Know how to roll back

Before upgrading production, confirm that the hosting environment allows you to return temporarily to the previous PHP version if a critical incompatibility appears. Rollback is a recovery measure, not a reason to remain permanently on obsolete software.

Current WordPress baseline

WordPress.org currently recommends PHP 8.3+, MariaDB 10.11+ or MySQL 8.0+, and HTTPS. WordPress Core clarified in May 2026 that WordPress 7.0 fully supports PHP 8.5.

Bottom line

Keep PHP modern, but treat runtime upgrades as application changes. Back up, update dependencies, test the whole site on staging and have a rollback path before changing production.

Sources: WordPress requirements, WordPress Core PHP support clarification.