Published: 03.07.2026
PHP powers the majority of websites, including WordPress and most shop engines. Each year a new version is released, and older ones stop receiving fixes. Staying on a supported version is one of the cheapest ways to speed up a site and to close security holes.
How PHP versions are supported
Every release is actively supported for about two years, and then it gets security fixes only for another two years. After that it reaches end of life: no more patches, even for serious problems. A site running on such a version stays open to known attacks that nobody will repair.
What you gain by upgrading
- Speed. Each modern release executes the same code faster and uses less memory than the previous one.
- Security. You receive fixes for new vulnerabilities and safer defaults.
- Compatibility. Current plugins and libraries drop support for old versions, so you cannot update them otherwise.
- New language features that make the code of your own projects shorter and clearer.
Check your version
Look at the PHP section in your control panel, or in the site health page of your platform. In WordPress, the Site Health tool shows the version and warns if it is outdated. You can also ask support which versions are available on your plan.
How to upgrade safely
- Make a backup of the files and the database.
- Update the platform, theme and plugins to the latest versions first, because new versions of them support new PHP.
- Test on a copy. Use a staging site or a subdomain with the new PHP version.
- Turn on error display on the copy and click through the main pages, the admin area and forms.
- Switch the version for the live site in the panel and watch the logs.
- Be ready to roll back. Panels allow you to return to the previous version in seconds.
What can break
- Old themes and plugins that are no longer maintained.
- Custom code that uses removed functions or old syntax.
- Warnings about deprecated features that appear as messages on the page.
- Extensions that are missing on the new version and must be enabled in the panel.
Settings worth checking
- memory_limit for heavy plugins and imports.
- max_execution_time for long tasks.
- upload_max_filesize and post_max_size for media uploads.
- OPcache if your platform allows it, as it caches compiled code and reduces the load.
Different versions for different sites
Many hosts let you choose a version per site or per folder. This is convenient when one old project cannot be upgraded yet: keep it on its own account or subdomain, and give new projects the current version.
Legacy applications
If a business application requires an old PHP, plan its replacement. Run it isolated, restrict access with a firewall and keep a clear migration date.
Frequently asked questions
How often should I upgrade? Move to a supported version at least once a year, and watch the end-of-life dates.
Will the upgrade change my design? No. It changes how the code runs, not how it looks. Only broken extensions can cause visible problems.
Is the newest version always the best? Prefer the latest stable version that all your extensions support.
