Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
PHP is configured on your web server, not updated by the normal WordPress core updater. Your hosting provider determines whether you can switch PHP yourself—often in a hosting panel—or must ask support. The safe process is to check the active version, choose a maintained version your entire stack supports, create a restorable backup, update WordPress and extensions, change PHP through the host, and test before considering the job complete.
What PHP version should a WordPress site use?
As of September 30, 2026, WordPress.org lists PHP 8.3 or greater as recommended, while noting that PHP 7.4 and later may run legacy sites. PHP 7.4 is officially end-of-life, however, so leaving a site there can expose it to unpatched security issues. See the current WordPress requirements.
For production hosting, the WordPress Hosting Handbook recommends PHP 8.4 or later. Its lifecycle notes say PHP 8.3 entered security-only support on December 31, 2025, and PHP 8.2 reaches end of life on December 31, 2026. Hosts are advised to test the complete stack before making a new branch their production default; read the Server Environment guidance.
These are not guarantees that every site can use the newest branch. WordPress Core’s May 2026 clarification records full PHP 8.3 support from WordPress 6.4, PHP 8.4 from WordPress 6.8, and PHP 8.5 from WordPress 6.9 and 7.0, while PHP 7.4 remains the minimum supported version. Plugins, themes and custom code can still be incompatible. The Core clarification explains the distinction.
| Decision check | What to confirm |
|---|---|
| Upstream lifecycle | Prefer a branch with active support; avoid end-of-life PHP. |
| WordPress core | Confirm your installed WordPress release supports the target branch. |
| Site components | Check every theme, plugin and custom integration, not just core. |
| Host operation | Verify the host offers the branch and a reversible change or support-assisted rollback. |
Check the PHP version currently running
- Sign in to WordPress.
- Open Tools > Site Health > Info.
- Expand Server and read PHP version.
A dashboard notice such as “PHP Update Required” or “PHP Update Recommended” is a reason to investigate, not a substitute for checking compatibility.
Prepare before changing PHP
Make a restorable backup
Back up both the WordPress files and database, and verify that the backup can actually be restored. Keep the host involved in your recovery plan: if the site cannot run on the new branch, the provider may need to reinstate the previous PHP version before a backup restoration will work.
Rank #2
Update the software stack
Update WordPress core, all themes and all plugins, then browse the site and dashboard while it is still on the old PHP version. Updating first removes known compatibility fixes before you make the server change.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Investigate compatibility
Review each developer’s PHP requirements and unresolved issue reports, especially for abandoned extensions or custom code. A PHP compatibility checker can help find likely problems, but WordPress warns that such tools can miss defects and can report false positives; treat the result as one input, not proof that the upgrade is safe.
Rank #3
Change PHP through your hosting provider
There is no universal WordPress or control-panel sequence. PHP is installed on the server. As WordPress.org puts it: “PHP is installed on your website’s server, so updating it involves either interacting with your host’s settings or asking your provider to do it for you.” Follow your host’s current documentation or open a support request.
If your host uses cPanel
“How do I change PHP in cPanel?” is a common question, but hosts label and configure cPanel differently. Your provider may expose a PHP selector, a multi-PHP manager, a per-domain setting, or no customer control at all. Use the provider’s instructions for your domain; do not assume a menu path from another host applies to yours.
If the host makes the change for you
Tell support the domain, current branch, requested target, maintenance window and rollback contact. Ask whether the change is reversible and which PHP extensions and configuration limits will be enabled. Do not change production first if the provider offers a staging site where the full stack can be tested.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Verify the site after the switch
- Recheck Tools > Site Health > Info > Server and confirm the new PHP version.
- Open the public homepage, several representative posts or products, forms, search, login and checkout or other revenue-critical paths.
- Use the dashboard: edit and publish a test item, open media, and visit plugin and theme screens.
- Review server, PHP and WordPress error logs for fatal errors or repeated warnings.
- Check scheduled tasks, external API connections, caching and email if your site depends on them.
Do not assume a faster site merely because PHP changed. Current guidance supports keeping PHP maintained for security and compatibility; a blanket performance multiplier is not established here.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do if the update breaks the site
- Record the symptom and the time of the change; capture any fatal-error message.
- Ask the host to restore the previous PHP branch, or use the host’s documented rollback control.
- Once the site is available, disable or replace the extension identified by the error and contact its developer.
- Restore the verified backup if necessary. The host may need to put the server back on the old PHP version first.
- Test the suspected component on staging or a copy of the site before attempting another production upgrade.
When you should delay the upgrade
- The target branch is end-of-life or unavailable from your host.
- A critical plugin, theme or custom application has no confirmed support for it.
- You cannot produce or restore a complete backup.
- The host cannot explain how to roll back or provide support during the change.
Resolve those conditions first rather than selecting a version solely because WordPress core lists it as supported.
Frequently Asked Questions
Can I update PHP from the WordPress Updates screen?
No. The Updates screen handles WordPress software, not the PHP runtime installed on your web server. Use your host’s control or request a server-side change.
Will updating PHP definitely break my site?
No outcome is guaranteed. Core may support a branch while an older plugin, theme or custom integration does not, which is why a tested backup, compatibility review and rollback plan are required.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is PHP 8.3 the right choice for every WordPress site?
No. WordPress.org recommends 8.3 or greater, while the Hosting Handbook recommends 8.4 or later for production. Choose the maintained branch your host offers that your complete site stack supports.
The Bottom Line
Check the server version, back up and test the whole stack, then change PHP using your host’s method. Keep the old setting available until the front end, dashboard and critical functions have passed verification.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
