Title: PHP 8 support clarification
Author: John Blackbourn
Published: April 9, 2025
Last modified: July 8, 2025

---

 [  ](https://profiles.wordpress.org/johnbillion/) [John Blackbourn](https://profiles.wordpress.org/johnbillion/)
9:14 am _on_ April 9, 2025     
Tags: [PHP ( 79 )](https://make.wordpress.org/core/tag/php/),
[PHP 8.0 ( 6 )](https://make.wordpress.org/core/tag/php-8-0/), [php-compatibility ( 6 )](https://make.wordpress.org/core/tag/php-compatibility/)

# PHP 8 support clarification

**tl;dr:** Use of the “compatible with exceptions” label for PHPPHP The web scripting
language in which WordPress is primarily architected. WordPress requires PHP 7.4
or higher 8 support has been retired and has been retroactively removed from all
versions.

 * WordPress 6.3 and later is now documented as fully supporting PHP 8.0 and 8.1
 * WordPress 6.6 and later is now documented as fully supporting PHP 8.2
 * WordPress 6.8 and later is now documented as fully supporting PHP 8.3
 * Support for PHP 8.4 remains in betaBeta A pre-release of software that is given
   out to a large group of users to trial under real conditions. Beta versions have
   gone through alpha testing in-house and are generally fairly close in look, feel
   and function to the final product; however, design changes often occur as part
   of the process. as of WordPress 6.8

[WordPress has supported PHP 8 since version 5.6 back in 2020](https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/),
but due to the acknowledgement that WordPress is rarely used in isolation (without
any theme or plugins) this support has been labelled as “beta support”, and later
as “compatible with exceptions” following the guidelines that were adopted as a 
result of [the proposal for criteria for removing the “beta support” label from each PHP 8+ version](https://make.wordpress.org/core/2023/06/20/proposal-criteria-for-removing-beta-support-from-each-php-8-version/).

In order to provide clarity and confidence to users and to encourage web hosts and
users to continue updating to the latest versions of PHP, use of the “compatible
with exceptions” label has now been retired. Documented support for any given version
of PHP will now go straight from “beta support” to fully supported once the agreed
criteria for removing that label have been met. The label has been removed retroactively
from all versions.

[PHP compatibility of all WordPress versions is documented here in the handbook and has been updated to reflect this change](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/).

## What prompted this change?

The criteria for removing the “beta support” label were adopted in 2023 just prior
to the release of WordPress version 6.3. In that version a significant amount of
work was done to resolve remaining PHP compatibility issues and to switch to using
the “compatible with exceptions” label for PHP 8.0 and 8.1. The same was done in
WordPress 6.6 for PHP 8.2, and the number and significance of these documented compatibility
exceptions is now very low.

Since then it’s become apparent that some end users and web hosts remain reluctant
to update to PHP 8 when the documented support in WordPress is still labelled as“
compatible with exceptions”, despite the actual support being complete as far as
most sites are concerned (over 60% of WordPress sites run PHP 8+). The label has
served its purpose over the last 18 months but now risks being detrimental to the
continued adoption of newer versions of PHP.

Removing this label — while still documenting the exceptions where necessary — will
help continue the adoption of newer and fully supported versions of PHP and provide
confidence to the remaining 40% of sites to update.

## What are the criteria for removing the “beta support” label?

These criteria have not changed. The criteria are:

 * Enough sites: At least 10% of all WordPress sites running on a specific or newer
   PHP version for at least 3 months.
 * Issues:
    - All reported and known compatibility issues are resolved.
    - All accepted incompatibilities are documented as exceptions from full compatibility.
 * BC: Full backward compatibility is maintained for all older PHP versions WordPress
   supports, demonstrated with automated tests for each compatibility change.

[Usage of PHP 8.3 and higher is at 8.9% of all WordPress sites as of April 2025](https://wordpress.org/about/stats/).
Once this surpasses 10% and assuming no further compatibility issues are reported
then it’s expected that the beta label for PHP 8.3 support will be removed in the
subsequent major releasemajor release A release, identified by the first two numbers(
3.6), which is the focus of a full release cycle and feature development. WordPress
uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are 
sequential and comparable in scope. of WordPress.

## What’s the minimum supported version?

The minimum supported version of PHP remains unchanged at 7.2.24+.

Props to [@desrosj](https://profiles.wordpress.org/desrosj/) [@joemcgill](https://profiles.wordpress.org/joemcgill/)
[@garyj](https://profiles.wordpress.org/garyj/) for input on this change.

[#php](https://make.wordpress.org/core/tag/php/), [#php-8-0](https://make.wordpress.org/core/tag/php-8-0/),
[#php-compatibility](https://make.wordpress.org/core/tag/php-compatibility/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/8cf7655071f82970f9635a0c7e7646551756c333b57166083e506a72cad98916?
     s=32&d=mm&r=g)
 2.   [David Anderson / Team Updraft](https://profiles.wordpress.org/davidanderson/)
     9:20 pm _on_ April 9, 2025
 3.  Tying the meaning of “betaBeta A pre-release of software that is given out to 
     a large group of users to trial under real conditions. Beta versions have gone
     through alpha testing in-house and are generally fairly close in look, feel and
     function to the final product; however, design changes often occur as part of 
     the process.” to level of adoption in production means that in the WP world, the
     word has its own special meaning, one different to elsewhere.
      As such, one could
     arbitrarily use any word(s). “This release has ‘chicken rodent’ status, where ‘
     chicken rodent’ means….. “
 4.  ![](https://secure.gravatar.com/avatar/de9c3b9a551aebaa1a0841c34bcaa3efe5158705e88460703652070992fbd089?
     s=32&d=mm&r=g)
 5.   [Sander](https://profiles.wordpress.org/zanderz/)  7:37 am _on_ April 10, 2025
 6.  > Since then it’s become apparent that some end users and web hosts remain reluctant
     > to update to PHPPHP The web scripting language in which WordPress is primarily
     > architected. WordPress requires PHP 7.4 or higher 8 when the documented support
     > in WordPress is still labelled as “compatible with exceptions” […]
 7.  > Usage of PHP 8.3 and higher is at 8.9% of all WordPress sites as of April 2025.
     > Once this surpasses 10% and assuming no further compatibility issues are reported
     > then it’s expected that the betaBeta A pre-release of software that is given
     > out to a large group of users to trial under real conditions. Beta versions 
     > have gone through alpha testing in-house and are generally fairly close in look,
     > feel and function to the final product; however, design changes often occur 
     > as part of the process. label for PHP 8.3 support will be removed in the subsequent
     > major releasemajor release A release, identified by the first two numbers (3.6),
     > which is the focus of a full release cycle and feature development. WordPress
     > uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 
     > are sequential and comparable in scope. of WordPress.
 8.  You’re still having a chicken and egg problem here. You’re saying web hosts/users
     are reluctant to upgrade, but then say the beta label is tied to how often it’s
     used. That will still keep people from updating their PHP version because they
     don’t want to run “beta software”.
 9.  ![](https://secure.gravatar.com/avatar/b61d1e43c6269b8e58bb223906660e6052029acc4efd5735ad5ec5a8f1197e98?
     s=32&d=mm&r=g)
 10.  [Maxime Jobin](https://profiles.wordpress.org/maximejobin/)  1:25 pm _on_ April
     10, 2025
 11. First, I want to say this is a good news to change the way versions were labeled.
     There is a difference between “it is not compatible” meaning it will crash versus“
     it might not totally support all new features. I’m more interested to know if 
     it will break a website versus will I be able to use all the new feature!
 12. > You’re still having a chicken and egg problem here. You’re saying web hosts/
     > users are reluctant to upgrade, but then say the betaBeta A pre-release of software
     > that is given out to a large group of users to trial under real conditions. 
     > Beta versions have gone through alpha testing in-house and are generally fairly
     > close in look, feel and function to the final product; however, design changes
     > often occur as part of the process. label is tied to how often it’s used. That
     > will still keep people from updating their PHPPHP The web scripting language
     > in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher
     > version because they don’t want to run “beta software”.
 13. I have to agree with [@zanderz](https://profiles.wordpress.org/zanderz/) (Sander)
     here. Could there be an alternative? Why updating WordPress’ code based on PHP
     release notes wouldn’t be enough to claim it is compatible and then adjust once
     launched? Maybe the beta and RCrelease candidate One of the final stages in the
     version release cycle, this version signals the potential to be a final release
     to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?output_format=md#alpha-beta).
     cycles are just too tight to have enough time for testers to do what should be
     done!?
 14. As we all know, all software come with incompatibilities and bugs. So no matter
     the effort, there will be problems. What I want to know is : are there known problems
     that will make the version update break my website?
 15. Again, that is good news! So thanks for that!
 16.  * ![](https://secure.gravatar.com/avatar/51f55d5974ff861cb88d8b52880f8c15b7f37150ccbad2f47352878a2c9dc2d1?
        s=32&d=mm&r=g)
      *  [John Blackbourn](https://profiles.wordpress.org/johnbillion/)  7:12 pm _on_
        April 10, 2025
      * [@maximejobin](https://profiles.wordpress.org/maximejobin/) [@zanderz](https://profiles.wordpress.org/zanderz/)
        I’m not particularly keen on the term “betaBeta A pre-release of software that
        is given out to a large group of users to trial under real conditions. Beta
        versions have gone through alpha testing in-house and are generally fairly 
        close in look, feel and function to the final product; however, design changes
        often occur as part of the process. compatible” either, but changing that was
        outside the scope of this change. I will see if there is any interest in changing
        that labelling during the 6.9 release cycle.
         - ![](https://secure.gravatar.com/avatar/d521b97a8e258da8fd25a336d5782fda8fbba00e7df792f789c06d708e5edbde?
           s=32&d=mm&r=g)
         -  [David Marín Carreño](https://profiles.wordpress.org/davefx/)  9:02 am 
           _on_ April 16, 2025
         - I think that it would be better to say if a given PHPPHP The web scripting
           language in which WordPress is primarily architected. WordPress requires
           PHP 7.4 or higher version is supported or not.
         - A supported PHP version would mean that it has been tested and there are
           not any known problems happening or warnings generated when running WP on
           it, and if users should expect that any problem that may appear when running
           WP on that PHP version will be fixed ASAP.
         - This is GPLGPL GNU General Public License. Also see [copyright license](https://make.wordpress.org/core/2025/04/09/php-8-support-clarification/?output_format=md#copyright-license).
           software, so we shouldn’t expect any warranties. It would be more than OK
           to know, at least, if the effort to make adaptations to a given PHP version
           have been completed and users shouldn’t expect sites down, or clogged warning
           logs, when upgrading.

Comments are closed.

# Post navigation

[← Performance Chat Summary: 8 April 2025](https://make.wordpress.org/core/2025/04/08/performance-chat-summary-25-february-2025-2/)

[Agenda, Dev Chat, Apr 9, 2025 →](https://make.wordpress.org/core/2025/04/09/agenda-dev-chat-apr-9-2025/)