How to check if your WordPress plugins are compatible with PHP 8.3 or 8.4 before upgrading
Three methods, in increasing reliability: read each plugin's declared support, scan the code, test on staging. Use all three for a client site; the scan alone is enough for a blog with ten plugins.
Method 1: what the plugin declares (5 minutes, weak)
Each plugin's page on WordPress.org shows "Requires PHP" and the "Tested up to" WordPress version. Neither says "works on PHP 8.4". A plugin last updated in 2022 may run on 8.4 by luck, or fail on the first request. Use this method only to spot plugins that have not been updated in two years: those go to the top of the list for the next two methods.
In the admin, Plugins → Installed shows the last update date in the "View details" popup.
Method 2: scan the code (10 minutes, catches most)
A scanner reads every PHP file and checks it against the list of functions, parameters, constants and syntax that the target version removed or deprecated. It finds removed functions (each(), create_function()), changed parameter orders (implode()), removed constants (E_STRICT), and the deprecations that will fill your log (dynamic properties, implicitly nullable parameters).
Upgravo does this from the WordPress admin: select the target version (8.1 to 8.5), click Scan, read the per-plugin result. Breaks means fatal on the target; Notices means deprecated but runs; Hidden means code the plugin only runs on old PHP versions (guarded by a version check) or style advice. Each finding has file and line. The scan runs in batches on your own server, so it completes on shared hosting and nothing is uploaded anywhere.
Install it from WordPress.org: Upgravo – PHP Compatibility Check.
What a scan cannot see: errors that depend on data at runtime. The classic is count($x) where $x is an empty option on one site and an array on another. Those need method 3.
Method 3: staging (30 minutes, catches the rest)
- Create a staging copy. Most hosts have a one-click staging feature; for a local copy, Local (by WP Engine) runs WordPress on your computer with a PHP version selector.
- Switch the copy to the target PHP version.
- In
wp-config.php:WP_DEBUGandWP_DEBUG_LOGtrue,WP_DEBUG_DISPLAYfalse. - Click through: admin screens of each plugin, the front page, a product page, checkout, each form, pages using shortcodes.
- Read
wp-content/debug.log.Fatal errorlines are blockers;Deprecatedlines are a to-do list.
Putting it together
| Plugin status after scan + staging | Action |
|---|---|
| Clean | Nothing |
| Notices only, plugin updated this year | Upgrade; notices will disappear in a future release |
| Notices only, plugin not updated in 2+ years | Plan a replacement; upgrade now |
| Breaks | Update the plugin; if still broken, replace before upgrading |
| Fatal on staging, clean in scan | Runtime bug; report to the author with the log line |
Which version to target
PHP 8.3 is the safe choice in 2026: three years old, every maintained plugin supports it, security fixes until end of 2027. PHP 8.4 is fine for sites whose plugins are all current. PHP 8.5 ships in November 2026; give plugins six months.
Sources
- PHP supported versions
- WordPress: PHP compatibility and WordPress versions
- Learn WordPress: Testing your products for PHP version compatibility
More guides
- "Deprecated: Creation of dynamic property" in WordPress – what it means and how to fix it
- "Implicitly marking parameter as nullable is deprecated" – PHP 8.4 and WordPress plugins
- "Uncaught TypeError: … must be of type …" – why PHP 8 turns old warnings into fatal errors
- "There has been a critical error on this website" after a PHP update
- PHP Compatibility Checker is abandoned – what to use instead
- WordPress debug.log full of "Deprecated" notices – should you worry?
- My host forced a PHP upgrade and broke my WordPress site
- PHP 7.4 is end of life: what breaks in WordPress when you move to PHP 8