SnowDriven Research · Data
End-of-life PHP on WordPress, tracked daily.
As of 28 October 2026, 33.5% of WordPress sites that report to WordPress.org run a PHP version that no longer gets security fixes from the PHP project. On the same figures, it would be 56.6% if PHP 8.2, whose security support ends on 31 December 2026, had already reached end of life.
- Snapshot
- 28 Oct 2026
- End of life
- 33.5%
- PHP 8.2
- 23.1%
- Snapshots
- 17 since 12 Oct 2026
- Gaps
- 0
- Source
- WordPress.org
The latest snapshot
WordPress.org’s figures for 28 October 2026, by PHP support status on that day.
33.5%
of WordPress sites that report to WordPress.org run a PHP version the PHP project no longer patches.
56.6% on the same figures, if PHP 8.2 had already reached end of life. Its security support ends on 31 December 2026.
- 33.5%End of life, no PHP project fixes
- 23.1%PHP 8.2, security fixes until 31 Dec 2026
- 43.4%PHP 8.3 to 8.5, supported
- Latest snapshot
- 28 October 2026
- On end-of-life PHP
- 33.5%
- On PHP 8.2
- 23.1%
- On supported versions
- 66.5%
- Daily snapshots
- 17
- First day
- 12 October 2026
- Gaps
- None
- Source
- WordPress.org PHP version statistics, support dates from php.net (checked 11 October 2026).
Quote this finding
“As of 28 October 2026, 33.5% of WordPress sites that report to WordPress.org run a PHP version that no longer gets security fixes from the PHP project. On the same figures, it would be 56.6% if PHP 8.2, whose security support ends on 31 December 2026, had already reached end of life.” Source: SnowDriven analysis of WordPress.org PHP version statistics, https://snowdriven.com/research/wordpress-php/
One click or tap selects it all. The figure is for 28 October 2026; it changes with each daily snapshot.
By PHP version
Every branch in the 28 Oct 2026 snapshot, oldest first, with its support status that day from php.net.
| PHP version | Share | Support on 28 Oct 2026 |
|---|---|---|
| 4.4 | 0.0% | End of lifeNo security fixes from the PHP project |
| 5.1 | 0.0% | End of lifeNo security fixes from the PHP project |
| 5.2 | 0.1% | End of lifeNo security fixes from the PHP project |
| 5.3 | 0.3% | End of lifeNo security fixes from the PHP project |
| 5.4 | 0.2% | End of lifeNo security fixes from the PHP project |
| 5.5 | 0.1% | End of lifeNo security fixes from the PHP project |
| 5.6 | 1.3% | End of lifeNo security fixes from the PHP project |
| 7.0 | 0.5% | End of lifeNo security fixes from the PHP project |
| 7.1 | 0.3% | End of lifeNo security fixes from the PHP project |
| 7.2 | 1.3% | End of lifeNo security fixes from the PHP project |
| 7.3 | 1.3% | End of lifeNo security fixes from the PHP project |
| 7.4 | 15.0% | End of lifeNo security fixes from the PHP project |
| 8.0 | 3.5% | End of lifeNo security fixes from the PHP project |
| 8.1 | 9.5% | End of lifeNo security fixes from the PHP project |
| 8.2 | 23.1% | Security fixes until 31 Dec 2026Bug fixes have ended |
| 8.3 | 27.4% | Security fixes until 31 Dec 2027Bug fixes have ended |
| 8.4 | 10.2% | Supported until 31 Dec 2028Bug fixes until 31 Dec 2026 |
| 8.5 | 5.8% | Supported until 31 Dec 2029Bug fixes until 31 Dec 2027 |
| 8.6 | 0.0% | Not listed by php.netNewer than any branch php.net lists; counted in neither share |
Shares are as WordPress.org published them, to three decimals, here rounded to one. They may not add up to exactly 100%. End of life: php.net lists the branch as end of life, so the PHP project no longer ships security fixes for it. Dates from php.net’s supported versions, checked 11 October 2026.
Day by day
Collected daily since 12 October 2026. One mark per stored day; a missing day stays missing.
- End-of-life PHP
- PHP 8.2
The data behind the chart (17 days)
| Day (UTC) | End-of-life PHP | PHP 8.2 |
|---|---|---|
| 33.5% | 23.1% | |
| 33.6% | 23.2% | |
| 33.8% | 23.2% | |
| 34.0% | 23.3% | |
| 34.2% | 23.3% | |
| 34.7% | 23.5% | |
| 35.8% | 23.7% | |
| 36.4% | 23.8% | |
| 36.5% | 23.9% | |
| 36.5% | 23.9% | |
| 36.6% | 23.9% | |
| 36.6% | 23.9% | |
| 36.7% | 24.0% | |
| 36.7% | 24.0% | |
| 36.8% | 24.0% | |
| 36.9% | 24.0% | |
| 36.9% | 24.1% |
Method and limits
A daily record of public figures, with its limits stated.
Whose figures these are. These are WordPress.org’s published PHP version statistics, saved once a day and summarized by us. We don’t control or audit them. They cover only WordPress sites that report to WordPress.org, can change or stop without notice, and say nothing about sites that get security fixes from their host or Linux distribution. Information only, provided as is (terms). SnowDriven isn’t affiliated with or endorsed by WordPress.org or the WordPress Foundation (trademarks).
What is counted
Once a day, at about 07:17 UTC, we save WordPress.org PHP version statistics as published: the share of WordPress installs on each PHP version, among sites that report it when they check for updates.
What isn’t
Sites that never contact WordPress.org. WordPress.org doesn’t document how it samples or rounds, and publishes no site count, so these are shares of reporting installs, not of all websites, and not a scan or a survey of the web.
How support is judged
Each day’s shares are classed with php.net’s dates on that day: branches older than 8.2 get no security fixes from the PHP project; 8.2 gets them through 31 December 2026. A branch newer than php.net lists is counted in neither figure. Some hosts and Linux distributions backport security fixes to older PHP versions. WordPress.org’s figures can’t show which sites have that, so these shares measure support from the PHP project only.
Missing days
A day whose fetch failed or looked wrong has no snapshot. It is listed as a gap and never filled in, copied forward or estimated. WordPress.org publishes only the current figures, so there is nothing before the first day.
Download the data
Free, with no account, and updated with each snapshot.
PHP versions on WordPress sites, daily. One snapshot a day of WordPress.org PHP version statistics: the share of reporting WordPress installs on each PHP branch, with the share on branches the PHP project no longer patched that day and the share on PHP 8.2, using php.net’s support dates. Collected daily since 12 October 2026; days without a snapshot are listed as gaps and never filled in.
- DataJSON
Every snapshot as JSON
Each day’s shares by branch as WordPress.org published them, the derived shares, the gaps, the method and php.net’s dates.
- DataCSV
The daily series as CSV
One row per stored day: the derived shares, then one column per PHP branch. A branch missing from a day’s figures is left empty.
- Terms
Reuse and attribution
Our derived shares and the daily series are free to download and quote, with credit to SnowDriven and WordPress.org and a link; WordPress.org’s own shares stay under its terms. Ask us before republishing the files in bulk: hello@snowdriven.com. See our terms of use.
If your site runs PHP 8.2 or older
Check the version first; it takes a minute and needs no tools.
Check
In WordPress, open Tools → Site Health → Info and the Server section: it lists the PHP version. Your hosting panel shows it too.
Aim for PHP 8.4
WordPress recommends PHP 8.3 or greater, and WooCommerce lists 8.4 as the newest it is tested with. Back up the site and test on a staging copy before switching the live site.
Read the guide
Our PHP 8.2 end-of-life guide covers the dates, the WordPress and WooCommerce steps, and custom Laravel, Symfony or plain PHP apps.
Or hand it over
We upgrade WordPress sites and WooCommerce stores on staging first, and for a custom PHP app start with a modernization audit.
About this page
Cite this page
SnowDriven. “End-of-life PHP on WordPress, tracked daily.” SnowDriven Research. https://snowdriven.com/research/wordpress-php/ (last updated 28 October 2026).
One click or tap selects the whole citation, ready to copy.
About these figures
The shares are WordPress.org’s, saved once a day, and the support dates are php.net’s, checked on the day shown. Either can change without notice, and our copy can fall behind or contain mistakes, so confirm with the source before you rely on a figure. Information only, provided as is (terms). Reuse: free to download and quote, with credit to SnowDriven and WordPress.org and a link (terms of use).
Start a project
Running WordPress or WooCommerce on PHP 8.2 or older?
We move sites and stores to a supported PHP on a staging copy first, fix or replace what won’t run, and switch with a way back. Tell us about the site; we’ll come back with questions or a time to talk.
Pittsburgh, PA · Since 2015 · First step: a 30-minute call