Upgrades and deprecations
Upgrade PHP 7.4 to 8.x: Hop Order, Dates and Blockers
In short
PHP 7.4 reached end of life on 28 November 2022, and 8.0 and 8.1 are unsupported too. php.net supports 8.2, 8.3, 8.4 and 8.5 today. The manual has one guide per step, so the route is 8.0, 8.1, 8.2, 8.3, then 8.4 or 8.5. I would aim for 8.4 or 8.5 because 8.2 loses security fixes on 31 December 2026.
Which PHP versions are supported on 19 November 2026?
php.net gives each branch two years of active support and two more years of critical security fixes only. Four branches are supported today, 8.2 to 8.5. PHP 7.4, 8.0 and 8.1 are all on the unsupported list, so both intermediate stops on this route are already out of support.
Two dates fall on 31 December 2026. PHP 8.2 loses its security fixes, and 8.4 moves from active support to security-only. The php.net front page also announced security releases for 19 November 2026 that address vulnerabilities in all supported versions, so use the newest patch release of whichever branch you land on.
| Branch | Status on 19 Nov 2026 | Active support until | Security fixes until or end of life |
|---|---|---|---|
| 7.4 | Unsupported | Not listed | End of life 28 November 2022 (last release 7.4.33) |
| 8.0 | Unsupported | Not listed | End of life 26 November 2023 (last release 8.0.30) |
| 8.1 | Unsupported | Not listed | End of life 31 December 2025 (last release 8.1.34) |
| 8.2 | Security fixes only | 31 December 2024 | 31 December 2026 |
| 8.3 | Security fixes only | 31 December 2025 | 31 December 2027 |
| 8.4 | Active support | 31 December 2026 | 31 December 2028 |
| 8.5 | Active support | 31 December 2027 | 31 December 2029 |
In what order should the hops go?
The PHP manual publishes one migration guide per step: 7.4 to 8.0, 8.0 to 8.1, 8.1 to 8.2, 8.2 to 8.3, 8.3 to 8.4 and 8.4 to 8.5. Each has its own list of backward incompatible changes, and I found no page that describes a multi-version jump.
A guide for 8.5 to 8.6 exists as well. But the end-of-life page shows 8.6.0RC7 as available for testing, and the supported-versions table does not list 8.6, so it is not a target yet.
I would plan the route as six hops and read the six lists in order, because each guide documents the changes of its own release. Deploying at every stop is not needed. Since 8.0 and 8.1 are unsupported, I would use them as test checkpoints and ship at 8.4 or 8.5.
Checked against: source 2, source 4, source 5, source 6, source 7, source 8, source 9, source 10
What does the first hop, 7.4 to 8.0, break?
This is the longest list of the six. These are the entries from the 7.4 to 8.0 guide that I would search for first. The guide has more.
- Removed:
create_function(),each(), the__autoload()function, the(real)and(unset)casts, thetrack_errorssetting, case-insensitive constants throughdefine(), curly-brace offset access such as$array{0}, and calling non-static methods statically. A method with the same name as its class is no longer a constructor. - Changed meaning: comparing a number with a non-numeric string now casts the number to a string, so
0 == "foo"is false.matchandmixedare reserved words. Assertion failures throw by default. The concatenation operator now has lower precedence than+and-. - Stricter errors: several notices became warnings, such as undefined variables and array keys. Several warnings became
Errorexceptions, such as undefined constants and the wrong number of arguments to a built-in function. Arithmetic on an array, resource or object throwsTypeError. - Defaults:
error_reportingnow defaults toE_ALL,display_startup_errorsis on, and the@operator no longer silences fatal errors. The guide tells you to keepdisplay_errors=Offin production and log instead. - Expect noisier logs after this hop even from code that still runs. If Composer refuses to install once PHP is upgraded, see this fix page.
Checked against: source 4
What do the later hops change?
The later lists are shorter, and each guide's own list is longer than the entries below. They are the ones I would read first, one per hop.
- 8.0 to 8.1: write access to the whole
$GLOBALSarray is gone. Inherited methods now sharestaticvariables with the parent. An optional parameter before a required one is always treated as required.readonlyandneverare reserved. FTP, IMAP, LDAP, PgSQL, PSpell and FileInfo functions return objects instead of resources, sois_resource()checks fail. The mysqli default error mode changed from silent to exceptions. - 8.1 to 8.2:
strtolower(),strtoupper(),ucfirst(),ucwords()and similar functions are no longer locale-sensitive.str_split()returns an empty array for an empty string.glob()returns an empty array instead offalsewhenopen_basedirrestricts every path.var_export()now writes fully qualified class names. - 8.2 to 8.3: code very close to the call-stack limit may now throw an
Error.range()throwsTypeErrorandValueErrorin cases it used to accept. Assigning a negative index to an empty array makes the next index$n+1instead of 0. The Date extension throws its ownDateErrorandDateExceptiontypes. - 8.3 to 8.4:
exit()now behaves like a function and throwsTypeErrorfor invalid types.E_STRICTis removed. DBA, ODBC and SOAP resources became objects. Many functions now throwValueErroron invalid arguments. The guide also warns that every new function or class can cause a redeclaration error with the same name in your code. - 8.4 to 8.5:
class_alias()no longer acceptsarrayorcallableas alias names. Traits are bound before the parent class. Thedisable_classessetting is removed. Destructuring a non-array value, and casting an unrepresentable float to int, now emit warnings. Loadingopcache.sothroughzend_extensionemits a warning because Opcache is always built in.
Checked against: source 5, source 6, source 7, source 8, source 9
Should the target be 8.4 or 8.5?
Both are supported, and 8.5 has the longer clock. Its active support runs to 31 December 2027 and its security fixes to 31 December 2029, against 31 December 2026 and 31 December 2028 for 8.4. The cost is one more guide to read, and the 8.4 to 8.5 list above is short.
I would not stop at 8.2 or 8.3. Their security fixes end on 31 December 2026 and 31 December 2027. The case for 8.4 is a framework or extension that does not yet declare 8.5 support.
This page compares php.net documents fetched on 19 November 2026. It does not cover your Composer constraints, your extensions or your code, so none of it says your application will pass any hop.
What else do people ask?
Is PHP 8.1 still supported?
No. The php.net end-of-life page lists 8.1 as ended on 31 December 2025, with 8.1.34 as the last release. It is a stop on the way from 7.4, not a destination.
Can I go from PHP 7.4 straight to 8.4?
The manual publishes one migration guide per step and I found no page for a longer jump. I would read all six lists even if you deploy only once.
Sources
- PHP manual, supported versions, fetched 2026-11-19
- PHP manual, unsupported branches (end of life), fetched 2026-11-19
- php.net front page, current patch releases and security release notice, fetched 2026-11-19
- Migrating from PHP 7.4.x to PHP 8.0.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.0.x to PHP 8.1.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.1.x to PHP 8.2.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.2.x to PHP 8.3.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.3.x to PHP 8.4.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.4.x to PHP 8.5.x, backward incompatible changes, fetched 2026-11-19
- Migrating from PHP 8.5.x to PHP 8.6.x, backward incompatible changes, fetched 2026-11-19
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. This page compares php.net documents I fetched on 19 Nov 2026 (the supported-versions and end-of-life pages and the migration guides from 7.4 to 8.5). I did not run these upgrades for it. It does not cover your extensions, Composer packages, framework or code. Found a mistake? Tell me.