The end of support for PHP 8.2 will not automatically take your website offline, but it is worth preparing in good time to ensure it continues to operate securely. Support for PHP 8.2 will end on 31 December 2026; after this date, the PHP project will no longer release new security patches for this version. Active support ended on 31 December 2024.

It’s understandable if you’re worried that a PHP update might cause an error or take your live website offline. The risk isn’t posed by the version change itself, but by an ill-prepared migration. Before making any changes to your live environment, check that your plugins, templates and custom code are compatible.

The article outlines the end-of-life date for PHP 8.2, the security implications of the version upgrade and the steps required to assess how your website is affected. You can find out how a backup and test run before the update can help with the transition, as well as the role played by the PHP settings available on your hosting account, such as those in the cPanel interface.

What does the end of support for PHP 8.2 mean, and when will it end?

There are two key dates to note in the PHP 8.2 lifecycle: the end of active support and the end of security support. Active support ended on 31 December 2024, whilst security support will end on 31 December 2026. The end of support for PHP 8.2 does not mean that websites will automatically stop working. It means that, after the cut-off date, the PHP project will no longer release security patches for this branch.

Active and security support: what’s the difference?

During the active support period, PHP releases may receive bug fixes and security updates. Once the active support period has ended, support focuses on fixing security issues. Adding new features is not the primary aim of the active support period; maintaining the version already released, however, is.

In short: During the security support period, the PHP project may release fixes for security vulnerabilities discovered in that version.

The support schedules for different PHP versions vary, so the dates for a newer version cannot automatically be applied to version 8.2. An overview of the development of the PHP programming language helps to understand why the version of the runtime environment is important. However, to check the specific lifecycle details, please use the official PHP support table.

What are the official support dates for PHP 8.2?

According to PHP’s official version support table, active support for PHP 8.2 ended on 31 December 2024, whilst security support will end on 31 December 2026. These are the support cut-off dates, not the dates of the initial release of PHP 8.2. The information was verified in October 2026. As support information is subject to change, please refer to the current official table at the time of publication and for any subsequent updates.

From 1 January 2027, the PHP project will no longer release official security patches for newly discovered vulnerabilities in PHP 8.2. This will not cause websites running on the server to go offline: they can continue to operate provided the hosting and other components are suitable. The risk is that there will be no patch issued by the project for any PHP bugs discovered at a later date.

Treat this date as a planning deadline. First, determine which version of PHP is running on your website, then check the plugins, the template and any custom code as well. The cPanel hosting interface provides the tools to manage the version and settings. Creating a backup of your site and carrying out tests before the migration reduces the risk of disruptions caused by live changes.

What might happen after support for PHP 8.2 ends?

After end-of-life, PHP 8.2 can still run on the server, but no new official security patches will be released for this version. This does not mean an automatic shutdown, nor does it make every PHP 8.2 website immediately vulnerable to hacking. It does mean that the PHP project will not release a patch for this version in response to any PHP-related vulnerabilities discovered at a later date. You can check the official PHP support schedule to see which versions are still receiving updates.

Security risk without supported patches

PHP forms part of a website’s runtime environment. If an update is required to fix a security issue identified at this layer, an official patch may not necessarily be available for unsupported versions. This can increase vulnerability, particularly if the application or other components of the server are also out of date or not properly maintained.

PHP, the content management system and its extensions each constitute a separate update layer. An up-to-date content management system does not replace the security patches released for PHP, just as upgrading the PHP version does not automatically update the extensions. When assessing risk, you should therefore check both layers separately.

In short: An unsupported version of PHP does not automatically become vulnerable or inoperable, but without an official update, newly discovered PHP vulnerabilities may not be patched.

Compatibility and performance: what should you expect?

Security and compatibility are two separate issues. An older code snippet, plugin or template may trigger a warning, error or behavioural difference when used with a newer version of PHP. It may also be the case that the website works flawlessly on the old version, but certain parts of the application do not support later PHP releases.

The version configured on the hosting account does not in itself guarantee that the entire website is compatible. Functionality also depends on the code and the versions of the installed dependencies. It may happen, for example, that the home page loads, but submitting a form, making a payment or logging in results in an error. Therefore, do not stop at just opening a single page.

• Check the versions of your website and its components, as well as the PHP error logs.
• Try out the key features, such as login, forms and administration.
• Before the live migration, test your chosen PHP version in an isolated environment and create a usable backup.

The cPanel hosting settings can help you manage your runtime environment, but they are no substitute for checking your website’s code. The end of support for PHP 8.2 therefore does not constitute an immediate emergency, but rather calls for an assessment and a planned migration.

How can you check whether your website is affected by the end of support for PHP 8.2?

Start the assessment by checking the actual running environment, then go through the key components of the application one by one. This way, you’ll not only find out whether the website uses PHP 8.2, but also what you need to check before upgrading.

Where can you find the PHP version of a website?

Look for the PHP version in the hosting control panel, amongst the settings for your website or runtime environment. If you are using cPanel, you can view the available settings in the cPanel hosting control panel. The menu items and options may vary depending on your hosting configuration, so please ensure you are viewing the settings for the correct website.

If the active version is not clear in the control panel, use verified server information or administrator data. Do not publish screenshots containing login details, server addresses or sensitive information. Make a note of the PHP version assigned to the website; if you have multiple domains, check each one separately.

Which components need to be checked for compatibility?

In the case of WordPress, the content management system, plugins and theme are separate components. The WordPress version alone does not guarantee that all plugins will function correctly in the new PHP environment. Using WordPress hosting is also no substitute for checking the compatibility of the application and its dependencies.

The following checklist will help ensure that the survey covers all the important details:

1. Identifying the PHP version: note down the version actually configured for the website via the hosting control panel or based on verified server information.
2. Compiling an application inventory: list the content management system and its version, the plugins, the template and any custom code. Don’t forget to include any separately managed subpages and online shop features.
3. Overview of dependencies: check the application and component documentation to see which PHP versions are supported. For a plugin that hasn’t been updated for a long time, check whether there is a maintained, compatible version available.
4. Identifying test points: list the operations that are important from a business perspective, such as logging in, searching, submitting forms and placing orders. Check each of these separately during the migration test.

When assessing the custom code, take stock of any in-house developed extensions and any modifications for which there is no up-to-date documentation. If the PHP version support for any element is unclear, note this in the inventory. This way, testing can focus on the areas of uncertainty, rather than just examining the appearance of the home page.

How can you prepare safely for a PHP version change?

Before changing the PHP version, record the current status and create a restoreable backup. Do not start testing on the live website. In an isolated test environment, you’ll spot compatibility issues sooner, reducing the chance that visitors will encounter malfunctions. As support for PHP 8.2 is coming to an end, plan the switch in advance so you don’t have to make a decision after a live site error occurs.

Backup and test environment prior to the change

The backup should cover both the website’s files and its database. Note down the current PHP version and record the website’s key operational status. For example, check that the homepage is accessible, that the login works, and that a test order can be completed. After the migration, you can compare the new status with these results.

The test environment should be separate from the live site so that tests and modifications do not affect the website used by visitors. If you create a copy of the site, ensure that operations on the test data and the live database do not get mixed up. Determine the restoration procedure before changing the PHP version: know where the backup is located, how to restore the previous version, and who will carry out the restoration.

Backup and testing reduce the risks associated with changing PHP versions: they help identify errors and provide the option to revert to the previous working state. This is no substitute for careful testing, but it ensures that there is a known recovery path in the event of an unexpected error.

Functional testing and phased roll-out

First, set up the new PHP version in the test environment. Then, don’t just open the home page; try out the website’s key processes as well. The test list should be tailored to the site’s functions and include operations that use the database.

• Pages and navigation: does the home page appear, do the subpages load, and do the links work?
• Forms and login: can a form be submitted, will a confirmation be received, and will login and logout work successfully?
• Databases and transactions: are changes saved, and do processes such as ordering or payment run through to completion?
• Logs and error messages: check the server logs and application messages for any warnings or critical errors.

If the tests have gone smoothly, switch the live website over at a pre-determined time, then repeat the key checks. In the event of an error, reverting to the previous version may serve as a temporary recovery measure, but it is not a long-term security solution, as it does not address the risk posed by an unsupported runtime environment. To manage PHP settings, explore the options available in cPanel hosting. Before making any changes, ensure you have a backup and a testing plan in place.

Where can the PHP version be managed, and what kind of hosting environment can help?

Where you can set the PHP version depends on your hosting environment and its configuration. With shared web hosting, the service settings determine which PHP versions are available. The cPanel interface may provide access to the hosting settings. With a VPS, managing the server environment typically requires greater access and more technical expertise. Neither solution automatically updates the website’s code.

cPanel hosting or VPS: what changes in PHP handling?

cPanel is a graphical web hosting control panel that allows you to manage settings related to your hosting account. The exact options available depend on the specific environment. A VPS provides a dedicated, more flexible server environment; however, the settings and operational tasks may require a higher level of expertise. VPS hosting can be a suitable solution where direct access to the server and flexibility in configuration are important.

Environment	Its role in PHP processing	What should you look out for?
Shared web hosting	PHP settings are determined by the capabilities of the specific hosting environment.	Check the available versions and the settings for your website.
cPanel	It allows you to manage your hosting settings via a graphical interface.	The cPanel interface does not, in itself, determine which PHP versions are available.
VPS	It provides a dedicated server environment, the configuration of which can be adjusted more flexibly.	Do bear in mind the operational knowledge required for server configuration.

What factors should you consider when choosing a runtime environment?

Make your decision based on the application’s PHP requirements, the level of access required and the operational expertise available. If the application’s requirements are compatible with the PHP version and settings available on the hosting service, the web hosting may be suitable. In the case of a custom server configuration, you should also consider who will manage and keep the environment up to date.

The end of support for PHP 8.2 does not, in itself, justify switching hosting providers. Changing the environment will not make old plugins, templates or custom code compatible, nor does it replace a secure update plan. First, clarify your website’s requirements, then choose a runtime environment that suits these requirements and your operational practices. If your application does not require custom server configurations, you may find a suitable environment amongst aWh’s web hosting solutions.

Plan your next upgrade now

The end of support for PHP 8.2 is a good opportunity to treat your website’s runtime environment not as a one-off version upgrade, but as a regularly reviewed operational task. Make sure you know who is responsible for the PHP settings, where the backups are stored, and how to check that the website’s key functions are working properly after the update.

When choosing a hosting environment, in addition to your application’s requirements, you should also consider the operating model and the security features available. With over 10 years’ experience in web hosting, aWh offers web hosting, cPanel and VPS solutions. Backups and HTTPS are important aspects of website security, but they are no substitute for an up-to-date runtime environment and compatibility testing.

Compare the options that suit your needs and take a look at aWh’s web hosting solutions. The well-thought-out, monitored update plan helps keep your website up to date.

Frequently asked questions about PHP 8.2 support

When exactly will security support for PHP 8.2 end?

Security support for PHP 8.2 will end on 31 December 2026. This is the end-of-support date, not the date of the version’s initial release. You can check the lifecycle details in the official PHP table, and it is worth keeping an eye on any future changes. If your website is still using this version, plan your migration before the end-of-support date to allow sufficient time to check for compatibility.

Will my website go down when support for PHP 8.2 ends?

No, the end of support does not in itself take the website offline. The site may continue to run, but no new official security patches will be released for that version of PHP. Whether it continues to function depends on the code, the hosting configuration and the application’s dependencies. The homepage, for example, may remain accessible, whilst a plugin or server setting causes an error.

Can you continue to use PHP 8.2 after support ends?

Technically, yes, provided that the hosting environment continues to support its use. However, once support for PHP 8.2 ends, no official patches for newly discovered PHP vulnerabilities are expected for this version. You should therefore not regard continued use as a long-term solution. If you decide to stick with it for the time being, assess the risk to the affected websites and draw up a specific upgrade plan.

How can you check the PHP version in cPanel?

Log in to your cPanel interface and locate the setting for managing the PHP version. The name and location of this menu item may vary depending on your hosting configuration, so please ensure you are viewing the settings for the correct domain. If you have multiple websites, please check each one individually. Do not share screenshots containing passwords, login details or server information publicly.

Which version of PHP should you upgrade to from PHP 8.2?

Choose a supported version that is compatible with your application, plugins and custom code. As of October 2026, PHP 8.5 is the latest stable release, whilst PHP 8.4 remains a supported, stable option. The latest version is not automatically the right choice for every website. First, check the compatibility of dependencies, then try out the version in a test environment.

Is the PHP version on the website automatically updated on the hosting account?

Not necessarily. The management of the PHP version depends on the hosting provider and its settings; there is no automatic upgrade rule that applies to all environments. Nor will your website’s content management system, plugins or code be updated simply because the hosting provider’s PHP version changes. Check the current setting in the control panel, and plan the switch by taking a backup beforehand and testing your website’s functionality.

• php
• release
• cpanel
• backups
• website security