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.
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.
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 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.
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.
Featured image: original illustration.