Skip to content
PHP Version Checker
PHP lifecycle data

PHP End of Life and Supported Versions

PHP branches move from active support to security-only fixes, then to end of life. This table shows where every branch stands today, so you can plan an upgrade before official support runs out.

Source: endoflife.date · Checked Oct 22, 2026
Check a websitePHP2Shell advisory
Active support

2

Branches receiving bug and security fixes

Security fixes only

2

Branches receiving security updates only

End of life

14

Branches with no official updates

Support schedule

PHP versions and security support dates

Each row is a PHP branch. Active support covers bugs and security fixes. Security support covers security issues only. End of life means the branch no longer receives official updates.

Swipe horizontally to see all columns.

PHP branches, release dates, support end dates, latest releases, and current status
BranchReleasedActive support endsSecurity support endsLatest releaseStatus
8.5Nov 20, 2025Dec 31, 2027Dec 31, 20298.5.12Active support
8.4Nov 21, 2024Dec 31, 2026Dec 31, 20288.4.27Active support
8.3Nov 23, 2023Dec 31, 2025Dec 31, 20278.3.36Security fixes only
8.2Dec 8, 2022Dec 31, 2024Dec 31, 20268.2.35Security fixes only
8.1Nov 25, 2021Nov 25, 2023Dec 31, 20258.1.34End of life
8.0Nov 26, 2020Nov 26, 2022Nov 26, 20238.0.30End of life
7.4Nov 28, 2019Nov 28, 2021Nov 28, 20227.4.33End of life
7.3Dec 6, 2018Dec 6, 2020Dec 6, 20217.3.33End of life
7.2Nov 30, 2017Nov 30, 2019Nov 30, 20207.2.34End of life
7.1Dec 1, 2016Dec 1, 2018Dec 1, 20197.1.33End of life
7.0Dec 3, 2015Jan 4, 2018Jan 10, 20197.0.33End of life
5.6Aug 28, 2014Jan 19, 2017Dec 31, 20185.6.40End of life
5.5Jun 20, 2013Jul 10, 2015Jul 21, 20165.5.38End of life
5.4Mar 1, 2012Sep 14, 2014Sep 14, 20155.4.45End of life
5.3Jun 30, 2009Jun 30, 2011Aug 14, 20145.3.29End of life
5.2Nov 2, 2006Nov 2, 2008Jan 6, 20115.2.17End of life
5.1Nov 24, 2005Aug 24, 2006Aug 24, 20065.1.6End of life
5.0Jul 13, 2004Sep 5, 2005Sep 5, 20055.0.5End of life
Data source: endoflife.date. Support dates are branch-level schedules; confirm release-specific details on php.net. The checked date in the page header shows when this table was generated.

Reading the table

What the statuses mean

PHP support is split into two phases. The branch first receives bug fixes and security fixes, then only security fixes, and finally no official updates at all.

Active support

The branch receives bug fixes and security fixes. This is the safest place to run a production site.

Security fixes only

New features and non-security bugs are no longer fixed. Security issues are still patched until the end-of-life date.

End of life

The branch no longer receives official fixes. Hosts may drop support, and new vulnerabilities are unlikely to be patched.

Choosing a version

Which PHP version should you run?

For a new project, choose the newest branch that your host, framework, and plugins support. The newest branches are the ones marked Active support in the table above. Running the newest stable release is usually the best way to keep receiving security fixes for longer.

A branch marked Security fixes only is still supported, but it is no longer the best home for a new project. Plan an upgrade before its end-of-life date. A branch marked End of life should be upgraded as soon as possible, especially on a public site.

Do not choose an old branch just because it still works. Test the application on a staging copy, check plugin and theme compatibility, and move to a supported release before the security window closes.

Quick guidance

  • New projects: pick the newest Active support branch your dependencies allow.
  • Existing sites: install the latest patch in your branch, then plan the next major upgrade.
  • Security-only branches: upgrade before the end-of-life date, not after it.
  • End-of-life branches: treat the upgrade as urgent.
How to check PHP version

Free checker

Check a site's PHP version

Paste a public URL to see the PHP version it exposes, its branch status, and whether it is patched against PHP2Shell. The checker uses read-only requests and never scans the server.

Try an example:

Free · No sign-up · We never store the URLs you check

Upgrading

What to do if your PHP version is end of life

An end-of-life branch will not receive a fix for the next security issue. Treat the upgrade as a maintenance project, not a one-line change, and test it before touching production.

  1. 1

    Back up and test on staging

    Take a full backup and run the upgrade on a staging copy first. Check the application, plugins, themes, and any custom PHP code against the target branch.

  2. 2

    Update PHP and dependencies

    Move to the newest release in a supported branch, then update your CMS, plugins, themes, and Composer packages. Old extensions are the most common reason an upgrade fails.

  3. 3

    Restart and verify the web SAPI

    Restart PHP-FPM, Apache, and any containers, then verify PHP_VERSION through the web server. The CLI and the web server can be running different PHP builds.

  4. 4

    Watch logs after the upgrade

    Check the PHP error log and application logs for deprecation warnings or fatal errors. Fix them before removing the old version from the staging environment.

FAQ

PHP support questions

Short answers about PHP end-of-life dates, supported branches, and checking a live site.

Official references

Support dates are branch-level estimates and can change. Always confirm time-sensitive details on php.net.

Check another site

The checker is free and does not require an account.

Back to the PHP version checker