cPanel ships MultiPHP, which lets each account pick one PHP version from the EasyApache 4 list. CloudLinux adds PHP Selector, which lets each account pick a PHP version and per-account extensions, INI settings, and even alternative PHP builds (LSPHP, low-mem builds). Most teams treat them as the same feature, but they differ in important ways once you operate at scale.
What’s happening
MultiPHP runs the standard EA4 PHP packages — ea-php74, ea-php82, etc. — and exposes them as alternative interpreters via mod_lsapi or PHP-FPM. The customer picks one through the cPanel UI. Configuration is per-account .htaccess or .user.ini; global PHP settings come from EA4’s /opt/cpanel/ea-php82/root/etc/php.ini.
PHP Selector sits in the LVE/CageFS context. It exposes additional PHP versions (including older ones beyond EA4’s reach), separate extensions, and per-account php.ini overrides through a simpler UI than MultiPHP. Crucially, PHP Selector ships its own builds that integrate tighter with LVE accounting — memory limits per LVE rather than per PHP process.
The practical difference: MultiPHP is sufficient for a host where every account picks one of the cPanel-supported versions and uses the default extensions. PHP Selector wins when accounts need custom extension sets (a customer who needs both imagick and oci8, which conflict in some builds) or when LVE PMEM accounting is important.
How to verify
What is installed:
# MultiPHP versions available
whmapi1 php_get_installed_versions
# Per-account assignment
whmapi1 php_get_vhost_versions
# PHP Selector status (CloudLinux only)
selectorctl --list
selectorctl --user-current --user=<username>
For a specific user, which PHP and which extensions are active:
ls -la /home/<user>/public_html/.htaccess
grep -i 'AddHandler\|application/x-httpd' /home/<user>/public_html/.htaccess
sudo -u <user> php --version
sudo -u <user> php -m | head -30
The fix
The choice depends on what you need:
- Stick with MultiPHP if: all customers use stock EA4 builds, you do not need per-account extension differences, and customers are okay with a fixed set of PHP versions.
- Switch to PHP Selector if: customers need legacy PHP (older than EA4 supports), per-account custom extensions, or LVE-integrated memory accounting.
- Migrate path: PHP Selector and MultiPHP can coexist; LiteSpeed and Apache pick up the active version per the same
.htaccessdirectives. To migrate an account, enable Selector for the user, set the version via Selector, and confirm withselectorctl --user-current. - Update routine: PHP Selector has its own update cycle separate from EA4. Run
selectorctl --update --interpreter=phpmonthly. EA4 updates apply automatically throughcpanel-yum. - Per-account php.ini: Selector exposes a UI; MultiPHP requires the customer to edit
.user.ini. For non-technical customers, Selector reduces support load.
The historical “Selector is better” argument is less true than it was — modern EA4 is comprehensive. The decision is now about extension flexibility and accounting integration, not raw capability. Stack Harbor picks per cluster based on customer mix as part of cPanel/WHM management.