New

The new HostCloud is live. Web Hosting for ₹1 for your first month.

Web Hosting for ₹1 · first month

Claim offerClaim
WordPress

WordPress 7.0 hosting requirements: PHP, MySQL and what to check before you upgrade

WordPress 7.0 raised the minimum PHP version to 7.4. Sites on older PHP will not receive it. Here is what changed, how to check your server in five minutes and how to upgrade without breaking plugins.

2 November 2026 · 9 min read
WordPress 7.0 hosting requirements: PHP, MySQL and what to check before you upgrade

WordPress 7.0 hosting requirements: PHP, MySQL and what to check before you upgrade

TL;DR: WordPress 7.0 raised the minimum PHP version from 7.2.24 to 7.4. If your site runs PHP 7.3 or older, WordPress will not offer you 7.0 and you stay on the 6.9 security branch until your host upgrades PHP. The database minimums did not change, but the recommended versions are much newer: PHP 8.4 or 8.5, MySQL 8.4 LTS or MariaDB 10.11, 11.4 or 11.8. The safe path is to check your versions, test on staging, upgrade PHP first, then upgrade WordPress, and keep major core updates under your control.

What changed in WordPress 7.0

WordPress 7.0 shipped on 20 May 2026, after a delay from an earlier target of 9 April. For hosting, the headline is simple: the minimum PHP version moved up from 7.2.24 to 7.4. Releases 7.2 and 7.3 fell below the project's usage threshold, so core stopped supporting them.

Some earlier coverage was written before release and described the database minimum as rising to MySQL 8.0. That did not happen. The database minimums stayed where they were.

Requirements at a glance

Component Minimum for 7.0 Recommended
PHP 7.4 8.4 or 8.5
MySQL 5.5.5 8.4 LTS
MariaDB 5.5.5 10.11, 11.4 or 11.8 (LTS releases)
HTTPS Not enforced Strongly recommended

"Minimum" means WordPress will run. It does not mean it is a good idea. PHP 7.4 and MySQL 5.7 no longer receive security fixes upstream, so staying at the minimum leaves you running unpatched software. Our guide to PHP versions, extensions and what to check when choosing hosting shows which branches are still supported.

Table-style chart of WordPress 7.0 minimum versus recommended PHP, MySQL, MariaDB and HTTPS settings

What happens if your PHP is too old

Nothing breaks immediately. WordPress checks your PHP version before offering a major update, and if it is below 7.4, the 7.0 update does not appear. Your site stays on the 6.9 branch, which continues to receive security releases for now.

That is a safety net, not a plan. You miss new features, plugin and theme authors increasingly drop support for old PHP, and the PHP itself is likely out of security support. The recent critical PHP flaws, covered in our PHP2Shell guide, are a reminder that old runtimes are a real risk.

How to check your versions in five minutes

Inside WordPress. Go to Tools, then Site Health, then the Info tab. Open the Server section to see the PHP and database versions.

From the command line. If you have SSH access and WP-CLI:

php -v
wp core version
wp db query "SELECT VERSION();"

From your hosting panel. Most control panels show the PHP version per site and let you change it. If you manage several sites, make a short list of each site's PHP version and database version, grouped by server. Anything below PHP 7.4 or on an end-of-life database goes to the top of the list.

Upgrade order that avoids breakage

Do the upgrade in this order, on staging first.

  1. Take a full backup and confirm you can restore it. See how to back up a WordPress site and test the restore.
  2. Create a staging copy. Our staging guide explains the workflow.
  3. Update plugins and themes on staging to their latest versions.
  4. Raise PHP on staging to 8.3 or newer, ideally 8.4. Browse the site, test forms, checkout and the admin area, and watch the error log.
  5. Update WordPress core to 7.0 on staging and test again.
  6. Repeat on production in the same order, in a quiet period.

Raising PHP before WordPress is deliberate. It lets you separate PHP problems from WordPress 7.0 problems. If something breaks, you know which change caused it. Our guide on systematic plugin conflict debugging helps when a plugin is the culprit.

Controlling major updates

Major releases can change database structure, defaults and deprecated functions that break plugins. If you run client sites or a store, you may prefer to apply security point releases automatically while holding major versions for testing. In wp-config.php, one common approach is:

define( 'WP_AUTO_UPDATE_CORE', 'minor' );

This tells WordPress to apply minor and security releases automatically but leave major versions for you to trigger. Our post on whether WordPress auto-updates are safe explains the trade-offs of each setting.

New features that touch hosting

Release coverage describes several changes that matter for servers. Treat the details as things to confirm in the official release notes for your version.

  • Real-time collaboration. Multiple editors can work on a post at once. It is reported to use HTTP polling by default, so it works on ordinary shared hosting. WebSockets can make syncing faster but are optional. Pages using classic meta boxes may not support collaboration.
  • Client-side media processing. Images are resized and compressed in the browser before upload, which reduces server work and storage.
  • AI connectors. A settings area for connecting AI providers, built on an API introduced in 6.9. These make outbound requests from your server, so check that your host does not block them.
  • Admin screens rebuilt on DataViews. Plugins that modify the Posts, Pages or Media list tables may need updates.

None of these requires special hosting, but they raise the value of enough PHP workers and memory. If editors collaborate heavily, see our guide to PHP memory limit and execution time settings.

What to ask your host

  • Which PHP versions can I choose, and can I set them per site?
  • Which PHP branches do you patch, and how quickly after a security release?
  • What database server and version do you run?
  • Do you offer staging, and are backups taken before upgrades?
  • Do outbound connections to external APIs work, in case I use AI features?

FAQs

Does WordPress 7.0 require PHP 8?

No. The minimum is PHP 7.4. However, PHP 8.4 or 8.5 is recommended, and anything below 8.2 no longer receives upstream security fixes.

Will my site break if I am on PHP 7.2 or 7.3?

It will not break, but WordPress will not offer 7.0. You stay on the 6.9 branch until the host upgrades PHP.

Did the MySQL requirement change?

No. The minimum remains MySQL 5.5.5 and MariaDB 5.5.5. Treat that as a floor, not a target, and aim for MySQL 8.4 LTS or a current MariaDB LTS release.

Should I update to WordPress 7.0 immediately?

For a brochure site with few plugins, once you have tested on staging, yes. For stores and heavily customised sites, wait for plugin authors to confirm compatibility and test thoroughly first.

How do I change my PHP version?

In most hosting panels there is a PHP selector per site. On a VPS, you install the versions you want and point your web server at the right PHP-FPM pool.

Do I need to change themes for 7.0?

Not necessarily. Test your current theme on staging. Themes that rely on old APIs or admin scripts are the most likely to need updates.

What if a plugin breaks after the upgrade?

Roll back to your backup or staging snapshot, update or replace the plugin, and retest. Do not leave a broken plugin active on a live site.

Will the upgrade slow my site?

Moving from PHP 7.4 to 8.3 or newer is usually faster, not slower. The WordPress version itself has a smaller effect than your plugins and hosting.

Conclusion

WordPress 7.0 made PHP 7.4 the floor, but the real target is a supported runtime: PHP 8.4 or 8.5 and a current database. Check your versions, test on staging, raise PHP before core, and keep major updates under your control. That order keeps a routine upgrade routine.

HostCloud's hosting plans let you run supported PHP versions for your WordPress sites. See the options at https://hostcloud.in.

Sources:

Related posts