A folder does not automatically receive an independent PHP runtime under every cPanel handler. For an application needing a different supported version, a separate domain or subdomain with its own document root is usually the clearer managed configuration.
IN THIS ARTICLE
What you need before you begin
Identify the application’s PHP and extension requirements, current handler and document root. Back up the site and plan any URL changes. PHP-FPM operates at the virtual-host or pool scope, so old per-folder .htaccess recipes may not apply.
01 Run a separate application on a different PHP version in cPanel
- Create an appropriate subdomain or separate domain entry using Domains, with a distinct document root for the application.
- Open MultiPHP Manager, select that hostname and assign the required available PHP version.
- Place the application in its assigned root and configure its base URL, database and HTTPS according to the application’s instructions.
- Test its effective runtime and required extensions. Verify the original site still uses its intended version.
- If the application must remain under a path such as
example.com/app, ask support to confirm a supported handler arrangement instead of copying a version-specific AddHandler line from another server.
Confirm the expected result
Test both applications independently, including background jobs and command-line tasks that may use a separate PHP binary. Confirm no document root is unintentionally shared.
Can .user.ini select a different PHP executable version?
A .user.ini file changes permitted PHP directives, not the PHP executable version. If a copied handler causes downloads of PHP source or server errors, remove the unsafe change and restore the backed-up configuration immediately. Do not use an unsupported runtime as a permanent substitute for application maintenance.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
