Overview
PHP applications should run on a maintained PHP branch whenever possible. The official PHP release pages explain which versions receive active support, security fixes or have reached end of life.
Why version support matters
A version upgrade can bring performance improvements, language features and security fixes. It can also expose deprecated behavior or incompatibilities in application code and third-party packages.
Planning an upgrade
Start by identifying the PHP version used by CLI, web server and scheduled jobs. Review the migration guide for every major or minor version you are crossing. Check Composer package constraints, required extensions and application test coverage. Run automated tests and staging checks before switching production traffic.
Useful checks
- Confirm the exact PHP version used by the web SAPI, not only the command line.
- Review deprecations and removed features in the migration guide.
- Verify extensions and Composer platform requirements.
- Keep a tested rollback plan.
Official resources
Supported versions: https://www.php.net/supported-versions.php PHP releases: https://www.php.net/releases/ Migration guides: https://www.php.net/manual/en/appendices.php