Quick answer
Change PHP only after checking the application, plugins, theme, and dependencies against the intended version. A newer PHP version can improve supportability, but incompatible code can fail immediately. Test on a staging copy and record how to return to the previous setting.
Before you start
Use an account with the relevant PHP controls and confirm the exact domain. Take current file and database backups and note the active PHP version, extensions, and application requirements.
What to do
- Check the application's current compatibility guidance and update unsupported dependencies through a reviewed staging workflow.
- Choose the target domain in the available PHP manager and test the intended version on staging first.
- Exercise login, forms, scheduled tasks, commerce, and any custom integrations, then inspect error logs for new failures.
- Apply the approved setting to production during an appropriate window and verify the same critical behavior. Keep the previous supported setting available for recovery when the platform permits it.
Check the result
Confirm the effective PHP version used by the website and by any scheduled CLI task, since these can differ. Do not leave a public phpinfo file behind as a diagnostic artifact.
If something does not work
If a change breaks the site, restore the previous supported setting and investigate the exact error. Do not silence all errors or disable security controls as a substitute for compatibility work.
Related help
- Understand PHP memory and upload limits before raising them
- Use website error logs to diagnose a failed request
- Update a WordPress plugin with a clear rollback plan
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
