Skip to content

PHP 8.6 release date and features: what changes for your site

PHP 8.6 is due November 19, 2026. Here's what's new for developers, what could break older plugins and themes, and why business sites should wait before upgrading.

PHP 8.6 is scheduled for general release on November 19, 2026, according to the official PHP 8.6 release schedule. The latest test build, RC4, came out on October 21, 2026, and the last release candidate, RC5, is planned for November 5. This guide covers the PHP 8.6 release date and features, and what they mean for a business website. PHP is the programming language behind WordPress, WooCommerce and Laravel.

The headline features are for developers: partial function application, a new clamp() function, default values for readonly properties, a Time\Duration class and a new polling API. The change most likely to reach a live business site is a set of safer session defaults, plus deprecation notices that older plugins and themes can trigger.

Should you upgrade on release day? No. Run a patched PHP 8.4 or 8.5 now, then move to 8.6 once WordPress, your plugins and your host support it.

Check your PHP version in 2 minutes: in WordPress, go to Tools, then Site Health, then the Info tab, and open Server. Or log in to your hosting panel and look for MultiPHP Manager or Select PHP Version in cPanel, or PHP Configuration in Hostinger's hPanel.

PHP 8.6 release date and features at a glance

PHP ships one new version a year, usually in late November, after alpha, beta and release candidate (RC) builds. Only the general availability (GA) release is meant for live sites. Wondering whether PHP itself has a future? See is PHP dead? Here is the PHP 8.6 timeline from wiki.php.net and php.net:

MilestoneDateWhat it means
Alpha 1July 2, 2026First test build
Beta 1August 13, 2026Soft feature freeze: all RFC votes concluded
Hard feature freezeSeptember 22, 2026New features only with release manager approval
RC2September 24, 2026First release candidate (RC1 was skipped after a packaging mistake)
RC3October 8, 2026Test build
RC4October 21, 2026Test build that includes the php2shell security fixes
RC5November 5, 2026Planned last release candidate
GANovember 19, 2026Scheduled stable release

The php.net RC4 announcement carries the usual warning: "Please DO NOT use this version in production, it is an early test version." Dates can still move if a serious bug turns up, so treat November 19 as the target, not a promise.

The headline PHP 8.6 features, explained

Every feature below has an RFC (the formal proposal PHP's core developers vote on) marked as implemented for PHP 8.6 on wiki.php.net, and each appears in the official PHP 8.6 migration guide. Each gets a short example and a plain answer for owners.

Partial function application

You can now call a function with some arguments filled in and a ? placeholder for the rest. Instead of running, the call returns a new function that waits for the missing value. From the migration guide: $stripSpaces = str_replace(' ', '', ?); then $stripSpaces('a b c') returns "abc". A ... placeholder stands for all remaining arguments. The partial function application RFC lists it as implemented for 8.6.

For your business site: nothing changes on its own. Developers get shorter callback code in custom plugins and Laravel apps.

The clamp() function

clamp($value, $min, $max) keeps a value inside a range. clamp(2, min: 1, max: 3) returns 2, and clamp(15, 1, 10) returns 10. The clamp RFC passed 23 to 3, and the function throws a ValueError if $min is greater than $max.

For your business site: a small helper for quantity limits or page numbers. WordPress 7.1 has already added a polyfill (a fallback copy) of clamp() for older PHP versions, according to the WordPress hosting handbook.

Default values for readonly properties

Readonly properties can now declare a default: public readonly int $timeout = 30;. Before 8.6 that line was an error, and the value had to be set in the constructor. The readonly property defaults RFC passed 24 to 0.

For your business site: no visible change. Configuration code in custom apps gets a little cleaner.

The Time\Duration class

A new built-in class for lengths of time, such as timeouts and retry delays: Time\Duration::fromMilliseconds(500). The Duration RFC calls it the first building block of a modernized date and time library. Existing functions like sleep() don't accept it yet.

For your business site: nothing to do. It matters later, as libraries adopt it.

Smaller additions

  • Polling API. A new Io\Poll API watches many network connections or streams at once. It's a building block for libraries, not async/await syntax.
  • Clearer error messages, if you want them. A new error_include_args setting, off by default, adds the actual arguments to errors, so unlink() becomes unlink('/tmp') in the message.
  • Language polish. #[\Override] works on class constants, and enums can define __debugInfo().

Ignore posts that promise generics, pattern matching or built-in async in PHP 8.6. On PHP's RFC list, the Bound-Erased Generic Types RFC is declined, and pattern matching and context managers are still under discussion.

Not sure what is costing you leads?

Send your website and we will record a free 2 minute video showing the 3 fixes we would make first.

Get my free video audit

Safer session defaults: the change most likely to reach a live site

PHP sessions are one way a site remembers a visitor between pages, for example a logged-in member or a multi-step form. The Secure Session Configuration Defaults RFC, accepted for PHP 8.6 with no votes against, changes 3 defaults:

  • session.use_strict_mode is now 1 (was 0). PHP rejects session IDs it didn't create, which helps prevent session fixation attacks.
  • session.cookie_httponly is now 1 (was 0). JavaScript can no longer read the session cookie.
  • session.cookie_samesite is now Lax (was unset). Browsers won't send the session cookie with a POST request that comes from another site.

For most sites this is a free security gain. The RFC lists what can break: JavaScript that reads the session cookie, custom session handlers that accept outside session IDs, and flows where another site POSTs back to yours, such as some single sign-on logins. If your checkout sends customers to a payment page and back, run a test order on staging.

WordPress core keeps you logged in with its own cookies, such as wordpress_logged_in_, rather than PHP sessions, per WordPress's cookies documentation. So on a WordPress site, this change mainly matters for plugins or custom code that start a PHP session.

For your developer or host: if a flow breaks, the fix is a setting, not a rewrite. Each default can be set back in php.ini or the PHP-FPM pool. For a cross-site POST flow, the migration guide says to set session.cookie_samesite to None and session.cookie_secure to 1. Better still, fix the flow and keep the safer defaults.

Deprecations and changes that can break older plugins and themes

A deprecation is advance notice that something will stop working in a future version. Deprecated code still runs in PHP 8.6, but it logs a notice, and if error display is on, visitors can see it. The PHP 8.6 deprecations RFC lists dozens. These are the PHP 8.6 deprecations most likely to show up in older WordPress plugins and themes:

  • Returning a value from a constructor. return $this; inside __construct() now triggers a notice. WordPress 7.1 removed this pattern from its own code (ticket #65637, per the hosting handbook).
  • Old function aliases. is_integer(), is_long(), is_double() and doubleval(). Use is_int(), is_float() and floatval().
  • spl_object_hash(). Use spl_object_id() instead.
  • return inside finally. It silently swallows exceptions, so it now triggers a notice.
  • The mb_ereg functions. The library behind them, Oniguruma, is no longer maintained. Removal is planned for PHP 9.0.
  • Custom session handlers that lack create_sid() and validateId() methods.

A few behavior changes arrive without a deprecation notice first, per the migration guide:

  • trim(), ltrim() and rtrim() now also strip the form feed character (\f).
  • More functions throw a ValueError for invalid input instead of quietly fixing it, for example number_format() with an out-of-range decimals value. An uncaught error stops the page, which WordPress shows as its critical error screen.

Should a business site upgrade to PHP 8.6 on release day?

No. Release day means the PHP project calls 8.6 stable. It doesn't mean WordPress, your theme, your plugins and your host have tested it.

Look at PHP 8.5. It came out on November 20, 2025, and the WordPress hosting handbook lists it as fully compatible as of May 2026, about 6 months later. As of October 27, 2026, the same handbook lists WordPress 7.1 as compatible with PHP 7.4 through 8.5 and recommends PHP 8.4 or later for production. Laravel 13 supports PHP 8.3 to 8.5, per the Laravel release notes.

The typical approach right now:

  1. Get onto a patched release now. After the php2shell vulnerabilities, that means PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or a later patch release. Our php2shell guide shows how to check.
  2. Leave PHP 8.2 before December 31, 2026, when its security support ends. See PHP 8.2 end of life.
  3. Pick 8.4 or 8.5 as your next stop. Both are supported by WordPress 7.1, Laravel 12 and Laravel 13.
  4. Move to 8.6 when all of these are true: WordPress lists 8.6 as compatible, your key plugins mention 8.6 in their changelogs, your host offers it, and a staging copy runs with no new errors in the log.
For your developer or host: test now, upgrade later. Add PHP 8.6 RC builds to CI, log E_DEPRECATED notices without displaying them, search the code for the deprecated functions above, and check anything that reads or sets session cookies.

How long PHP 8.6 will be supported

Under the policy on php.net's supported versions page, each branch gets 2 years of active support (bug and security fixes), then 2 more years of critical security fixes only. Every current branch ends support on December 31. Applied to a November 19, 2026 release, PHP 8.6 support should look like this:

VersionReleasedActive support untilSecurity fixes until
8.2Dec 8, 2022Dec 31, 2024Dec 31, 2026
8.3Nov 23, 2023Dec 31, 2025Dec 31, 2027
8.4Nov 21, 2024Dec 31, 2026Dec 31, 2028
8.5Nov 20, 2025Dec 31, 2027Dec 31, 2029
8.6 (expected)Nov 19, 2026 (scheduled)Dec 31, 2028Dec 31, 2030

php.net adds a version to that table once it's released, so confirm the 8.6 dates then. Since 8.4 and 8.5 are supported for years, there's no reason to rush to 8.6 before your plugins are ready.

What to do next

Find out which PHP version your site runs today and whether it's a patched release. If it's 8.2 or older, plan the move to 8.4 or 8.5 this quarter. PHP 8.6 can wait.

If you'd rather not handle PHP upgrades yourself, we build and maintain WordPress and Laravel sites, including version upgrades tested on staging first. Or send us your site and we'll record a free 2 minute video audit showing the 3 fixes we'd make first.

Common questions

When is PHP 8.6 released?

PHP 8.6.0 is scheduled for general release on November 19, 2026, according to the official schedule on wiki.php.net. The last release candidate, RC5, is planned for November 5. Release dates can move if a serious bug is found late, so wait for the release announcement on php.net before you plan any upgrade around that date.

What are the main new features in PHP 8.6?

Partial function application, the clamp() function, default values for readonly properties, a Time\Duration class, a new polling API and better stream error handling. PHP 8.6 also switches on safer session cookie defaults and deprecates old functions such as is_integer(), doubleval() and spl_object_hash(). Most of it matters to developers rather than to how your site looks or performs.

Will PHP 8.6 break my WordPress site?

It might, if a plugin or theme relies on something 8.6 changed. Deprecations only add notices to the log, but stricter input checks can stop a page with a fatal error, and the new session defaults can affect plugins that use PHP sessions. WordPress doesn't list 8.6 as compatible yet, so test on a staging copy before you switch.

Should I upgrade to PHP 8.5 now or wait for 8.6?

Upgrade now if you're on 8.2 or older. PHP 8.2 loses security support on December 31, 2026, and current WordPress and Laravel versions support 8.4 and 8.5. Make sure you land on a patched release, such as 8.5.12 or 8.4.27. Move to 8.6 later, once WordPress, your plugins and your host support it.

How long will PHP 8.6 be supported?

PHP's policy is 2 years of active support plus 2 years of security fixes, with each period ending on December 31. For a November 2026 release, that means bug fixes until December 31, 2028 and security fixes until December 31, 2030. php.net publishes the official dates on its supported versions page once 8.6 is released.

Get your free video audit

The 3 fixes we'd make first on your site, within 1 business day.

Send my website
Free video auditWhatsApp