Upgrade WordPress PHP to 8.3 Safely, Staging First for UK Sites
If your site runs a PHP version older than WordPress’s recommended baseline of PHP 8.3, the answer is yes, and the first move is simple. Head to Tools, then Site Health, then Info, and check the Server section for your current PHP version. If it’s outdated, take a full backup before you touch anything else.
TL;DR:
- Running an unsupported PHP version leaves your site vulnerable to unpatched security flaws, with no way to receive fixes for new vulnerabilities.
- Themes and plugins may break or refuse to activate if their required PHP version exceeds your current version, risking compatibility issues.
- Testing the PHP upgrade in staging after updating core and extensions minimizes downtime and helps identify potential conflicts early.
- Most hosting providers, including cPanel and Plesk, allow easy PHP version changes but require thorough testing before applying changes to production.
- Regularly updating PHP alongside other site maintenance prevents dependency on outdated code and maintains optimal speed and security.
Table of Contents
Why updating PHP matters for performance, security and compatibility
Newer PHP releases process requests more efficiently, and that shows up directly in how quickly your pages load, which feeds into Core Web Vitals and, in turn, user experience. WordPress itself recommends keeping PHP current for exactly this reason, noting that updating to the recommended version can bring measurable gains in both speed and security.
Security is the sharper concern. Each PHP release branch gets around two years of active support followed by roughly two more years of security-only fixes, and once that window closes, the branch stops receiving patches altogether. Running an end-of-life version means any newly discovered vulnerability stays open indefinitely, with no fix coming.
A site running an unsupported PHP branch has no path to a security patch if a new vulnerability is found, which is why WordPress’s own requirements page flags outdated PHP as a genuine exposure, not just a performance nuisance.
The trade-off is compatibility. Older themes and plugins built years ago sometimes rely on functions or syntax that newer PHP versions handle differently or drop entirely. That’s the real risk in this process, and it’s why the rest of this guide is built around testing before you commit.
How to check your current PHP version and spot compatibility signals
Open your WordPress dashboard, go to Tools, then Site Health, then Info, and expand the Server section. Your PHP version sits near the top, and WordPress walks through this exact path if you want a second reference point.
Site Health also flags problems in plain language. A message reading “PHP Update Required” means your version is genuinely too old and needs attention soon. “PHP Update Recommended” is softer, a nudge that you’re behind the curve rather than in immediate danger. Either message is worth acting on, but the first one shouldn’t wait.
Beyond Site Health, look at your themes and plugins themselves. Many declare a “Requires PHP” value in their header files, essentially a minimum version they’ve been built and tested against. If a plugin lists PHP 8.0 as its floor and you’re running 7.4, that’s a clear signal it may misbehave, or simply refuse to activate, once you upgrade past its ceiling in the other direction too.
Prepare safely: backups, updates and staging before you touch PHP
Rushing straight into a PHP upgrade is how sites end up offline for a weekend. A short, ordered routine avoids most of the pain.
- Take a full backup of your files and database, then actually verify the restore process with your host rather than assuming it works.
- Update WordPress core, all themes and all plugins to their latest versions before changing PHP, since outdated software is far more likely to clash with a new PHP release.
- Run a compatibility scanner plugin to flag obvious issues, but treat the results as a starting point rather than a guarantee.
- Set up or use an existing staging copy of your site and run the PHP upgrade there first, testing every important page and feature before going anywhere near production.
Pro Tip: If you don’t already have a backup plugin in place, a resource like Top 8 Backup Plugins WooCommerce 2026 is a useful starting point for comparing options before you commit to one.
Scanner plugins are genuinely handy for catching obvious deprecated functions, but WordPress’s developer documentation is clear that they’re guidance, not proof. Custom code, child themes and bespoke integrations often need a human to click through the site and confirm things still work as expected. That’s the gap staging fills, and it’s worth the extra half hour it takes to set up.
How to change PHP versions on the most common hosting setups
Once staging has passed its checks, the actual PHP switch happens at the hosting level, and the process varies a fair bit depending on your setup.
- cPanel: open MultiPHP Manager or Select PHP Version, choose your target version from the dropdown, apply it to the relevant domain, then reload the site and test key pages immediately.
- Plesk: find the domain’s PHP settings, where you can select a PHP handler and version per domain, which is handy if you run several sites under one account at different PHP levels.
- Managed WordPress hosts: many offer a simple toggle in their dashboard, though some route the change through support instead. Either way, check whether the host runs an automated caching layer that needs clearing after the switch.
- Unmanaged servers or VPS setups: PHP updates typically go through the server’s package manager, and you, or whoever manages your infrastructure, will need to consider whether you’re running PHP-FPM, Apache’s mod_php, or Nginx with FPM, since the upgrade steps differ slightly for each.
Managed hosting environments make this part easier, but easier isn’t the same as automatic. As WordPress’s own guidance on PHP and performance points out, even a one-click toggle can cause downtime if you skip testing beforehand. The safest sequence, regardless of host type, stays the same: back up, update core and plugins and themes, test in staging, change PHP in staging, test again, and only then repeat the PHP change in production.
If your current host makes any of this awkward, doesn’t offer version control at all, or you’re simply outgrowing what a basic shared plan can handle, our guide on migrating WordPress hosting walks through what a move looks like in practice.
Testing and troubleshooting after the upgrade goes live
Once PHP is switched over, don’t assume everything’s fine just because the homepage loads. Click through the front end, log into wp-admin, submit any forms, run through checkout if you sell online, and check that scheduled tasks, WP-Cron jobs and anything running on a timer, still fire correctly.
If something breaks, your error log is the first place to look, and turning on WP_DEBUG briefly, then switching it off again once you’ve captured the message, is a safe way to see what’s actually failing without exposing errors to visitors long-term.
The most common fix is isolating the culprit: deactivate the plugin most recently flagged in your compatibility check, or temporarily switch to a default WordPress theme, to confirm whether the problem sits there. If a plugin or theme is genuinely incompatible, you’re choosing between patching the code yourself, if you’re comfortable doing so, or bringing in a developer, particularly when the fix touches custom functionality rather than a simple update.
Rolling back and recovering if the upgrade causes problems
If the site goes down and a quick fix isn’t obvious, don’t spend hours guessing. Change the PHP version back to what it was before, either through your hosting control panel or by contacting host support directly, since WordPress’s own advice on updating PHP recommends this as the fastest way to restore service.
From there, restore your files and database from the verified backup you took earlier, and test the site thoroughly before re-enabling any caching or CDN layer, which can otherwise mask whether the underlying problem is actually fixed.
Once things are stable, let anyone affected, colleagues, clients, or customers, know what happened and roughly how long it took to resolve. A short note on what went wrong and what you’d do differently next time makes the next upgrade smoother.
Keeping PHP current without it becoming a recurring headache
A PHP upgrade shouldn’t be a once-a-decade panic. Build it into your routine maintenance alongside core, theme and plugin updates, and check your PHP version against WordPress’s current recommendation every few months.
Keep an eye on Site Health messages and your error logs as a matter of habit rather than only when something visibly breaks, and watch performance metrics for any drift that might point to a growing compatibility issue. Our piece on essential website maintenance steps covers how this fits into a broader update schedule.
A simple changelog of what you updated and when, plus a note of who to contact for each plugin or theme if something goes wrong, saves real time the next time a PHP upgrade is due.
When it makes sense to hand this off to an agency
If your site runs a complex online shop, relies on heavily customised code, or you simply don’t have the time to test properly in staging, handing the upgrade to someone else is often the sensible call rather than a shortcut.
This is the kind of work we do as part of ongoing support at MB Web: setting up staging, working through compatibility fixes on themes and plugins, planning a rollback route before we touch production, and keeping an eye on things afterwards through regular maintenance. If page speed is part of what’s driving the upgrade, our Core Web Vitals guide shows how server-level changes like this feed into real performance numbers.
Our honest take on PHP upgrades
The advice you’ll find most often treats a PHP upgrade as a one-off technical chore: check the version, flip the switch, done. That undersells the actual risk, which sits almost entirely in old themes and plugins nobody’s touched in years, not in PHP itself. Newer PHP is faster and more secure by design; the danger is what it exposes in code that was never built to modern standards.
What’s overrated is relying solely on a compatibility scanner plugin and skipping staging because “it’s probably fine.” Scanners catch the obvious stuff. They miss custom functions, quiet edge cases in checkout flows, and anything a developer wrote in a hurry three years ago.
If you take one thing from this guide, prioritise the staging test over the speed of the switch. An upgrade that takes an extra day because you tested properly beats one that takes ten minutes and breaks your checkout on a Saturday.
— James Golding
Let us handle the risky part of your PHP upgrade
Testing themes and plugins in staging, planning a rollback, and fixing whatever a PHP upgrade breaks takes time most business owners don’t have spare. Our Website Maintenance and Updates service covers exactly this, keeping your site’s core, plugins, themes and PHP version working together safely, with someone accountable when something needs fixing.
If your current hosting makes PHP upgrades difficult or slow, our Website Hosting plans start from £290 per year and are built to keep this kind of maintenance simple rather than stressful. Get in touch and we’ll take an honest look at what your site actually needs.
Sources
- Get a faster, more secure website: update PHP today — WordPress support
- WordPress developer docs — PHP and performance
FAQ
How do I update the PHP version for WordPress?
Check your current version under Tools, then Site Health, then Info, then Server, and back up your site fully before making any change. Update WordPress core, themes and plugins first, test the upgrade on a staging copy, then switch PHP through your hosting control panel, whether that’s cPanel, Plesk or a managed host’s dashboard.
What is the best PHP version for WordPress in 2026?
WordPress recommends running PHP 8.3 or higher as the current baseline for both performance and security. Running an older, unsupported branch leaves your site without security patches if new vulnerabilities are found.
Is PHP 8.3 stable for WordPress?
Yes, PHP 8.3 is the version WordPress currently recommends for sites running its software. Older themes or plugins built for earlier PHP versions may still need compatibility testing before you switch.
Which version of PHP should I use for WordPress?
Match whatever WordPress’s official requirements page currently lists as its recommended version, which sits at PHP 8.3 or above. Confirm your themes and plugins support that version first by checking their “Requires PHP” header or testing on staging.
How do I know if my site needs a PHP update?
Open Tools, then Site Health, then Info, then Server in your WordPress dashboard to see your current PHP version and any warning message. A “PHP Update Required” notice means action is needed soon, while “PHP Update Recommended” means you’re behind but not in immediate danger.