PHP 8.2 End of Life: What WordPress Owners Do Now

Your host has emailed you about PHP, or someone quoting for your website mentioned it, and now you want to know whether "PHP 8.2 end of life" on your WordPress site is actually urgent. Short answer: it matters, and you still have a few weeks. On 31 December 2026, PHP 8.2 stops getting security fixes. Your site will not go dark that morning, but it will be running on software nobody patches.
This guide covers four things in order: what changes on that date, how to check your PHP version in two minutes, what usually breaks when PHP is upgraded, and how to decide between upgrading the site you have and rebuilding it. It ends with the questions to ask anyone who quotes you for the work.
PHP 8.2 end of life for WordPress: what changes on 31 December
PHP runs on a fixed cycle, published on php.net's supported versions page. Each version gets two years of active support, then two more years of fixes "for critical security issues only", and then it reaches end of life. PHP 8.2 was released on 8 December 2022, its active support ended on 31 December 2024, and its security support ends on 31 December 2026.
| PHP version | Security fixes until | Status on 1 January 2027 |
|---|---|---|
| 8.2 | 31 Dec 2026 | End of life, no more fixes |
| 8.3 | 31 Dec 2027 | Security fixes only |
| 8.4 | 31 Dec 2028 | Security fixes only (active support ends 31 Dec 2026) |
| 8.5 | 31 Dec 2029 | Active support until 31 Dec 2027 |
Two things follow from this. First, nothing switches off. PHP's own wording for an end-of-life release is that users "may be exposed to unpatched security vulnerabilities" and "should upgrade as soon as possible". The risk grows quietly; it does not arrive as an outage.
Second, you may not get until 31 December. As the developer whose dev.to write-up prompted this guide puts it, "the hosting company is going to move you to 8.3 or 8.4 sooner or later". One hosting platform, WP Cloud, has announced it will remove PHP 8.2 on 15 December 2026, before the official date.
You are in large company. Of the WordPress sites that report their PHP version to WordPress.org, about 22% run PHP 8.2, about 14% are still on PHP 7.4 and about 9% are on PHP 8.1. The last two are already past end of life and supported by WordPress "for backward compatibility only".
Check your PHP version in two minutes
You do not need a developer for this step.
- Log in to your WordPress dashboard.
- Open Tools → Site Health → Info, then expand the Server section. The PHP version is listed there.
- Open the Status tab on the same screen. If WordPress considers your PHP old, it shows a security item: "Your site is running an outdated version of PHP, which requires an update".
If you cannot log in to the dashboard, your hosting control panel usually shows the PHP version, or you can ask the host directly. Server settings are often managed by the host, so in many cases only they can change the version anyway.
Write the number down. If it reads 8.2, the date above is yours. If it reads 7.4, 8.0 or 8.1, you are already on an unsupported version and the same steps apply with more urgency.
What breaks when the host upgrades PHP
Start with the reassuring part: WordPress itself is rarely the problem. WordPress has been compatible with PHP 8.3 since version 6.4 and with PHP 8.4 since version 6.7. If your WordPress core is up to date, it is ready.
The catch is in the same documentation: WordPress "is rarely used in isolation (without any theme or plugins)". On a site that is five or ten years old, with a custom theme and a long plugin list, the theme and plugins are where upgrades fail.
A public scan of two real WordPress plugins shows what that looks like:
- An events plugin with 50 PHP files produced zero fatal errors, but 17 items that can fail when they receive unexpected input, plus 5 deprecation warnings.
- One of those problems: since PHP 8.3, a common date function,
DateTime::modify(), throws an exception when it cannot parse a date instead of failing quietly. - Another: "dynamic properties", a pattern older plugin code uses everywhere, were deprecated in PHP 8.2.
- A social feed plugin ran on PHP 8.4 with one deprecation warning that, in the author's words, "will fill the error log and break in a later PHP version".
So the typical failure is not a white screen on day one. It is something like a booking form that breaks on one unusual date, or a warning that becomes an error two versions later. PHP publishes a list of backward-incompatible changes for every release, down to details such as how a negative index on an empty array behaves; that list is what a developer works through.
There is also a trap in the fixing. The same author refused to auto-apply one fix because it "would turn a deprecation notice on PHP 8.4 into a parse error on PHP 7.0", and notes that for date handling "a person has to decide what the right fallback is". Fixes need judgement, and they need a test.
The safe way to upgrade PHP on WordPress
Whoever does the work, your host, a freelancer or an agency, the order should look like this:
- Full backup of files and database, so there is a rollback point.
- A staging copy of the site. The WordPress hosting handbook asks hosts to "test their full stack before making a new PHP version the default"; ask the same for your site.
- Update WordPress core, the theme and every plugin on staging first.
- Switch staging to the target PHP version. WordPress recommends "PHP version 8.3 or greater", and its hosting handbook recommends 8.4 or later for production.
- Fix what the error log and a code scan flag, plugin by plugin.
- Click through the site on the new version: forms, checkout, booking, search, logins. The scan's own advice is to "click through the plugin on the target PHP version after fixing".
- Switch the live site, then watch the error log for a few days.
If a plugin has had no update in years and fails on staging, that is your signal for the next decision.
Upgrade or rebuild?
Most sites should simply be upgraded. A rebuild is a bigger, slower purchase, and our own redesign guide says it plainly: when nothing else is wrong, "resist anyone selling you a rebuild". Read what actually moves a redesign quote before you accept one.
Upgrade when:
- the theme and most plugins still receive updates;
- staging shows only a handful of fixable warnings;
- the site already loads well and brings in enquiries.
Consider rebuilding when:
- the theme was custom-built years ago and nobody maintains it;
- key features depend on plugins whose authors have gone quiet;
- the site was slow and hard to edit before PHP ever came up;
- you change three things a year. As our redesign guide puts it, "If you change three things a year, paying for a heavy CMS is paying for flexibility you will not use".
WordPress is still the right answer for some businesses, for instance a content-heavy site with several editors. If you do rebuild, on WordPress or anything else, every old URL needs a 301 redirect before launch, because "Rankings move when redirects are forgotten, not when a site is rebuilt".
Questions to ask before you pay anyone
Use this list for the host, a freelancer or an agency:
- Which PHP version will you move us to, and why that one?
- Will you work on a staging copy first, and can I open it?
- Which plugins and which theme files did you check, and what did you find?
- Who fixes plugin warnings: you, the plugin author, or nobody?
- What is the rollback plan if the live switch goes wrong?
- Which plugins do you recommend replacing, and with what?
- If you recommend a rebuild, what is wrong with the current site apart from PHP?
- For a rebuild: where is the redirect map for the old URLs?
- What will hosting and maintenance cost after the work is done?
- Is this a quote after a written scope, or a number before anyone has looked?
A good answer to the last two protects you more than any price comparison.
What to do this week
Check the version in Site Health today. If it reads 8.2 or lower, ask your host when they plan to move you, then get a staging upgrade done before they do it for you. Upgrade if staging is clean; rebuild only if the site was already failing you.
If a staging check or a rebuild is on the table, see how Gigzman builds and rebuilds business websites. Our published website prices start from ₹45,000 with a typical timeline of 3–6 weeks, and those are floors, not averages; the full list is on our pricing page.
I'm Tarun, founder of Gigzman. We build websites for a living, and for most marketing sites we recommend Next.js over WordPress, so weigh the rebuild section with that in mind.
Questions people ask
Will my WordPress site stop working on 1 January 2027?
No. PHP 8.2 stops receiving security fixes after 31 December 2026, but the site keeps running. The risk is unpatched vulnerabilities, and your host may move you to a newer PHP version on its own schedule.
Which PHP version should I move to?
WordPress recommends PHP 8.3 or greater, and its hosting handbook recommends 8.4 or later for production. PHP 8.4 receives security fixes until 31 December 2028.
Does updating WordPress also update PHP?
No. PHP runs on the server and is usually managed by your host; WordPress updates only change WordPress itself. Update both, testing on staging first.
Will my plugins break on PHP 8.3 or 8.4?
Maybe. Maintained plugins usually keep up, but older plugin code can throw exceptions or warnings, for example in date handling and dynamic properties. A staging test shows you before your visitors do.
Should I rebuild my site instead of upgrading?
Only if the site was already failing you: an unmaintained custom theme, abandoned plugins, or a site that is slow and hard to edit. Otherwise, upgrade.
Tell us what you are working with and we will come back with a plan.










