How to Change the PHP Version in cPanel

cPanel servers offer one of two tools for changing PHP versions: MultiPHP Manager (standard cPanel) or Select PHP Version (on CloudLinux servers). In either, you pick the domain or account, choose the new PHP version, apply it, and test the site. Back up first, update your CMS and plugins, and keep note of the previous version so you can switch back quickly if something breaks.

Why the version matters is explained in which PHP version should your website use.

Before you change

1. Back up files and database; see how to back up your website in cPanel.
2. Update WordPress (or your CMS), themes and plugins, so they support the newer PHP.
3. Note the current version and any custom PHP settings.
4. If possible, test on a staging copy or subdomain first.

Option 1: MultiPHP Manager

1. In cPanel, open Software → MultiPHP Manager.
2. You will see each domain with its current PHP version.
3. Tick the domain(s) you want to change.
4. Choose the new version from the PHP Version dropdown and click Apply.

The change takes effect almost immediately. Each domain can use a different version.

To change PHP settings (memory limit, upload size, max execution time), use Software → MultiPHP INI Editor, choose the domain, and edit the values in Basic Mode.

Option 2: Select PHP Version (CloudLinux)

1. In cPanel, open Software → Select PHP Version.
2. Choose the version from the Current PHP version dropdown and click Set as current.
3. On the Extensions tab, tick the extensions your site needs (for example intl, imagick, zip, opcache). Extensions are set per version, so check them after switching.
4. On the Options tab, adjust settings such as memory_limit, upload_max_filesize and max_execution_time.

On some servers this selector applies to the whole account; on others, per-domain versions are configured differently. Follow what your host provides.

After switching: test

• Home page and a few key pages load correctly
• Admin login and dashboard work
• Forms send, checkout works (test mode)
• No new errors in Metrics → Errors or the site's error_log
• For WordPress: Tools → Site Health shows the new version without critical issues

If something breaks

1. Switch back to the previous version in the same tool; the site should recover immediately.
2. Read the error log to find the plugin, theme or code that failed.
3. Update or replace that component, then try the newer version again.

A white screen or "critical error" in WordPress is covered in how to fix the WordPress white screen of death.

Common issues

Problem	Fix
"Call to undefined function"	Required extension not enabled for the new version
Deprecated warnings shown on pages	Turn off display_errors on production; fix in code
Different version in terminal vs website	CLI php -v can differ; the website's version is set in cPanel
Settings reset after switching	PHP options are per version; set them again

Worked example: moving a WordPress site from PHP 8.1 to 8.3

PHP 8.1 has reached end of life, so a site still on it should move. A safe sequence:

1. Check what will run. In WordPress, Tools → Site Health shows the current PHP version. Look up each active plugin's "Requires PHP" and "Tested up to" information, and check that your theme has been updated recently.
2. Back up and update. Take a full backup, then update WordPress, the theme and all plugins while still on 8.1.
3. Test on a copy. If your host offers staging, switch the staging copy to 8.3 first. Otherwise, choose a quiet time for the live site.
4. Switch to 8.3 in MultiPHP Manager or Select PHP Version and, if you use Select PHP Version, re-tick the extensions the site needs.
5. Test the key journeys: home page, a post, the contact form, login, and for shops a test order.
6. Watch the error log for an hour. A "Deprecated" notice is a warning to fix later; a "Fatal error" names the plugin or theme file that must be updated or replaced.
7. If something breaks, switch back to 8.1 immediately, fix or replace the component, and try again.

Moving one version at a time (8.1 → 8.2 → 8.3) is not required, but it can make it easier to see which change caused a problem on complex sites.

Checking the version your site really uses

The version shown by php -v over SSH is the command-line version, which can differ from the website's. To see the website's actual version, check Site Health in WordPress, or create a temporary file containing <?php echo PHP_VERSION; in the site folder, open it in a browser, then delete it straight away.

Frequently Asked Questions

Which version should I choose?

The newest version your software supports that still receives security updates.

Can different sites in my account use different versions?

With MultiPHP Manager, yes, per domain. With Select PHP Version, it depends on the server setup.

Will changing PHP affect email or databases?

No. It only changes how PHP code runs for websites.

Related reading

PHP version choices are part of keeping a site secure; see website security basics. Current PHP versions are available on the ServerNeed shared hosting plans.

Sources

• cPanel documentation: MultiPHP Manager
• cPanel documentation: MultiPHP INI Editor
• CloudLinux documentation: PHP Selector