PHP 8.2 stops receiving security fixes on December 31, 2026. Learn how to check your WordPress site's PHP version, why PHP 8.4 is the sensible target, what usually breaks, and how to upgrade safely.
Sooner or later, an email from your hosting provider will mention "PHP 8.2 end of life" and ask you to take action.
Most business owners don't know what PHP is, let alone which version their website runs on. That's fine. You only need to know whether you're affected and what to ask for.
This guide is for WordPress and WooCommerce sites. Magento owners have a short section further down, because the answer is different.
The Short Version
- PHP is the software that runs WordPress and WooCommerce on your server.
- PHP 8.2 stops receiving security fixes on December 31, 2026. After that, new security problems found in it are not fixed.
- Your website will not switch off on January 1. But your host may set an earlier deadline and move you to a newer version.
- For most WordPress sites, PHP 8.4 is the sensible target. PHP 8.3 works too, but its security fixes end a year earlier.
PHP Support Dates at a Glance
Each PHP version gets two years of active support, then two years of security fixes, then nothing.
| PHP version | Security fixes end | Status in October 2026 |
|---|---|---|
| PHP 8.1 | December 31, 2025 | End of life, move now |
| PHP 8.2 | December 31, 2026 | Security fixes only, ends in under three months |
| PHP 8.3 | December 31, 2027 | Security fixes only |
| PHP 8.4 | December 31, 2028 | Active support |
| PHP 8.5 | December 31, 2029 | Active support, newest release |
On PHP 7.x or 8.0? It has been unsupported for years. Treat the upgrade as urgent, not a December task.
Check Your Website in Two Minutes
On WordPress: go to Tools → Site Health → Info and open the Server section, which lists your PHP version.
On any website: log in to your hosting control panel (cPanel, Plesk or your host's dashboard) and look for "PHP version" or "PHP selector".
What Actually Happens After December 31
Three things change. None takes your site down immediately.
Security gaps stop being fixed. Attackers scan for websites running outdated software. When a new PHP vulnerability is found, supported versions get a patch and PHP 8.2 doesn't. If you take card payments, expect your PCI compliance assessment to ask about this.
Your host sets its own timeline. Some hosts act months early. Acquia, for example, ended PHP 8.2 support on October 1, 2026, and automatically moved its remaining PHP 8.2 sites to PHP 8.4. If that happens before you have tested, an incompatible plugin can break pages overnight.
Plugins move on. Developers test against supported PHP versions, so over time their updates stop working on older ones.
Which Version Should You Move To?
PHP 8.4, for most WordPress sites. It receives security fixes until the end of 2028, so you won't be repeating this next year.
- Why not 8.3? It works, and WordPress.org's recommended minimum is "8.3 or greater". But its security fixes end in December 2027, so you would be doing this again in twelve months.
- What about 8.5? It's supported longest, until the end of 2029, and WordPress 6.9 or newer is compatible with it. But not every host offers it yet (Acquia's newest is 8.4), and plugins have had less time on it. Choose it if your host offers it and your plugins are confirmed ready.
WordPress compatibility: WordPress 6.8 or newer is listed as compatible with PHP 8.4, and 6.9 or newer with PHP 8.5. If WordPress is up to date, you're covered. Your plugins and theme still need checking separately.
What Usually Breaks
Current WordPress releases are compatible with PHP 8.4. In our experience, problems come from what's around WordPress:
- Abandoned plugins: check the "Last updated" date on each plugin. As a rule of thumb, anything untouched for two years or more deserves a closer look.
- Old or heavily modified themes: especially ones bought years ago and no longer updated.
- Custom code: snippets in
functions.php, custom plugins, or integrations a past developer built. - Plugins with expired licences: you can't update them, so they stay on old code.
Typical symptoms: a "There has been a critical error on this website" message, a blank page, a broken contact form, or a checkout that fails silently.
Moving from 8.2 to 8.4 is usually a smaller jump than the PHP 7 to 8 upgrade many sites struggled with. But small is not zero.
How to Upgrade a WordPress Site Safely
- Take a full backup of files and database, and confirm you can restore it.
- Update WordPress, plugins and themes while still on your current PHP version.
- Create a staging copy of the site. Most hosts offer this in one click.
- Switch staging to PHP 8.4 and test the pages that make you money: contact forms, checkout, payments, login and search.
- Replace or fix anything that fails. For an abandoned plugin, this usually means finding a maintained alternative.
- Switch the live site during a quiet period, then watch your error logs and form submissions for 48 hours.
Done this way, it's routine maintenance, not an emergency.
Running Magento or Adobe Commerce?
Don't apply the advice above to a Magento store. Its PHP version is tied to the Magento version, and Adobe supports only these combinations:
| Magento / Adobe Commerce | Supported PHP |
|---|---|
| 2.4.6 | 8.2 or 8.1 |
| 2.4.7 | 8.3 or 8.2 |
| 2.4.8 | 8.4 or 8.3 |
| 2.4.9 | 8.5 |
So a 2.4.6 store can't simply switch to PHP 8.4. Leaving PHP 8.2 means upgrading Magento itself. Adobe warns that 2.4.6 stores on PHP 8.2 put their PCI compliance at risk from the end of 2026, and advises planning the move before then. Our guide on Magento 2.4.6 end of support covers the dates and options.
What to Ask Your Developer or Host
Copy these into an email:
- Which PHP version is our website running on right now?
- Are WordPress, our theme and all plugins compatible with PHP 8.4?
- Will you test the upgrade on a staging copy before changing the live site?
- Are you planning to change our PHP version automatically? If so, when?
- If something breaks after the switch, how quickly can we roll back?
If nobody can answer the first question, your website is probably not being actively maintained.
When a PHP Upgrade Becomes a Bigger Decision
Sometimes the check reveals more than a few plugin updates: a theme nobody can safely edit, key features built on abandoned plugins, or custom code nobody understands.
At that point, patching may cost more than it saves. Our guide on redesign vs rebuild vs migration helps you decide. If you're considering leaving WordPress, see WordPress vs Next.js for business websites.
For most sites, a careful PHP upgrade is all that's needed.
FAQs
Will my website stop working on January 1, 2027?
No. PHP 8.2 keeps running, but security problems found after that date won't be fixed. The real risks are an untested switch by your host, and a vulnerability that never gets patched.
Will upgrading PHP make my website faster?
Sometimes. Newer PHP versions can be faster, but it depends on your theme, plugins and hosting. Treat the upgrade as a security task and any speed gain as a bonus. If your site is slow, PHP is rarely the main cause. See why a website can feel slow despite a good PageSpeed score.
Can I upgrade PHP myself?
On many hosts it's a dropdown in the control panel. The switch is easy; the testing is what matters. Test on staging first.
My host says it will upgrade PHP for me. Do I need to do anything?
Yes. Ask when, and test your site on the new version before that date. Your host upgrades the server, not your plugins.
Does this affect Shopify or Next.js websites?
Shopify is fully hosted, so there's no PHP for you to manage. A Next.js frontend doesn't run on PHP, but a headless WordPress backend behind it still does.