WordPress 6.6, announced for July 2024, drops support for PHP 7.0 and 7.1. So there are three things to check on your hosting: the PHP number in use, whether your theme and plugins work with a newer release, and whether you can go back to the previous setting.
The WordPress PHP version is a parameter most site owners only learn about from a warning in the dashboard or a message from their hosting company. Don’t worry. A notice like that is not a failure, just a signal that it is time to plan a change. In June 2024 the 6.6 release is still only an announcement, so you can prepare for it calmly.
Table of contents
Minimum WordPress PHP version in 6.6: what changes?
The new minimum is PHP 7.2.24, and the recommendation stays at 7.4 or higher. This comes from the WordPress core team announcement of April 8, 2024. Why now? Because the combined share of PHP 7.0 and 7.1 fell in April 2024 to 2.45% of monitored installations, which is clearly below the customary 5% threshold at which the project drops old releases. The requirements were last raised in WordPress 6.3, in August 2023.
The minimum and the recommendation are two different things (and often confused). Yes, the site will run on the lowest allowed release. But that is not a target setting, only a lower limit below which the core update will not install at all.
What happens to a site that stays on PHP 7.0 or 7.1?
Nothing sudden. The site will not stop working, it will just stay on the 6.5 branch, which according to the post about the requirements change will keep receiving security fixes. For PHP 7.0 and 7.1, the end of support in WordPress therefore means development stops, not that the site is switched off overnight.
The effects show up over time. The site will not get the features from the new release or from the ones after it. Plugin and theme authors will start raising their own requirements, so some updates will simply stop being available. And the least pleasant part: old PHP releases no longer get fixes from the language’s developers, so the vulnerabilities in them stay open. In an online store, customer and order data are at stake, which is why WooCommerce store security starts with an up-to-date server environment.
How do you check the PHP version on your site?
You can see the PHP number in the dashboard: Tools - Site Health, the Info tab, the Server section. It takes a moment and needs no server access:
- Log in to the dashboard as an administrator.
- Open the Tools menu and choose Site Health.
- Go to the Info tab.
- Expand the Server section.
- Read the entry with the PHP version.
The neighboring Status tab shows a warning when PHP is outdated. It is the same notice that probably made you look for information. The second place is the hosting panel. One caveat here: the setting is sometimes assigned separately to each domain or directory, so one site on the account may run differently from the others. Oh, and while you are there, write down the database version and the list of active plugins. They will come in handy before the change.
Plugin and theme compatibility with PHP 8: what to verify before the change
After PHP is raised, what breaks most often is not WordPress itself but plugins and a theme that have not been updated. The core, according to the notice from the WordPress developers, is compatible with PHP 8.0 and 8.1 with exceptions, and support for 8.2 and 8.3 has been considered beta since WordPress 6.4.
Plugin compatibility with PHP 8 has to be assessed separately for each extension. What should you look at?
- the date of the last update in the repository,
- the required PHP declared by the author,
- the changelog, which shows whether newer releases of the language were taken into account.
Custom-made templates and old child themes will not update themselves. There is no way around a code review here. Anyone who built a custom WordPress theme from scratch should look especially at the functions file and the custom templates. And extensions abandoned by their authors? Replace them with equivalents before the switch, not after.
Updating PHP on your hosting step by step
A safe change means a backup, a test on a copy of the site, switching the version and checking that everything works. Plus a ready rollback plan. The order is not accidental, because each stage protects the next one:
- Make a full backup of the files and the database.
- Update WordPress, the plugins and the theme on the current PHP.
- Create a test copy, that is a staging site, and turn on the new release there.
- Go through the key paths: forms, cart, payment, login.
- Switch production outside peak traffic hours.
- Check the server error log right after the change and again the next day.
The rollback plan is short. Note the previous setting from the panel, because reverting it takes a moment, and keep the backup in case data gets damaged. A very old site is better moved gradually, release by release, than by jumping several at once. It is then much easier to point to exactly what broke. And one more thing: when choosing website and email hosting, ask the provider which PHP releases it offers and whether you can change them yourself.
Which PHP version should you choose and what does the site gain?
The goal is the newest release on which the theme and all plugins work correctly. Not just meeting the minimum. Every PHP release goes through the same life cycle: first active support with bug fixes, then a period with security patches only, and finally no updates at all. The closer your setting is to the start of that cycle, the less often you will have to come back to the topic.
And it is not only about protection. Newer PHP usually runs the same code more efficiently, so changing the environment can be one of the simpler steps when the goal is faster WordPress page loading.
In my opinion, the WordPress PHP version should be a regular item in a site review, not a one-off action before the 6.6 release. In practice it is enough to glance at it during larger updates and react before the warning in the dashboard turns into a blocker.
Frequently asked questions
Will WordPress 6.6 run on PHP 7.1?
No. The announced minimum is higher, so the core update will not install. The site will stay on the earlier branch and keep receiving security fixes, but without new features.
Can changing the PHP version break a site?
It can, if a plugin or the theme uses code that is incompatible with the new release. The symptom may be a white screen, a critical error or a single element that stops working, for example a form. That is exactly why you need a backup, a trial on staging and the previous setting written down.
Who changes the PHP version - me or the hosting company?
Usually the account owner, in the hosting panel, in the domain settings. And when there is no such option? A ticket to the provider’s technical support asking for the switch and stating the target release is enough.








