To update PHP in WordPress, first check your current version under Tools > Site Health > Info > Server, then back up your site, update your plugins and theme, and switch to a supported PHP version in your hosting panel (MultiPHP Manager in cPanel, PHP Configuration in Hostinger, or PHP Settings in Plesk). In late 2026, PHP 8.3 or 8.4 is the safe choice for most sites. Test the site right after the switch and keep the old version handy in case something breaks.
- WordPress recommends PHP 8.3 or greater. It still runs on PHP 7.4, but WordPress itself warns that old versions have reached end of life and may expose your site to security problems.
- PHP 8.1 and older no longer get any fixes. PHP 8.2 stops getting security fixes on 31 December 2026, so plan to move off it now.
- Always back up first, update plugins and theme before PHP, and test on a staging copy if your host offers one.
- Most errors after a PHP update come from one old plugin or theme. They are usually quick to find and fix.
Why does your WordPress PHP version matter?
PHP is the programming language WordPress is written in. Your host runs it on the server every time someone loads a page. The version your host runs affects three things you care about.
Security
Each PHP branch gets security fixes for a fixed period. After that, it reaches “end of life” and new holes are never patched by the PHP project. The official end-of-life list warns that unsupported releases may expose you to security vulnerabilities and unfixed bugs.
A recent example: on 21 October 2026, the PHP project patched two remote code execution flaws now known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). According to Help Net Security, the fixes shipped in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older only got source backports for people who build PHP themselves. We cover what this means for site owners in our PHP2Shell guide.
Speed
WordPress’s own Site Health tool says newer versions of PHP are created with increased performance in mind, so you may see a faster site after updating. The gain depends on your theme, plugins and hosting. For the full process of finding and fixing slowdowns, see our WordPress speed optimization guide.
Plugin and theme compatibility
Plugin developers test against current PHP versions. Over time, many stop supporting old ones. Stay on old PHP and you may not be able to install security updates. But an abandoned plugin may also fail on new PHP, so the order of steps below matters.
How to check your PHP version in WordPress
There are three easy ways to check your PHP version.
1. WordPress Site Health (easiest)
- Log in to your WordPress dashboard.
- Go to Tools > Site Health.
- Click the Info tab.
- Expand the Server section. The PHP version is listed there.
The Site Health documentation explains that this screen is information only, so you cannot change anything from it. If the Status tab says “Your site is running an outdated version of PHP, which requires an update”, this guide is for you.
2. Your hosting control panel
In cPanel, open MultiPHP Manager and look at the PHP Version column next to your domain. In Hostinger’s hPanel, open your website’s dashboard and search for PHP Configuration. In Plesk, open your domain’s PHP Settings. The current version is shown at the top.
3. A phpinfo() file (use with care)
Developers sometimes upload a small file that runs phpinfo() to see every PHP setting. It works, but that page shows a lot of detail about your server that attackers would love to see. If you use it, give the file a random name, look at it once, and delete it straight away. For most owners, Site Health is the better choice.
Which PHP version should you use in 2026?
Here is the status of each PHP branch, taken from php.net’s supported versions and end-of-life pages as of October 2026.
| PHP branch | Released | Status (Oct 2026) | Security fixes until | Our advice |
|---|---|---|---|---|
| 8.5 | 20 Nov 2025 | Active support | 31 Dec 2029 | Good choice if your plugins support it |
| 8.4 | 21 Nov 2024 | Active support | 31 Dec 2028 | Best balance for most sites |
| 8.3 | 23 Nov 2023 | Security fixes only | 31 Dec 2027 | Safe, and WordPress’s minimum recommendation |
| 8.2 | 8 Dec 2022 | Security fixes only | 31 Dec 2026 | Move off before the end of the year |
| 8.1 | 2021 | End of life | Ended 31 Dec 2025 | Update now |
| 8.0 | 2020 | End of life | Ended 26 Nov 2023 | Update now |
| 7.4 | 2019 | End of life | Ended 28 Nov 2022 | Update now (often needs plugin work first) |
On the WordPress side, the PHP compatibility table lists WordPress 7.0 and 7.1 as compatible with PHP 7.4 through 8.5, and the handbook states that WordPress requires PHP 7.4 or higher. Your plugins and theme are the real question.
Our rule of thumb: pick PHP 8.4 if your plugins list it as tested, otherwise PHP 8.3. Whatever branch you use, make sure your host keeps you on its latest patch release, such as 8.3.36 or 8.4.27, which include the PHP2Shell fixes.
Before you update: the safe-update checklist
Work through these in order.
- Take a full backup. Files and database, using your host’s backup tool or a plugin. Make sure you can download the copy.
- Update WordPress, plugins and your theme first. New plugin versions often contain fixes for newer PHP. Do this on your current PHP version, then check the site still works.
- Look for abandoned plugins. On each plugin’s WordPress.org page, check “Last updated” and “Tested up to”. A plugin with no update in two or more years is the most likely thing to break. Find a replacement before you switch.
- Use staging if you have it. Many hosts offer a one-click staging copy. Switch PHP there first, click through the site, and only then change the live site.
- Pick a quiet time, when few customers are using the site.
- Write down the current version. If anything goes wrong, you know exactly what to roll back to.
How to update PHP in cPanel
cPanel hosts use one of two tools. Look for both in the Software section.
MultiPHP Manager
- Log in to cPanel and open MultiPHP Manager under Software.
- Tick the checkbox next to your domain.
- Choose the new version from the PHP Version drop-down.
- Click Apply.
- Visit your site straight away to confirm nothing broke.
These steps follow cPanel’s own support article. According to the MultiPHP Manager documentation, a domain marked “Inherited” uses the server’s default version. If the version you want is missing, it is not installed on the server, and your host has to add it.
Select PHP Version
Some cPanel hosts, especially those running CloudLinux, show a Select PHP Version tool instead. Open it, pick the new version from the drop-down next to “Current PHP version” and click Set as current. This screen also lists PHP extensions. Note which ones are ticked before you switch, and make sure the same ones are ticked on the new version.
How to update PHP in Hostinger hPanel
- Go to Websites and click Dashboard next to your site.
- Search the sidebar for PHP Configuration.
- Choose the PHP version you want and click Update.
- Wait a couple of minutes, then check your PHP version again in Site Health.
Two things to know from Hostinger’s help article. First, the change applies to every website on your hosting plan, so test all of them. Second, Hostinger says existing sites can move to a higher version but generally cannot downgrade, except within the same login session if a problem appears. That makes your backup and staging test even more important here.
How to update PHP in Plesk
- Log in to Plesk and go to Websites & Domains (or Domains).
- Find your domain and open PHP or PHP Settings. On some setups it sits under Hosting & DNS.
- Pick the new version from the PHP version drop-down.
- Click OK or Apply, then test the site.
Plesk’s knowledge base points to the domain’s PHP Settings page for this. Menu names vary a little between hosts.
What about a VPS or Docker?
If you run your own server, there is no “switch” button. On a VPS, you install the new PHP packages (including PHP-FPM and the same extensions you use now), point your web server to the new version, and restart it. On Docker, you update the base image tag in your Dockerfile or compose file, for example to an image built on PHP 8.4, then rebuild and redeploy the container. Rebuilding regularly is also how you pick up patch releases like the PHP2Shell fixes. If you are new to running your own VPS, our BillionMail on Hostinger VPS guide shows how to work safely with Docker apps, logs and backups.
Common errors after a PHP update, and how to fix them
| What you see | Likely cause | Fix |
|---|---|---|
| “There has been a critical error on this website” | A plugin or theme uses code the new PHP removed | Check the email WordPress sends to the admin address. It usually names the plugin and offers a recovery mode link. Deactivate or update that plugin. |
| White screen or 500 error | Same as above, or an old PHP handler line in .htaccess | Switch back to the old version, then look for the broken plugin on staging. Ask your host to check .htaccess for old handler lines. |
| Warnings or “Deprecated” notices on the page | Debug display is on and a plugin uses outdated code | Turn off WP_DEBUG_DISPLAY on the live site, then update or replace the plugin that causes them. |
| Image uploads, PDFs or a payment plugin stop working | A PHP extension (such as imagick, intl or zip) is not enabled on the new version | Enable the same extensions you had before in your hosting panel. |
| Upload limit or timeouts changed | PHP settings are stored per version and reset to defaults | Set memory_limit, upload_max_filesize and max_execution_time again for the new version. |
| A premium plugin says a loader is missing | Encoded plugins need a loader (such as ionCube) built for that PHP version | Ask your host to enable the loader, or check the plugin supports the new version. |
If you cannot fix it fast, switch back to the version you wrote down and solve the problem on staging. If the site still misbehaves, restore your backup. And if you see strange redirects, unknown admin users or files you did not add, that is not a PHP update problem. Read our guide on what to do if your WordPress site is hacked.
When should you get help?
Updating PHP yourself is fine if you have a simple brochure site, a recent theme, a handful of well-known plugins and a host with staging and easy backups.
It is worth getting help if your site is still on PHP 7.4 or 8.0, if it takes online payments or bookings, if it uses a custom or very old theme, or if a developer built custom features you do not fully understand. A jump of several versions on a site like that often needs code fixes, not just a toggle. PHP is also only one part of keeping a site safe, so pair this with our WordPress security checklist.
If you need deeper work, such as rebuilding an old custom theme that will not run on modern PHP, our WordPress development service covers that. For ongoing peace of mind, our care plans (from $49/month) include keeping PHP, plugins and WordPress up to date.
Frequently Asked Questions
How do I check my PHP version in WordPress?
Go to Tools > Site Health in your dashboard, click the Info tab and expand the Server section. Your PHP version is listed there. You can also see it in your hosting panel, such as MultiPHP Manager in cPanel.
Will updating PHP break my WordPress site?
It can, usually when a plugin or theme is outdated. If you back up, update everything first and test on staging, the risk is low, and you can normally switch back in a minute.
What PHP version does WordPress recommend?
WordPress recommends PHP 8.3 or greater. WordPress 7.x is listed as compatible with PHP 7.4 through 8.5, but versions older than 8.2 no longer get security fixes from the PHP project.
How do I update PHP in cPanel?
Open MultiPHP Manager under Software, tick your domain, pick the new version from the PHP Version menu and click Apply. Some hosts use a tool called Select PHP Version instead, where you choose the version and click Set as current.
When is PHP 8.2 end of life?
PHP 8.2 gets security fixes until 31 December 2026, according to php.net. After that date it is end of life, so plan to move to PHP 8.3 or 8.4 before then.
Can I update PHP myself, or should my host do it?
On most shared hosting you can change the version yourself in the control panel. Your host keeps the patch releases within each branch up to date. If your site is old, custom or takes payments, it is safer to have a developer test the update first.
Want us to update PHP for you?
If you would rather not risk it, we can do it for you. We back up your site, test the new PHP version on a staging copy, fix any plugin or theme problems, and only then switch the live site. Send us your website address and we will run a free check of your PHP version and plugins, and reply within 24 hours. Ask for a free PHP check.
