To change your PHP version without breaking WordPress, update core, themes, and plugins first, then switch PHP in your hosting panel. PHP is the server software that runs WordPress code, so test the new version in staging and keep a backup for revert. WordPress.org recommends hosts run PHP 8.3 or greater with MySQL 8.0 or MariaDB 10.11 or newer. The PHP Group's current supported-versions schedule leaves only 8.2 through 8.5 supported in late 2026, so 8.3 or newer is the practical target.
Table of Contents
- Which PHP version should you target?
- Where do you check your current PHP version?
- How do you prepare safely?
- What is the safe switching sequence?
- Why do PHP upgrades break sites?
Which PHP version should you target?
Choose PHP 8.3 or newer for a live WordPress site. Older branches still run WordPress but are end-of-life and may expose the site to vulnerabilities.
Make WordPress Core lists WordPress 7.0 and 7.1 as requiring at least PHP 7.4 and compatible with PHP 7.4 through 8.5. WordPress 7.0 dropped support for PHP 7.2 through 7.3, so very old themes and custom code may need fixes.
Where do you check your current PHP version?
Open wp-admin and go to Tools, then Site Health, then Info, then Server. WordPress.org Documentation explains the active version appears in its Site Health screen guide under that Server section.
Use the same screen to review the server setup before a change. Export the full technical details when troubleshooting, especially if a host or developer asks for them.
How do you prepare safely?
Create a complete backup of both database and files before upgrading. WordPress Developer Resources advise testing in a separate staging environment before changing production.
Keep PHP configurable separately for staging and production. Update WordPress core, themes, and plugins in staging first, then change only the staging PHP version and test.
What is the safe switching sequence?
Hosting guides such as WP Rocket describe the same order: update everything first, switch PHP second, verify third. The hosting control panel usually offers the change under MultiPHP Manager or Select PHP Version in cPanel.
Do the production switch during a quiet period. Keep the backup and know the revert setting in advance.
- Back up files and database.
- Update WordPress core, themes, and plugins.
- Switch PHP in staging, then in the hosting panel for production.
- Check Site Health, home and key pages, forms and checkout, then clear cache.
Why do PHP upgrades break sites?
Themes and plugins built for older PHP can trigger a fatal error on newer PHP. One outdated plugin, theme function, or custom snippet can bring down the whole front end.
Automated PHP-compatibility checkers are not fully accurate, according to WordPress Developer Resources. Treat staging tests plus an immediate revert or backup-restore plan as required, not optional.
