PHP Settings

Switching PHP Versions in cPanel With MultiPHP Manager

Use cPanel's MultiPHP Manager to set the right PHP version per domain, then fine-tune extensions and limits in the MultiPHP INI Editor.

Instant

PHP version switch with no server restart

Per-Domain

Set a different PHP version for each site on the account

24/7

Human support if a version switch breaks a plugin

Free

Managed migration keeps existing PHP settings intact

In short

To change the PHP version in cPanel, open MultiPHP Manager under the Software section, tick the checkbox next to the domain that needs a different version, pick the target version from the dropdown menu, and click Apply. The switch takes effect immediately, with no server restart, so the new version is live within seconds of clicking Apply.

Extensions, memory limits, and upload sizes aren't part of that screen — those live in the MultiPHP INI Editor, a separate cPanel tool for the same domain.

Every WordPress plugin, Laravel app, or custom PHP script a site runs was built against a specific PHP version, and running it on the wrong one is a common cause of white-screen errors, deprecated-function warnings, or plugins refusing to activate at all. cPanel doesn't lock an account to one PHP version — MultiPHP Manager lets several versions run side by side across different domains under the same account.

This matters most right after a plugin update, a fresh WordPress install with a minimum PHP requirement, or a migration from another host that had a different default version set. Knowing exactly where to change it — and where to adjust the settings that go with it — avoids guessing and repeated support tickets.

Finding MultiPHP Manager in cPanel

MultiPHP Manager sits in the Software section of cPanel, usually a few icons down from Softaculous Apps Installer. Opening it displays every domain and subdomain on the account in a table, with a column showing which PHP version each one currently runs — useful for spotting a site that's still stuck on an old version after a migration.

The dropdown at the top-right of that table lists every PHP version available on the server, typically spanning several recent major and minor releases. Selecting multiple domains at once, then picking a version and clicking Apply, changes all of them together — handy when several add-on domains all need the same update.

Choosing the Right Version for the Application

WordPress, Laravel, and most modern PHP frameworks publish a minimum and a recommended PHP version in their own documentation, and that number should be the starting point rather than just picking the newest option available. Jumping straight to the newest version can break plugins built against older function signatures, especially anything that hasn't been updated in a year or two.

A safer approach is testing the site immediately after the switch — loading the homepage, logging into the admin area, and checking a plugin or two that handles something critical like payments or forms. If anything breaks, MultiPHP Manager reverts just as fast as it switched, so rolling back to the previous version costs nothing but a few clicks.

Tuning Extensions and Limits in MultiPHP INI Editor

Once the version itself is set, MultiPHP INI Editor — the tool right next to MultiPHP Manager — controls the PHP extensions and configuration values tied to that version for the selected domain. Extensions like imagick, intl, or opcache can be toggled on or off here without touching a php.ini file directly.

The same editor exposes memory_limit, upload_max_filesize, post_max_size, and max_execution_time as editable fields. A WordPress site failing to import a large media file, or a plugin timing out during an update, is often solved by raising these values here rather than assuming a hosting limitation.

Common Problems After a PHP Version Change

A white screen with no visible error usually means PHP's error display is off by default and a fatal error is being logged rather than shown; checking the domain's error_log through File Manager reveals the actual cause, often a deprecated function call from an outdated plugin. A 500 Internal Server Error right after switching frequently traces back to a custom php.ini or .htaccess directive written for the old version's syntax.

Plugins that suddenly show 'requires a newer version of PHP' were previously running fine because their compatibility check was silently skipped on old code paths — updating the plugin itself, not just reverting PHP, is usually the real fix. When in doubt, changing the version back in MultiPHP Manager and confirming the site returns to normal isolates whether PHP or the plugin update caused the issue.

Hosting Built for Multi-Version PHP Environments

Hosting Cheap's cPanel-style panel ships with MultiPHP Manager and MultiPHP INI Editor available out of the box, so switching versions or raising a memory limit doesn't require opening a support ticket first.

Pair that with pure NVMe SSD storage and LiteSpeed, and a version change that used to mean a slow page-by-page test now loads fast enough to spot a broken plugin within seconds instead of minutes.

MultiPHP Manager and INI Editor included in the control panel
Pure NVMe SSD + LiteSpeed for fast before/after testing
24/7 human support if a version change breaks a site
Daily backups to restore from if a switch goes wrong

Why Hosting Cheap

What you get

Per-Domain PHP Control

Run different PHP versions on different domains under the same hosting account.

MultiPHP INI Editor Included

Adjust memory limits, upload sizes, and extensions without editing php.ini by hand.

Pure NVMe SSD + LiteSpeed

Test a new PHP version's effect on page speed instantly instead of waiting on slow storage.

24/7 Human Support

Get a real person's help if a plugin breaks after a version switch.

Daily Backups

Roll back the whole site if a PHP change causes unexpected errors.

Free Managed Migration

Moving in from another host preserves working PHP settings instead of resetting to defaults.

How It Works

Get set up in a few steps

Open MultiPHP Manager

Find it in the Software section of cPanel and locate the domain that needs a different PHP version.

Select the version and apply

Tick the domain, choose the target PHP version from the dropdown, and click Apply for an instant switch.

Tune settings in MultiPHP INI Editor

Adjust extensions, memory limits, and upload sizes for that same domain if the application needs them.

Included

Everything you need, on every plan

Check the application's documented minimum PHP version before switching
Note the current PHP version before changing it, in case a rollback is needed
Apply the change to one domain first rather than every domain at once
Reload the homepage and log into the admin area immediately after switching
Check error_log in File Manager if the site shows a blank white screen
Adjust memory_limit or upload_max_filesize in MultiPHP INI Editor if uploads fail
Update any plugin that reports a PHP version requirement rather than reverting PHP
Confirm a cron job or scheduled task still runs correctly after the switch

FAQ

Frequently asked questions

Will changing the PHP version in cPanel delete any files or data?

No. MultiPHP Manager only changes which PHP interpreter processes requests for the domain — it doesn't touch files, databases, or uploaded media. The switch is reversible at any time by selecting the previous version again.

How do I know which PHP version a WordPress site actually needs?

Check the plugin and theme documentation for each active one, since the strictest requirement among them sets the real minimum. WordPress core itself typically supports a wide range of recent versions, so plugins and themes are usually the limiting factor.

Can different domains on the same cPanel account run different PHP versions?

Yes. MultiPHP Manager applies changes per domain or subdomain, so one site can run on a newer version while another stays on an older one it still depends on, all under the same account.

What's the difference between MultiPHP Manager and MultiPHP INI Editor?

MultiPHP Manager picks which PHP version runs a domain. MultiPHP INI Editor adjusts the configuration for that chosen version, such as enabling extensions or raising memory and upload limits, without editing a php.ini file manually.

Why did my site break immediately after switching PHP versions?

A plugin or custom code likely used a function or syntax that was removed or changed in the newer version. Checking the domain's error log in File Manager usually names the exact file and line, and reverting to the previous version restores the site instantly while a fix is worked out.

Does raising the memory_limit in MultiPHP INI Editor slow down the site?

No — memory_limit is a ceiling, not a reserved allocation, so a script only uses what it needs up to that limit. Raising it just prevents a memory-hungry task like a large import from failing partway through.

Get PHP Version Control Built Into Your Panel

Switch versions, tune extensions, and test changes fast on NVMe SSD hosting with 24/7 support.

Get Started