Skip to content
New: Laravel Hosting, Node.js Hosting & GitHub DeploysSee the plans →
Products
Solutions
Developers

Guides

Which PHP version should you run?

How to pick a PHP version for a real site, what actually breaks when you upgrade, and how to test it without taking the site down.

Introduction

You should run the newest PHP version your application supports, and confirm which version that is by testing it. This guide covers the risks of upgrading and of staying put, how to choose a version, and how to test the change safely.

Upgrade Considerations

Upgrading

Newer PHP versions are faster and receive security fixes. PHP 8 is substantially quicker than PHP 7 on the same code, and versions past end of life receive no patches at all.

However, PHP major versions remove features, so code that ran for years may hit a fatal error on a newer runtime. The failure is often somewhere you did not test, such as a theme’s admin screen, a payment callback, or a nightly cron job.

Staying on an Old Version

An end-of-life version runs with known, published, unpatched vulnerabilities. It also becomes harder to leave over time, because the gap keeps widening and the plugins you would upgrade to may have dropped support for your version. Running PHP 5.6 in 2026 means accepting that risk.

Choosing a Version

Follow these steps to choose a version:

  1. Check the application. WordPress, Laravel, Drupal, and others all publish a supported PHP range.
  2. Check the plugins and themes. WordPress core may support a new version while one abandoned plugin does not.
  3. Choose the newest version that everything in that list supports.
  4. Check again every six months or so. The answer changes as your dependencies are updated.

In 2026, most current WordPress sites will land on PHP 8.2 or 8.3, and an actively maintained Laravel application will usually land on 8.3 or 8.4. An old bespoke PHP application nobody has touched since 2016 may still need 7.4. In that case, you should plan and budget to update the application.

Testing an Upgrade

The PHP version is set per site rather than per account. Our selector covers PHP 5.6 through 8.5, with 8.4 as the default, so you may test and roll back from a dropdown:

  • Put a copy of the site on a staging or secondary site and switch that copy to the new version. Then log in to the admin, submit a form, run a checkout, and trigger the cron job.
  • Turn error display on for the copy while testing, so failures are visible rather than a blank white page.
  • Move the live site once the copy passes, and keep the old version in mind as a one-click way back if a problem appears in the first day.

Common Upgrade Failures

Most failed upgrades show one of two symptoms:

  • A blank white page. PHP hit a fatal error with error display turned off. The reason is in the error log.
  • One feature stops while everything else works. This is almost always one plugin or library using something the new version removed.

Both symptoms mean something in your dependency list needs updating.

Keep reading

Other guides

Start building today

Laravel apps with queues and Horizon, WordPress stores, Node.js servers. One container with SSH, deploys from GitHub and people who answer. One bill a year.

Launch my site