Menu
Build with us

PHP 8.2 End of Life: What Agencies Must Do Before 2027

BLOG

If some of your client sites still run on PHP 8.2, the clock is ticking. PHP 8.2 end of life is December 31, 2026. After that date, the PHP project stops shipping security fixes for the 8.2 branch, and any new vulnerability found in it stays open on every server that has not moved on.

For an agency, this is not a one-site problem. It is a portfolio problem: dozens of client sites, mixed hosts, older themes and plugins, and only a few weeks of runway, right through the holiday season. This guide explains what the deadline means, which PHP version to move to, and a practical plan to upgrade client sites without breaking them or burning your team’s margin.

When is PHP 8.2 end of life?

According to the official PHP supported versions page, PHP 8.2 was first released on December 8, 2022. Its active support ended on December 31, 2024, and its security support ends on December 31, 2026. From January 1, 2027, PHP 8.2 is end of life (EOL).

Here is how the currently supported PHP branches line up, based on php.net:

PHP branchInitial releaseActive support untilSecurity support until
8.2Dec 8, 2022Dec 31, 2024Dec 31, 2026
8.3Nov 23, 2023Dec 31, 2025Dec 31, 2027
8.4Nov 21, 2024Dec 31, 2026Dec 31, 2028
8.5Nov 20, 2025Dec 31, 2027Dec 31, 2029
8.6Nov 19, 2026Dec 31, 2028Dec 31, 2030

Each PHP branch gets two years of active support (bug and security fixes), then two more years of critical security fixes only. Once those four years are up, the branch gets nothing at all.

What end of life actually means for client sites

A site does not stop working on January 1. That is exactly why EOL deadlines get ignored. What changes is the risk:

  • No more security patches. If a flaw is found in PHP 8.2 after the deadline, the PHP project will not fix it. Your client’s site keeps running on known-vulnerable software.
  • Plugins and themes move on. Vendors raise their minimum PHP versions over time, so a site stuck on an old version slowly loses access to updates, including security updates.
  • Hosts can force the issue. Hosts may move accounts off EOL versions or charge for extended support. A forced switch on the host’s schedule, not yours, is how sites break at the worst moment.
  • Compliance questions. Clients with security questionnaires, insurance forms or enterprise procurement may be asked whether they run supported software. “No” is a hard answer to give.

For your agency, an unplanned PHP switch means emergency tickets, unbilled hours and nervous clients. A planned upgrade is a scoped, billable project that shows clients you are looking ahead for them.

Which PHP version should WordPress sites move to?

WordPress.org’s official requirements page recommends PHP 8.3 or greater. WordPress still runs on PHP 7.4+, but the same page warns that older versions have reached end of life and may expose a site to security vulnerabilities.

The core team’s PHP compatibility table shows that WordPress 7.0 and 7.1 support PHP 7.4 through 8.5. In practice, that leaves agencies with a simple choice:

  • PHP 8.3 is the safest jump for older or plugin-heavy sites. It is supported until the end of 2027 and is the version WordPress recommends at minimum.
  • PHP 8.4 buys more runway (security fixes until the end of 2028) and suits well-maintained sites with current plugins.
  • PHP 8.5 is supported by current WordPress core, but check every plugin and theme on the site before you choose it.
  • PHP 8.6 was released on November 19, 2026. Treat it as too new for client production sites until your plugin stack confirms support.

Remember that core support is only part of the story. A site is only as compatible as its oldest custom plugin or unmaintained theme.

A PHP 8.2 end of life upgrade plan for agencies

The goal is to move every client site to a supported version before December 31, 2026, with no surprises. Here is a plan you can run across a portfolio.

1. Inventory every site and its PHP version

Start with a list: client, host, current PHP version, WordPress version, theme, page builder and key plugins. WordPress shows the PHP version under Tools → Site Health → Info → Server, and most management dashboards can report it in bulk. Flag every site on 8.2 or older.

2. Triage by risk, not by alphabet

Sort the list into three groups:

  • Green: current theme, maintained plugins, no custom code. These usually upgrade cleanly.
  • Amber: custom plugins, older page builders, WooCommerce or membership sites, payment integrations.
  • Red: abandoned plugins, heavily customized themes, sites nobody on the team has touched in years.

Do green sites first to build momentum, and give amber and red sites a proper staging pass.

3. Scan the code for compatibility issues

Run a static check before anything goes live. The open-source PHPCompatibilityWP ruleset for PHP_CodeSniffer flags code that will break or warn on newer PHP versions, and it accounts for the polyfills WordPress core already provides. Read the official PHP 8.3 migration guide for the backward-incompatible changes, and check each premium plugin’s changelog for its tested PHP versions.

4. Test on staging with real data

Clone the site to staging, switch it to the target PHP version and click through what matters to the client: forms, checkout, logins, search, booking flows and anything with custom code. Turn on debug logging and watch for deprecation notices and fatal errors. Deprecation notices are not urgent today, but they tell you what will break on the next upgrade.

5. Back up, switch and verify

Take a fresh, restorable backup. Switch PHP on production in a low-traffic window, clear caches, then repeat your smoke tests. Keep the old version selectable for a short rollback window if the host allows it, and check error logs again the next day.

6. Report it to the client

Send a short note: what was upgraded, why it mattered, what was tested and when the next deadline is (PHP 8.3 reaches end of life at the end of 2027). This turns invisible maintenance into visible value, and it sets up the next renewal conversation.

Common problems when upgrading from PHP 8.2

Most clean, current WordPress sites move from 8.2 to 8.3 or 8.4 without drama. Trouble usually comes from:

  • Old custom plugins written years ago and never updated.
  • Nulled or abandoned themes with outdated code and no vendor to fix it.
  • Outdated page builder versions that were never updated because “the site works”.
  • Hard-coded server assumptions in custom code, such as old extensions or functions removed in newer PHP releases.

When you find one of these, you have three options: update it, replace it, or rebuild that part of the site. Each is a scoped piece of work the client should approve, not something your team absorbs for free.

How to turn the deadline into margin, not overtime

A hard deadline across a whole portfolio can swamp a small delivery team in December. It does not have to:

  • Package it. Offer a fixed-scope “PHP upgrade and compatibility check” for clients outside a care plan, and include it as standard inside your WordPress maintenance and care plans.
  • Use the deadline honestly. December 31 is a real date from php.net, not a sales tactic. Share the source and let clients decide.
  • Upsell the right fixes. Sites that fail compatibility checks are often the same sites that need a rebuild, a speed pass or a security review.
  • Add capacity without hiring. A white label development partner can run the inventory, staging tests and fixes under your brand while your team keeps client relationships and new projects moving.

This is where a partner protects your margin. Instead of pulling senior developers off billable projects to debug a ten-year-old plugin, you hand the upgrade queue to a team that does this every week, and you keep the client-facing credit.

PHP 8.2 end of life checklist

  • List every client site with its PHP, WordPress, theme and plugin versions.
  • Flag every site on PHP 8.2 or older.
  • Group sites into green, amber and red by risk.
  • Run PHPCompatibilityWP on custom themes and plugins.
  • Test each amber and red site on staging with the target PHP version.
  • Back up, switch production, clear caches and smoke-test.
  • Watch error logs for 24–48 hours.
  • Send a short upgrade report to each client.
  • Add the PHP 8.3 end-of-life date (Dec 31, 2027) to your maintenance calendar.

Want the same discipline on every handover? Pair this with our website launch checklist for agencies.

FAQ

When is PHP 8.2 end of life?

PHP 8.2 reaches end of life on December 31, 2026, according to php.net. After that date, the PHP project releases no more security fixes for the 8.2 branch.

Will my WordPress site stop working when PHP 8.2 reaches end of life?

No. The site keeps running, but it runs on software that no longer gets security patches. Over time, plugins and themes also stop supporting it, and hosts may move or charge for accounts on EOL versions.

What PHP version does WordPress recommend?

WordPress.org recommends PHP 8.3 or greater. WordPress 7.0 and 7.1 support PHP 7.4 through 8.5, but older versions are end of life and not recommended.

Should we upgrade client sites to PHP 8.3 or 8.4?

PHP 8.3 is the safer jump for older or plugin-heavy sites and is supported until the end of 2027. PHP 8.4 gives you security support until the end of 2028 and suits well-maintained sites with current plugins. Test on staging either way.

How do I check which PHP version a WordPress site uses?

In the WordPress admin, go to Tools → Site Health → Info and open the Server section. Your hosting control panel and most site management tools also show it.

Can a white label partner handle PHP upgrades for our clients?

Yes. A white label web development partner can audit, test and upgrade client sites under your agency’s brand, so your clients see your name and your team stays focused on sales and strategy.

Need a hand before December 31?

Lines + Pixels works as a behind-the-scenes development team for agencies. We can audit your client portfolio, test every site on staging and move them to a supported PHP version, all under your brand. If you are planning bigger changes for 2027, our guide to enterprise WordPress development covers how we approach larger builds.

Book a partner call and let’s plan your PHP upgrades together.

Author logo

L + P

admin@linesandpixels.team

Explore more Blogs

Ready to Transform Your Online Presence?

Elevate your business with a custom-designed website that captivates and converts. Let our expert team craft a digital experience perfectly tailored to your brand's needs.

BUILD WITH US
•