How to Update PHP Version Safely on a Small Website
Your hosting dashboard shows a yellow warning that your site runs on an outdated PHP version, and you are worried that trying to update PHP version settings will take the site down.

Your hosting dashboard shows a yellow warning that your site runs on an outdated PHP version, and you are worried that trying to update PHP version settings will take the site down. That worry is reasonable: a careless switch can produce a blank white page. But staying on an old version is the bigger risk, because unsupported PHP stops getting security fixes. With a backup, a quick compatibility check and a test, the whole job takes under an hour on a small website.
This guide walks through the process for typical shared hosting and WordPress sites, which covers most small business and personal websites.
Why you need to update PHP version support at all
PHP is the programming language that runs WordPress, most other content management systems and many contact forms. Each version gets two years of active support, then roughly two more years of security fixes only, then nothing.
- Security. Once a version reaches end of life, newly found vulnerabilities are not patched. PHP 8.1 lost security support at the end of 2025, and PHP 8.2 reaches the same point on 31 December 2026.
- Speed. Each major release has been faster than the last. Moving from PHP 7.4 to 8.3 commonly cuts server response times by 10 to 30 percent on WordPress sites with no other changes.
- Compatibility. New plugin and theme versions increasingly require PHP 8.1 or later. Stay behind long enough and you will be unable to install updates at all.
Some hosts now charge an extra monthly fee to keep running an end of life version. That fee is a strong hint to move.
Check your current PHP version
There are three quick ways to find out what you are running:
- WordPress: go to Tools, then Site Health, then the Info tab, and open the Server section.
- Hosting panel: in cPanel, look for "MultiPHP Manager" or "Select PHP Version". Plesk and most custom panels have a PHP settings page per domain.
- Other sites: ask your host's support chat. They can see it instantly.
Write down the exact current version, for example 7.4.33. If anything goes wrong, this is what you will roll back to.
Back up and check compatibility first
Take a full backup of both files and database before you touch the setting. Many hosts offer one click backups, but download a copy to your own computer as well. If you have never restored a backup, read our guide on how to back up your website and actually test the restore before going further.
Next, check that your code supports the target version:
- Update everything first. Update WordPress core, the theme and every plugin on your current PHP version. Old plugin versions are the most common cause of errors after a PHP change. Our piece on how often to update website plugins explains a safe routine.
- Read plugin pages. Each plugin in the WordPress directory lists "Requires PHP" and is often tested against newer releases. Note any plugin not updated in more than 12 months.
- Check custom code. If a developer built your theme or added custom functions, ask them which PHP versions they tested. Code written for PHP 7 often uses functions removed in PHP 8.
Remove plugins you no longer use. Every inactive plugin is still code that has to work with the new version.
How to update PHP version settings step by step
- Use a staging site if your host offers one. Clone the live site to staging, switch PHP there and test. This removes almost all risk.
- Turn on error logging. In cPanel, make sure error logs are enabled for the domain. You will check them after the switch.
- Change the version. In MultiPHP Manager or Select PHP Version, choose your domain, pick the new version from the dropdown and apply. The change takes effect within seconds.
- Clear caches. Purge any caching plugin, the server cache and your CDN, then load the site in a private browser window.
- Test the important pages. Home page, a blog post, the contact form, the checkout if you sell anything, the login page and the admin dashboard. Submit the contact form and confirm the email arrives.
- Read the error log. Look for lines marked "Fatal error" or "Deprecated". Fatal errors need fixing now. Deprecated notices are warnings for future versions and can wait, but note them.
- Repeat on live. If staging looks good, make the same change on the live site and test again.
If the site breaks, switch back to the version you noted earlier. The rollback is instant, and you can then deal with the problem plugin calmly.
Common errors after a PHP change and what they mean
Most problems after a switch fall into a few patterns, and each points to a clear fix:
- A blank white page or "There has been a critical error". A plugin or theme uses code the new version no longer accepts. The error log names the file. Rename that plugin's folder by FTP or the file manager to disable it, then look for an update or a replacement.
- "Call to undefined function". Usually a missing PHP extension, such as intl, gd or mbstring. In the Select PHP Version screen, tick the extension for the new version; extension choices do not always carry over.
- Layout or forms broken but no errors. Almost always an old cache. Purge every cache layer again, including the CDN.
- "Allowed memory size exhausted". The new version may have a lower default memory limit. Raise memory_limit to 256M in the PHP options.
Why the newest version is not always the right target
A lot of advice says to always pick the newest PHP release your host offers. For a small site without a developer on call, I disagree. A new PHP version arrives every November, and plugins and themes usually take a few months to catch up. Switching in the first weeks after release means you are the one discovering the bugs.
A better rule: choose the newest version that is at least three months old and that every plugin you rely on lists as supported. In late 2026, that usually means PHP 8.3 or 8.4. You still get full security support for years, without being an early tester. If you would rather not think about any of this, a managed WordPress hosting plan handles PHP upgrades for you, usually with testing included.
Frequently asked questions
Will updating PHP break my website?
It can, mainly when old plugins or custom code use functions removed in newer versions. Updating everything first, testing on staging and keeping a backup makes problems rare. If something breaks, switching back takes seconds.
Which PHP version should I use for WordPress?
Use a version that still receives security support and that your theme and plugins list as compatible. In late 2026, PHP 8.3 or 8.4 is a safe choice for most WordPress sites. Avoid any version that has reached end of life.
How often should I update the PHP version on my site?
Plan a move roughly every two years, or whenever your current version is within six months of losing security support. Many hosts send reminders. Checking once a year during a routine maintenance session keeps you ahead.
More in Maintenance and Security
Maintenance and Security
How to Stop Spam Comments Without Killing Real Ones
The first spam comment on a site I built for a friend's bike repair shop arrived nine days after launch, before the site had a...
Maintenance and Security
How to Fix an Expired SSL Certificate on Your Website
A site I help with went dark on a Sunday morning in March. Not down, exactly.
Maintenance and Security
How to Set Up Two-Factor Authentication on Your Website
Most small websites that get broken into are not hacked through clever code.