
As of November 15, 2026, four PHP branches are supported: 8.2, 8.3, 8.4 and 8.5. PHP 8.4 and 8.5 still receive bug fixes. PHP 8.2 and 8.3 receive security fixes only, and PHP 8.2 reaches end of life on December 31, 2026. PHP 8.1 and everything older is already unsupported. If a site runs 8.2 or below, plan its upgrade now.
The tables below give the exact dates. After them you will find advice on which version to run and a step-by-step way to plan an upgrade.
Supported PHP Versions and End-of-Life Dates
These dates are from the official PHP supported versions page.
| Branch | First released | Active support until | Security support until | Status on Nov 15, 2026 |
|---|---|---|---|---|
| PHP 8.5 | Nov 20, 2025 | Dec 31, 2027 | Dec 31, 2029 | Active support |
| PHP 8.4 | Nov 21, 2024 | Dec 31, 2026 | Dec 31, 2028 | Active support |
| PHP 8.3 | Nov 23, 2023 | Dec 31, 2025 | Dec 31, 2027 | Security fixes only |
| PHP 8.2 | Dec 8, 2022 | Dec 31, 2024 | Dec 31, 2026 | Security fixes only, ends in weeks |
Older branches are listed on the PHP end-of-life page:
| Branch | End of life | Last release |
|---|---|---|
| PHP 8.1 | Dec 31, 2025 | 8.1.34 |
| PHP 8.0 | Nov 26, 2023 | 8.0.30 |
| PHP 7.4 | Nov 28, 2022 | 7.4.33 |
PHP 8.6 is close. Release candidate 8.6.0RC7 came out on November 12, 2026, and php.net lists the first stable release as planned for November 19, 2026. Release candidates are for testing, not production.
What Active and Security Support Mean
Every PHP branch gets four years of support in two phases.
- Active support, two years. Reported bugs and security issues are fixed and shipped in regular point releases.
- Security support, two more years. Only critical security issues are fixed. Releases come out as needed, so there may be several or none.
- End of life. The PHP project publishes no more fixes for that branch.
The dates line up with the calendar year. Each December 31, one branch leaves active support and another reaches end of life.
Why End of Life Matters
October 2026 gave a clear example. On October 21 the PHP project published a security advisory about critical remote code execution vulnerabilities and urged all users to update immediately. It affected every kind of web-facing PHP installation.
The fixes shipped in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The advisory stated plainly that PHP 8.1 and older no longer receive updates from the PHP project. The security team offered minimal source patches for 7.4, 8.0 and 8.1 to people who compile PHP themselves, but no new releases. Everyone else on those versions had to rely on a Linux distribution or hosting vendor to backport the fix, or upgrade under pressure.
That is the real cost of running an unsupported version. Nothing breaks on the day support ends. The problem arrives later, when a serious flaw is announced and there is no official release to install.
Some hosts and operating system vendors do maintain old PHP versions with their own patches. If you depend on that, confirm in writing which versions they cover and until when.
Which PHP Version to Run Now
- New sites: PHP 8.4 or 8.5. Both are in active support, and 8.5 is covered until the end of 2029.
- Sites on PHP 8.3: you are fine through 2027. WordPress currently recommends PHP 8.3 or greater on its requirements page.
- Sites on PHP 8.2: move to 8.4 before December 31, 2026.
- Sites on PHP 8.1 or older: treat the upgrade as overdue security work.
- PHP 8.6: test it on staging once it is released. For production, we suggest waiting for the first few point releases and for your plugins and extensions to confirm support.
How to Check Your PHP Version
From the command line:
php -v
Be careful with this one. A server can have several PHP versions installed, and the command line may not use the same one as the website. To see what the site really runs, check from the web side:
- WordPress: go to Tools, then Site Health, then the Info tab, and open the Server section.
- Hosting control panel: look for a PHP version or PHP manager setting for each domain.
- Any PHP site: upload a temporary file containing
<?php echo PHP_VERSION;, open it in a browser, then delete it.
If you manage many sites, record the version of each in one spreadsheet. You cannot plan what you have not counted.
How to Plan a PHP Upgrade
1. Check compatibility before you touch the server
For WordPress, update core, themes and plugins first. Current releases of maintained plugins are the ones tested against new PHP versions. Replace anything that has been abandoned.
For projects that use Composer, ask it what would block the new version:
composer why-not php 8.4
Then read the "Backward incompatible changes" page for each version you are crossing. The PHP manual appendices have a migration guide for every release.
2. Test on a copy
Clone the site to staging and switch only the staging copy to the new version. Turn on full error logging there:
error_reporting = E_ALL
display_errors = Off
log_errors = On
Click through the pages that earn money: forms, checkout, login, search. Then read the PHP error log. Fatal errors must be fixed. Deprecation notices tell you what will break in a future version, so pass them to whoever maintains the code. Our guide on fixing PHP errors in WordPress explains how to read them.
3. Switch production with a way back
Take a backup, change the version, and test the same pages again. Hosting control panels usually set PHP per domain, so switching back is the same quick change. Keep the old version installed for a week before you remove it.
For the clicks involved on common hosts, see how to update the PHP version of a WordPress site. For a WordPress-specific walkthrough of one version, see upgrading WordPress to PHP 8.4.
4. Watch the logs for a week
Some code only runs on a schedule or in rare cases, such as a monthly export or a refund. Check the error log daily for the first week.
You can jump more than one version at a time, for example from 8.1 straight to 8.4. Read the migration guide for each version in between, because the breaking changes add up.
Dates for Your Calendar
| Date | What happens |
|---|---|
| Nov 19, 2026 | PHP 8.6.0 planned release |
| Dec 31, 2026 | PHP 8.2 reaches end of life. PHP 8.4 moves to security fixes only |
| Dec 31, 2027 | PHP 8.3 reaches end of life. PHP 8.5 moves to security fixes only |
| Dec 31, 2028 | PHP 8.4 reaches end of life |
| Dec 31, 2029 | PHP 8.5 reaches end of life |
Notes for Agencies and Hosting Companies
- Make a supported version the default for new accounts. Today that means 8.4 or 8.5.
- Tell customers on PHP 8.2 about the December 31 deadline now, and again in December.
- If you keep end-of-life versions available, say clearly whether you backport security patches to them.
- Run the upgrade as a yearly project each autumn, so no site is ever more than two versions behind.
If you would rather hand the work over, our WordPress update service includes PHP version updates. More background is in our PHP articles.
