What Is the Latest PHP Version? (October 2026)

Latest release of each supported version

Four PHP versions are supported today. Whichever one you run, you should be on its latest patch release, because that’s where the security fixes are:

Checked against php.net downloads on 4 October 2026. New patch releases come out roughly every four weeks. For how the release cycle works and the full history, see PHP releases explained.

Which PHP version should you use?

Why not jump straight to PHP 8.6?

Being on the newest version isn’t the goal. Being on a supported version that all your dependencies support is. In the first weeks after a release, frameworks, CMS plugins and Composer packages are still catching up, and the x.y.0 release often has a few bugs that the next patch fixes. For most businesses the right time to move production to a new PHP version is two to six months after it ships.

That said, you don’t lose much by going to 8.5 first. The move from 8.5 to 8.6 is small.

How to check which PHP version you’re running

The version on the command line and the version your website uses are often different, especially on servers that host several sites. Check both:

# Command line (may differ from what your website uses)
php -v

# What your website actually runs: check the PHP-FPM versions installed
ls /run/php/

# Will your Composer dependencies run on this PHP?
composer check-platform-reqs

• WordPress: go to Tools → Site Health → Info → Server.
• Shared hosting: look for “PHP version” or “Select PHP version” in cPanel, Plesk or your host’s dashboard.
• Anything else: upload a file that calls phpinfo(), open it in a browser, then delete it straight away. It exposes details about your server.

What’s new in PHP 8.5

PHP 8.5 is mainly about making everyday code tidier. The headline feature is the pipe operator, which passes a value from left to right through a series of functions instead of nesting them inside each other:

// PHP 8.5: the pipe operator passes a value through a chain of callables
$slug = $title
    |> trim(...)
    |> strtolower(...)
    |> (fn (string $s): string => str_replace(' ', '-', $s));

A few other additions you will actually use:

// PHP 8.5
$newest = array_last($orders);                  // null if the array is empty
$paid   = clone($order, ['status' => 'paid']);   // "clone with"

#[\NoDiscard('the payment may have failed')]
function charge(Order $order): Result { /* ... */ }

charge($order); // warning: the return value is ignored

It also adds a built-in URI extension that parses URLs according to the official standards, so different parts of your application stop disagreeing about what a URL means, and persistent cURL share handles to reuse connections between requests. The deprecations are minor: see what breaks between PHP 8.2 and 8.5.

What’s coming in PHP 8.6

PHP 8.6 builds on 8.5. Partial function application lets you leave arguments open with a ? placeholder, which removes the wrapper closure from the pipe example above:

// PHP 8.6: partial function application drops the wrapper closure
$slug = $title
    |> trim(...)
    |> strtolower(...)
    |> str_replace(' ', '-', ?);

// PHP 8.6
$quantity = clamp($requested, 1, 99);   // keeps a value within bounds

final class Invoice
{
    public readonly string $currency = 'GBP';   // readonly properties can have defaults
}

Also new: a Time\Duration class, a SortDirection enum and a polling API for non-blocking I/O.

The change most likely to catch people out is not a feature. PHP 8.6 switches on safer session cookie defaults: strict mode, HttpOnly, and SameSite=Lax. That is good for security, but anything that needs the session cookie on a POST from another site, such as some payment gateway or single sign-on callbacks, can silently lose the session. Test checkout and login flows carefully, or set the old values explicitly in your configuration if you need them.

Full details are in the official PHP 8.6 upgrade notes.

Will my framework or CMS run on the latest PHP?

• Laravel and Symfony support new PHP versions quickly, usually within days of release, but only in their current versions. Symfony 8 requires at least PHP 8.4. If you’re several framework versions behind, you will need to upgrade the framework as well as PHP.
• WordPress core marks new PHP versions as having “beta support” until enough sites run them. The real risk is plugins and themes, especially ones that are no longer maintained. See WordPress PHP upgrades.
• Composer packages: run composer why-not php 8.5 to list everything that stands in the way.

Frequently asked questions

What is the latest version of PHP?

PHP 8.5 is the latest stable version. Its most recent patch release is PHP 8.5.11, released on 24 September 2026. PHP 8.6 is due on 19 November 2026 and is currently a release candidate, which should not be used in production.

What is the latest stable version of PHP for production?

PHP 8.5. It is stable, has been out for almost a year, and receives security fixes until 31 December 2029. Always run the latest patch release of whichever version you choose.

Is PHP 8.4 still supported?

Yes. PHP 8.4 gets bug and security fixes until 31 December 2026, then security fixes only until 31 December 2028. If you are planning an upgrade from an older version, though, go straight to PHP 8.5.

Should I wait for PHP 8.6 before upgrading?

No. Upgrading to PHP 8.5 now and moving to 8.6 later is a small step, because 8.5 to 8.6 changes very little. Waiting only makes sense if you are already on PHP 8.4 or 8.5 and nothing is forcing a change.

Is the latest PHP version faster?

Usually a little. Every PHP 8 release has brought small performance gains, but the big jump was from PHP 7.x to PHP 8. Upgrade for security support and for compatibility with your framework and packages. Treat speed as a bonus.