Drupal PHP version and hosting requirements
🎧 Listen to every article back to back
A website may appear to work while the server already runs an outdated PHP version. That quiet risk should be visible before a Drupal upgrade, PHP change or hosting migration.
Drupal depends on PHP
Drupal is written in PHP. This means Drupal security and reliability also depend on the PHP version running on the server.
The official PHP site lists supported PHP versions (opens in a new tab). If the server uses a version that no longer receives security fixes, updating Drupal modules is not enough.
The site may still work. The risk is that old PHP blocks future upgrades and may leave security issues without fixes.
If you are choosing a new environment, start with the broader Drupal hosting requirements checklist. This article focuses on the PHP-specific checks that often block Drupal upgrades.
What to check in hosting
At the start of Drupal maintenance, hosting should be checked together with Drupal itself. The important questions are simple:
- which PHP version is used;
- whether the server allows a newer PHP version;
- whether Composer runs in the same environment;
- whether command-line PHP and web server PHP use the same version;
- whether a staging environment exists;
- whether backups can be restored, not only downloaded.
If these answers are missing, a simple upgrade may turn into slow investigation.
Old PHP can block an upgrade
A common problem is that Drupal needs a newer PHP version, but hosting does not support it. In that case Drupal cannot be upgraded safely before the server is fixed.
Another common problem is a difference between command-line PHP and the web server. Composer may use one PHP version while the public site uses another. This creates errors that are hard to understand if the environment is not documented.
Good hosting makes maintenance easier
Good Drupal hosting provides more than speed. It needs a controlled environment with access to logs and the command line, staging, clear backup procedures and the ability to update PHP.
When WebPro takes a Drupal site into maintenance, we review hosting as part of Drupal maintenance. If needed, an audit helps show whether the issue is in Drupal code, modules or the server.
For a new provider shortlist, region matters too. A US client may be better served by a North American Drupal platform, while an EU client may need stronger data-residency and procurement fit. The hosting checklist should be read before comparing provider names.
What to do before changing PHP
The PHP version should not be changed directly on the live site without checks. Before the change, create a backup, test the same change in staging and check the main pages, forms and background tasks.
If the checks pass, the live change can follow a planned release and rollback procedure. If something breaks in staging, the team can fix it before users are affected.
An outdated hosting environment eventually limits how safely Drupal can be maintained and upgraded.
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.