Updating PHP for WordPress: Why Your Host Is Warning You

Why your host says your PHP version is outdated

PHP is the programming language WordPress runs on. Your host installs it on the server, and each site picks a version. Old versions stop receiving security patches, and hosts warn customers before they force an upgrade or charge for extended support.

The PHP project's supported versions page explains the cycle: every release branch gets two years of active support (bug and security fixes), then two more years of critical security fixes only. After four years it reaches end of life and gets no fixes at all.

Running an end-of-life version does not break your site on its own. It means any newly found flaw in PHP itself will never be fixed on your server, and plugin developers gradually drop support for it.

Which PHP version WordPress recommends in 2026

WordPress.org's requirements page recommends PHP 8.3 or greater, with MariaDB 10.11+ or MySQL 8.0+ and HTTPS. It notes that WordPress still works on PHP 7.4, but warns that end-of-life versions may expose your site to security vulnerabilities.

The core team's PHP compatibility table shows the current release, WordPress 7.1, is compatible with PHP 7.4 through 8.5. WordPress 6.8 and older are not listed as compatible with PHP 8.5, so update WordPress itself before you jump to the newest PHP.

A sensible target in October 2026 is PHP 8.3 or 8.4. Both are supported until at least the end of 2027, and most maintained plugins support them. PHP 8.5 is fine if your host offers it and your plugins declare support.

Check compatibility before you switch

Ten minutes of checking saves most of the pain. Start in the WordPress dashboard, then look at each plugin.

• Tools > Site Health: shows your current PHP version and flags it if it is outdated. The Info tab lists the server PHP version and extensions.
• Plugins screen: look at the 'Last updated' date for each plugin on WordPress.org. Anything not updated in over a year deserves a closer look or a replacement.
• Plugin pages: WordPress.org plugin pages show a 'Requires PHP' value and 'Tested up to' WordPress version. Paid plugins publish this in their changelog or docs.
• Custom code: a child theme or code snippets added by a past developer may use functions removed in PHP 8. These need testing, not guessing.
• Error log: if your host gives you a PHP error log, check it now so you know which warnings existed before the change.

Update WordPress core, the theme and all plugins first, on the current PHP version. Many compatibility fixes are already in the latest plugin versions, and updating first separates plugin problems from PHP problems.

How to update PHP for WordPress, step by step

Most Singapore-hosted WordPress sites run on cPanel, Plesk or a host's own dashboard. The menu names differ, but the steps are the same. Our guide to setting up a WordPress staging site covers the staging part in detail.

1. 1

   Take a full backup

   Back up files and the database, and confirm you can download it. Host snapshots are good; a plugin backup stored off the server is better.

2. 2

   Create a staging copy

   Use your host's staging tool or a staging plugin. The copy should run on the same server type as the live site.

3. 3

   Switch PHP on staging only

   In cPanel this is usually 'Select PHP Version' or 'MultiPHP Manager'; in Plesk, 'PHP Settings' for the domain. Pick 8.3 or 8.4.

4. 4

   Test the pages that earn money

   Home page, contact form, checkout, booking, member login, search and the admin area. Submit a real test form and a test order.

5. 5

   Check the error log

   Turn on WP_DEBUG_LOG on staging and read wp-content/debug.log. Deprecation notices are warnings; fatal errors must be fixed before going live.

6. 6

   Fix or replace failing plugins

   Update them, contact the developer, or swap in a maintained alternative. Do not edit plugin files directly, as the next update overwrites them.

7. 7

   Switch the live site

   Pick a quiet hour, change the PHP version on live, then repeat the same tests straight away.

Site broke after the PHP update: how to roll back

If the site shows 'There has been a critical error on this website' or a blank page after the switch, do not panic. Changing PHP does not change your content or database.

• Switch back first: go to the same PHP selector and choose the previous version. The site normally recovers within a minute.
• Check the recovery email: WordPress emails the admin address with the plugin or theme that caused the fatal error, plus a recovery-mode login link.
• Read the error log: the fatal error line names the file and plugin folder that failed.
• Fix on staging, then retry: update or replace that plugin on staging and test again before switching live.

For the white-screen case in more detail, see our guide to the WordPress critical error and white screen fix. If the trouble started with a plugin or core update rather than PHP, our WordPress update broke my site guide walks through it.

Keeping PHP current after this upgrade

PHP releases a new version every November, and each one is retired four years later. That means the question comes back every year or two. Put the security end date of your current version in your calendar, six months early.

Do it yourself or get help?

If you have a staging tool, a recent backup and a handful of well-maintained plugins, you can do this yourself in under an hour using the steps above. It gets harder with custom code, WooCommerce, membership plugins or a site built years ago by someone you can no longer reach.

For a one-off upgrade, our Quick Fix (1 hour) (S$119) covers testing and switching PHP on a typical small site. If you would rather not think about PHP, core and plugin updates again, our Care plan (S$129 a month) includes updates, backups and monitoring.