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 →Repair Windows errors before they cause bigger problemsFix Now →To change PHP for a WordPress site, use your host’s control panel—not the WordPress dashboard. On most cPanel accounts, open Software → Select PHP Version (also called PHP Selector), choose the target release, and select Apply or Set as current. Back up the site and run a PHP compatibility check before switching, then confirm the result at Tools → Site Health → Info → Server in WordPress.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
As of October 2026, WordPress supports PHP 7.4 as its minimum, but the WordPress Core team recommends PHP 8.3 or newer. WordPress 7.x does not support PHP 7.2 or 7.3. The right target is therefore the newest version your themes, plugins and host support reliably—not simply the newest number shown in a menu.
As an Amazon Associate I earn from qualifying purchases.
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 problemsWhich PHP version should WordPress use in 2026?
PHP is the server-side language that executes WordPress core, themes and plugins. Changing it changes the runtime for every PHP request, so the decision affects both security maintenance and compatibility.
| PHP version or range | WordPress position as of 2026 | What it means for your site |
|---|---|---|
| 7.2 and 7.3 | Unsupported by WordPress 7.x | WordPress 7.0 dropped these releases. A site that remains on them cannot move to WordPress 7.x and must stay on the 6.9 branch until PHP is upgraded. |
| 7.4 | Official minimum supported version | It satisfies the floor, but it is an aging runtime. Use it only when a required plugin, theme or hosting constraint prevents a move to a newer release. |
| 8.3 or newer | Recommended minimum | This is the WordPress Core team’s current recommendation for hosts and sites, provided your extensions are compatible. |
| 8.5 | Documented as fully supported by WordPress 6.9 and 7.0 | The beta label was removed in May 2026. Confirm that your host offers it and that your extensions have passed a compatibility check before selecting it. |
Some older third-party articles still call PHP 8.2 the recommended minimum. That advice is behind the current WordPress.org guidance; use the official 8.3-or-newer recommendation when planning an upgrade.
#1 Best Overall
There is no announced date for another minimum-PHP increase. The project uses a 5% usage baseline when deciding whether to retire a PHP version. A September 2026 WordCamp US discussion summary put PHP 7.4 usage at roughly 18% of websites; that is context about adoption, not a promise that 7.4 will remain supported.
How to choose between 8.3, 8.4 and 8.5
Start with the newest release that your host and your software stack both support. A newer number is not automatically the correct production choice if a payment, membership, page-builder or custom plugin has not been checked against it. If your checker reports no meaningful issues on 8.5 and the host provides it, WordPress 6.9 and 7.0 document full support for that release. If an extension has only been validated on 8.3 or 8.4, use that tested release while you arrange an update or replacement.
Think of 7.4 as a compatibility fallback, not a goal. It is still the official floor, but remaining there leaves less room for future WordPress updates. Moving from 7.2 or 7.3 is especially important because WordPress 7.x cannot be installed while the server remains on either of those versions.
What to do before changing PHP
A PHP switch can expose code that has been tolerated by an older interpreter. Prepare a recovery path before touching the selector. The safest sequence is backup, compatibility review, testing, change, and verification.
1. Make a complete, restorable backup
Back up both parts of the site:
- All WordPress files, including
wp-content, uploaded media, themes, plugins and configuration files. - The WordPress database, exported in a form your host or backup tool can restore.
Check that the backup finished and that you know how to restore it. A backup that exists but cannot be retrieved does not protect you from a failed switch. Keep the current PHP version noted so you can return to it quickly.
Do not rely on a database-only export: PHP failures can affect theme and plugin files as well as stored content. Conversely, a files-only copy cannot restore posts, settings or orders. Record the backup time and the exact version currently shown in Site Health so support can distinguish a PHP problem from a later content change.
2. Run a PHP compatibility check
Use a PHP compatibility checker that scans the active theme and plugins for syntax or function changes between your current release and the target. Review the results rather than assuming every warning is fatal: the checker may flag code that is never executed, while a small number of active components can still cause a fatal error.
Record which plugin or theme generated each serious warning. If a component is abandoned or has no compatible release, decide whether to replace or disable it before upgrading PHP. Update the components that do have compatible releases, then run the check again. Keep a note of any extension that is essential to publishing, checkout, forms, logins or scheduled tasks; those workflows deserve a live test after the switch.
3. List every site under the hosting account
Confirm whether the cPanel account contains add-on domains, aliases or subdomains. The ordinary PHP Selector setting is commonly account-wide, so changing it can affect more than the WordPress installation you had in mind. If another site depends on the old runtime, plan a per-domain configuration instead.
Make an inventory before opening the selector: include development subdomains, parked or alias domains that route to the same files, and any separate WordPress installs. An apparently unused subdomain may still run an older plugin set. Ask the host whether its selector is account-wide if the interface does not make the scope clear.
Free tools Windows power users keep installed
One-click scans. No signup required.
4. Choose a low-risk test window
Make the change when you can immediately check the front end, log in to WordPress and contact the host if needed. If your host provides a staging copy, test the target version there first; treat staging as a rehearsal, not a substitute for a current production backup.
Tell anyone who publishes content or processes orders that a maintenance check is taking place. Pause a high-value campaign or scheduled import if practical, then test those processes explicitly when the new runtime is active. This avoids mistaking a quiet homepage for a healthy site.
How to change PHP version WordPress on cPanel
The labels differ slightly between hosts, but the common cPanel workflow is short.
- Sign in to cPanel. Use the hosting account’s control-panel login, not your WordPress administrator URL.
- Open the Software section. Select Select PHP Version. Some hosts label the same tool PHP Selector.
- Choose the PHP release. Pick the version you tested. If the menu offers 8.3 or newer and your compatibility check is clean, that aligns with the current WordPress recommendation. Do not choose a version your host marks as unavailable or unsupported.
- Apply the setting. Click Apply, Set as current or the equivalent button. The exact wording is host-specific.
- Wait for the panel to confirm the change. Do not repeatedly submit the form if the interface takes a moment to update.
- Test the site immediately. Open the home page, several content pages, the login screen and the WordPress dashboard. Submit a representative form or checkout flow if the site uses one.
- Verify from inside WordPress. Go to Tools → Site Health → Info, expand Server, and read the PHP version shown there.
The switch is performed by the hosting panel. WordPress itself does not provide a dashboard setting that changes the server’s PHP interpreter.
If your host displays selectable extensions or modules beside the version, leave those controls unchanged unless support or your application documentation specifically requires a change. The version assignment is the operation covered here; changing several server settings at once makes a failure harder to diagnose.
PHP Selector WordPress site versus MultiPHP Manager
The key decision is whether one PHP version should apply to the entire cPanel account or whether domains need separate versions.
| cPanel tool | Scope | Use it when | Important caution |
|---|---|---|---|
| Select PHP Version / PHP Selector | Typically the whole account | All add-on domains, aliases, subdomains and the main site can run the same tested release. | Changing it may alter other sites you did not intend to touch. Test every site on the account. |
| MultiPHP Manager (sometimes Per Domain Settings) | Individual domains | Different sites require different PHP versions during a staged migration or because their software has different compatibility limits. | Check each domain’s assignment. A domain not selected in MultiPHP Manager will not necessarily follow the setting you changed elsewhere. |
Both tools appear in the cPanel Software area on hosts that enable them. If you need one domain on a newer release while another remains temporarily on an older supported release, MultiPHP Manager is the appropriate control. Keep the older site on the minimum version only as long as necessary and continue working toward a common, supported target.
A practical staged migration is to assign the test domain in MultiPHP Manager, run the complete compatibility and workflow checks, and then move the production domain. Keep a written list of which domain has which assignment. This prevents a later account change from accidentally putting a carefully tested site back on an unintended version.
How to verify the new PHP version and site health
Confirm the server reports the target release
In WordPress, open Tools → Site Health → Info, expand Server, and compare the displayed PHP version with the release you selected. This confirms what WordPress is actually executing, rather than what a cPanel dropdown appeared to save.
Take a screenshot or note the value after a successful change. If you manage several domains, verify each installation separately; one Site Health screen cannot prove that another domain received the same assignment.
Check both logged-in and public requests
- Load the home page and several pages or posts with different templates.
- Sign in and open the dashboard, media library and editor.
- Test navigation, search, comments or forms that visitors use.
- Check scheduled functions, email notifications and payment or membership flows when those features are part of the site.
- Look for PHP warnings, fatal-error screens, missing styles or broken images.
A site can appear healthy on the home page while a rarely used plugin fails on an administration screen. Test the workflows that matter to your visitors and staff, not just one URL. If a failure appears only for logged-in users, check the dashboard and editor before declaring the public site fixed.
Allow caches to refresh
Page and object caches can continue serving an old response after the runtime changes. Purge the caches your site normally uses, then repeat the key checks in a private browser window. Do not interpret a cached page as proof that every request is running correctly on the new version.
Recommended Free Tools
Run the checks once immediately and again after normal traffic has exercised less frequently visited templates. A delayed error in a scheduled task or a checkout endpoint can be just as serious as a visible homepage error.
What to do if the change causes an error
White screen, fatal error or HTTP 500 response
- Return to cPanel and select the previous PHP version, if the panel still allows it.
- Reload the site and WordPress dashboard to confirm service is restored.
- Use the compatibility-check results and the host’s PHP error log to identify the extension that failed.
- Update, replace or temporarily disable the incompatible plugin or theme, then test the newer PHP release again.
- If you cannot access the panel or the site remains unavailable, contact the host and provide the domain, the old and new PHP versions, the time of the switch and the exact error text.
Do not delete WordPress files or edit random configuration values while responding to a fatal error. The fastest recovery is usually to restore the last known-good PHP assignment, then isolate the incompatible component.
When contacting support, state whether the failure affects one domain or the whole account, whether Site Health can be opened, and which front-end and dashboard URLs fail. Those details help the host determine whether the assignment was applied at account scope or per domain.
Only one domain breaks
If the account uses an account-wide PHP Selector, another site may have been affected even though the WordPress site you tested works. Check each add-on domain, alias and subdomain. If the sites need different runtimes, assign versions with MultiPHP Manager where the host supports it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The selected version does not appear in Site Health
Allow a short propagation interval, clear caches and check that you changed the correct cPanel account. If Site Health still reports the old version, the host may be using a different PHP handler or may not have applied the setting. Ask support to confirm the PHP version assigned to the domain.
The PHP Selector icon is missing
Not every host enables self-service PHP changes, and some do not permit customers to change versions. Contact the host and ask which PHP releases are available for the specific domain and how a change is performed. Do not assume that a PHP-version snippet copied into .htaccess will work: folder-level overrides are host- and handler-specific and are not a verified, universal procedure.
When cPanel is not your control panel
This guide covers the cPanel workflow documented for common shared-hosting accounts. Managed WordPress services, Plesk panels, VPS installations and nginx-based servers use different controls and were not covered by the same procedure. On those platforms, use the provider’s documented PHP assignment method or ask support to make the change. The principles still apply: back up first, check extension compatibility, change the runtime at the hosting layer, and verify the result inside WordPress.
Do not infer that a cPanel label or procedure exists on another platform. A provider may perform the change for you, expose a different domain-level control, or restrict available releases. Ask which PHP version is active for the exact domain, whether a rollback is available, and how to confirm the result in WordPress.
PC 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 & 11Outdated 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 matchCommon questions about changing PHP on WordPress
Can I change PHP from the WordPress dashboard?
No. The dashboard can report the server version through Site Health, but the version is selected in the hosting control panel or by the hosting provider.
Is PHP 7.4 safe to keep?
PHP 7.4 meets WordPress’s official minimum as of October 2026, but WordPress recommends 8.3 or newer. Keep 7.4 only when a tested dependency or hosting limitation prevents an upgrade, and treat that as a migration task rather than a permanent target.
What if a plugin has not been tested with PHP 8.3?
Use the compatibility checker, review the plugin’s current maintenance status and test on a staging copy when available. If a required plugin fails, stay on the last compatible supported release while replacing or updating it; do not switch production blindly.
Does changing PHP update WordPress itself?
No. It changes the server runtime only. WordPress core, themes and plugins remain at their existing versions and must be maintained separately.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Why did WordPress stop supporting PHP 7.2 and 7.3?
WordPress 7.0 removed support for those releases. Sites that remain on PHP 7.2 or 7.3 cannot move to WordPress 7.x and stay on the 6.9 branch until PHP is upgraded.
How often should I recheck the PHP version?
Check after every hosting change, WordPress migration or domain reassignment, and whenever Site Health reports a version different from the one expected. Hosting panels can apply settings at account or domain scope, so verification prevents an unnoticed mismatch.
What is the WordPress PHP version requirement in 2026?
The official minimum supported PHP version is 7.4. The WordPress Core team recommends PHP 8.3 or newer. WordPress 7.x does not support PHP 7.2 or 7.3, so those sites must upgrade PHP before moving beyond the 6.9 branch.
Does PHP Selector change every WordPress site in cPanel?
Usually, yes. Select PHP Version or PHP Selector commonly applies at account scope, including add-on domains, aliases and subdomains. Check every site before switching. Use MultiPHP Manager, also called Per Domain Settings on some hosts, when domains need separate versions.
Why does cPanel show a version that WordPress does not?
The setting may have been applied to a different account or domain, may still be updating, or may use a different handler. Clear caches, recheck Tools → Site Health → Info → Server, and ask the host to confirm the PHP assignment for the specific domain if the values still disagree.
Is PHP 8.5 supported by WordPress?
WordPress 6.9 and 7.0 document full support for PHP 8.5, and the beta label was removed in May 2026. Host availability and plugin or theme compatibility still need to be checked before production use.
Frequently Asked Questions
How do I change the PHP version on a WordPress site in cPanel?
Back up the files and database, run a compatibility check, open cPanel’s Software section, choose Select PHP Version or PHP Selector, select the tested release, and click Apply or Set as current. Verify it at Tools → Site Health → Info → Server.
Which PHP version should WordPress use in 2026?
WordPress’s minimum supported version is PHP 7.4, while the recommended minimum is PHP 8.3 or newer. Use the newest release your host, theme and plugins have passed compatibility testing for.
Does cPanel PHP Selector affect all domains?
It commonly applies account-wide, including add-on domains, aliases and subdomains. Test every site, or use MultiPHP Manager/Per Domain Settings for separate domain assignments.
What should I do if the site breaks after changing PHP?
Revert to the previous PHP version if possible, confirm the site recovers, review compatibility results and PHP error logs, then update, replace or disable the incompatible component before testing again.
Can a host change PHP if Select PHP Version is missing?
Yes, ask the host which versions are available and how the specific domain is assigned. Some hosts do not offer self-service switching or do not permit customer changes.
The Bottom Line
Back up the complete site, check your active plugins and theme, and choose the newest PHP release they support—PHP 8.3 or newer is WordPress’s current recommendation. In cPanel, use Select PHP Version for an account-wide change or MultiPHP Manager for per-domain assignments. Test the important workflows, then confirm the active version under Tools → Site Health → Info → Server. If anything fails, roll back to the last known-good version and work with the host to isolate the incompatible component.
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.
