To check your PHP version, open Tools, then Site Health, then Info, then Server in WordPress. On 28 October 2026, php.net lists PHP 8.2 to 8.5 as supported, and WordPress.org recommends 8.3 or newer. PHP 8.2 security support ends 31 December 2026.
How do you check your PHP version in WordPress?
You can find your PHP version in the WordPress dashboard in under a minute. Follow these steps.
- Log in to WordPress as an administrator.
- Go to Tools, then Site Health.
- Open the Info tab, then expand the Server section.
- Read the PHP version line.
WordPress.org’s Site Health documentation places this screen under Tools, Site Health, Info, and says the Server section covers your server setup and PHP variables. The Status tab also shows a critical issue titled “Your site is running an outdated version of PHP” when WordPress detects one. If you cannot log in, your hosting control panel normally shows the PHP version in its settings, or your host’s support can tell you.
Which PHP versions are supported right now?
On 28 October 2026, php.net lists four supported branches: 8.2, 8.3, 8.4 and 8.5. The table reproduces the dates exactly as php.net shows them.
| Branch | Initial release | Active support until | Security support until |
|---|---|---|---|
| 8.2 | 8 Dec 2022 | 31 Dec 2024 | 31 Dec 2026 |
| 8.3 | 23 Nov 2023 | 31 Dec 2025 | 31 Dec 2027 |
| 8.4 | 21 Nov 2024 | 31 Dec 2026 | 31 Dec 2028 |
| 8.5 | 20 Nov 2025 | 31 Dec 2027 | 31 Dec 2029 |
The same page explains the policy. A branch gets full support, with bug and security fixes, for two years after its first stable release. It then gets two more years of critical security fixes only. After four years it reaches end of life.
Why does PHP support matter now?
An unsupported PHP version no longer receives security fixes, so every newly found flaw stays open. PHP.net says users of end-of-life releases “should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities”. Any branch older than 8.2 does not appear in php.net’s supported table.
Patchstack’s 2026 report says about half of the high-impact WordPress vulnerabilities it tracked were exploited within 24 hours of disclosure, which shows exploitation can start within hours of a flaw going public, so a version with no fixes is a poor place to be. The WordPress security checklist places this step fourth, after updates and plugin clean-up.
Note that PHP 8.2 sits on the edge. It is already past active support and its security support ends on 31 December 2026, about two months after this article’s date.
What version does WordPress recommend?
WordPress.org’s requirements page recommends PHP 8.3 or newer, with MariaDB 10.11 or newer or MySQL 8.0 or newer, and a host that supports HTTPS. It mentions 7.4 only as a lowest figure for legacy setups, and warns that those versions no longer get support and can leave your site open to known security flaws.
Aim for 8.3 or 8.4 for a site you are upgrading today. Version 8.4 has active support until 31 December 2026, and security support until 31 December 2028 according to php.net. Version 8.5 gives the longest runway but is newer, so check that your theme and plugins list it as compatible.
What should you do if your PHP version is out of support?
Plan the upgrade as a short project, and do it in this order.
- Back up the files and the database, and confirm you can restore them.
- Update WordPress, plugins and themes first, because newer releases usually support newer PHP.
- Remove plugins you do not use. Each one is another thing that may break on upgrade.
- Create a staging copy if your host offers one, switch it to the target PHP version, and click through your key pages, forms and checkout.
- Change the PHP version on the live site, from your host’s control panel or through its support team.
- Recheck Site Health and watch for errors over the next few days.
If a plugin breaks on the newer version and its developer has abandoned it, replace it. A plugin that cannot run on supported PHP is a bigger risk than the change itself.
How often should you recheck?
Check your PHP version twice a year, and again whenever php.net moves a branch to a new stage. The dates in the table are fixed in advance, so you can plan around them. PHP 8.4 leaves active support on 31 December 2026 but keeps security fixes until 31 December 2028, which gives most sites a comfortable runway.
Write the end date for your chosen branch in your calendar a few months ahead, and ask your host in advance whether it will move you automatically. Some hosts retire old versions on their own schedule, and that can arrive before php.net’s date. Check your host’s notices, as php.net only publishes the upstream dates.
What can go wrong during a PHP upgrade?
The usual failure is an old plugin or theme that uses features the newer PHP version removed. The site then shows a white screen or an error message. Your backup and a staging copy make this a ten-minute fix: switch the PHP version back, then update or replace the plugin that failed.
PHP.net publishes a migration guide for each branch, linked from its supported-versions page, listing what changed. Hand the guide for your target branch to your developer if a custom theme or plugin is involved. Test forms, search, logins and checkout, since those pages run the most code.
Common questions
What PHP version should WordPress use?
WordPress.org recommends PHP 8.3 or newer. Check php.net's supported versions page for the current list.
What happens if my PHP version is out of support?
PHP.net warns that users of end-of-life releases may be exposed to unpatched security vulnerabilities and should upgrade as soon as possible.
Can I update PHP myself?
On most managed hosting you change the PHP version from your hosting control panel or by asking support. Take a backup first and test the site afterwards.
Sources
- PHP.net: Supported Versions(php.net)
- WordPress.org: Requirements(wordpress.org)
- Patchstack: State of WordPress Security in 2026(patchstack.com)
- WordPress.org: Site Health screen(wordpress.org)
