How to Upgrade Your WordPress PHP Version: A Step-by-Step Guide
If you've seen the "Your site is running an outdated version of PHP" warning in your WordPress dashboard, you're not alone. PHP is the programming language WordPress runs on, and its version directly affects both your site's speed and its security. Done with the right steps, a PHP upgrade is a reversible job that takes a few minutes.
In this guide, we explain step by step how to find your current PHP version, what to check before upgrading, how to change the PHP version in cPanel and how to go back if something goes wrong. There's also a separate section for VDS users.
First take a full backup of your site and update WordPress, your theme and your plugins. Then choose the new version on the Select PHP Version or MultiPHP Manager screen in cPanel and test your site. If a problem occurs, you can go back to the old version with one click on the same screen. As of November 2026, the most balanced choice is PHP 8.3; if your plugins are compatible, PHP 8.4 can also be used.
- 01 Why Should You Upgrade Your PHP Version?
- 02 Which PHP Version Should You Choose?
- 03 Find Your Current PHP Version
- 04 Before Upgrading: Backups and Compatibility
- 05 Changing the PHP Version in cPanel
- 06 Testing After the Upgrade
- 07 What to Do If Errors Occur
- 08 Upgrading the PHP Version on a VDS
- 09 Checklist
- 10 Frequently Asked Questions
- 11 Conclusion
Why Should You Upgrade Your PHP Version?
Each major version of PHP is updated for a set period; when that period ends, no patches are released for new security vulnerabilities. Staying on an old version carries three concrete risks:
- Security: Vulnerabilities found in a PHP version whose support has ended aren't fixed. Even if the rest of your site is up to date, the underlying platform remains exposed.
- Speed: The PHP 8 series runs the same code more efficiently than the old 7.x versions. This is especially noticeable on pages that can't be cached (dashboard, cart, checkout).
- Compatibility: Plugin and theme developers drop support for old PHP versions over time. Sites that stay on old PHP eventually stop receiving plugin updates.
If your site is slow in general, the PHP version may not be the only reason; you can find the other possible causes in our guide explaining why your website is slow.
Which PHP Version Should You Choose?
After its release, each major PHP version gets two years of active support, followed by two years of security-only support. The table below summarizes the situation as of November 2026:
| PHP version | Support status | Recommendation |
|---|---|---|
| 7.4 and earlier | End of life (7.4: November 2022) | Upgrade urgently |
| 8.0 | End of life (November 2023) | Upgrade urgently |
| 8.1 | End of life (December 31, 2025) | Upgrade |
| 8.2 | Security support ends December 31, 2026 | Upgrade before the end of the year |
| 8.3 | Security support until December 31, 2027 | Recommended balanced choice |
| 8.4 | Active support until the end of 2026, security support until the end of 2028 | Choose it if your plugins are compatible |
| 8.5 | The newest version, in active support | Try it in a test environment first |
WordPress core adapts quickly to new PHP versions; problems usually come from plugins and themes that aren't updated. On sites that use many plugins or have a custom-built theme, a mature version with a long support period (8.3 for now) causes fewer surprises.
Find Your Current PHP Version
The easiest way is WordPress's own Site Health screen:
- In the WordPress dashboard, open Tools β Site Health.
- Switch to the Info tab and expand the Server section.
- You'll see the version your site uses on the PHP version line.
You can also see the same information at the top of the Select PHP Version screen in cPanel. If you have SSH access to the server, you can find it with WP-CLI too:
wp --info
wp plugin list --update=available The second command lists plugins with pending updates. This list shows what you need to update before upgrading.
Before Upgrading: Backups and Compatibility
Take a full backup
Back up your files and database together. The Backup tool in cPanel or WP Toolkit's backup feature is enough for this. Also keep the backup off the server, for example on your own computer.
Update WordPress, your theme and plugins
Most upgrade errors are caused by old plugin versions. Before changing PHP, update WordPress core, your theme and all of your plugins.
Identify plugins that haven't been updated for a long time
On the plugin page at WordPress.org, check the "Last updated" and "Tested up to" information. Plugins that haven't been updated for more than a year are the most likely to cause problems on new PHP versions. If possible, use up-to-date alternatives to them.
For important sites, try it in a test environment first
For e-commerce or high-traffic sites, create a copy of the site on a subdomain and try the PHP upgrade there first. WP Toolkit's Clone feature creates this copy in a few clicks. If the copy works without problems, do the same on the live site.
Changing the PHP Version in cPanel
In cPanel, the PHP version is managed from two different screens depending on the server's configuration. On hosting platforms that use CloudLinux, the first method usually applies.
Method 1: Select PHP Version
- Log in to cPanel and click the Select PHP Version icon in the Software section.
- Choose the new version (e.g. 8.3) from the Current PHP version drop-down at the top.
- Apply the change. In some interfaces, you need to click the Set as current button for this.
- On the Extensions tab, check that the extensions WordPress needs are ticked:
mysqli,curl,gdorimagick,intl,mbstring,zip,xmland, for performance,opcache.
Extensions you enabled on the old PHP version may not be enabled automatically on the new version. Before upgrading, take a screenshot of the current version's Extensions list and tick the same extensions on the new version. Likewise, check the memory_limit, upload_max_filesize and max_execution_time values on the Options tab.
Method 2: MultiPHP Manager
- In cPanel, open Software β MultiPHP Manager.
- Tick the domain whose version you want to change in the list.
- Choose the new version from the PHP Version list in the top right and click Apply.
If there's more than one site on your account, MultiPHP Manager lets you choose a separate version for each domain. That way, you can upgrade the sites one by one, in turn.
Testing After the Upgrade
After changing the version, clear the cache first. If you use LiteSpeed Cache, start with LiteSpeed Cache β Toolbox β Purge All. Then check the following in a private (incognito) browser window:
- Do the home page and a few posts and pages load properly?
- Can you log in to the WordPress dashboard and save a post?
- Do the contact forms send email?
- If it's an e-commerce site, do adding a product to the cart and the checkout steps work?
- Does the Site Health screen show the new PHP version, and are there any critical warnings?
What to Do If Errors Occur
If you see the message "There has been a critical error on this website" or a white screen, don't panic. First get the site back up, then find the cause.
Select the old PHP version again
Going back to the old version from the screen where you changed the PHP version usually fixes the site within a few seconds. Your files and database aren't affected by the PHP change.
Turn on the error log
To find the plugin causing the problem, add the following settings to the wp-config.php file, before the /* That's all, stop editing! */ line, and try the new PHP version again:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false ); Errors are now written to the wp-content/debug.log file without being shown to visitors. The line starting with Fatal error in the file contains the folder name of the plugin or theme causing the problem. After solving the problem, delete these three lines or set WP_DEBUG to false.
If you can't access the dashboard, rename the folder
If you can't access the dashboard, go to the wp-content/plugins folder with cPanel's File Manager and rename the problematic plugin's folder (e.g. plugin-name β plugin-name-disabled). WordPress automatically disables that plugin. Then install the plugin's latest version or switch to an alternative.
Lines in the error log starting with Deprecated show that a plugin uses a PHP feature that will be removed in the future. The site keeps working; however, the plugin developer needs to fix these warnings in future versions. Lines that stop the site start with Fatal error.
Upgrading the PHP Version on a VDS
If you run WordPress on your own VDS without a control panel, you install PHP with the package manager. The default version in the Ubuntu 24.04 repository is PHP 8.3. On a server using Nginx and PHP-FPM, the installation looks like this:
sudo apt update
sudo apt install php8.3-fpm php8.3-mysql php8.3-curl php8.3-gd php8.3-intl php8.3-mbstring php8.3-xml php8.3-zip
php -v Then make sure the fastcgi_pass line in your Nginx site configuration points to the new version's socket, and reload the services:
# In /etc/nginx/sites-available/yourdomain:
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
sudo nginx -t
sudo systemctl reload nginx php8.3-fpm Don't remove the old version's FPM service until you're sure everything works on the new version; if you need to go back, changing just the fastcgi_pass line is enough. If you've just set up the server, also take a look at our Ubuntu VDS initial setup guide for security.
Checklist
- β I noted the current PHP version from the Site Health screen.
- β I took a file and database backup and kept a copy off the server.
- β I updated WordPress, the theme and all plugins.
- β I took a screenshot of the current PHP extensions and settings.
- β I selected the new PHP version and ticked the extensions again.
- β I cleared the cache and tested the front end, dashboard, forms and checkout steps.
- β If I turned on debug settings, I turned them off when I was done.
Frequently Asked Questions
Will upgrading the PHP version break my site?
With up-to-date WordPress, themes and plugins, it usually goes smoothly. Problems usually come from a plugin that hasn't been updated for a long time. Because the change is reversible, if a problem occurs you can fix the site right away by going back to the old version.
Will a PHP upgrade delete my data?
No. The PHP version only determines which interpreter runs the code; your files and database don't change. Still, it's recommended to take a backup first, just in case.
Should I choose PHP 8.3 or 8.4?
As of November 2026, PHP 8.3 is a mature version with security support until the end of 2027, compatible with the vast majority of plugins. PHP 8.4 offers a longer support period; if the plugins you use support 8.4, you can choose 8.4.
Why does the WordPress dashboard still show the old version?
The change sometimes takes from a few seconds to a few minutes to take effect. Clear your browser and plugin cache and refresh the Site Health page. If your account has more than one PHP management screen, make sure you made the change for the right domain.
How often should I upgrade PHP?
Keep track of the end-of-support date of the version you use and move to the next version before that date. In practice, this means a planned maintenance job about every two years.
Conclusion
Upgrading the PHP version in WordPress isn't risky when done in the right order; it's a routine maintenance task: take a backup first, update everything, select the new version and check the extensions, test, and roll back with one click if needed. For now, PHP 8.3 is a balanced target; if you're using PHP 8.2, plan to upgrade before the end of 2026.
If you can't find current PHP versions in your hosting provider's panel, or you struggle to get support with every upgrade, this may be one of the signs that it's time to switch hosting providers.
Explore Netiyo WordPress Hosting plans with cPanel, LiteSpeed, CloudLinux, NVMe SSD, WP Toolkit and free SSL. If you need more resources and full control, also take a look at our VDS server options.
Explore WordPress Hosting