How to change the PHP version in cPanel

When to use this

Change your PHP version when your software asks for a newer one, when a plugin or framework update needs it, or when your current version has reached end of life and no longer receives security fixes. You might also switch back temporarily if an old site breaks after an upgrade.

PHP releases are supported for a limited time. The php.net supported versions page lists each branch's end dates. As of October 2026 it lists PHP 8.2, 8.3, 8.4 and 8.5 as supported, with 8.2 reaching end of life on 31 December 2026; 8.1 and older no longer receive security fixes. Running unsupported PHP is a security risk, as explained in how to secure a website.

ODHOST note: Which PHP versions and which tool you see depend on your server's configuration. Open your cPanel to check, or ask support.

Before you switch

1. Check your software's requirements: the WordPress requirements page, your theme and plugin pages, or your framework's documentation.
2. Update WordPress core, themes and plugins on the current PHP version first, so they are ready for the new one.
3. Back up your files and database, as described in restoring a backup in cPanel.
4. Note your current PHP version so you can switch back.

Option 1: MultiPHP Manager

1. Open Software > MultiPHP Manager in cPanel. Menus vary by version and host configuration.
2. Tick the domain you want to change. Each domain and subdomain can use a different version.
3. Choose the new version from the PHP Version menu at the top right.
4. Click Apply.

To change settings such as memory_limit, upload_max_filesize or max_execution_time for that version, use Software > MultiPHP INI Editor.

Option 2: Select PHP Version (CloudLinux)

1. Open Software > Select PHP Version.
2. Choose the version from the Current PHP version menu and click Set as current (labels vary slightly between releases).
3. Review the Extensions list. Make sure the extensions your app needs, such as mysqli, gd, intl, zip or imagick, are ticked for the new version.
4. Open the Options tab to adjust limits like memory_limit if needed.

If your account has both tools, follow your host's guidance on which one controls your sites; when in doubt, ask support.

Test immediately

1. Load your home page and several inner pages in a private window.

2. Log in to the admin area, save a post or setting, and test forms and checkout.

3. Check Metrics > Errors and any error_log file for new warnings or fatal errors.

4. Confirm the active version with a temporary file named phpinfo.php containing the code below, open it in the browser, then delete it, because it reveals server details.

   <?php phpinfo();
   

If something breaks

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

A white screen or 500 error right after a switch is usually a fatal error from old code; fixing a 500 error covers how to find it.

If it still fails

Open a support ticket and include:

• The domain, the PHP version before and after, and which tool you used
• The error message and log lines that appeared after the switch
• Extensions your app needs that you cannot find in the list
• The time you made the change (IST)

Developers who need precise control over PHP and extensions can compare options on hosting for developers.