X
X
X
X

Update PHP Version Before PHP 8.2 Support Ends: How to Prepare Your Site

HomepageArticlesWeb HostingUpdate PHP Version Before PHP 8.2 S...

In short: To update PHP version means moving your site from its current PHP branch to a newer branch that is still supported. According to the official PHP schedule, security support for PHP 8.2 ends on 31 December 2026. The safe order is: take a full backup, try the change on a staging copy if you can, update WordPress core, plugins and theme, switch to the new PHP version, test the site and watch the error log for a few days.

Why do you need to update PHP version?

PHP is the server-side language that WordPress and many other web applications run on. Every PHP branch gets two years of active support after its release, with bug fixes and security patches. For the next two years it only receives security fixes. After those four years the branch reaches end of life and gets no more patches at all (PHP supported versions).

A site on an unsupported version usually keeps working; the problem is that when a new security hole is found, no fix is released for it. Plugin and theme developers also drop support for old versions over time. That is why treating a PHP update as planned maintenance, instead of a last-minute job, carries less risk.

Which PHP versions are still supported?

According to the table on php.net (as of November 2026), the support dates are:

  • PHP 8.2: active support ended on 31 December 2024; security support ends on 31 December 2026.
  • PHP 8.3: active support ended on 31 December 2025; security support runs until 31 December 2027.
  • PHP 8.4: active support until 31 December 2026, security support until 31 December 2028.
  • PHP 8.5: released on 20 November 2025; security support until 31 December 2029.

PHP 8.1 and older are no longer on the supported list. On the WordPress side, the official requirements page recommends PHP 8.3 or greater. WordPress can also run on legacy versions from PHP 7.4 upwards, but the page notes that these have reached end of life and may leave your site exposed to security vulnerabilities (WordPress requirements).

PHP version update steps: backup, staging copy, plugin updates, choosing the new version, testing the site and watching the error log

Before you switch: a checklist

  1. Find your current version. On WordPress, the Server section in the Info tab of Tools > Site Health shows the PHP version you run. Site Health also flags an outdated PHP version as a critical issue.
  2. Take a full backup. Back up files and the database together and make sure the backup can really be restored. See why website backups matter for a backup strategy.
  3. Update core, plugins and theme. Fixes for newer PHP versions usually arrive in current releases. Follow the safe order in our WordPress updates guide.
  4. Remove abandoned plugins. A plugin that has not been updated for a long time may break on a new PHP version. Use the criteria in how to choose WordPress plugins to pick a maintained alternative.
  5. Review custom code. If you added your own code to a theme or plugin, check the removed and deprecated features in the PHP migration guide (PHP 8.3 migration guide).

How to update PHP version step by step

  1. Try it on a staging copy. If you can, create a copy of the site and test the new version there first. Without a copy, pick a time with few visitors.
  2. Select the new version. How you change the PHP version depends on your hosting plan and server setup. If you cannot find the option in your panel or are not sure, open a support ticket and ask which versions are available.
  3. Test in order. Check the home page, a few inner pages, the contact form, member login and, if you have one, the cart and checkout. Log in to the admin area and save a post as well.
  4. Watch the error log. During the first days, look for new warnings in the error log. If a warning points to a specific plugin, look for an update or an alternative.

A setup that runs cleanly on staging will most likely run cleanly on the live site, but it is worth checking parts such as caching and scheduled tasks on the live site separately.

What if the site breaks after the update?

If a fatal error occurs on the new PHP version, WordPress may show a "critical error" message and send a recovery link to the admin e-mail address. First use the error log to find which plugin or theme causes it; the steps are in our WordPress critical error guide.

If you cannot fix it right away, switching back to the previous PHP version for a short time and trying again after updating the plugin is a sensible route. It is only a temporary fix, though: once that version loses support you will need to make the same move. Not leaving it to the end of the schedule gives you time to fix problems when they appear.

Common mistakes during the switch

  • Not testing the backup: a backup that cannot be restored is often only noticed when something goes wrong. Before a major change, check that the backup is complete.
  • Changing several things at once: switching PHP, the theme and a few plugins on the same day makes it hard to find the cause when an error appears. Finish the updates first, then change the PHP version.
  • Checking only the home page: errors often show up in less visited places such as form submissions, checkout or the admin area.
  • Leaving debug settings on: turn off error display once you have finished troubleshooting; visitors should not see errors.

Which version should you move to?

The general rule is to choose the newest stable branch that your theme and plugins support. Since WordPress recommends PHP 8.3 or greater, 8.3 or 8.4 is a reasonable target for most up-to-date WordPress sites. Before moving to the newest branch, check the pages of your critical plugins for a compatibility note for that version. If you run several sites, move the simplest one first and continue with the others once you have seen the results.

Frequently Asked Questions

Will my site go down when PHP 8.2 support ends?

No, the site usually keeps working. But after 31 December 2026 no security patches are released for this branch, so newly found vulnerabilities stay open.

Will updating the PHP version slow down my site?

Usually not. The main risk is compatibility rather than speed; an old or abandoned plugin may throw errors on the new version. That is why you back up and test first.

How do I find my current PHP version?

On WordPress, look at the Server section in the Info tab of Tools > Site Health. If you are not sure, ask your hosting support.

What should I do if I get errors on the new version?

Use the error log to find the faulty plugin or theme, then update or disable it. If it cannot be fixed quickly, switch back to the previous version for a short time and fix the issue on a staging copy.


Powered by WISECP
Top