PHP 8.6 Hosting: Switch Now or Wait?
PHP 8.6.0 was released on 19 November 2026. On ITSH web hosting you can select PHP 8.6 per site now, alongside PHP 8.3, 8.4 and 8.5. So you do not have to move everything at once: the blog tries 8.6 while the shop stays on 8.5. New sites deliberately still start on PHP 8.5.
In short:
- Your own code with tests, on a framework that supports 8.6: switch now.
- WordPress with many plugins, or a shop: wait until WordPress and your plugins officially support PHP 8.6.
- You switch per site, and switching back is just as quick.
What’s new in PHP 8.6 for your site
New for developers
- Partial function application: provide some of a function’s arguments in advance, with
?and...as placeholders for the rest. The result is a Closure. clamp(): keeps a value within a range, returning the nearest boundary otherwise.- Readonly properties with defaults: including in readonly classes, without going through the constructor.
Time\Duration: elapsed time with nanosecond precision, meant for timeouts and benchmark timings.
According to php.net, PHP 8.6 also brings performance improvements, among them faster JSON encoding and faster printf() calls. Whether your site gains anything measurable depends on your code.
What can affect an existing site
- More secure session defaults. PHP 8.6 turns on
session.use_strict_modeandsession.cookie_httponlyby default and setssession.cookie_samesitetoLax, unless your application sets its own values. If your JavaScript reads the session cookie, or a flow needs the session after a POST from another site (returning from a payment provider or an external login, for example), test exactly that flow. - Errors instead of silent fixes. Many functions now throw a
ValueErrorfor out-of-range values, invalid flags or strings containing NUL bytes, instead of silently truncating or ignoring them. - Small behaviour changes.
trim(),ltrim()andrtrim()now also strip form feed (\f) by default.fclose(),file_put_contents()andcopy()returnfalsewhen flushing on close fails. - Many deprecations, among them
returninside afinallyblock, returning a value from__construct(), the mbstring regex functions such asmb_ereg()andmb_split(), theis_double(),is_long(),is_integer()anddoubleval()aliases, andspl_object_hash(). A deprecation breaks nothing today. It is advance notice.
PHP 8.6 removes no extensions. On ITSH web hosting, every PHP version ships the same set of extensions, 8.6 included.
WordPress and PHP 8.6: is it compatible yet?
As of 22 November 2026: WordPress has not yet declared official support for PHP 8.6. The PHP compatibility table in the WordPress handbook does not list 8.6 yet. In the notes of the 20 November PHP chat, the core team writes that WordPress “is in good shape for 8.6” and that confidence in PHP 8.6 compatibility for WordPress 7.2 is high. WordPress 7.2 is scheduled for 8 December 2026.
The bigger risk is plugins and themes. The core team itself calls the plugin ecosystem “the big unknown”. An example from the same notes: flipping images by passing negative dimensions no longer works on PHP 8.6. WordPress core has moved away from that pattern, but plugins that copied it may still break.
Laravel, Symfony and your own code
Before you switch, check that your framework version and your Composer packages officially support PHP 8.6. If you have a test suite, run it on PHP 8.6 before you switch the site.
The console and cron jobs run on the same PHP version as the site. After switching, composer check-platform-reqs in the console tells you whether your installed packages are satisfied with PHP 8.6 and the extensions available.
PHP 8.6: switch now or stay on PHP 8.5?
Switching now makes sense if:
- you run your own code and can test it,
- your framework and packages officially support PHP 8.6,
- a few minutes of debugging on this site would not hurt anyone.
Wait if:
- the site runs WordPress with many plugins and earns money (a shop, bookings, leads),
- your framework or an important plugin does not support PHP 8.6 yet,
- nobody can click through the key flows right after the switch.
There is no rush: according to php.net, PHP 8.5 gets bug fixes until the end of 2027 and security fixes until the end of 2029.
Changing the PHP version: how to switch to PHP 8.6
-
Create a backup on the Backups tab. It is kept for 72 hours, which is enough for the test. The backup documentation covers what it includes.
-
Go to the Settings tab, choose
PHP 8.6as the Runtime and save. The portal warns you first:Saving will briefly take your site offline (a few seconds while the new runtime starts). Continue? -
The site’s containers are replaced. The old ones keep running until the new ones pass their health check, so you see a few seconds of mixed old and new rather than a hard outage. It takes longer the first time PHP 8.6 is used on the server your site runs on.
-
In the PHP Settings card, set Error reporting to
E_ALLfor the duration of your test. The default,E_ALL & ~E_DEPRECATED, hides deprecation notices, and those are exactly what you want to see now. Leave Display errors onOff:Onshows visitors file paths and sometimes source code. Every save restarts the site briefly. -
Click through what matters: login, forms, image uploads, checkout. Then check the Error Logs in the site’s Logs.
Once everything is clean, set Error reporting back to E_ALL & ~E_DEPRECATED. The documentation explains every runtime and PHP setting.
Switching back to PHP 8.5
The runtime can be changed at any time. If something misbehaves, choose PHP 8.5 on the same tab and save. It works like the switch: the same warning, the same few seconds of mixed old and new. Then fix the problem calmly, with the troubleshooting guide if you need it, and try 8.6 again later.
Conclusion
You decide per site when it moves to PHP 8.6. Your own tested code can switch now. A WordPress site with many plugins is better off waiting until WordPress and your plugins officially support 8.6.
Need an extension web hosting does not ship, or long-running processes? A container fits better: Kubernetes vs. Shared Hosting.
Already have a site with us? Switch it in the portal as described above.
Not yet? See web hosting plans with PHP 8.3 to 8.6 → New plans are released by hand, so allow a few working days.