
PHP 8.2 reaches the end of upstream security support on 31 December 2026. Check your website’s version and agree a tested upgrade before the deadline.
If your website uses PHP 8.2, it needs an upgrade plan. The PHP project lists 31 December 2026 as the end of security support for that branch.[1]
That is an upstream support deadline, not a date when every website on PHP 8.2 suddenly stops loading. It does mean the PHP project will no longer support the branch after its scheduled end of life.[1]
For a business website, I would rather check compatibility and arrange the work now than discover an old dependency during a rushed change later.
Ask the person responsible for hosting which PHP branch runs the live site. Ask about any separate applications too, rather than assuming one answer covers everything you use.
Get the version and the support arrangement in writing. The PHP project notes that some distribution and long-term-support vendors provide backported fixes for older branches. If that is the arrangement you rely on, ask the vendor exactly what it covers.[2]
A vendor’s extended-support service and the PHP project’s own support schedule are different things. Do not assume you have the former because the website is still online.
The PHP support table lists the security-support end dates for supported branches. It also distinguishes active support from security support.[1]
Use that information alongside the compatibility requirements of your CMS, extensions and custom code. Do not choose a target solely because its number is higher, and do not assume that a newer branch has been tested with your particular site.
The goal is to agree a supported target that works for the application, then verify it in a suitable test environment.
Agree a test plan for the functions the business depends on, a recovery route and who signs off the live change.
If PHP 8.2 is still part of your setup, ask for an upgrade date, a target version and a short test plan. If the answer is that a dependency is blocking the move, make that a specific item with an owner.
The deadline is known. The work is easier to organise while there is still time to deal with what testing finds.
If you are unsure where your site stands, contact us with the information you have. Do not send passwords or hosting credentials in an enquiry.