PHP Compatibility Checker is abandoned – what to use instead
PHP Compatibility Checker, the WP Engine plugin with 200,000 installs, has not been updated since 2023, checks code only up to PHP 8.0, and is tested up to WordPress 6.4. If your host offers PHP 8.2 to 8.5, it cannot tell you whether your plugins are ready for them. It still shows up first in the plugin directory search, which is why people keep installing it.
What it still does, and doesn't
- Scans plugins and themes against PHP 5.3 through 8.0. Nothing newer.
- The scanning library it bundles (PHPCompatibility 9.x) predates PHP 8.1, so a plugin that breaks on 8.2 passes as clean.
- Its listing has carried the "no longer maintained" notice since 2023; its support forum says the same.
What to look for in a replacement
- Targets you actually need. PHP 8.2, 8.3, 8.4 at least; 8.5 ships in November 2026.
- Runs on your server, in PHP. Some scanners need
exec()(disabled on SiteGround, Kinsta, WP Engine and most shared hosts) or upload your code to an external service. Neither is acceptable on a client site. - Separates "breaks" from "deprecated". A tool that reports 400 notices for a plugin that will run fine on the new version is noise. You need to know which lines are fatal.
- Handles large plugins without a timeout. WooCommerce alone is 3,600 files. The scan has to run in batches that survive a 30-second PHP limit.
- Free for the version check. One listed alternative, also named "Plugin Compatibility Checker", shows results only up to PHP 8.0 for free and charges a monthly fee to see newer targets; its reviews say exactly that.
Upgravo
Upgravo – PHP Compatibility Check targets PHP 8.1 to 8.5, runs as PHP on your own server with no exec() and no upload, and scans in resumable batches so it completes on shared hosting. Results are grouped per plugin into Breaks (fatal on the target), Notices (deprecated, still runs) and Hidden (code guarded by a version check, or advice rather than compatibility). Each finding has file and line. Export to CSV; WP-CLI command for scripted runs.
It also checks two PHP 8.2 deprecations that the standard library misses: dynamic properties (the most common PHP 8.2 notice) and self::/parent:: string callables.
Install it from WordPress.org: Upgravo – PHP Compatibility Check. Free; a Pro add-on adds scheduled scans with email alerts and PDF client reports.
What it does not do: run your code. A scanner reads source; errors that depend on data at runtime show up only in a staging test with the new PHP version.
Other maintained scanners
Fair to mention, because they exist: CompatNav (PHP 8.0-8.5 rules written by hand), Upgrade Readiness Monitor and Azvian Preflight (both also check WordPress-level deprecations). Any of them is a better choice than the abandoned original. Compare them on your own site; a scan takes two minutes.
Sources
- PHP Compatibility Checker on WordPress.org
- PHPCompatibility on Packagist (stable 9.3.5, 2019)
- Plugin Compatibility Checker reviews, November 2025
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
- WordPress debug.log full of "Deprecated" notices – should you worry?
- My host forced a PHP upgrade and broke my WordPress site
- How to check if your WordPress plugins are compatible with PHP 8.3 or 8.4 before upgrading
- PHP 7.4 is end of life: what breaks in WordPress when you move to PHP 8