Website creationPHP 8.5 WordPress

PHP 8.5 and WordPress: which PHP version to aim for on your site

PHP 8.5 and WordPress: which version to aim for on an SME site, what the update really brings, what can break and how to roll back.

Mehdi B.

Co-founder · SEO & digital strategy

PHP 8.5 and WordPress: which PHP version to aim for on your site
In brief

For a WordPress site, we now aim for PHP 8.5, or PHP 8.4 if an important extension does not yet keep up. WordPress has supported PHP 8.5 since version 6.9, and this branch will receive security fixes until the end of 2029. The first gain is security; the switch is tested on a copy of the site, with a rollback prepared.

For an SME’s WordPress site, our answer is fairly clear: today, we aim for PHP 8.5, or PHP 8.4 when an important extension has not yet caught up. The PHP 8.5 and WordPress pairing has been officially supported since WordPress 6.9, and the PHP 8.5 branch will receive security fixes until 31 December 2029. What you gain first is a site that stays covered the day a vulnerability is discovered, as the PHP2Shell case in October reminded many companies. Speed comes second, and it is measured on your own site rather than promised.

What remains is the part that rightly worries people: the update itself. The WordPress team tests its core on every PHP version it declares supported. Your theme, your extensions and the tweaks made over the years go through no such testing. That is therefore where we look first, and it is also where the rollback is prepared.

Which PHP version to aim for on a WordPress site today

Let’s start with the calendar, because it is public and predictable. According to php.net, each PHP branch is fully maintained for two years after its release, then receives two further years of fixes reserved for critical security vulnerabilities. After that, the branch reaches end of life and no more fixes are published.

For its part, WordPress keeps in its handbook a table showing, for each of its versions, the PHP branches with which the core is tested and compatible. Cross-referencing the two sources, here is where each branch stands as of 12 November 2026.

PHP version Security fixes WordPress support Our view for an SME site
7.4, 8.0, 8.1 Ended (end of 2022, end of 2023, end of 2025) 7.4 remains the required minimum To leave as a priority
8.2 Until 31 December 2026 Since WordPress 6.1 Switch before the end of the year
8.3 Until 31 December 2027 Since WordPress 6.4 Acceptable, move to plan in 2027
8.4 Until 31 December 2028 Since WordPress 6.7 Good choice if a key extension does not keep up with 8.5
8.5 Until 31 December 2029 Since WordPress 6.9 Our current target
8.6 Release scheduled for 19 November 2026 Core announced as compatible in WordPress 7.2, still in testing Wait for extensions to be validated

PHP 8.3 deserves a clarification. It still receives security fixes until the end of 2027, and it is in fact the minimum version recommended by WordPress.org. Its active support, however, ended on 31 December 2025: ordinary bugs are no longer fixed. A site on 8.3 is therefore not in danger, it is simply on the downward slope, and we prefer to organise the move calmly rather than in an emergency.

PHP 8.4 is in a similar situation, one year later. Its active support runs until 31 December 2026, after which it will receive only security fixes until the end of 2028. It is a sound base, but for the same effort, 8.5 gives you an extra year of peace of mind.

WordPress still accepts PHP 7.4: that is not a green light

Many business leaders reassure themselves with an argument that seems solid: “WordPress installs and runs, so our PHP version is fine.” Technically, that is true. Since WordPress 7.0, the core has dropped PHP 7.2 and 7.3, but it still requires at least PHP 7.4, and the WordPress.org requirements page confirms that it works with PHP 7.4 and above.

That same page nonetheless adds a sentence that is easy to read too quickly. These older versions have reached their official end of life and may expose your site to security vulnerabilities. In other words, WordPress keeps running on PHP 7.4 so as not to abandon older sites, not because that combination is advisable. The Site Health screen in the WordPress administration area also displays a warning when the PHP version is judged too old.

If your site starts from PHP 7.4, 8.0 or 8.1, this is no longer a simple update but a jump of several versions. We detailed the pitfalls specific to this jump in our article on migrating a PHP 7 application to PHP 8, and they also apply to a custom-built theme.

What PHP 8.5 really brings to a WordPress site

The first benefit is nothing spectacular: it is the length of support. When a serious vulnerability is discovered, like those fixed on 21 October 2026 in versions 8.2 to 8.5, a site on a maintained branch receives a fixed version. A site on an end-of-life branch, by contrast, is left with makeshift workarounds. That criterion alone justifies the update.

Performance, next, calls for a little honesty. The WordPress.org page on updating PHP says your site “may be faster”, because PHP becomes more efficient from one version to the next. The official PHP 8.5 release note also mentions better performance, but without any figures or benchmarks. You sometimes read that a new “predictive” JIT compiler would make pages 15% faster: nothing of the kind appears in the php.net announcements.

Our position is therefore simple. We do not sell a PHP update as a lever for speed or SEO. We measure the server response time (the delay before the browser receives the first byte) on the test copy, before and after the switch, with the same cache settings. If your site serves most of its pages from a cache, the difference will often be small on public pages and more visible in the administration area or in a shop’s basket.

As for the new features in PHP 8.5, they are aimed mainly at developers: an operator that chains functions, a built-in module for parsing web addresses, an attribute that flags when a function’s result is ignored. They serve the extensions that choose to use them. In themselves, they change nothing about what your visitors see.

The core, the theme and the extensions: who needs to keep up

The WordPress core is easy to check. The compatibility table shows, for example, that WordPress 6.8 is not supported with PHP 8.5, whereas versions 6.9, 7.0 and 7.1 are. A site that stayed on 6.8 must therefore first update WordPress, and only then change PHP version. The latest maintenance releases, published on 28 October 2026, are WordPress 7.1.4 and 7.0.8.

Extensions are trickier, for a reason few people know. An extension’s page in the WordPress.org directory gives two pieces of information: “Requires PHP”, the minimum PHP version it needs, and “Tested up to”, the latest WordPress version on which its author has tested it. Neither says whether the extension works with PHP 8.5. To find out, you have to read the publisher’s changelog, ask them, or test it yourself.

The theme, finally, is often where surprises lie dormant. A commercial theme that is updated regularly generally keeps pace with PHP’s evolution. A child theme tweaked six years ago, with functions added by hand in its functions.php file, has on the other hand not been reviewed by anyone since. It is the first thing we open.

The WordPress documentation gives a practical criterion for extensions: look at the date of their last update and replace abandoned ones with a maintained alternative. An extension that has not moved for several years is rarely a problem on the day of the switch. It becomes a problem the day PHP removes a function it was still using.

PHP 8.5 WordPress: how the update works

Take an accounting firm in Lausanne with about ten people. Its WordPress site presents its services, receives enquiries through a contact form and offers appointment booking through an extension. It runs on PHP 8.2, which leaves barely seven weeks before fixes end.

  1. Back up. The files and the database are copied, and we check that the backup can actually be restored, not just that it exists.
  2. Update on the old PHP version. WordPress, the theme and the extensions move to their latest version while the site is still running on 8.2. This is the order recommended by the WordPress documentation, and it avoids mixing two causes of failure.
  3. Switch the test copy to PHP 8.5. We run through the journeys that matter to the business: a request sent through the form must reach the right mailbox, an appointment must be recorded in the calendar. We read the server’s error log in parallel.
  4. Switch the live site. PHP runs on the server, not in WordPress: the change is made at the host, through a menu in the customer area or by a request to support, depending on the case.
  5. Check and monitor. The same journeys are run again on the live site, then the error log is monitored for a few days.

For an online shop or a site connected to other tools, the testing phase requires more method: a representative copy, payments in test mode, emails redirected to internal addresses. We described it in detail in our article on compatibility testing before WordPress 7.2 and PHP 8.6, and the method is the same for PHP 8.5.

What can break, and what you will see on screen

PHP 8.5 does not turn old warnings into blocking errors. It mainly adds deprecations, that is, messages announcing that a way of writing code will disappear in a future version. The release note lists several: certain old ways of writing type casts, the use of null as an array key, and an operator that served as a shortcut for running system commands. These messages do not block the site, but they fill the error log and point to the code that will need fixing before the next versions.

The real breakage comes from elsewhere. It happens when an extension or a theme calls a function that no longer exists, or depends on behaviour that PHP changed between two versions. The result is a fatal error, and the page no longer displays.

WordPress has provided for this case since version 5.2. Instead of a blank page, your visitors see a generic error message, and an email is sent to the site administrator’s address. This email contains a link to a recovery mode that pauses the faulty extension or theme, for that browser only, so that you can get into the administration area. The WordPress team states it clearly: this mode fixes nothing, it only gives access to the dashboard so that the faulty item can be disabled or corrected.

A practical detail follows. Check that the administrator’s address, in WordPress’s general settings, is a mailbox that someone still reads. If it belongs to a former employee or a former contractor, the alert will go nowhere.

Plan the rollback before switching

The rollback is prepared before the switch, never during it. In most cases it is even very simple: the WordPress documentation points out that you can go back to the previous PHP version from the hosting, or ask the host to do it. If nothing else has changed in the meantime, the site then returns to how it worked before.

A backup needs to be restored only if files or the database have been modified in the meantime. In that case, the order matters: first put the old PHP version back, then restore the backup. For an online shop, beware of orders placed since the switch, which an overly broad restore would erase.

Before the intervention, three points must therefore be settled with you. Who has access to the hosting, what triggers a rollback (a contact request that no longer arrives is enough, in our view), and who makes the decision. A rollback is not a failure: it is the safety net that allows the update to be done calmly, and the faulty extension to be fixed at leisure afterwards.

PHP 8.6 is released on 19 November: should you wait for it?

The question comes up often at the moment, and our answer is no. According to php.net, the final version of PHP 8.6 is scheduled for 19 November 2026, and the latest test release, published on 5 November, still carries a warning not to use it in production. On the WordPress side, version 7.2 is scheduled for 8 December 2026; its fifth test release states that all known core problems with PHP 8.6 are resolved, while reminding users that extensions and the theme must be checked before any update.

So waiting for PHP 8.6 to leave PHP 8.2 would be a scheduling mistake. Nothing says your plugins will have confirmed compatibility with 8.6 by then, while PHP 8.2 stops receiving fixes on 31 December. Moving to 8.5 now is not wasted effort: that branch is supported until the end of 2029, which leaves plenty of time to prepare for 8.6 in 2027, once the ecosystem has settled.

That is the pace we recommend for the WordPress sites we build in our web design projects: roughly one PHP version upgrade a year, tested on a copy, with a rollback ready. If you do not know which version your site runs on, or if a plugin gives you pause, let us talk it through in a first conversation.

Sources

PHPWordPressMaintenance
Mehdi B.
About the authorMehdi B.

Co-founder of Smart Impact. Hooked on the web from the start, he launched his first project in 2006: an online music magazine still running today. With close to 20 years of SEO experience, a Swiss federal diploma in marketing and a solid geek streak, he turns clients' ideas, sometimes hazy ones, into concrete digital projects with his team.

LinkedIn
Further reading