How to change your PHP version

PHP version is one of the few settings that affects both speed and whether a site runs at all. Newer versions are substantially faster and receive security fixes; older applications sometimes refuse to run on them. We support 5.6 through 8.x and let you set the version per site rather than per account, so a legacy application does not hold back everything else you host.

As a rule: run the newest version your application supports, and treat anything below 8.0 as a temporary state you are working to leave. Versions below 8.0 no longer receive security updates from the PHP project.

Before you start

• Take a backup first. A version change is instant to make and instant to revert, but a site that breaks in between is still broken while you are looking at it.
• Check what your application supports. WordPress core handles 8.x well; individual plugins are the usual source of trouble.
• Change one site at a time if you host several.

Steps

1. In cPanel, open MultiPHP Manager.
2. Tick the domain or subdomain you want to change.
3. Choose the PHP version from the dropdown on the right.
4. Click Apply. The change takes effect immediately, with no restart and no downtime.
5. For extensions and settings such as memory_limit, use MultiPHP INI Editor rather than editing php.ini directly.

Check that it worked

• Load your site and click through the pages that do real work — checkout, login, search, anything that talks to a database.
• Check the error log in cPanel afterwards. A version mismatch often produces warnings before it produces a visible failure.
• On WordPress, Tools → Site Health reports the running version and flags anything incompatible.

If it goes wrong

The site shows a blank white page after the change

A fatal error with display disabled. Switch back to the previous version to restore the site immediately, then read the error log to find which plugin or library caused it. Reverting takes seconds; diagnosing on a live site does not.

A required extension is missing

Extensions are enabled per version, so switching version resets them. Open MultiPHP INI Editor, or ask support to enable it — telling us the exact extension name makes it a two-minute job.

The change does not seem to apply

Check you selected the right domain rather than the account default, and clear any caching layer in front of the site. LiteSpeed and Varnish will happily serve the previous response for a while.

If an application cannot run on a supported version, that is worth treating as a security finding rather than a preference. Unsupported PHP receives no fixes, and an outdated application is the most common route into a compromised site.

Shared and WordPress plans run LiteSpeed with Varnish, Redis and Memcached at server level, so a modern PHP version compounds with caching that is already in place. The gain from 7.4 to 8.x on a real site is usually visible without a benchmark.