WordPress 6.9 and 7.0 now fully support PHP 8.5, and WordPress core dropped the old “beta support” label for it back in May 2026 — but that doesn’t automatically make 8.5 the right choice for a production WordPress site today. PHP 8.4 remains the recommended production version as of August 2026, and the reason isn’t about WordPress core at all — it’s about the plugin ecosystem sitting on top of it.
Short answer: for most live WordPress sites in 2026, run PHP 8.4. Move to PHP 8.5 on new builds with a small, actively maintained plugin stack, or once every plugin you depend on confirms 8.5 support. Both versions are supported by WordPress core; the difference is how well-tested your plugins are on each.
What Actually Changed
| PHP Version | WordPress Support Status | Security Patches Through |
|---|---|---|
| 8.4 | Fully supported since WordPress 6.8 | December 2028 |
| 8.5 | Fully supported since WordPress 6.9/7.0 (documented May 2026) | December 2029 |
WordPress 7.0, released May 20, 2026 following the 6.9 security patch cycle, confirmed full PHP 8.4 compatibility while adding PHP 8.5 support at the same time. Core itself is ready for both.
PHP 8.4 vs 8.5: what is actually different
PHP 8.4 was released in November 2024 and PHP 8.5 in November 2025. Neither is a big rewrite like the jump from PHP 7 to 8, so you should not expect a dramatic speed change between them. The differences are mostly new language features for developers, plus a few deprecations that can affect older plugins.
New in PHP 8.4
- Property hooks and asymmetric visibility (for example, a property that is public to read but private to write).
- New array helpers:
array_find(),array_find_key(),array_any()andarray_all(). - A standards-compliant HTML5 parser (
Dom\HTMLDocument), lazy objects, and a#[\Deprecated]attribute. - Deprecated: implicitly nullable parameter types. Older plugins trigger deprecation notices for this, which is harmless but noisy if debug logging is on.
New in PHP 8.5
- The pipe operator (
|>) for chaining function calls. - A built-in URI extension for parsing URLs safely, and
array_first()/array_last(). - Clone with (changing properties while cloning), the
#[\NoDiscard]attribute, and stack traces for fatal errors, which makes debugging a white screen easier. - Deprecated: the backtick shell operator and non-canonical cast names such as
(integer)and(boolean). Old or abandoned plugins are the most likely to still use these.
For a site owner, the practical takeaway: none of these features make your site faster or safer on their own. What matters is whether your plugins and theme run cleanly on the version you choose.
Why 8.4 Still Wins for Production
The gap isn’t in WordPress core — it’s in the plugin and theme ecosystem’s own testing coverage. PHP 8.4 has had more time in the wild, meaning more plugins, themes, and custom code have actually been run against it and had their edge cases found and fixed. PHP 8.5, despite being officially supported by core, simply hasn’t accumulated the same real-world mileage across the tens of thousands of third-party plugins a typical WordPress site depends on. “Officially supported by core” and “safe to run every plugin you have on” are two different claims, and the second one takes longer to become true in practice.
The Longer-Term Case for 8.5
PHP 8.5’s security support runs a full year longer than 8.4’s (December 2029 vs. December 2028), which matters for planning an upgrade timeline rather than for today’s decision — a fresh site build with minimal, well-maintained plugins is in a much better position to go straight to 8.5 than an older site carrying a long plugin history.
How to check and change your PHP version
- Check what you run now. In wp-admin go to Tools › Site Health › Info › Server. The PHP version is listed there. Site Health also warns you if your version is outdated.
- Copy the site to staging and switch the staging copy first. Most hosts let you pick the PHP version per site in their control panel (for example cPanel’s MultiPHP Manager, Plesk’s PHP Settings, or the host’s own dashboard).
- Test the pages that make you money: checkout, contact and quote forms, login, search, and any page built with a page builder. Turn on
WP_DEBUG_LOGon staging and readwp-content/debug.logfor new warnings. - Switch production at a quiet time, with a fresh backup, and check the same pages again. If something breaks, switching back takes a minute in the same control panel.
How to Decide for Your Site
- Check plugin compatibility notices in your plugin changelogs specifically for PHP 8.5 mentions — if your core plugins haven’t confirmed it, that’s a strong signal to wait.
- Test on staging before touching production, regardless of which version you’re moving to — this applies to any PHP version bump, not just 8.5 specifically.
- New builds with a lean, actively-maintained plugin stack can reasonably target 8.5 now for the longer support runway.
- Established sites with a large plugin footprint are generally better served staying on 8.4 through 2026, reassessing again as 8.5 compatibility data accumulates.
Always test a PHP version change on a staging environment first — see WordPress Staging Sites: How to Test Changes Safely Before You Publish. Want your site’s PHP compatibility checked before upgrading? Get in touch.
Need the upgrade done for you? We test WordPress and WooCommerce sites on the new PHP version in staging, fix incompatible plugins and switch production with a rollback plan. Ask for a PHP upgrade quote.
Frequently Asked Questions
Does WordPress core actually support PHP 8.5 now?
Yes — WordPress 6.9 and 7.0 are documented as fully supporting PHP 8.5 as of May 2026. The caution around 8.5 is about third-party plugin compatibility, not WordPress core itself.
Is staying on an older PHP version like 8.2 or 8.3 safe?
Not for long-term production use — older PHP versions eventually lose security support entirely, which is a bigger risk than the plugin-compatibility caution around a very new version like 8.5.
How do I know if my specific plugins support PHP 8.5?
Check each plugin’s own changelog and support forum for explicit PHP 8.5 compatibility statements, and test on a staging copy of your site before changing production.
Which PHP version should I use for WordPress in 2026?
PHP 8.4 for most existing sites; PHP 8.5 for new builds with a lean plugin list, or once your plugins confirm support. Avoid anything older than PHP 8.2 on a live site, because it is close to or past the end of security support.
Is PHP 8.5 faster than PHP 8.4 for WordPress?
Not in a way most visitors would notice. The 8.4 to 8.5 change is about language features and fixes, not a large performance jump. Caching, hosting and plugin choice affect your speed far more.
How do I check which PHP version my WordPress site uses?
Go to Tools › Site Health › Info in wp-admin and open the Server section. Your hosting control panel shows it too.