Upgrade the PHP version of your WordPress site: the safe way, in the right order.
Your host has announced a PHP upgrade, or your site still runs an old version. Most sites move without a hitch. The ones that break are the ones nobody checked first. Here is what is changing and why, which version to pick, six steps in a safe order, and how to undo it if something goes wrong.
First: your host sets the date, you control the readiness
PHP runs on your host's server, not inside WordPress, so the host decides which versions exist and, in the end, when an old one is switched off. What you control is whether your theme and plugins are ready when that day comes. An upgrade you plan takes an afternoon. An upgrade that happens to you, with no backup and no test, is how a working site ends up on a white screen.
What has changed: the dates that matter
These are the facts from WordPress, WooCommerce and the PHP project, as of 13 November 2026. Hosts are acting on them, and you will see the effect as emails, dashboard notices or a version that changes on its own.
WordPress recommends PHP 8.3 or greater
The WordPress requirements page asks hosts for PHP 8.3 or greater. WordPress still runs on PHP 7.4 and up, but it describes those versions as end of life and open to security problems. WordPress 7.0 has already dropped PHP 7.2 and 7.3.
PHP 8.1 and older: no more fixes
The PHP project no longer releases updates for PHP 8.1 or anything older. Some hosts and Linux vendors backport fixes on their own, so ask yours whether it does. If it does not, the version your site runs on has stopped getting security patches.
PHP 8.2: security fixes end 31 December 2026
According to php.net, PHP 8.2 receives only security fixes now, and those stop on 31 December 2026. Then 8.3 runs to 31 December 2027, 8.4 to 31 December 2028 and 8.5, released 20 November 2025, to 31 December 2029.
Two critical PHP fixes on 21 October 2026
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical flaws that can allow remote code execution without logging in. The PHP team says all installations serving web requests are at risk and urges everyone to update. Check that your host has installed the patched release for your version.
WooCommerce is tested up to PHP 8.4
WooCommerce's server recommendations, for version 10.8 and later, ask for PHP 8.3 or greater and say it is tested up to PHP 8.4. If you run a store, 8.3 or 8.4 is the sensible target, not the newest release.
Nothing breaks on a calendar date
A date on the PHP calendar does not switch your site off. It means the PHP project stops fixing that version. Your host then decides when to retire it, and whether an extended-support option exists. What changes on your site is whatever your host does about it.
How to upgrade PHP on WordPress: six steps, in this order
The order matters. Each step makes the next one safer, and the switch itself is the fifth step, not the first.
Find out what you run today
In the WordPress dashboard go to Tools, Site Health, open the Info tab, expand Server and read PHP version. If it shows 8.3 or higher, WordPress says you do not need to update at this time. A dashboard notice reading PHP Update Required or PHP Update Recommended means the same question is open. Write the version down, and note which plugins and the theme are active on the same screen.
Ask your host three questions
Which PHP versions do you offer for my plan? On what date will you retire my current version, or move me yourself? Have you installed the 21 October 2026 security release for my version? Also ask whether there is a staging site and how to roll back. The WordPress update-PHP page has a short email you can copy, and many hosts publish their own instructions.
Take a backup and update everything first
A backup you can restore is the only real way back, so make one before anything else and know where it is stored. Then update WordPress, the theme and every plugin. Current releases are the ones most likely to run on newer PHP, and an update that breaks the site is easier to sort out now than in the middle of a PHP change. Check the site still works afterwards.
Check which plugins and the theme are at risk
Open each plugin's page on WordPress.org and look at when it was last updated. Anything untouched for a long time is the likeliest to fail, whatever the PHP version. A scanner can add evidence: the PHP Compatibility Checker lints theme and plugin code against a version you choose. It does not run the code, can report false positives and is no longer actively maintained, so treat it as a list of places to look, never as a pass.
Test on a copy, with errors written to a log
If your host has a staging site, switch the PHP version there first. On staging, set WP_DEBUG and WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false in wp-config.php, above the line that says to stop editing. Then click through the pages that matter: home, a form, login, and for a shop the cart and checkout. Read wp-content/debug.log afterwards. Do not leave debug on for a live site.
Switch the live site and watch it
Change the version in your host's settings, or ask the host to do it, at a quiet time. Repeat the same click-through on the live site, then check the log or your host's error log over the next days. If something breaks, ask the host to put the old version back, or do it yourself if the panel allows. Then fix the cause before trying again.
Which PHP version should you pick?
Most guides say "the latest". That is not the best answer for a site that earns money. Choose by what you run and how much time you have to test.
WordPress recommends 8.3 or greater and lists 8.4 and 8.5 as supported by WordPress 7.0. PHP 8.3 has security fixes until the end of 2027 and 8.4 until the end of 2028. If your plugins are current, 8.4 buys you an extra year. If you are not sure about a plugin, 8.3 is the smaller step.
WooCommerce states it is tested up to PHP 8.4. PHP 8.5 may well work with your store, but a checkout is the wrong place to be the first to find out. Move to 8.3 or 8.4 now and look at 8.5 once your payment, shipping and accounting extensions all say they support it.
PHP 8.1 and older get no fixes from the PHP project. Going to 8.2 only fixes that for a few weeks, because 8.2 security support ends on 31 December 2026. Go straight to 8.3 or 8.4 and test once.
8.2 is supported with security fixes only, until 31 December 2026. That is enough time to do the six steps properly, which is better than doing them in a rush in December. Check that your host has installed 8.2.35, the release with the October fixes.
Do not hold the whole site on an old PHP version for the sake of one abandoned plugin. That plugin is the real risk. Replace it with a maintained one, or have the code reviewed. Keeping the old version only works for as long as your host offers it.
What the PHP warnings in your log mean
A deprecation notice does not stop a page. It says the code uses something that PHP plans to remove. They fill the log and are the early warning, so read them on staging and fix them before they turn into errors. These are examples from the PHP manual, not a full list.
Creating a property on an object without declaring it is deprecated. The usual fix is to declare the property in the class. The "${var}" style of putting a variable inside a string is deprecated, and so are the functions utf8_encode() and utf8_decode(). This is the kind of notice an older plugin throws a lot of.
A function parameter with a default of null and a type, such as Foo $a = null, is deprecated. It must be written ?Foo $a = null instead. This one shows up in many older libraries and is easy for a developer to fix.
Deprecated now: the backtick operator for running shell commands, casts such as (boolean) and (integer) in place of (bool) and (int), using null as an array key, and the functions curl_close() and imagedestroy(), which are no longer needed because PHP frees those objects itself. Notices from the code you do not own are a reason to ask the plugin author, not to edit the plugin yourself.
A fatal error, such as a white screen or the message that there has been a critical error on the website, means code stopped. In the case study below, old plugins and an outdated theme used functions and syntax that newer PHP no longer accepts. If you see a fatal error after the switch, read the guide to the WordPress critical error for how to get back into the dashboard.
After the switch: what to check and what to do if it breaks
Match what you see to the most likely cause. If you did steps 3 to 5, most of these never come up.
Almost always a plugin or the theme that cannot run on the new version. Ask the host to restore the previous PHP version so the site is back while you work out which one. WordPress also sends a recovery email with a link into the dashboard. See the critical error guide.
The error is happening in one feature and the rest of the page hides it. Open the log from step 5 and look for lines that name a plugin folder. Update that plugin, or replace it if it has not been updated for years.
Switch the PHP version back in the host panel or ask the host to do it. Once you are in again, deactivate the plugin named in the log, or rename its folder over FTP, and switch the version again.
Roll back first, then diagnose, because each minute of a broken checkout costs orders. After the old version is back, test a real order on staging with the new version. See what to do when an update breaks WordPress for the roll back or fix forward decision.
Keep watching the log for a week, because rarely used code only runs when someone uses it: a yearly report, a password reset, a rare shipping method. Then turn debug off. Next year the same routine applies, and a maintenance plan is the way to have updates tested before they reach the live site.
A real one: the site that broke when the server's PHP was updated
A martial arts school's site had run for years on a legacy premium theme, bundled shortcodes and outdated plugins. When the server's PHP version was updated, the site began throwing repeated fatal errors, the admin area was hard to reach and a promo box on the front page stopped rendering. It was not one plugin: the theme, shortcodes and builder components depended on each other. We worked through the errors one at a time instead of updating everything at once. Read the case study.
Questions about upgrading PHP on WordPress
Sources
Last checked 13 November 2026. PHP dates, host plans and plugin support change, so check the current documentation before you rely on a detail.
WordPress.org: Requirements: PHP 8.3 or greater recommended, 7.4 as the legacy floor.
WordPress.org: Update PHP: where to check the version, backup, update, check compatibility, staging, rollback through the host.
Make WordPress Core: PHP Compatibility and WordPress Versions: which PHP versions each WordPress release supports.
php.net: Supported Versions: security support end dates for 8.2 to 8.5.
php.net: 2026 news archive: the 21 October 2026 security release and the end of updates for 8.1 and older.
WooCommerce: Server Recommendations: PHP 8.3 or greater, tested up to 8.4.
WordPress.org: PHP Compatibility Checker: what a static code scan can and cannot find, and its maintenance status.
PHPCompatibilityWP: the ruleset developers use to check WordPress projects against a PHP version.
WordPress developer docs: Debugging in WordPress: WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY.
php.net: deprecated features in 8.2, 8.4 and 8.5: the examples in the warnings section.
Do not let the upgrade happen to your site. We will test it first.
Free diagnosis, and we respond within 30 minutes during business hours. Fixed price in writing before we start, from €199 excl. VAT.