WordPress Core Retires "Beta Support" Labels, Pushes PHP Adoption as WordPress.org Updates Recommendations
Last reviewed
30 September 2026
WordPress has been quietly clarifying and advancing PHP compatibility, signaling a growing push toward newer PHP versions. While the WordPress.org recommendations page still lists PHP 7.4+ as viable, the official minimum supported PHP version has quietly risen to 7.4 for WordPress 7.0. On the recommendation page, however, the latest version - PHP 8.3 or greater - is explicitly endorsed.
PHP 8.3+ Is The New Recommended Version
The official WordPress developers recently updated the requirements page to recommend PHP 8.3 or greater. While the 7.4 recommendation persists in legacy environments, newer PHP versions are fully recommended.
"We’ve added a requirement for PHP 8.3 or greater. This will ensure that WordPress can provide the best experience to users by allowing us to take advantage of all the new features and improvements in PHP 8.3+. At the same time, we recognize there are still users of older versions, and we’re committed to continuing to support those for the foreseeable future," says the requirements page.
However, WordPress's latest updates uphold older standards, with PHP 7.4+ stated as an entry-level compatibility requirement. This discord exists because the requirements page, geared to end users, remains legacy-friendlier. Publishers of end-user platforms, or those building software for other developers, are encouraged to embrace PHP 8.3+.
Beta Support and Compatibility Labels Are Retired
WordPress Core has retired the "beta support" and "compatible with exceptions" labels, clarifying their stance for PHP 7.4 as the official minimum supported version. However, they've retained their commitment to preserving backward compatibility for older environments.
The team announced the retirement of the "compatible with exceptions" and "beta support" labels in a May statement. "We are retiring the "compatible with exceptions" and "beta support" labels and removing them retroactively from all versions." Importantly, WordPress has kept the minimum supported PHP revision as 7.4 since April 2025.
PHP 8.1 and 8.2 were compatible with exceptions, and in earlier iterations of this policy, at least 10% of PHP usage needed to have predated a 3-month entry to the 'beta' tier. However, this was complex for contributing developers to conform to, and was associated with a slow adoption rate. So, the beta support model was opted out of.
What This Means for WordPress Publishers
For developers and publishers currently using PHP 7.4 and later, this is business as usual. WordPress continues to operate in this mode smoothly.
However, for a developer currently using PHP 7.3 or earlier, you should plan to upgrade to 7.4 if you haven't already. WordPress considers PHP 7.4 as the last in a succession of versions still officially pronounced 'deprecated' - and this is because of their retained formal backward compatibility.
More concretely, with WP 7.0, PHP 7.2 and 7.3 support will cease, with the new minimum officially rising to 7.4. Publishers of popular plugins and themes have already begun updating their PHP support conventions - 7.4 and later has become the new expectation, and an accelerated pace of adoption is likely.
WordPress 6.8, released in 2023, was the last version to officially support PHP 8.0, while WP 6.9, 7.0 and 7.1 expanded their compatibility further, to PHP 8.1 through 8.3. However, WordPress has clarified that the full PHP 8.4 and 8.5 supports depend on the underlying server's compatibility.
PHP Acquisition: What Should Publishers and Hosts Do
For plugin and theme publishers, it's crucial to embrace PHP 8.3 or newer if possible, and remain seated on top of PHP's progression path as it emerges. Publishing PHP requirements alongside official information is useful for end-users, expedites in-house testing, and enables building toward full compatibility before issues arise. Where consumers or contributors are still on PHP 7, communications targeted at encouraging upgrades are an opportunity.
For hosts, this puts you in a position where normalizing on PHP 8.3+ ought to be a priority. What about servers on versions below 8.3 - migrating them on time is required. Hosts should ensure they talk to consumers about new PHP changes, particularly propelling hosting partnerships through these evolutions.
As a publisher, upgrade to recommend PHP 8.3+, or higher where feasible, building outline of WordPress Core's updates. Ensure your server stack is upgraded to the latest - servers on older versions will fail to create a fully compatible WP site. Testing is an opportunity before upgrading the matter server-side.
As for hosts, migrate to recommend and use PHP 8.3+, or newer, proportionate to signs from WordPress Core. Your priority is indicated - a proactive migration and shutdown is a must. Share changes with end-users, deploy plugins for security and include consumer-facing materials to position the change.


