PHP is changed on your web server, not through the normal WordPress updater. Your hosting provider decides whether you can switch PHP yourself in a control panel or must request the change. A safe update means checking the active version, selecting a maintained version your entire site supports, creating a restorable backup, updating WordPress and extensions, changing the server setting through your host, and testing before you make the change permanent.
WordPress.org currently recommends PHP 8.3 or newer (Requirements), while the WordPress Hosting Handbook recommends PHP 8.4 or later for production (Server Environment). Those are guidelines, not a guarantee that every plugin, theme, or custom integration supports the same version.
What you are actually updating
PHP is the server-side language that runs WordPress. As WordPress.org explains, “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.” See the official WordPress PHP update guide.
Updating WordPress core from Dashboard > Updates does not change PHP. Depending on the host, the server setting may be exposed in cPanel, another control panel, a managed-host dashboard, or only through support. There is no universal cPanel path or button name, so use the instructions for your provider.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Which PHP version should you choose?
Choose the newest branch that is still maintained by the PHP project and is supported by your WordPress release, themes, plugins, extensions, and custom code. WordPress core support alone is insufficient.
| Reference | Version guidance | What it means |
|---|---|---|
| WordPress.org Requirements (accessed 2026) | PHP 8.3 or greater recommended | The published WordPress.org recommendation; older PHP 7.4+ may work in legacy environments but is officially unsupported upstream and can expose the site to security risk. |
| WordPress Hosting Handbook (current in 2026) | PHP 8.4 or later for production | A newer production-oriented recommendation that assumes the host has tested the complete stack. |
| PHP lifecycle information in the Hosting Handbook | PHP 8.3 became security-only on 2025-12-31; PHP 8.2 reaches end of life on 2026-12-31 | Lifecycle status matters separately from WordPress compatibility. |
| WordPress Core clarification, 2026-05-22 | PHP 7.4 minimum supported; full PHP 8.3 support from WordPress 6.4, PHP 8.4 from 6.8, and PHP 8.5 in WordPress 6.9 and 7.0 | These statements describe core support, not compatibility of every installed extension. |
Check your host’s available branches and compare each candidate on four points:
- Whether upstream support is active, security-only, or ended.
- Whether your WordPress core version and required PHP extensions support it.
- Whether every theme, plugin, and custom integration supports it.
- Whether the host can switch back quickly and will help with rollback.
For the core-support details, see WordPress Core’s May 2026 PHP support clarification. Do not select a version solely because WordPress itself lists it as supported.
Rank #2
Safe update procedure
1. Record the active PHP version
- Sign in to WordPress.
- Open Tools > Site Health > Info.
- Expand the Server section.
- Read and record PHP version, along with the WordPress version and any server details you may need when contacting support.
If the dashboard displays PHP Update Required or PHP Update Recommended, treat it as a prompt to investigate; it does not perform the server change for you.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems2. Select a target and check the whole stack
Confirm the target branch with your host’s documentation. Review the change logs or compatibility statements for your theme and plugins, especially components that contain custom PHP, connect to payment services, or have not been updated recently. WordPress’s guide points to a PHP compatibility checker, but warns that automated checks can miss real problems or report false positives. Use a checker as one input, then resolve warnings with the developer or replace unsupported components.
3. Make a restorable backup
Create a complete backup of the database and files, including uploads, themes, plugins, and configuration files. Store it somewhere independent of the live server and confirm that you know how to restore it. A backup is useful only if it can actually be recovered.
Rank #3
Restoration may require the host to move the server back to the previous PHP version first, so record the current version and ask the host how that rollback works.
4. Update WordPress, themes, and plugins first
Apply available updates for WordPress core, active and required themes, and plugins. Test the site on the existing PHP version after updating. This removes known compatibility fixes before you introduce a server-runtime change.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →5. Change PHP through the hosting provider
Follow the provider’s documented method. In a control panel, the setting may be labeled PHP Manager, Select PHP Version, or something else; some hosts use a site settings page, while managed hosts make the change for you. If you cannot find a supported control, open a support request containing:
- Your domain and site or subscription identifier.
- The current PHP version and requested target.
- The date and time you want the change made, if a maintenance window is needed.
- A request for the precise rollback procedure.
Do not change PHP by editing WordPress files. The setting belongs to the server account or hosting environment.
6. Test immediately
Use a private browser window and check:
- The home page and several representative posts or pages.
- Login, the dashboard, and the editor.
- Forms, search, comments, and other functions visitors use.
- Orders, memberships, APIs, scheduled jobs, or integrations relevant to your site.
- Media uploads and any caching or security controls.
Review the hosting error log and WordPress Site Health for new PHP errors. Test from both an unauthenticated visitor session and an administrator session.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do if the update breaks the site
If the front end or dashboard fails
- Contact the host and request an immediate return to the previously recorded PHP version.
- Note the exact error, affected URL, time of failure, and any plugin or theme named in the log.
- Ask the relevant developer for a compatibility fix, or disable or replace the unsupported component using the host’s recovery tools.
- After PHP is restored, recover the backup only if the site state requires it. Confirm that the backup date and PHP version are appropriate.
WordPress specifically notes that the host may need to reinstate the old PHP version before a backup can be restored. Do not assume that restoring files alone will undo a server-runtime change.
Will updating PHP break your site?
It can, when a plugin, theme, custom code path, or required PHP extension uses code that the target branch no longer accepts. A compatibility scan cannot prove safety, and PHP maintenance status cannot prove extension compatibility. Reducing the risk requires the backup, updates, developer checks, and post-change testing described above.
Common questions about changing PHP
How do I check my WordPress PHP version?
Go to Tools > Site Health > Info, expand Server, and read PHP version.
How do I change PHP in cPanel?
There is no single cPanel sequence that applies to every host. Look for the provider’s PHP manager or selector, follow its documentation, or ask support to make the change. The host controls which versions and controls are available.
Is PHP 7.4 acceptable because WordPress supports it?
PHP 7.4 is listed as the minimum supported version in the WordPress Core clarification, but it has reached upstream end of life. Core support does not make an end-of-life PHP branch a good production target when a maintained, compatible branch is available.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
