If your website or web application runs on PHP, the version number decides whether security problems still get fixed. PHP version support is time-limited: each release gets bug fixes for a while, then security fixes only, then nothing. This guide is for owners and managers who need to decide when to upgrade. It covers which versions are supported today, what end of life means, why PHP 8.2 needs attention before the end of 2026, and how to plan the move without breaking anything.
The key points
- According to php.net, PHP 8.2, 8.3, 8.4 and 8.5 are supported today. PHP 8.1 and everything older is end of life.
- PHP 8.2 stops receiving security fixes after 31 December 2026.
- Running a supported branch is not enough on its own. You also need the latest patch release.
- Patch updates within a branch are low-risk. Moving to a new branch needs testing.
- Pick a target version with a long runway, so you are not back here in a year.
Not sure which PHP version you run?
We check your sites and systems and tell you what needs to happen next.
How PHP version support works
Every PHP branch, such as 8.3 or 8.4, moves through three stages:
- Active support. The PHP team fixes both ordinary bugs and security issues.
- Security fixes only. Only critical security issues are fixed. Other bugs stay as they are.
- End of life. No fixes of any kind. Any vulnerability found after this date stays open for good.
A branch in the security-only stage is still a reasonable place to be. A branch at end of life is not, however well the site itself is built.
PHP version support dates for 2026
These are the supported branches and their dates, according to php.net:
| Branch | Released | Active support until | Security fixes until | Status |
|---|---|---|---|---|
| PHP 8.5 | 20 Nov 2025 | 31 Dec 2027 | 31 Dec 2029 | Active support |
| PHP 8.4 | 21 Nov 2024 | 31 Dec 2026 | 31 Dec 2028 | Active support |
| PHP 8.3 | 23 Nov 2023 | 31 Dec 2025 | 31 Dec 2027 | Security fixes only |
| PHP 8.2 | 8 Dec 2022 | 31 Dec 2024 | 31 Dec 2026 | Security fixes only, end of life after 31 Dec 2026 |
Older branches are already end of life: PHP 8.1 since 31 December 2025, PHP 8.0 since 26 November 2023 and PHP 7.4 since 28 November 2022. Their last releases were 8.1.34, 8.0.30 and 7.4.33. There will be no more.
PHP 8.2 end of life: what to do before 31 December
From January 2027, PHP 8.2 gets no security fixes. The site keeps working, but the next serious vulnerability will not be patched on 8.2. Every month after that adds risk.
Your hosting provider may also act for you. Providers often move customers off end-of-life versions, either by upgrading them automatically or by charging for extended support. An untested upgrade on someone else’s schedule can break a plugin or a checkout.
If you run 8.2, start now: list what runs on it and test a newer version on a copy. If you run 8.1, 8.0 or 7.4, you are already without fixes, and the upgrade should move to the top of the list.
How to check which version you run
- Hosting control panel. The PHP settings page shows the version for each site.
- WordPress Site Health. Tools → Site Health → Info → Server lists the PHP version.
- phpinfo. A small file calling
phpinfo()shows the version. Delete it afterwards, as it exposes server details. - Command line.
php -vgives the command-line version, which can differ from what the web server uses. Check both.
Patch updates versus branch upgrades
Patch updates stay within a branch, for example 8.4.26 to 8.4.27. They fix bugs and vulnerabilities without changing how your code behaves. They are low-risk and should be applied quickly.
Branch upgrades, for example 8.1 to 8.3 or 8.4, are a different job. Features get deprecated or removed, and older plugins, libraries and PHP extensions may stop working. This kind of upgrade needs testing before it reaches production.
A practical upgrade path
- Inventory. List your sites, applications, plugins, libraries and extensions, with the PHP version each runs.
- Test on staging. Set up a copy on the new version and run the parts that matter: login, forms, payments and integrations.
- Fix deprecations. Read the error log for deprecation warnings, and update or replace anything that does not support the new version.
- Upgrade. Take a backup, switch the production version, and keep a way to roll back.
- Monitor. Watch the error log and key functions in the days after the switch.
If the code was inherited from a previous vendor, a code audit before the upgrade shows what is likely to break.
Which PHP version to choose today
At the time of writing, the latest PHP version is PHP 8.5, with security fixes until 31 December 2029. A new branch is usually released towards the end of each year, so check php.net before you decide. It gives you the longest runway, provided every plugin, library and extension you depend on supports it.
For many businesses PHP 8.4 is the practical choice. It has security fixes until 31 December 2028 and wide support in common software. PHP 8.3 works if something in your stack is not yet ready for 8.4, but it reaches end of life after 31 December 2027, so you will be upgrading again soon. As a rule, choose the newest branch your software runs on reliably, and test before you switch.
How we help with PHP upgrades
We can take the upgrade off your hands:
- Version inventory. We find out which PHP version each of your sites and systems actually runs.
- Code audit before a big upgrade. Our code audit services show what will fail and what to fix first.
- Testing and fixes. We test on staging, fix deprecated code and update or replace plugins and libraries.
- The upgrade itself. We switch the version on your server, or work with your hosting provider.
- Ongoing maintenance. A software maintenance agreement keeps patch releases applied and the next end-of-life date on the calendar.
If an older PHP application needs more than an upgrade, our web development services can rebuild the parts that need it.
Planning a PHP upgrade?
Start with a code audit, so you know what will break before it does.
Frequently asked questions
At the time of writing (November 2026) it is PHP 8.5, released on 20 November 2025. A new branch usually arrives towards the end of the year, so check php.net for the current version and patch number.
No. PHP 8.4 is a supported branch, but 8.4.26 is affected by the October 2026 vulnerabilities covered in our PHP security update article. Update to 8.4.27 or a later patch.
No. PHP 7.4 reached end of life on 28 November 2022 and PHP 8.1 on 31 December 2025. New vulnerabilities in them will not be fixed by the PHP project.
Apply patch releases as soon as they come out. Plan a branch upgrade well before your current branch reaches end of life, and check the support dates once a year.
The short version
Find out which PHP version each site runs and apply the latest patch now. If you are on 8.2 or older, plan the branch upgrade, test it on staging, and choose a version with years of support ahead. For larger work on legacy PHP systems, our software development services can help.
Ready to upgrade PHP?
Book a short call and we will look at your setup and propose a plan.


