Managed WordPress Hosts Begin Defaulting to PHP 8.3, Urging Upgrades for Legacy Plugins

10 October 2026

As of 2026, the landscape of WordPress hosting is shifting to prioritize PHP 8.3 as the new standard, propelled forward by WordPress' recommendation and the proactive moves of major hosting providers. However, while the hosts push PHP forward, site owners need to be vigilant about legacy plugins that won't come along for the ride.

PHP 8.3 is now the recommended version

PHP 8.3 became the new minimum recommended PHP version in a WordPress Core blog post last May, with beta support in WordPress 6.4 and full support in all later versions. This aligns with WordPress' push for compatibility with newer PHP versions to boost performance and security.

WordPress.org's Requirements page still lists PHP 7.4 as the minimum, while their Recommended Requirements page specifies 8.3. Their Support page notes that sites on PHP 8.3 don't require an immediate update, creating a key decision point for those running older versions.

Converging Standards

Kinsta led the shift among major WordPress hosts by making PHP 8.3 the default in November 2023. They now support up to PHP 8.5. WP Engine and Cloudways currently default to 8.2 for new sites, with 8.3 and 8.4 available as opt-in upgrades. GoDaddy's Managed WordPress Hosting supports PHP 8.1 through 8.3.

Site owners shouldn't delay upgrades, with PHP 8.2's end-of-life arriving December 31, 2026. PHP 7.4 follows on September 26, 2027, with 7.3 on December 6, 2027. Delaying upgrades means missing significant performance improvements.

Legacy plugins will be left behind

The core challenge remains outdated plugins. Incompatible plugins frequently cause WordPress sites to break during PHP version updates, especially those unmaintained for years. This legacy code represents both the biggest risk and the most frustrating challenge.

A year and a half ago, major hosts offered limited PHP 8.3 access due to these risks. While availability has improved through education and plugin updates, troubleshooting windows remain - including time to prompt plugin authors for updates.

Prepare with a compatibility audit

Site owners should create a structured upgrade plan: verify current PHP versions, inventory outdated plugins, run compatibility scans, then test the new PHP version in staging before going live. Skipping this audit invites problems ranging from readability issues to deprecated functions.

For owners constrained by critical but outdated plugins, hosts like Kinsta and Cloudways still offer PHP 8.2 as a temporary option. Enterprise-focused platforms like Pantheon and Acquia support wider PHP version ranges, but may lack specific upgrade assistance.

The middle ground involves neither clinging to outdated packages nor hastily adopting new PHP versions when plugins break. A thorough audit comes first - the worst outcome is merely that proactive maintenance takes longer than letting the host dictate the timeline.