Originally published at https://monstermegs.com/blog/wordpress-hosting-php-requirements/
If your hosting environment still defaults to PHP 7.2 or 7.3, you have fewer than 30 days before that becomes a live problem. WordPress 7.0 officially launches on May 20, 2026, and the updated WordPress hosting PHP requirements for this release set a hard floor that every site owner, developer, and hosting provider needs to act on now. The WordPress hosting PHP requirements are not a soft advisory – they are technical cutoffs that will block upgrades outright on non-compliant stacks.
The WordPress core team confirmed the May 20 date after an extended review period pushed the original April target back by several weeks. The delay addressed unresolved issues with the new real-time collaboration feature, but it changed nothing about the infrastructure demands the release carries. With the window narrowing, this is the moment to confirm where your stack actually stands.
WordPress 7.0 Locks In a Hard May Launch Date
On January 9, 2026, the Make WordPress Core team published a formal notice dropping support for PHP 7.2 and PHP 7.3 with the 7.0 release. The post was authored by core contributors and converted what had been anticipated for months into a firm technical commitment. The WordPress hosting PHP requirements announcement drew immediate attention from hosting providers who had been keeping those legacy versions available for compatibility reasons – and who now had a fixed date against which they needed to act.
The scale of the problem is documented. According to endoflife.date, which tracks official support timelines for major open-source runtimes, PHP 7.2 lost all security support in November 2020 and PHP 7.3 followed in December 2021. Shared hosting providers who kept those versions available as opt-in options have effectively been running customers on unpatched software for years. WordPress 7.0 draws a line: sites hosted on PHP 7.2 or 7.3 that attempt to upgrade on or after May 20 will fail before the upgrade process can begin.
What the WordPress Hosting PHP Requirements Mean for Your Site
The WordPress hosting PHP requirements for version 7.0 have two tiers that carry very different practical meanings. The minimum supported version is PHP 7.4, which is the floor below which WordPress 7.0 will refuse to run. The recommended version is PHP 8.3, which is where the platform's performance and security posture are fully realised. Understanding your position on that spectrum matters because the two tiers are not equally acceptable for a production environment.
PHP 7.4 itself reached end of life in November 2022. Running a site that meets the WordPress hosting PHP requirements at the minimum level means running WordPress 7.0 on a PHP version that has had no security patches for over three years. The site will technically work, but the PHP layer below it remains exposed. That gap between the minimum and the recommended version is where most of the real-world risk lives for sites that scramble to comply before May 20 without thinking through what version they are actually upgrading to.
Why PHP 8.3 Is the Practical Target
PHP 8.3 remains in active support through late 2027 and delivers measurable performance gains over the entire 7.x branch. For WordPress sites running WooCommerce, Elementor, or other resource-intensive plugins, PHP 8.3 typically produces lower server response times and reduced memory overhead compared to PHP 7.4 or even PHP 8.0. Meeting the WordPress hosting PHP requirements at the 8.3 level rather than the 7.4 floor aligns the PHP lifecycle with where WordPress is pointing: WordPress.org already lists PHP 8.3 as the officially recommended runtime on its requirements page. The case for targeting 8.3 now rather than the minimum is that you will not need to revisit this again for several years.
The Database Requirements Are Changing Too
PHP is not the only dependency changing with WordPress 7.0. Alongside the WordPress hosting PHP requirements, the database minimum is also moving up – to MySQL 8.0 or MariaDB 10.6. Previous releases would run on MySQL 5.5.5, a version Oracle stopped supporting years ago. Modern hosting stacks should clear this threshold easily, but budget shared environments or legacy managed database instances may not, and customers on those stacks will encounter upgrade errors that look unrelated to PHP.
This detail gets less coverage than the PHP change but carries equal weight for providers managing large fleets of shared hosting accounts. A server that clears the PHP check but fails the database check will still block a WordPress 7.0 upgrade. Site owners preparing for May 20 should confirm both the PHP version and the database version before attempting the upgrade – one check does not cover the other.
Why Outdated PHP Persists Across Shared Hosting
The WordPress hosting PHP requirements gap between where the platform is heading and where much of the industry sits reflects a long-standing operational tension rather than pure negligence. When a provider pushes a default PHP version change across an entire shared hosting fleet, some percentage of older sites built against deprecated functions will break. Legacy themes from 2016, custom code written against PHP 5.x syntax, and abandoned plugins that have not been updated in years can all generate fatal errors on a modern PHP runtime. The path of least resistance for providers has been to keep old PHP versions available as manual opt-ins and allow inertia to carry forward.
The Cost of Doing Nothing Has Changed
The calculus on that approach is visibly shifting. PHP 8.1 reached end of life on December 31, 2025. PHP 8.2 enters security-only support in 2026 before retiring on December 31 of that year. The window of PHP versions that both meet the WordPress hosting PHP requirements and have been widely tested against legacy code is narrowing from both ends. For site owners, the external pressure of a WordPress major release provides a clearer forcing function than any security advisory: “your current PHP version will block you from running WordPress 7.0” is a harder message to defer than a bulletin about a hypothetical vulnerability.
Real-Time Collaboration Adds a New Server-Side Variable
One element of WordPress 7.0 that extends beyond the core WordPress hosting PHP requirements is the new real-time collaboration feature, which allows multiple editors to work on the same post simultaneously in the block editor. This component was the primary reason the launch date shifted from April to May – it required additional stabilisation work that delayed the release. The WordPress development team has indicated that specific server-side requirements for real-time collaboration will be published closer to the launch date.
The practical implication for site owners running production editorial environments is that the full infrastructure picture for WordPress 7.0 may not be finalised until days before May 20. For teams where real-time editing is the primary reason for upgrading immediately, there is a reasonable case for waiting a few days post-launch to review the published requirements before pushing the upgrade on a live site. For everyone else, clearing the PHP and database requirements is the actionable task right now.
Meeting WordPress Hosting PHP Requirements Before the Launch
The first step in meeting the WordPress hosting PHP requirements is confirming the PHP version your site is currently running. In cPanel environments, this is visible under MultiPHP Manager or the Software section of the control panel. In WordPress itself, the Site Health tool under Tools in the dashboard reports the PHP version under the Info tab. Once you have that number, the WordPress hosting PHP requirements check is straightforward: anything below PHP 7.4 must be upgraded before May 20 to keep receiving WordPress core updates.
After confirming the PHP version, run a compatibility check on plugins and themes before upgrading the runtime itself. Most actively maintained plugins already declare PHP 8.3 compatibility. The friction tends to surface with abandoned plugins or heavily customised themes built against older function signatures. Staging environments are the right place to test a PHP version change before touching a live site – a test upgrade on a staging instance takes minutes and eliminates the risk of a broken production site on launch day.
For site owners whose current provider makes PHP version management a manual ticket process, the WordPress 7.0 transition is a practical prompt to evaluate whether the hosting stack can keep pace with where WordPress is heading. Hosts offering modern NVMe hosting performance combined with per-account PHP switching through a proper control panel remove the coordination overhead that makes these transitions painful on legacy shared environments.
The Bottom Line
WordPress 7.0 arrives on May 20, 2026, with WordPress hosting PHP requirements fixed at PHP 7.4 minimum and PHP 8.3 recommended, paired with a new database floor at MySQL 8.0 or MariaDB 10.6. These are hard cutoffs, not suggestions. Sites running on non-compliant environments will be blocked from upgrading, and site owners who discover that on launch day will find the support queues long.
The broader picture is a platform that powers more than 40 percent of the web using a major version milestone to force an overdue infrastructure refresh across an ecosystem that has resisted it. PHP 7.2 has been without security patches since 2020. The WordPress hosting PHP requirements update in version 7.0 marks the point where the cost of legacy PHP on shared hosting is no longer absorbed quietly – it becomes a visible blocker that affects every site attempting to stay current.
If your current host makes PHP version management difficult or does not offer proper staging environments for testing version changes, it is worth looking at MonsterMegs WordPress hosting – environments built on current PHP versions, maintained ahead of releases like WordPress 7.0, and managed through a control panel that makes version switching straightforward.
Top comments (0)