WordPress and PHP 8.4 Compatibility: Supported Versions and Testing

PHP 8.4 is supported by WordPress Core 6.7 through 7.1 in the official matrix checked on 2 October 2026.

The production decision still belongs to the site’s complete stack.

Security update, 21 October 2026: PHP 8.4.27 contains fixes for two critical runtime vulnerabilities. Check the patching instructions and vendor-backport caveat. WordPress support for PHP 8.4 does not prove that your host has installed these fixes.

Official WordPress support

The current WordPress PHP compatibility matrix lists PHP 8.4 as supported by WordPress 6.7 through 7.1, and not by WordPress 6.6 or earlier:

Check the live matrix before an upgrade. “Supported by core” still does not mean that every installed component is compatible.

PHP 8.4 support dates and upgrade checks

PHP 8.4 receives active support until 31 December 2026 and security fixes until 31 December 2028, according to php.net. It remains a supported production option after active support ends, but routine bug fixes stop.

Two changes deserve a specific check when moving from an older branch:

• Implicitly nullable parameters are deprecated. A typed parameter defaulting to null can produce notices in older custom code or plugins. Update the affected component and review logs.
• IMAP, OCI8, PDO_OCI and PSpell are no longer bundled. If an integration needs one, confirm that the host supplies the separate extension for PHP 8.4.

What to inventory

• parent and child theme;
• standard and must-use plugins;
• page builder and add-ons;
• WooCommerce and every payment, shipping, tax, subscription, and checkout extension;
• custom snippets, integrations, and webhooks;
• required PHP extensions;
• cron jobs, queues, imports, exports, backups, and cache layers.

The list is more useful than a generic plugin-name table because versions and configurations matter.

Safe upgrade sequence

1. Create a production-like staging copy.
2. Update WordPress, themes, and maintained plugins.
3. Back up files and database and verify the rollback path.
4. Switch staging to PHP 8.4 with matching extensions and limits.
5. Test public pages, admin editing, media, search, forms, email, APIs, and scheduled jobs.
6. Test all commerce and authenticated flows where present.
7. Inspect PHP, WordPress, and server logs for fatals, warnings, and deprecations.
8. Deploy during a monitored window and repeat critical checks.

Our PHP version checker may detect a remotely exposed version, but an unknown result is not proof that a site does or does not use PHP. WordPress Site Health and the hosting panel are stronger sources for your own site.

When to choose 8.4

PHP 8.4 is a reasonable production candidate when the WordPress version supports it, the upstream branch remains supported, and the full stack passes. It can also be a temporary choice when a documented component blocks PHP 8.5. If you are leaving PHP 8.2 before its security support ends on 31 December 2026, the PHP 8.2 end-of-life upgrade plan compares 8.4 with 8.3 and 8.5 and covers the rollout.

For sites on WordPress 6.9, 7.0 or 7.1 that pass the newer branch, review WordPress and PHP 8.5. For the broader selection policy, use the recommended PHP version guide.

The evidence boundary is simple: WordPress Core 6.7 and later support PHP 8.4. Only staging and production monitoring can establish whether your particular site does.