Change PHP version and extensions in cPanel

Which cPanel tool does what

cPanel has three PHP tools under cPanelSoftware. Most people only ever need the first one.

The rule that explains most confusion: Select PHP Version only affects domains whose MultiPHP Manager setting is "inherit", which is the default. Once you pin a domain to a specific version in MultiPHP Manager, it stops following Select PHP Version, including its extensions and options.

Which version to pick, as of October 2026:

Step 1: Switch the PHP version

1. Open Select PHP Version

   Go to cPanelSoftwareSelect PHP Version. The top of the page shows the Current PHP version for the account.

   cPanel›Software›Select PHP Version

   PHP SelectorExtensions · Options

   Current PHP version

   8.3 ▾

   Applies to

   Domains set to inherit

   bcmathgdimagickintlioncube_loaderopcacheredissoapzip

   Set as currentReset to default

2. Choose a version and apply it

   Pick the version from the drop-down and click Set as current if your screen shows that button; on newer screens the change applies as soon as you choose. Reload your site in a private window and click through a few pages.

3. Need one domain on a different version?

   Open cPanelSoftwareMultiPHP Manager, tick the domain, choose a version from the PHP Version list and click Apply. To hand it back to Select PHP Version later, choose inherit.

   cPanel›Software›MultiPHP Manager

   DomainPHP versionDocument root

   yourdomain.ininherit (8.3)/public_html

   old.yourdomain.inPHP 8.1 (ea-php81)/old.yourdomain.in

   Apply

Step 2: Turn extensions on or off

Extensions are optional PHP modules, for image processing, encrypted scripts or caching. In Select PHP Version, open the Extensions tab and tick or untick a box; each change saves straight away. Each PHP version keeps its own list, so check it again after switching versions.

Step 3: Raise limits: memory, uploads and timeouts

Open the Options tab in Select PHP Version and click a value to change it. These are sensible values for a typical WordPress or WooCommerce site:

For a domain pinned in MultiPHP Manager, change the same values in cPanelSoftwareMultiPHP INI Editor: choose the domain in Basic Mode, edit and click Apply.

Check the change took effect

For WordPress, the quickest check is WordPressToolsSite HealthInfoServer, which lists the PHP version, memory limit and upload size. For anything else, use a phpinfo page:

1. Create the file

   In cPanelFilesFile Manager, open the site's folder (usually public_html), create a file with a hard-to-guess name such as info-7f3k2q.php and add this single line:

   <?php phpinfo();

2. Open it and read three values

   Visit https://yourdomain.in/info-7f3k2q.php. Check PHP Version at the top, then search the page for memory_limit and upload_max_filesize. The Local Value column is what your site actually uses.

3. Delete the file straight away

   Never leave phpinfo online. It shows your server paths, loaded modules and configuration, which is exactly what someone probing for weaknesses looks for. Delete it as soon as you've read it.

Using the cPanel Terminal? php -v shows the account's version, not the version of a domain pinned in MultiPHP Manager, so the browser check is the reliable one.

WordPress: Upgrade PHP without surprises

WordPress itself runs on every version we offer, and running a current one is part of our website speed checklist. What breaks on a PHP upgrade is usually an old plugin or theme. This order avoids most trouble:

1. Update everything first

   Update WordPress, all plugins and the theme on your current PHP version. Remove plugins you no longer use, and check the "Requires PHP" and "Tested up to" lines of the ones that haven't been updated in a year.

2. Try it on staging, then switch

   Change the version on your staging copy (or take a backup, and know how to restore a cPanel backup), then test the pages that matter: home, a post, a form, wp-admin and, for stores, a test checkout.

3. Log errors quietly while you test

   Add these lines to wp-config.php above /* That's all, stop editing! */. Errors then go to wp-content/debug.log instead of your visitors' screens. Remove them when you're done:

   define( 'WP_DEBUG', true );
   define( 'WP_DEBUG_LOG', true );
   define( 'WP_DEBUG_DISPLAY', false );

If something breaks, switch back to the previous version: it takes effect in seconds. Then update or replace the plugin named in the log. Setting up a fresh site to test on? See Install WordPress with Softaculous.

PHP version troubleshooting in cPanel