7 Checks Before Upgrading Your PHP Version

Each PHP version only receives security updates for a limited time. A site on an unsupported version has to live with security holes that will never be patched. On the other hand, an old plugin or theme may not work on the new version. The checks below make the switch painless.

1. Find out which versions are supported

The php.net/supported-versions page shows which PHP versions get active support or security-only support. If you're on an unsupported version, we recommend not putting the upgrade off.

2. Note your current version

In WordPress, Tools › Site Health › Info › Server shows the PHP version the site runs on. Note it so you can go back if something breaks.

3. Take a backup

Don't change versions without a current copy of the files and database. See backing up in cPanel.

4. Update WordPress, themes and plugins

Most compatibility problems come from outdated plugins. Update everything first, as described in our safe update guide. Identify plugins that haven't been updated for a long time and, where possible, replace them with an actively developed alternative.

5. Check the versions your plugins support

Most premium themes and plugins list supported PHP versions in their release notes. Check this especially for page builders, payment plugins and plugins that verify licences.

6. Test first

If you can, open a copy of the site on a subdomain and try the new PHP version there first. How to create one is in the addon domain and subdomain article. To keep the test site out of search engines, tick "discourage search engines from indexing this site" in WordPress.

7. Switch and check straight away

Choose the new version in cPanel's PHP version tool. Then check:

• Do the home page, a few inner pages and the dashboard load?
• Does the contact form send, and do the payment steps work if you have them?
• Does Tools › Site Health show a new critical issue?
• Has an error_log file appeared in your site's folder in File Manager? If so, its last lines point to the problem plugin.

If something breaks

If the site shows a white screen or a "critical error", switch back to the old version you noted. The site recovers immediately and you can identify the problem plugin calmly. Staying on the old version is temporary; the real fix is updating or replacing the incompatible plugin. If you need help, open a support ticket with the lines from the error log.