- Picks which PHP version your account runs on (anything from the oldest still-supported branch up through the latest stable release).
- Toggles which PHP extensions are loaded (Extensions tab).
- Tunes core
php.inidirectives like memory limit and upload size (Options tab).


The PHP version applies to the whole account. Every domain, every subdomain, every script you run uses the version you pick. Per-domain selection is on the roadmap and we’ll surface it here when it ships. Until then, if one site needs a newer version and another needs an older one, you have to either pick the one both can live with, or split into separate cPanel accounts.
Switch PHP versions
Pick the version from the dropdown
Top of the page. The dropdown shows every PHP version installed on the server you’re on. We keep the list current with the latest stable release (currently up to 8.5) and prune branches as they leave upstream security support, so you’ll always see the newest stable down to the oldest still-safe version.Coverage varies by server, so not every node has every version. If a specific version you need isn’t in the dropdown, open a ticket and we’ll see whether we can install it on your server.
Click 'set as current'
The change is instant. New PHP requests use the new version starting with the next request.
Where to go next
Extensions
Toggle individual PHP extensions like
intl, gd, mysqli, redis.Options
Tune
memory_limit, upload_max_filesize, max_execution_time, and other php.ini settings.What it doesn’t do
- It doesn’t change PHP per-domain. Coming soon.
- It doesn’t roll back automatically if a site breaks. You’re responsible for picking a working version. Take a JetBackup snapshot before risky version jumps (5.x → 8.x in particular).
- It doesn’t manage Composer or Pecl. Those still go via SSH or via Perl Modules / PEAR Packages for their respective ecosystems.
How it relates to PHP X-Ray
X-Ray traces requests against the current selected PHP version. If you switch versions, restart any X-Ray tasks. See X-Ray App.Common issues
The site shows 500 errors after a version change
The site shows 500 errors after a version change
First place to check: Errors tool. Almost always a deprecation or a missing extension. Switch back to the old version while you fix the code.
The version dropdown is greyed out
The version dropdown is greyed out
A pre-existing custom configuration in
~/php.ini or a server-level lock can disable the selector. Open a ticket; we can clear it.My code uses /usr/bin/php and ignores the version I picked
My code uses /usr/bin/php and ignores the version I picked
The selector controls the cPanel-managed PHP handler used for HTTP requests. CLI scripts that hard-code
/usr/bin/php use the system default. Use php (no path) in your shebang to pick up the cPanel-selected version, or hard-code the version-specific path under /opt/cpanel/ea-phpXX/root/usr/bin/php (replace XX with the version, e.g., 85).
