PHP versions, extensions, and MultiPHP

MultiPHP lets you choose a different PHP version for each domain on your cPanel account. You also control which extensions load and how much memory PHP may use. On shared hosting this runs through LiteSpeed and CloudLinux LVE, so you never need root or a system-wide PHP restart.

Choose a version in MultiPHP Manager

Open MultiPHP Manager in cPanel, select the domain, and pick a supported version such as 8.2 or 8.3. Save the change and the site begins using that interpreter. One account can run 8.2 on the live shop and 8.3 on a staging subdomain. That per-domain control is the reason MultiPHP exists.

Plugins that still require PHP 7.4 are usually unmaintained. WordPress expects 8.1 or newer by 2026, so plan upgrades before you hit a hard cutoff on your themes or plugins.

php -v; php -m | head

The php -v command in Terminal shows the CLI binary for your account. That binary may not match the lsphp version your website actually uses. Confirm the live version in MultiPHP Manager for the domain first. Then run php -m when you need a list of loaded extensions for scripting or cron work.

Enable only the extensions you need

Most sites want intl, gd or imagick, and zip. Add soap when a payment gateway requires it, and the Redis client only if you use object caching. Disable extensions you do not use so the stack stays lean. Leave OPcache turned on; disabling it to debug a plugin rarely helps and usually slows the site. Use the plugin’s own debug tools instead.

Edit limits in MultiPHP INI, not .htaccess

For WordPress, set memory_limit to at least 256M. Use 512M when you run WooCommerce with a heavy page builder. Keep post_max_size larger than upload_max_filesize so large uploads do not fail partway through. Do not set memory_limit with php_value inside .htaccess on LiteSpeed. Use the MultiPHP INI Editor in cPanel instead.

A newer PHP version is not always faster by itself. Version 8.3 is a solid default, but a slow database query stays slow no matter which interpreter you pick. Measure before you chase version numbers alone.

If a plugin fatals on 8.3, name the plugin and paste the full fatal when you open a ticket. We will not guess from a vague description. Cron jobs that call /usr/local/bin/php should match the version you chose for the vhost, or scheduled tasks can run under a surprise interpreter.