Contents
PHP 8.2 reaches the end of security support on December 31, 2026, and 8.1 ended a year earlier. A WordPress site should run on PHP 8.3 or 8.4 — newer versions are not only more secure, but noticeably faster. Changing the version is one click in your hosting control panel, but without checking plugin and theme compatibility, it can end in a white screen. Below: how to check what you're running, how to switch safely, and why it's worth doing now rather than waiting until your host does it for you.
The thesis: hosting providers are disabling old PHP versions en masse — and doing it without consulting you
How most Polish hosting providers operate: after support for a given PHP version ends, they give you a few months of grace period, send emails (which end up in spam or with a former contractor), and then switch all sites to a newer version automatically. A site with an incompatible plugin wakes up in the morning with a critical error.
The end of 2026 is when this will happen to sites on PHP 8.1 and 8.2 — which, from what we've seen, means most business websites that nobody has touched since launch.
PHP support deadlines
| Version | Release | End of security support | Status as of October 2026 |
|---|---|---|---|
| 7.4 | 2019 | December 2022 | Unsafe — minimum for WP 7, but no patches for 4 years |
| 8.0 | 2020 | November 2023 | Unsafe |
| 8.1 | 2021 | December 31, 2025 | Unsafe — no patches for 9 months |
| 8.2 | 2022 | December 31, 2026 | Final quarter — plan your migration |
| 8.3 | 2023 | December 31, 2027 | Recommended — mature, all plugins compatible |
| 8.4 | 2024 | December 31, 2028 | Recommended — fastest; check compatibility of older plugins |
| 8.5 | 2025 | 2029 | Latest — hold off on production until plugins catch up |
Source: php.net supported versions schedule. WordPress 7.x requires a minimum of 7.4 but recommends 8.2+; more context in our article on WordPress 7.
Step 1. Check what you're running
Three ways, starting with the simplest:
- WordPress dashboard: Tools → Site Health → Info → Server — the PHP version and a warning if it is outdated.
- Hosting panel: the "PHP" or "PHP Configuration" section — this is also where you'll change it.
- Site Health plugin will additionally show which plugins report incompatibility.
If you see 7.4, 8.0 or 8.1 — your site has no security patches. If it's 8.2 — you have a quarter left.
Step 2. Check compatibility
Before you change the version:
- WordPress: 6.6+ and 7.x run on 8.3/8.4 without issues.
- Plugins: in Plugins → Installed Plugins each one has a link to its repository page with the "Requires PHP" and "Tested up to" fields. A plugin that hasn't been updated in 2 years is a candidate for problems — and for replacement, regardless of PHP. Selection criteria in our plugin review.
- Theme: premium themes from before 2022 often use functions removed in PHP 8. Check the theme's changelog.
- Own code (snippets, child theme): the most common source of errors — deprecated functions (
create_function, dynamic properties, concatenationnull).
Tool: a PHP compatibility checker plugin scans your code and flags issues before the change.
Step 3. Make the change on staging
An order of steps that won't end in a white screen:
- Backup (always).
- Version change on a staging copy — we explain how to set one up in our article on staging.
- Test: front end, dashboard, forms, cart and checkout in a store, editor.
- Check the PHP logs — warnings don't block anything, but they point to code that needs fixing.
- Deploy to production outside peak traffic hours.
- Re-run the tests; if something goes wrong, roll back to the previous version with one click (the only "update" you can undo instantly).
What you gain beyond security
PHP 8.x delivers a real performance gain over 7.4 thanks to the JIT compiler and engine optimizations. In practice: shorter server-side page generation time (TTFB), which translates into a better LCP. Measurements from 7.4 → 8.3 migrations usually show a clear reduction in server response time with no other changes — the cheapest optimization you can make. More context in the article on Core Web Vitals.
White screens and errors — what to do
| The symptom | Cause | Solution |
|---|---|---|
| White screen / "critical error" | A plugin or theme uses a removed function | Roll back the PHP version, check the log, disable the culprit |
| Site works, admin panel doesn't | Incompatible admin plugin | Rename the plugin folder via FTP |
| "Deprecated" warnings on the site | Error display is turned on | Turn off WP_DEBUG_DISPLAY; fix the code when you have time |
| Form doesn't send | Incompatible email plugin | Update or replacement |
| Store: payment error | Payment gateway or checkout plugin | Update the gateway; test in sandbox |
A host that doesn't offer PHP 8.3
This is a sign to change your hosting, not just your PHP version. A provider without current PHP versions doesn't keep other parts of the server up to date either. Criteria in the hosting comparison.
From our experience
All the sites under our care moved to 8.3 in the first half of 2026, and stores did so after testing on staging with a test transaction. The most common problem isn't plugins from the repository, but custom code added by a previous developer in theme files, without a child theme.
With ongoing administration we plan, test, and carry out PHP version changes before your hosting does it on its own — with a backup and the option to roll back.
FAQ — PHP Version and WordPress
8.3 — mature, supported through the end of 2027, and compatible with almost all plugins. 8.4 is faster and supported for longer, but if you use older plugins, it's worth checking compatibility on staging first.
It can, if a plugin, theme, or custom code uses functions that were removed in the newer version. That's why the change should be made on a test copy. The upside is that rolling back to the previous version is just one click in your hosting control panel.
Your site will keep working, but without security patches — every newly discovered PHP vulnerability will remain open. Most hosting providers will disable 8.2 within a few months of the end of support, switching sites over automatically.
Author: Adrian Kamiński — Websky Studio, Poznań. WordPress site and store maintenance — we change PHP versions as planned, on staging, before the hosting provider does it for you.
Your feedback
Was this article helpful?
One click — it helps me choose future topics.

