What your host is really asking when it mentions a PHP update
One day you open an email from your host and find a notice: «we are going to update the PHP version on your server». That message mixes two things that look similar and are not the same.
PHP is the language WordPress uses to generate pages on the server. Its version is managed through hosting and can also be checked in Site Health. The notice may concern one domain or several sites: check the scope your provider specifies.
That is not the same as updating WordPress, the «A new version is available» button in the dashboard. It is also not the same as updating a plugin or the theme. You can have WordPress up to date and PHP outdated, or the other way round.
The notice may appear by email, in the hosting panel or in Site Health. Check the proposed date, PHP branch and available support. The official PHP table helps assess maintenance independently of the provider’s commercial options.
Why they are warning you now and what happens if you ignore it
PHP branches have a period of active support followed by security fixes. Once official support ends, the PHP project stops maintaining that branch. Some providers offer their own extended maintenance, which should be identified and assessed separately; it is not ongoing official support.
Check that calendar on the official supported versions page to see which branches are active, which only receive security fixes and which are out of support. It tells you where the version your host is proposing actually sits.
Ignoring the notice does not itself cause a failure, but the provider may switch versions on the stated date. Confirm that deadline and what will happen if you do not choose a version first. Keeping an old version can also lead to these problems:
- A security report, the day you ask for one, will flag «PHP version out of support» as a recurring finding.
- Your plugins and theme will struggle with normal updates: many raise their minimum PHP over time and the update button fails along the way.
- New WordPress releases will eventually stop fitting on your server. WordPress publishes the technical requirements on the requirements page.
- A plugin that failed quietly starts breaking a specific page: a form that no longer sends, a gateway that errors out, a private area that no longer opens.
Your site working today does not mean it is up to date. The host’s notice simply puts a date on the matter.
Before touching anything: your current PHP version and the target
The first step is not to press the update button, but to build a status sheet: which version you start from and which one the host wants you to move to.
Two places to check the current PHP version:
- Hosting panel. Most panels have a section called «PHP version», «PHP selector» or «MultiPHP Manager», showing the version each domain is serving and, often, the menu to change it. The authoritative source.
- Your own WordPress. From the dashboard,
Tools > Site Health > Info > Server. There you will see the PHP version, the database version and the available memory. - If the readings differ, ask support to confirm the version and configuration serving that domain. You do not need a public
phpinfo()file, which can expose configuration details.
In the notice look for the target version, the deadline and whether the change is mandatory or recommended. Many providers let you choose during a window and, at the deadline, move the site themselves; others schedule the change without asking; some offer rollback for a few days. If the notice does not state it clearly, ask support.
Write the reference details somewhere stable:
Hypothetical example: your provider proposes a specific PHP version for next month. Record the current and target versions, affected domains and whether rollback is available. Add the WordPress, theme and plugin versions for comparison; this example does not recommend a particular PHP branch.
Without that sheet, every check turns into an «I think I saw that…» and details slip through.
Check compatibility of WordPress core, your theme and your plugins
The jump has to be supported by three actors: the WordPress core, the installed theme and each active plugin. Cross-reference the target version against what each piece declares.
For the core you have the official WordPress requirements and the core team’s PHP compatibility and WordPress versions table. If your branch does not support the target version, the jump also involves updating WordPress.
Check each component’s listing and documentation. “Requires PHP” is the minimum PHP version; “Tested up to” refers to WordPress, not PHP. Look for an author’s statement, release notes or support confirmation about the target PHP version. Meeting the minimum does not prove compatibility with every later version.
A clear way to avoid getting lost is to lay out this table and fill it in:
| Component | Installed version | Minimum PHP | Tested PHP | Status against the target |
|---|---|---|---|---|
| WordPress (core) | The one in Site Health | Official requirements | Official compatibility table for the target PHP version | Compatible / update first / incompatible |
| Active theme | Appearance > Themes | Author’s value | Author’s value | Compatible / review / no information |
| Each active plugin | Plugins screen | Requires PHP | Author documentation for the target PHP | Compatible / review / no information |
This table is an operational tool, not a universal recipe. The goal is ending with a clear list of which pieces are ready and which need a decision: update before the jump, ask whoever maintains the website for a new build, replace or retire. A plugin «with no information» is not automatically a problem, but a question to close; one untouched in years tends to cause more issues than one with recent updates.
Prepare a full backup and a rollback plan
Before changing the PHP version, even if your inventory says everything is ready, you want a recent backup and to know how to restore it.
Prepare recoverable files and database backups. Include media, themes, plugins, configuration and custom code, even outside wp-content. Keep the hosting settings needed to rebuild the environment too, storing secrets outside public access.
Having a backup is not the same as knowing how to restore it. Before the switch day, test the restore on a separate place, even a local environment or a subdomain. The official WordPress documentation on backups describes both the scope and the usual restore paths. For a small-business view, see how to check that your website backup actually works.
Alongside the backup, prepare a rollback plan:
- Change window. A quiet slot: outside business hours, a lower-traffic day. Not Friday afternoon.
- People on call. You, whoever maintains your website, hosting support.
- How to roll back. The specific procedure to drop the PHP version from the panel, and who to write to if the panel does not allow it.
- What to communicate. If you have a customer area or a payment gateway, decide in advance what you will say if there is an outage.
With the backup and the plan ready, the change stops being a leap into the dark.
Run the upgrade on staging before touching production
Testing on the live site is a bad idea. What you want is a place where you can get it wrong without consequences. Three common options on shared hosting:
- Built-in staging. Many providers include a button to create a temporary clone on a protected subdomain. Smoothest route if your plan offers it.
- Manual clone on
staging.yourdomain.comwith a password or blocked to the public. More work, but it is an option if your hosting plan allows the clone to be created and properly isolated. - Local environment with WAMP, XAMPP or Local, for anyone who can set it up. Most controlled option.
Protect and isolate the clone: no customer emails, live payments or connections that update external systems. Your team can change PHP there and test normal functions with test accounts and gateways. The WordPress and PHP compatibility table covers core, but does not replace these checks:
- The home page loads with the right design.
- The admin panel opens without errors and the main sections respond.
- Your forms send and the expected email reaches you.
- The payment gateway, if present, accepts a test purchase.
- Your outgoing email works from the site itself.
- The customer area, if it exists, lets a test account in.
- Pages with shortcodes or dynamic blocks show the same content as before.
A useful distinction: not enough to check that something «works», you want to check it «works the same as before». A form that sends but stops reaching an address, a gateway that charges without the receipt or a page that loads three times slower are quiet warnings spotted late. Note what you expect in each test and compare it with what happens.
What to check on the live site right after the switch
Once the new version is applied on production, the first few minutes matter most. Not a «looks fine», but an active check with judgement. A short checklist:
- Open the key pages from a private window, without your session signed in. Header, footer, menus, payment gateway.
- Go into the admin panel and walk through the main sections. No red warnings, no white screens.
- Send a test form and confirm the email reaches the correct address.
- Check the hosting error log. If there are
PHP FatalorDeprecatederrors, note them to discuss with whoever maintains the website. - Flush the caches (caching plugin, CDN and host’s cache if any) and check the key pages again.
- If you use PageSpeed or Search Console, keep an eye on performance and Core Web Vitals over the following days.
Your team can review private hosting logs. If extra debugging is necessary, keep errors off visitor screens and store the log outside public access, with restricted access and retention. Enabling WP_DEBUG_LOG alone does not protect the file. The WordPress debugging documentation explains the options.
If everything went well, turn debugging off at the end of the trial. If you spotted warnings, group them and pass the list to whoever maintains the website instead of patching them one by one.
If something breaks: rollback or fix
Decide according to business impact, not only how many pages show an error. A failing enquiry form or payment can matter more than a warning across several pages.
If the previous version remains available and the fault relates to the PHP change, your team can consider rolling back temporarily. This does not guarantee full recovery if plugins, code or data were also updated. Confirm what changed before restoring anything, especially when new orders or registrations have arrived.
If one component is incompatible, test an update or replacement on staging. Disabling it live can remove an essential function. The guide to assessing an unsupported plugin helps decide whether to keep it. Returning to an unsupported PHP branch needs a plan to resolve compatibility, rather than staying there indefinitely.
If you want us to walk you through it
If you have received the notice and are unsure what it means for your site, share it with us, without passwords. We can help compare versions, identify compatibility questions and agree the checks or changes needed before carrying them out.
If your intent is more preventive than reactive, it usually fits well to frame this within our performance area, where we address the technical health of the site as a whole. And if the switch were to cause serious problems, you know where to pick up: what to do when WordPress stops working after an update walks through the same criterion for the worst case, so you can decide with a steady hand even then.