WordPress and PHP 8.5 Compatibility: Official Support and Safe Testing

WordPress Core now documents PHP 8.5 support for WordPress 6.9 and 7.0. That is the correct starting point for an upgrade decision.

It is not a certification of every theme, plugin, WooCommerce extension, payment integration, server module, or custom function on a real site.

Official support boundary

The WordPress Core PHP compatibility matrix lists:

WordPress first prepared PHP 8.5 support in 6.9. In May 2026, the project retired the older beta-support label and documented 6.9 and 7.0 as fully supporting PHP 8.5.

Check the live matrix before upgrading; the table can change after this article’s review date.

What “supported” does not mean

Core support means the WordPress project tests and documents its own code for the PHP branch. A production site also includes:

• a theme and possibly a child theme;
• standard and must-use plugins;
• page builders and add-ons;
• WooCommerce and its payment, shipping, tax, subscription, and checkout extensions;
• custom snippets and integrations;
• PHP extensions and host configuration;
• scheduled jobs, queues, imports, and backups.

One incompatible component can still break a critical flow. Claims such as “50 sites with zero fatal errors” require a published inventory, versions, test matrix, dates, and logs. This article does not make that claim.

PHP 8.5 staging checklist

1. Update WordPress, maintained themes, and maintained plugins on staging.
2. Confirm that every critical vendor supports PHP 8.5 or provides a testable release.
3. Back up files and database and verify the host’s PHP rollback.
4. Switch staging to PHP 8.5 with the same required extensions as production.
5. Test public templates, admin editing, media, search, forms, logins, emails, APIs, webhooks, and scheduled jobs.
6. For commerce, test product variations, cart, checkout, tax, shipping, payment callbacks, order emails, refunds, and subscriptions where used.
7. Review PHP, WordPress, server, and application logs for fatals, warnings, and deprecations.
8. Deploy in a monitored window and repeat the critical checks.

PHP 8.5 versus PHP 8.4

PHP 8.5 has a later upstream support runway because it is newer. That does not make it the best immediate branch for a plugin stack that has not passed testing.

Use PHP 8.4 temporarily when WordPress supports it, the branch remains supported upstream, and a documented component blocks 8.5. Use the PHP 8.4 compatibility guide for that boundary, and keep an owner and review date for the eventual move.

If you are moving up from PHP 8.2, whose security support ends on 31 December 2026, the PHP 8.2 end-of-life upgrade plan covers backups, staging, testing and rollback for the whole move.

The evergreen recommended PHP version guide explains how to select a production branch. The correct conclusion is conditional: PHP 8.5 is supported by WordPress 6.9 and 7.0, but your complete site must still prove it is ready.