Published 10 October 2026
Short answer: choose a PHP version that is both supported by PHP and compatible with your WordPress version, theme and plugins. WordPress 7.1’s Hosting Team recommends PHP 8.4.x or 8.5.x for new installations, but that is not a reason to switch a working live store without testing. As of October 2026, PHP 8.2 security support is due to end on 31 December 2026, so sites using it should plan a tested upgrade rather than leave the decision until the deadline.
PHP is the server-side programming language WordPress runs on. Changing its version can affect the site’s code even when WordPress itself is compatible: plugins, themes and custom snippets may behave differently. Treat a PHP change as a maintenance task with a rollback plan, particularly if your site takes orders or bookings.
What PHP version should a WordPress site use?
For a new WordPress 7.1 installation, the WordPress Hosting Team recommends PHP 8.4 or 8.5. It lists PHP 7.4 as the minimum WordPress requirement, but minimum compatibility is not the same as a good long-term choice: some older PHP branches are no longer receiving upstream fixes. The team also notes that WordPress 7.1 is compatible with PHP versions 8.2 through 8.5, while PHP 8.2 reaches end of life on 31 December 2026.
PHP’s own lifecycle matters alongside WordPress compatibility. Its supported-versions page distinguishes active support from security-only support and end of life. Check that page when planning, because lifecycle dates can change as new branches are released. A version number alone does not tell you whether your whole WordPress installation is ready for it.
One practical distinction: WordPress core compatibility does not certify every plugin and theme on your site. A business site with an old booking extension or custom checkout code may need more careful testing than a simple brochure site. If the host’s control panel labels one version “recommended”, treat that as a useful starting point, not proof that your site-specific stack has been tested.
Before changing PHP, check the site
- Record the current setup. In WordPress, open Tools > Site Health > Info and note the PHP version, WordPress version, active theme and active plugins. The information panel can be exported for reference.
- Review compatibility. Update WordPress, themes and plugins where appropriate, and check plugin and theme documentation for PHP support. Remove or replace abandoned components where feasible; do not assume a compatibility scanner can catch every issue.
- Make a restorable backup. Include both website files and the database, and keep a copy separate from the live hosting account. Confirm how to restore it and how to switch back to the earlier PHP version before beginning.
- Use staging if available. A staging site is a separate copy for testing. Try the intended PHP version there first, especially for WooCommerce, membership, booking or other transaction-related functions.
WordPress Site Health can flag an outdated PHP version and report configuration issues, but it is a diagnostic aid, not a full compatibility test. A clean Site Health screen cannot confirm that every customer journey or custom feature works. For a busy shop, schedule the change during a quieter period and ensure someone can investigate or revert it.
How to change PHP in cPanel
If your hosting account provides cPanel MultiPHP Manager, it can set the PHP version for a domain. The interface may be disabled by the host, and a version will only appear if it is installed and available to your account. If the option is missing, ask the hosting provider which supported versions are available and how to change them.
- Sign in to cPanel and open Software > MultiPHP Manager, if available.
- Select the domain you intend to change. Double-check the domain name, especially if several websites share one account.
- Choose the target PHP version from the menu and click Apply. If the version you expect is absent, do not try to force it through an unverified configuration edit; contact the host.
- Test the website straight away. If errors appear, use the host’s documented rollback process or request help rather than repeatedly changing settings without recording them.
Control-panel labels and available versions depend on the hosting provider’s configuration. In particular, do not assume that every cPanel account offers the same versions or exposes the MultiPHP Manager. The cPanel documentation confirms that providers can enable or disable this interface and that unavailable versions may need administrator action.
What to test after the PHP change
Open the site in a private browser window and test it as a visitor, not only as an administrator. Clear or bypass caches when a page appears unchanged. Check the actions that matter to your business, then review WordPress Site Health and available error logs for new warnings or fatal errors.
- Load the homepage, key landing pages, images and navigation on mobile and desktop.
- Sign in to WordPress; edit and publish a test draft if appropriate.
- Submit contact, enquiry and newsletter forms, and confirm that messages arrive.
- For WooCommerce, test product pages, add-to-cart, coupon handling, checkout and order confirmation using a safe test method supported by your payment provider.
- Check scheduled tasks or integrations your site relies on, such as booking notifications, inventory synchronisation or email delivery.
If a feature breaks, note the exact page, action, time and error message. Revert to the previous PHP version if needed to restore service, then investigate the incompatible plugin, theme or custom code before trying again. Do not leave public error display enabled while troubleshooting; diagnostic output can expose technical details to visitors.
A sensible upgrade decision
Do not choose PHP solely because it is the newest option, nor stay indefinitely on an unsupported version because the site currently loads. Compare the PHP project’s support lifecycle with the WordPress compatibility reference, then check your site’s specific components. Plan upgrades early enough to test, fix conflicts and schedule a controlled change.
HostCupid Web Solutions Private Limited, a Chennai-based provider of shared, WordPress and reseller hosting, sees PHP version questions as a compatibility and maintenance decision—not a one-click performance promise. If you manage a WordPress site and are unsure which versions your account supports, ask your hosting provider before changing the live environment. A careful test and a known rollback route are more useful than guessing.
Sources
- WordPress 7.1 Server Compatibility – Make WordPress Hosting · 2026-08-19
- PHP: Supported Versions
- MultiPHP Manager for cPanel – cPanel & WHM Documentation · 2026-07-08
- Site Health screen – WordPress Documentation · 2026-07-12
- Get a faster, more secure website: update your PHP today – WordPress Documentation
