VPS

PHP 8.2 End of Life on 31 December 2026: The Upgrade Plan for Agencies

This article is a step-by-step PHP 8.2 upgrade plan for agencies: how to inventory every runtime, choose a target version by compatibility, test on a snapshot copy and release with a rollback. php.net lists 31 December 2026 as the end of security support for PHP 8.2.

Follow the steps in order, because the inventory decides the target version and the test copy decides when you can release.

The date

What the Date Actually Means

As of 9 November 2026, php.net lists four supported branches:

Supported PHP Branches

Branch
Security fixes until
PHP 8.2
31 December 2026
PHP 8.3
31 December 2027
PHP 8.4
31 December 2028
PHP 8.5
31 December 2029

End of life does not switch a site off on 1 January. After end of life the PHP project publishes no further security fixes for 8.2, so any fixes from a distribution or vendor come from outside its releases. If you rely on one, write down who provides it and until when.

Your real deadline

For an agency, the useful deadline is earlier than 31 December: it is the last date you can test, get client approval and release without rushing.

Step 1

Inventory the Runtimes That Do the Work

Make one row per application, not one per server. A site often uses more than one PHP runtime: the web request goes through PHP-FPM or Apache, while cron jobs and queue workers call the command-line binary. They can be different versions. The finished inventory also shows which sites need testing first.

Inventory columns

  • Application and client, plus who approves downtime
  • PHP version serving web requests
  • PHP version used by cron jobs, workers and CLI scripts
  • CMS or framework version
  • Plugins, themes and Composer packages, with their supported PHP range

php -v only tells you which binary your shell picks up. To see what serves the site, check the web server config. On Nginx, this shows which PHP-FPM socket each site uses:

Find the PHP-FPM socket for each Nginx site

grep -R fastcgi_pass /etc/nginx/

Also look at the full path of the PHP binary in each crontab entry. If you want to confirm from the browser, use a temporary file that prints phpversion() behind authentication and delete it straight after. Do not leave a public phpinfo page online.

Step 2

Pick the Target From Compatibility, Not Habit

Choose the newest supported branch your application and its dependencies declare support for. In late 2026 that is usually 8.4 or 8.5. A newer target buys you more years before you repeat this exercise, but only if your CMS, plugins and extensions are ready for it.

Composer can do part of the checking for you. composer why-not php 8.4.0 lists the packages that block a given version, and composer check-platform-reqs checks the installed packages against the PHP you are running.

Check what blocks a target version

composer why-not php 8.4.0

Check installed packages against the PHP you are running

composer check-platform-reqs

WordPress, Laravel, Symfony and Drupal all publish their supported PHP ranges, so read those rather than assuming. Jumping from 8.2 to 8.5 means reading the migration guides for 8.3, 8.4 and 8.5, because changes from each release apply. If you choose an older target, write down why and set a date to revisit it.

Step 3

Test on a Copy, and Make the Copy Safe First

A server built from a recent snapshot is a realistic test environment: real database, real uploads, real plugin set. On Webdock you can create a new server directly from any snapshot, so no rebuild is needed.

A production clone is not automatically a safe test environment, though. It boots with the same cron jobs, queue workers, payment keys and mail settings. Before anything runs, know which jobs and integrations could reach real customers and how you will stop them: pause the scheduler and workers, switch payment and mail integrations to test credentials, and keep public DNS pointing at production. If a job could do real harm in the first minutes, such as sending a newsletter or charging a card, build a sanitised copy instead of cloning.

Then confirm the copy works on the current version, switch it to the target, and walk through the site as a user would: log in, submit a form, place a test order, run a scheduled task by hand. On Webdock LEMP and LAMP stacks you can change the PHP version from the Manage PHP interface; check which versions it offers for your stack. On other stacks, or if you prefer the command line, the same docs page walks through the manual switch: new PHP-FPM packages, the web server socket, and the CLI binary. Take a snapshot first.

Watch the PHP error log while you test. Deprecation notices are warnings today and may become errors in a later release, so fix them rather than hiding them.

Step 4

Fix What Broke, in a Sensible Order

  1. 1Update the CMS or framework first, on the test copy
  2. 2Update plugins and Composer packages that declare support for the target
  3. 3Replace or remove anything abandoned by its author
  4. 4Fix your own code last, because by then the remaining errors are clearly yours

Re-run the same checks after each meaningful change. It makes a regression much easier to trace than updating everything at once.

Step 5

Release With a Rollback That Protects New Data

Agree a maintenance window with the client in writing. Take a manual snapshot right before you change the PHP version, so your recovery point is minutes old rather than a night old. Switch the version, run the same checklist you used on the copy, and keep an eye on the error log afterwards.

Decide rollback first

Decide in advance what rollback means. Often switching the PHP version back is enough. If the upgrade also involved dependency updates or a database migration, restoring the whole server is possible, but it also removes orders, comments and edits made after the snapshot. For a shop, plan how you would keep or re-enter those before you restore.

Step 6

Tell the Client What You Did

A short note is enough: the site now runs PHP 8.4 (or 8.5), supported until December 2028 (or 2029), tested on a copy before release, rolled out on this date, with these workflows checked and the next review due on this date.

Webdock

Your Test Copy Is Included

Every Webdock server includes automatic snapshots, two daily and three weekly, plus three manual snapshot slots, and the option to create a new server from any snapshot. That is the test copy for your PHP upgrade, included in the price.

Frequently Asked Questions

The date does not switch anything off. After it, vulnerabilities in PHP 8.2 are no longer fixed by the PHP project.

The newest one your application and dependencies support. 8.4 is supported until 31 December 2028 and 8.5 until 31 December 2029. 8.3 gets security fixes for one more year, so choose it when something blocks the newer branches, and plan the next upgrade now.

Treat it as a security issue, not only a compatibility issue. Plan its replacement or removal as part of the upgrade.

No. It shows the command-line binary. The website may be served by a different PHP-FPM version, and cron jobs may call yet another binary. Check each.

Test the upgrade on a copy

Automatic snapshots, manual slots and new servers from any snapshot, included on every server