How a PHP version ages
Every PHP versionA PHP version is a numbered edition of PHP, like 8.3. Each edition is looked after for a limited time, then gets security fixes only, then nothing. follows the same path. First comes active supportActive support is the phase in which a PHP version is fully looked after: both ordinary bugs and security problems get fixed, with regular updates., with fixes for bugs and security problems. Then the branch moves to security supportSecurity support is a phase in which a PHP version only gets fixes for security problems. Ordinary bugs are no longer repaired., where only security problems get fixed. After that the branch reaches end of lifeEnd of life (EOL) means the makers have stopped looking after a version of software. It still works, but it no longer gets updates, not even security fixes. and the PHP project stops publishing fixes for it altogether.
According to php.net (checked 21 October 2026), PHP 8.2 and 8.3 only receive security fixes, until 31 December 2026 and 31 December 2027. PHP 8.4 and 8.5 have active support until 31 December 2026 and 31 December 2027. PHP 8.1 and 8.0 are past end of life. Some Linux distributions and long-term support vendors still ship a backportA backport takes a fix made for a newer version of software and applies it to an older version, so the old one gets the fix without a full upgrade. for older branches, so the version number alone does not always tell the full story.
Settings and building blocks
PHP rarely runs on its own. It sits behind a web serverA web server is the program, such as Apache, Nginx or LiteSpeed, that answers when a visitor opens your site and sends back the page and files. through PHP-FPMPHP-FPM is a helper on your hosting that runs your site's PHP code as a separate job and hands the finished page back to the program that answers visitors. or mod_phpmod_php is an older way of running PHP, in which PHP is built into Apache, the program that answers visitors, instead of running as a separate helper., reads its limits from php.iniphp.ini is the settings file for PHP on your hosting. It sets limits, such as how much memory a script may use, how big an upload may be and if errors show., keeps compiled code in OPcacheOPcache is a PHP feature that remembers your site's code in a ready-to-run form, so PHP does not have to prepare it again for every visitor. and pulls in libraries through ComposerComposer is a tool that downloads the code libraries a PHP project needs and notes exactly which versions, so the project can be rebuilt the same way anywhere.. When one of these pieces lags behind, an upgrade can break things, which is why each new PHP version comes with a list of deprecationsA deprecation is an early warning that a feature still works today but will be removed in a future PHP version, so code using it must be changed in time. to clear first.
What to do with this knowledge
Start by finding out which PHP version your site runs. The free PHP exposure check shows what your site reveals from the outside. If the answer is a branch that only has security fixes left, or none at all, plan the move now. When we update PHP in WordPress, we test the upgrade on stagingA staging environment is a private copy of your website where you try updates first, so any mistakes happen there and not on the live site. first and keep a rollbackA rollback means going back to the last version of your website that worked, after an update has gone wrong. ready. If your code or host cannot make the jump, our PHP migration service moves the whole site to a modern stack.