PHP version for WordPress hosting: choose and test safely

Check the PHP version actually running the website

PHP executes WordPress and much of its theme and plugin code. Check the live website’s runtime before choosing a replacement: in WordPress, open Tools, Site Health, then Info and the Server section. Record that version alongside the WordPress, theme and plugin versions you use.

A hosting order’s PHP preference and the version shown by the delivered website are different pieces of evidence. Verify the application environment after access is available. If your project also runs scheduled or command-line tasks, check their runtime configuration rather than assuming every execution path uses the same settings.

Choose between the versions your application supports

VPSLibre website hosting offers PHP 8.3 and 8.4 preferences. Check the current WordPress requirements and the compatibility information for your exact theme, plugins and custom code. WordPress core compatibility does not establish that every extension on your website works with that runtime.

PHP version changes can introduce incompatibilities and deprecated behavior. Use the relevant migration notes when maintaining custom code. Choose the available version that passes the project’s checks; neither the highest version number nor a successful homepage load proves a faster, reliable or fully compatible website.

Check store extensions and application requirements

Prepare a test copy with controlled side effects

Create a recoverable copy of the files and database, and test the proposed PHP version in a separate environment before changing the live site. Use your own test tooling or an agreed hosting arrangement. A staging environment and an instant version-switch control are not established by selecting PHP at checkout.

Protect the test environment and ensure it cannot send live notifications, process real payments or change connected production data. Check the test copy’s URLs, integration settings and scheduled jobs. If it contains customer information, handle access and retained copies according to your project’s data policies.

Isolate a WordPress staging copy before testing PHP changes

Exercise the paths that matter to the project

Repeat the activities your visitors and editors rely on, then inspect the relevant application and PHP error logs. Compatibility scanners and release notes can help identify risks, but neither replaces testing the actual combination of software and settings. Investigate new errors before repeating the change on production.

For WooCommerce, include the store’s complete transaction workflow using safe gateway test settings. A PHP change that leaves product pages visible can still affect checkout, order processing or an integration. Compare the same actions before and after the runtime change so failures have useful context.

• Open important pages and check navigation, search and account logins.
• Create or edit content and verify media upload and image handling.
• Exercise forms and their agreed notification behavior.
• Check scheduled jobs and custom integrations in the isolated test setup.
• Test store checkout and order updates where WooCommerce is used.
• Review new warnings and errors rather than relying only on visible page output.

Plan the change and a usable rollback

Record who can change the live runtime and whether the previous version remains available for recovery. Take a current backup and choose a maintenance window appropriate to the project. After the agreed change, verify the actual runtime again, repeat the important checks and inspect errors.

If the change fails, diagnose the problem and restore the previous runtime through the available management process where appropriate. A file-and-database restore may also be needed, but avoid overwriting new orders, messages or other live data without a reconciliation plan. A backup and a version rollback solve different parts of recovery.

Prepare recoverable files and database copies before changing PHP

Keep the version decision separate from maintenance promises

For a new hosting order, choose the PHP preference supported by your tested application and keep the compatibility notes. The preference describes the initial configuration request; it does not provide a managed migration, a guarantee for future plugin updates or a promise that the site is already running.

Assign ongoing responsibility for application compatibility and runtime updates. Revisit the test plan when changing themes, major plugins or custom integrations. For a store, use the WooCommerce requirements guide to keep runtime checks connected to the order and payment paths that matter.