PHP 8.2 Reaches End of Life on 31 December: Check Your Website Now
PHP is the language that powers most small business websites built on WordPress and many other content systems. Version 8.2 stops receiving security fixes on 31 December 2026, according to the official PHP supported versions page. Your site will not switch off on New Year's Day, but any new security hole found in 8.2 after that date will not be patched by the PHP project. If your site still runs on 8.2 or anything older, the next six weeks are a sensible window to move it.
What the dates actually say
Each PHP branch gets two years of active support, with bug fixes and security fixes, followed by a further period of security-only fixes. As of November 2026, the PHP project lists these dates:
- PHP 8.2: security support until 31 December 2026.
- PHP 8.3: active support ended 31 December 2025; security support until 31 December 2027.
- PHP 8.4: active support until 31 December 2026; security support until 31 December 2028.
- PHP 8.5: active support until 31 December 2027; security support until 31 December 2029.
PHP 8.1 and earlier are already outside support. If your site is on one of those, this is overdue rather than upcoming.
WordPress, for its part, currently recommends PHP 8.3 or greater. It notes that older versions can still run WordPress but have reached end of life and may expose a site to vulnerabilities.
Finding out which version you are on
You do not need to be technical to check this. Try these in order:
- WordPress Site Health. In the dashboard, go to Tools, then Site Health, then the Info tab, and open the Server section. It shows the PHP version in plain text. Site Health will also flag an outdated version on its Status tab.
- Your hosting control panel. Most UK hosts using cPanel, Plesk or their own panel have a "PHP version" or "PHP selector" screen for each domain.
- Ask the host. A support ticket asking "which PHP version is example.co.uk running, and which versions can I switch to?" usually gets an answer within a day.
If someone else built and looks after the site, ask them the same question, and ask when they plan to move it. It is a fair thing to raise even if you are not on a maintenance contract.
Which version to move to
Skipping straight to the newest version is tempting, but compatibility matters more than novelty. For most small sites the sensible target in late 2026 is 8.3 or 8.4. Version 8.4 buys an extra year of security support over 8.3, so if your theme and plugins work on it, it saves you repeating this exercise in twelve months. Version 8.5 is the newest and the longest-supported, but older plugins are the most likely to trip over it.
The deciding factor is rarely WordPress itself. It is the theme, page builder and the handful of plugins that make your site do something specific, such as a booking form or a product filter. A plugin that has not been updated for two years is the one most likely to fail.
A safe way to do the switch
Before
- Take a full backup of files and database, and make sure you know how to restore it. Many hosts offer one-click restore points; check it exists before you rely on it.
- Update WordPress core, the theme and all plugins to their latest versions while still on the old PHP. Developers fix compatibility issues in updates, so this solves most problems in advance.
- List plugins that have not been updated in more than a year. Look for alternatives or ask your developer whether they are still needed.
- If your host offers a staging site, copy the live site to staging and test the new PHP version there first.
During
- Choose a quiet time. For most local businesses that is a weekday evening, not Friday afternoon.
- Change the PHP version in the host's panel. It usually takes effect within a minute.
After
Walk through the site as a customer would. Load the home page, a service page and a blog post. Submit the contact form and confirm the email arrives. If you sell online, add something to the basket and go as far as the payment page. Log in to the admin area and open the editor. If anything shows a white screen or an error, switch PHP back to the previous version in the panel and the site should recover while you investigate.
A form that quietly stops sending messages is the failure people miss most often. It is worth re-reading our guest contributor's notes on form errors that explain the next step while you test, because a broken form after an upgrade is exactly when good error messages earn their keep.
What if the host will not move?
Some budget and legacy hosting plans are slow to offer new PHP versions. If yours only offers 8.2 or older and has no plan to change, that is a strong signal to move host. A site on unsupported software is harder to defend if it is compromised and customer data is involved. Moving a small WordPress site between hosts is routine work, and many UK hosts include a free migration.
Why it is worth the hour
Running a supported PHP version is one of the cheapest bits of security housekeeping available. Newer versions are often faster too, which helps visitors on mobile data. As we said in what makes a small business website work, a site has a job to do, and it cannot do that job while it is offline or defaced. Put a reminder in the calendar for each December so the next deadline does not arrive by surprise.