Black FridayCyber Monday 2026
14Days
15Hrs
34Mins
45Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

How to Update PHP on WordPress: Check Compatibility and Update Safely

Old PHP stops getting fixes, but a rushed update can break plugins. Learn to check your version, test compatibility and switch PHP safely with a way back.

wpallsolution Updated 6 min read

To update PHP on WordPress you change the PHP version your hosting runs, not something inside WordPress itself. Older PHP versions stop receiving security fixes, and newer ones are usually faster, but a plugin or theme written for an older version can break after the switch. This guide explains how to check your version, which versions are supported, how to test compatibility on a copy, how to switch in your hosting panel and how to go back if something breaks. It also links to the recent PHP security release, which makes the topic more urgent.

Quick answer

Check your PHP version in Tools → Site Health → Info → Server. Compare it with the supported branches on php.net, and check that your plugins and theme support the newer version. Back up, test the new version on a staging copy, then switch the live site in your hosting panel and test again, with the old version ready for a rollback. WordPress.org currently recommends PHP 8.3 or greater, and the PHP project’s October 2026 security release makes staying on a patched, supported version important.

How this guide was prepared: it is research-based. We used php.net’s supported versions page, the PHP security advisory and WordPress.org’s requirements page listed under Sources, checked on October 23, 2026. Hosting panels differ, so we describe the steps in general terms and make no claim about your host.

Which PHP versions are supported

According to php.net on October 23, 2026, the supported branches are 8.2 (security fixes only until December 31, 2026), 8.3 (security fixes only until December 31, 2027), 8.4 (active support until December 31, 2026 and security fixes until December 31, 2028) and 8.5 (active support until December 31, 2027 and security fixes until December 31, 2029). Anything older, such as 8.1 and earlier, no longer receives official fixes. WordPress.org’s requirements page recommends PHP 8.3 or greater and warns that older versions have reached end of life and may expose your site to security vulnerabilities.

The PHP project announced two critical security fixes on October 21, 2026, in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Our article on PHP2Shell and website security explains it. A version number alone does not prove whether your host has applied a fix, because hosts can backport patches, so ask your host.

The decision tree: is it time to update PHP?

Flowchart for updating PHP on WordPress: five questions about support status, plugin compatibility, backup and staging, testing and rollback
Five questions show whether and how to update PHP.
  1. Is your PHP branch still supported? If not, plan the update (Step 1).
  2. Do plugins and theme support the newer version? If not, update or replace them (Step 2).
  3. No backup or staging copy? Make both first (Step 3).
  4. Worked on the new version in testing? Switch the live site (Step 4).
  5. Broke after switching? Switch back and investigate (Step 6).

6 steps to update PHP safely

Step 1: Check your current version and the support status

In Tools → Site Health → Info → Server you will see the PHP version, and the Status tab can warn when your PHP is outdated. Compare it with the supported branches above. Our guide to WordPress Site Health explains the screen.

Step 2: Check compatibility of plugins, theme and custom code

Read each plugin’s and theme’s page for the PHP versions it supports and when it was last updated, and replace anything abandoned. WordPress itself checks a plugin’s declared minimum requirements when you activate it, as in “Plugin could not be activated because it triggered a fatal error”. Ask your developer to check custom code for features removed or changed in newer PHP, and look for deprecation warnings in the debug log on staging; see how to read the WordPress debug log safely.

Step 3: Back up and create a staging copy

Take a full backup and test that it restores; see is your WordPress backup really safe. Then create a staging copy that runs on the new PHP version if your host allows it; see how to set up a WordPress staging site.

Step 4: Switch the version in your hosting panel

Most hosts let you choose a PHP version per site in the control panel. Switch the staging copy first, test it, and then switch the live site at a quiet time. If your host offers no choice, ask them for a supported version. Keep a note of the old version so you can switch back.

Step 5: Test the whole site

Open the home page, inner pages, the admin, forms, search, login and, on a store, a full test order. Check the error log for new warnings and fatal errors. Compare speed and Site Health before and after. For an error such as a memory problem, read Allowed memory size exhausted.

Step 6: Roll back if needed, then fix the cause

If something important breaks, switch back to the old PHP version, confirm the site works and investigate on staging: update or replace the incompatible plugin, theme or code. Then try again. Staying on an unsupported version for long is a risk, so treat the rollback as temporary.

Version and hosting differences

  • Some managed hosts update PHP for you or limit the choices.
  • A plugin may support a newer PHP than your WordPress version supports; check both.
  • Large jumps (for example two minor versions) need more testing than a single step.

How to verify the update

  • Site Health shows the new PHP version and no new critical issue.
  • Pages, forms, login and checkout work, and the error log is clean.
  • You know how to switch back if a problem appears later.

How to prevent falling behind

  • Check the PHP support calendar once or twice a year.
  • Choose plugins and themes that are actively maintained.
  • Include PHP in your maintenance routine.

Frequently asked questions

Will updating PHP break my site?

It can if a plugin or theme is not compatible, which is why you test first.

Which PHP version should I use?

A supported one. WordPress.org currently recommends 8.3 or greater, and php.net lists which branches still receive fixes.

Does updating PHP make the site faster?

Often newer versions perform better, but results vary by site, so measure.

Is a version number enough to know I am patched?

No. Hosts can backport fixes, so ask them.

Related guide: WordPress Mixed Content Warnings After Installing SSL: Fix “Not Secure”

What to do next

Check your version, test on a copy and switch with a rollback ready. wpallsolution offers WordPress maintenance packages and an emergency WordPress fix if an update goes wrong. We cannot promise a result without seeing your hosting setup.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us