Changing the PHP version can improve a WordPress site’s security, performance, and compatibility with newer software. It can also expose problems in outdated plugins, themes, or custom code. In the worst cases, an unplanned change can cause fatal errors, broken layouts, failed checkouts, or an inaccessible dashboard.
The safest approach is to treat the change as a small maintenance project: check compatibility, create a restorable backup, update the correct domain in cPanel, and test the site’s most important functions. If the site processes orders or payments, schedule the work during a quieter period and use a staging site when one is available.
What PHP version should WordPress use?
Use a PHP version supported by your host and compatible with your WordPress installation, active theme, plugins, and custom code. The newest version available is not automatically the best choice if the site still depends on older software.
Start by checking the requirements shown in WordPress under Tools > Site Health. Then review the documentation and update notes for important plugins, including WooCommerce, page builders, membership systems, caching tools, and security plugins. Custom plugins and theme code should also be checked rather than assumed to be compatible.
Step 1: Check the current PHP version and site health
In WordPress, open Tools > Site Health > Info and expand the Server section. Record the current PHP version, memory limit, web server, and other relevant environment details.
You can also find the PHP setting in cPanel. Depending on the hosting provider, the tool may be called MultiPHP Manager, Select PHP Version, or PHP Version Manager. The exact controls and available versions vary between hosts.
Review the Site Health screen before making any change. Existing plugin errors, low memory, database warnings, or server problems can make a PHP upgrade harder to diagnose. Resolve obvious issues first where possible.
Create a compatibility checklist
List the active theme, plugins, WooCommerce extensions, custom code, and external integrations. Check their update screens and official documentation for PHP requirements or known compatibility notes. Updating abandoned or outdated components may be necessary, but do it only after confirming that your backup and rollback plan are usable.
If you need to inspect PHP code before upgrading, a local development site, PHP error logs, and a code editor can help. Our guide to PHP development tools for WordPress covers practical options for this type of review.
Step 2: Create a complete backup
Create a backup before changing the server configuration. It should include both:
- The database: Posts, pages, settings, users, orders, and other WordPress data.
- The site files: WordPress core files, themes, plugins, uploads, and configuration files.
You can use your host’s backup system, a reputable backup plugin, or cPanel tools such as Backup or Backup Wizard. Download a copy outside the server if possible. For a WooCommerce store, confirm that the backup includes recent orders and customer data.
Record the current PHP version and take a screenshot of the relevant cPanel setting. This provides a useful rollback reference. A backup is only helpful if it can be restored, so review your host’s restoration procedure before beginning.
Step 3: Change the PHP version in cPanel
Log in to cPanel and open MultiPHP Manager or the equivalent PHP version tool.
- Select the correct domain or subdomain. Check carefully if the account contains staging, addon, and production sites.
- Choose the target PHP version from the available list.
- Apply or save the change.
- Allow a short time for the hosting platform to reload the PHP configuration.
Some hosts let you set PHP separately for each domain. Others provide a selector that also controls PHP extensions and configuration values. Avoid changing unrelated settings unless you understand why they are needed. Depending on the site, important values may include the memory limit, maximum execution time, upload size, and required PHP extensions.
Once the change is saved, open the public site in a private browser window. Test the WordPress login and dashboard as well. If the site uses page, object, or server caching, clear the relevant caches so an old response does not conceal the result.
Step 4: Test the important parts of the site
Loading the homepage is not enough. Test the workflows that matter to visitors and your business:
- Open several posts, pages, archives, and search results.
- Submit contact forms and confirm that email notifications work.
- Test user registration and login if those features are enabled.
- For WooCommerce, check product pages, the cart, checkout, coupons, shipping, payment handoff, and order creation.
- Test page-builder editing and important frontend templates.
- Open the media library and upload a small test image if appropriate.
- Review Site Health, PHP error logs, and your hosting account’s resource or monitoring panel.
If email stops working, check the SMTP configuration and mail logs. The problem may involve SMTP or domain authentication rather than PHP. Our guide to fixing WordPress emails can help with that distinction.
How to troubleshoot PHP version errors
White screen or fatal error
A PHP fatal error commonly points to an incompatible plugin, theme, or custom code. Check the error log for the file, function, or component named in the message.
If you cannot access wp-admin, temporarily disable the suspected plugin through cPanel File Manager by renaming its folder. You can also use a WordPress management tool provided by your host. After regaining access, update, replace, or repair the component rather than leaving it disabled without investigation.
For a structured recovery process, see our guide to fixing the WordPress White Screen of Death.
Plugin or theme warnings
Warnings may not break the site immediately, but they can indicate code that needs attention. Update the affected component from a trusted source, replace abandoned software, or have custom code reviewed and patched. Avoid “nulled” plugins, which can introduce malware and unauthorized access while appearing to solve a compatibility problem.
The dashboard is slow or requests time out
A PHP change may reveal inefficient queries, low memory, or a plugin conflict rather than directly cause the slowdown. Check the PHP error log, hosting resource usage, memory settings, and active plugins. Our guide to fixing a slow WordPress dashboard covers additional diagnostic steps.
When should you involve a WordPress developer?
Consider getting technical help before changing PHP if the site uses a custom theme, legacy plugins, WooCommerce checkout customizations, important third-party integrations, or no reliable staging environment. A developer can audit compatibility, prepare a rollback plan, test custom code, and investigate errors without relying on repeated changes to the live site.
Professional assistance is especially useful when the site supports payments, bookings, memberships, or other workflows where a brief outage or failed transaction could have serious consequences.
Frequently asked questions
Will changing PHP delete my WordPress content?
No. Changing the PHP version does not normally delete posts, pages, media, or database records. However, incompatible code can make the site unavailable, which is why a complete, restorable backup is important.
Can I change PHP from WordPress?
Usually not. PHP is controlled by the hosting environment. You normally change it through cPanel, your host’s dashboard, or a server configuration panel.
Should I change PHP on a live WooCommerce store?
Use a staging copy first whenever possible. If staging is unavailable, create a complete backup, choose a low-traffic period, and test checkout, payment, shipping, email notifications, and order creation immediately afterward.
What if the new PHP version breaks the site?
As a first rollback step, change the domain back to its previous PHP version. Then review the logs and identify the incompatible component. Restore files or the database only when necessary, and plan to update or replace outdated software instead of leaving the site on an older version indefinitely.
Conclusion
Changing PHP for WordPress in cPanel is more than selecting a new version from a menu. Check compatibility, back up the files and database, change only the intended domain, test important workflows, and keep a rollback option available. For sites with custom code or revenue-critical features, use staging or involve a WordPress professional before making the change on production.