Free tool

PHP version checker: is your PHP still supported?

Enter a website address. This PHP version checker reads the PHP version the server reports, then shows whether that version still gets security fixes and the date they stop. PHP 8.2 loses security support on 31 December 2026.

One address, or up to 20, one per line. The checker can only show a version the server reports; if it reports none, pick your version from the list.

Shift+Enter adds a line. We read only the response headers, and keep the answer for 10 minutes at most.

Already know your version?

Questions about a result? Ask us in writing

End-of-life dates

PHP end-of-life dates, PHP 5.6 to 8.5.

Dates from php.net and endoflife.date, checked Nov 15, 2026. Active support means bug and security fixes; after that a branch gets security fixes only, then nothing.

PHP versions with their support dates
VersionReleasedActive support untilSecurity fixes untilStatus on Nov 15, 2026
PHP 8.5Nov 20, 2025Dec 31, 2027Dec 31, 2029Active support
PHP 8.4Nov 21, 2024Dec 31, 2026Dec 31, 2028Active support
PHP 8.3Nov 23, 2023Dec 31, 2025Dec 31, 2027Security fixes only
PHP 8.2Dec 8, 2022Dec 31, 2024Dec 31, 2026Security fixes only
PHP 8.1Nov 25, 2021Nov 25, 2023Dec 31, 2025End of life
PHP 8.0Nov 26, 2020Nov 26, 2022Nov 26, 2023End of life
PHP 7.4Nov 28, 2019Nov 28, 2021Nov 28, 2022End of life
PHP 7.3Dec 6, 2018Dec 6, 2020Dec 6, 2021End of life
PHP 7.2Nov 30, 2017Nov 30, 2019Nov 30, 2020End of life
PHP 7.1Dec 1, 2016Dec 1, 2018Dec 1, 2019End of life
PHP 7.0Dec 3, 2015Jan 4, 2018Jan 10, 2019End of life
PHP 5.6Aug 28, 2014Jan 19, 2017Dec 31, 2018End of life

On 31 December 2026 two things happen at once: PHP 8.2 reaches end of life, and PHP 8.4 moves from active support to security fixes only. A site on 8.1 or older is already past end of life. On a supported branch, also check the patch level: the PHP project’s 21 October 2026 security releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35) fix two remote code execution bugs, and the checker flags a version older than them. The October 2026 releases. PHP 8.6 is planned for 19 November 2026 and joins the table when it ships. Sources: php.net supported versions and endoflife.date/php.

Find your version

How to find your PHP version when the checker cannot.

In a sample of 20 websites we checked on 6 November 2026, only one named its PHP version in its headers. These five places show it.

WordPress
In the dashboard, open Tools, then Site Health, then the Info tab. The Server section lists the PHP version the site runs on.
cPanel hosting
Open MultiPHP Manager (or Select PHP Version on some hosts). It shows the version each domain uses, and it is where the host lets you switch.
Other hosting panels
Plesk, managed WordPress hosts and cloud panels show the PHP version in the site or domain settings, usually next to the option to change it.
SSH access
Run php -v. This shows the command-line PHP, which can differ from the version that serves web pages, so confirm it in the panel or Site Health too.
A phpinfo() file
Upload a file containing <?php phpinfo(); and open it in the browser. It lists the exact PHP version that serves the site. Delete the file straight after: it exposes server details.
What breaks

What a PHP upgrade usually breaks.

The changes in each step that most often trip up older WordPress and PHP code, from the PHP manual's migration guides.

7.4 to 8.0
create_function() and each() were removed, so old plugins that still call them stop with a fatal error. Comparisons between numbers and non-numeric strings changed, which can quietly change an if-statement.
8.0 to 8.1
Passing null to a built-in function that expects a string or number is deprecated, so logs can fill with warnings such as "Passing null to parameter #1 ($string) of type string".
8.1 to 8.2
Creating a property that a class never declared ("dynamic properties") is deprecated. Themes and plugins written before PHP 8.2 can do this, and those that do raise deprecation notices until they are updated.
8.3 to 8.4
A typed parameter with a default of null and no ? in its type ("implicitly nullable") is deprecated. Deprecations are warnings, not errors, but they flag code to review before the next upgrade.

WordPress itself is rarely the problem: WordPress.org recommends PHP 8.3 or greater, and its compatibility table lists WordPress 7.0 and 7.1 as running on PHP 7.4 to 8.5, even though 7.4 to 8.1 no longer get security fixes. The breakage usually comes from a plugin or theme that has not been updated. Laravel ties each major version to a PHP range:

Laravel 10
PHP 8.1 to 8.3. Security fixes ended 4 Feb 2025.
Laravel 11
PHP 8.2 to 8.4. Security fixes ended 12 Mar 2026.
Laravel 12
PHP 8.2 to 8.5. Security fixes until 24 Feb 2027.
Laravel 13
PHP 8.3 to 8.5.

Sources: PHP 8.0 incompatible changes, 8.1, 8.2 and 8.4 deprecations, WordPress PHP compatibility and Laravel support policy, read Nov 15, 2026.

Fixed-price upgrade

If your PHP is at or near end of life.

We upgrade one WordPress or PHP site to the latest security release on a supported version for US$499 fixed. 500+ websites optimized and 700+ migrated without downtime since 2019.

  • A backup and a staging copy of the site or app before anything changes
  • A compatibility check of the theme, plugins, Composer or npm packages and the lockfile
  • Up to 4 hours of fixes for what the new version breaks
  • The move to the latest security release on a supported version: PHP 8.4 or 8.5 (8.3 if a plugin blocks them), or Node.js 24 LTS (22 if a dependency blocks 24)
  • A test of the main user flows on staging, then the switchover with a written rollback plan
  • Handover notes: what changed, what we tested and how to roll back
Turnaround
Upgraded and switched over in 3 business days after we have access
After the switch
A 7-day window to roll back, and 14 days in which we fix any regression the upgrade caused, at no charge
Payment
Pay by card online, or ask first. Full refund if the job is bigger than one site or app, or needs more than 4 hours of fixes and you decide not to go ahead

If the compatibility check shows more than 4 hours of fixes, we tell you before doing extra work and give you a fixed quote for it. If you would rather not go ahead, or the job is bigger than one site or app, we refund in full. Hosting moves, malware cleanup and rewrites are separate jobs.

Need it sooner? For US$1,190, the upgraded and tested staging copy is ready within 1 business day, and we switch the live site at your next agreed quiet window. Full terms are on the PHP and Node.js upgrade page.

FAQ

PHP version questions.

How do I check the PHP version of a website?

Enter the address in the checker above. It reads the response headers, and some servers name the PHP version in the X-Powered-By header. If the server hides it, look in WordPress under Tools, Site Health, Info, Server, or in your hosting panel, then pick the version in the checker to see its support dates.

Why does the checker say the PHP version is hidden?

Many servers are set not to announce their PHP version (only 1 of 20 sites we sampled on 6 November 2026 did), which is common hardening practice: it gives attackers one less detail. A hidden version tells you nothing about whether it is current, so check it in WordPress Site Health or your hosting panel.

When does PHP 8.2 reach end of life?

PHP 8.2 gets security fixes until 31 December 2026, according to php.net. After that date the PHP project releases no more fixes for 8.2, including security fixes.

Is PHP 7.4 still supported?

No. PHP 7.4 stopped getting security fixes on 28 November 2022, and PHP 8.0 on 26 November 2023. Some Linux distributions and hosts backport fixes for their own packages, but the PHP project itself no longer patches either branch.

Which PHP version should WordPress run?

WordPress.org recommends PHP 8.3 or greater. Its compatibility table lists WordPress 7.0 and 7.1 as running on PHP 7.4 to 8.5, but only 8.2 and newer still get security fixes from the PHP project. Plugins and themes set their own limits, so test them on a staging copy before switching the live site.

Does the checker keep the sites I check?

We read each site’s response headers once and keep the answer in memory for up to 10 minutes, so a repeat check is fast. Nothing is saved to a database, and no page content is read.

What does the PHP upgrade cost?

Upgrading one WordPress or PHP site is US$499 fixed: a staging copy first, up to 4 hours of fixes for what the new version breaks, then the live switch with a rollback plan, in 3 business days after we have access. A priority version, with the tested staging copy ready in 1 business day, is US$1,190.