PHP End-of-Life Dates for 2026 (and What Breaks When You Upgrade)


Quick answer: as of October 13, 2026, PHP 8.2, 8.3, 8.4 and 8.5 are the only supported versions. PHP 8.2 gets security fixes only and reaches end of life on December 31, 2026. PHP 8.1 and everything older no longer receive any fixes from the PHP project. If your site runs 8.1 or older, schedule the upgrade now. If it runs 8.2, plan it before the end of the year.

Which PHP versions are still supported?

VersionActive supportSecurity fixes untilStatus on October 13, 2026
PHP 8.5Until December 31, 2027December 31, 2029Active support
PHP 8.4Until December 31, 2026December 31, 2028Active support
PHP 8.3Ended December 31, 2025December 31, 2027Security fixes only
PHP 8.2Ended December 31, 2024December 31, 2026Security fixes only
PHP 8.1EndedEnded December 31, 2025End of life
PHP 8.0EndedEnded November 26, 2023End of life
PHP 7.4EndedEnded November 28, 2022End of life

PHP's own definitions: active support means reported bugs and security issues are fixed and regular releases are made. Security fixes only means critical security issues are fixed, with releases made as needed. Sources: php.net supported versions and php.net end-of-life branches, checked October 13, 2026.

What happens if you stay on an unsupported version?

Nothing breaks the day support ends, which is why it gets ignored. The risk builds quietly. A security flaw found in PHP is fixed in the supported branches and left open in yours. Hosts tend to retire old versions from their control panels eventually. And platforms stop testing against them: WordPress's requirements page now recommends PHP 8.3 or greater.

Old versions are still common. W3Techs reports that PHP is used by 69.7 percent of websites whose server-side language is known. Of those, 64.7 percent run PHP 8, 27.4 percent run PHP 7, 7.8 percent run PHP 5 and 0.1 percent run PHP 4 (W3Techs, October 13, 2026). That is about one PHP site in three on a version that went end of life in 2022 or earlier.

What typically breaks when you upgrade?

Most of the trouble is in older code: custom themes, one-off plugins and scripts written when PHP 5 or 7 was current. Deprecation notices do not stop a site from running, but they fill logs, and removed features do break it. These are the changes that cause the most work, by the version that introduced them:

Moving toWhat changesWhere it shows up
8.0A number compared with a non-numeric string is now compared as strings, so 0 == "foo" is false. Arithmetic on an array throws a TypeError. Curly-brace offsets, each() and create_function() are removed. Reading an undefined variable or array key is a warning, and the default error_reporting is E_ALL.Old themes, one-off scripts, loose comparisons in form handling
8.1Passing null to a non-nullable built-in parameter is deprecated, as are FILTER_SANITIZE_STRING and strftime().Input cleaning and date formatting
8.2Creating properties on an object that never declared them is deprecated. utf8_encode(), utf8_decode() and "${var}" interpolation are deprecated.Classes that set properties on the fly, text-encoding code
8.3range() with mixed numeric and string bounds returns different results. Assigning a negative index to an empty array changes the next key. ++ on non-alphanumeric strings is deprecated.Code that builds ranges or sequential codes from input
8.4A parameter typed with a default of null but no nullable marker (Type $x = null) is deprecated, as is trigger_error() with E_USER_ERROR.Function signatures, custom error handlers
8.5The long-form casts (integer), (boolean), (double) and (binary) are deprecated, as are null as an array offset and the backtick operator.Older code written with long-form casts

Sources: the php.net migration guides for 8.0, 8.1, 8.2, 8.3, 8.4 and 8.5. Each guide lists more than this table does.

How do you upgrade without taking the site down?

  1. Find out what you run. Check the PHP version in your hosting control panel or with php -v on the server, and list the extensions, cron jobs and command-line scripts too. Scheduled scripts sometimes use a different PHP than the website does.
  2. Copy the site to a staging area and switch the copy to the new version. Do not test an upgrade on the live site.
  3. Turn on full error reporting on staging, log errors to a file instead of printing them on the page, and click through every form, login, checkout and scheduled job.
  4. Run a compatibility scan. A static analyzer such as PHPStan, or PHP_CodeSniffer with the PHPCompatibility ruleset, catches many removed functions and signature changes before a visitor does. Both run on a developer's machine, and nothing from them ships to the site.
  5. Fix in order: fatal errors first, then warnings, then deprecations. Update third-party code before your own, and replace any plugin that has not been updated for a current PHP version. An abandoned plugin is a bigger risk than the upgrade.
  6. Switch production at a quiet hour with the old version one click away in the hosting panel, and read the error log for a week.

Which version should you move to?

If you are on 8.1 or older and your code and plugins allow it, go to 8.4 or 8.5. PHP 8.5 has the longest runway, with security fixes through December 2029, and 8.4 runs through December 2028. PHP 8.3 is a reasonable stopping point when a plugin or library has not caught up. It is supported through December 2027 and sits at the version WordPress recommends.

You do not have to climb one minor version at a time. Testing the whole site on staging against the target version surfaces the same breakages, all at once. If the error log is too noisy to read, stepping through 8.0 and 8.1 first can make the causes easier to separate.

When is it worth bringing in a developer?

A standard WordPress install with maintained plugins can often be upgraded from the host's version selector after an afternoon on staging. A custom application, a theme with years of one-off edits, or anything that handles payments or customer records is different. Have a developer run the compatibility scan and fix what it finds. That is usually a small, bounded project, and it is the kind of work a fractional developer absorbs in the course of a month. We build and maintain hand-written PHP sites and can run this upgrade for yours.

Frequently Asked Questions

Is PHP 8.1 still supported?

No. PHP 8.1 reached end of life on December 31, 2025, and its last release was 8.1.34. It no longer receives security fixes. A site still running 8.1 or older should move to 8.4 or 8.5 if its code and plugins allow, with 8.3 as an acceptable stopping point.

When does PHP 8.2 reach end of life?

December 31, 2026. PHP 8.2 has been in security-fixes-only support since December 31, 2024, so it receives critical security fixes as needed until then and nothing afterward. Sites on 8.2 should plan the upgrade before the end of the year.

What is the latest version of PHP?

PHP 8.5, released on November 20, 2025, is the newest branch listed on php.net as of October 13, 2026. It has active support through December 31, 2027 and security fixes through December 31, 2029. PHP 8.4 is also under active support until December 31, 2026.

Will my site break if I upgrade PHP?

It can, if it relies on code that was removed or changed after the version it was written for. Typical causes are removed functions, stricter type handling and old plugins. Most deprecations only log notices. Testing a staging copy with full error reporting shows what will fail before visitors see it.

Can I go straight from PHP 7.4 to 8.4?

Yes. PHP does not require upgrading one minor version at a time. The risk is the sum of the changes across all the versions you skip, so test the whole site on staging and work through the error log. Stepping through intermediate versions is optional and mostly helps when the log is too noisy to read.

Have a project in mind?

15-minute call. No sales pitch. We'll tell you straight what's worth building.

Book the call →