Hosting · Guide
How to Check and Change the PHP Version on Your Host
Short answer
To check your PHP version, open Tools, then Site Health, then the Info tab, and expand Server in WordPress. To change it, use your host control panel, such as MultiPHP Manager in cPanel or PHP Manager in SiteGround Site Tools. Pick PHP 8.4 or 8.5 if your plugins support them, and confirm the new version in Site Health after the change.
Key takeaways
- WordPress.org recommends PHP 8.3 or greater, as of November 2026.
- Find your PHP version under Tools, Site Health, Info, Server in WordPress.
- PHP 8.2 loses security fixes on 31 December 2026, and PHP 8.1 gets none.
- Change PHP in cPanel with MultiPHP Manager or in SiteGround Site Tools.
- Back up your site and check plugin support before you change PHP.
- Confirm the new version in Site Health after the change.
What PHP version does WordPress recommend?
WordPress.org recommends PHP 8.3 or greater, with MariaDB 10.11 or greater or MySQL 8.4 or greater, as of November 2026.
WordPress still runs on PHP 7.4 and MySQL 5.5.5, but WordPress.org warns that those versions reached end of life and may expose a site to security flaws. The WordPress minimum requirements page lists the same versions in one place.
The full list sits on the WordPress.org requirements page, which names PHP, the database, and HTTPS support as the three items a host should provide.
| Item | Recommended, as of November 2026 | Still works, but end of life |
|---|---|---|
| PHP | 8.3 or greater | 7.4 and above |
| Database | MariaDB 10.11 or MySQL 8.4 | MySQL 5.5.5 and above |
| Connection | HTTPS support | No secure fallback |
How do you check your PHP version in WordPress?
Open Tools, then Site Health, then the Info tab, and expand the Server section to read your PHP version.
Site Health is built into WordPress 5.2 and later, so no plugin is needed for this check. It shows the PHP version your site truly runs on, which is the number that matters.
Follow these steps in your WordPress dashboard:
- Log in as an administrator.
- Go to Tools > Site Health.
- Click the Info tab at the top of the page.
- Expand the Server section.
- Read the PHP version row.
The Status tab of Site Health also flags an outdated PHP version as a recommended improvement. If you see that warning, plan a change soon rather than leaving it for later.
How do you check your PHP version outside WordPress?
Your hosting panel shows the PHP version too, but it can differ from the version your site runs.
Some hosts set one PHP version for the whole account and a different one per domain. Site Health reads the version that serves your site, so trust it when the two numbers disagree.
A second method is a phpinfo() file, which is useful when you cannot log in to WordPress:
- Create a file named
phpinfo.phpwith this one line:<?php phpinfo(); ?> - Upload it to the folder that holds
wp-config.php. - Visit
yoursite.com/phpinfo.phpin a browser. - Read the version at the top of the page.
- Delete the file at once, since it exposes server details.
From a terminal, php -v prints a version, and wp cli info shows the WP-CLI version. Both can report the command-line PHP, which may not match the web PHP your site uses.
How do you change the PHP version in cPanel?
Use MultiPHP Manager in cPanel to change the PHP version for one domain at a time.
Log in to your hosting account and open cPanel, then scroll to the Software section and click MultiPHP Manager. Tick the box next to your domain, pick the new version from the drop-down at the top, and click Apply.
Bluehost says the site starts running the new version within 5 to 10 minutes after you apply the change. Other cPanel hosts apply it at once or within a few minutes, so check Site Health after a short wait.
If your host uses CloudLinux, the tool may be called Select PHP Version instead. Pick the version from the list, then click Set as current to apply it.
How do you change the PHP version in SiteGround and Hostinger?
SiteGround and Hostinger each put the PHP setting in their own dashboard, not in cPanel.
On SiteGround, go to Websites, click Site Tools next to your site, then open Devs > PHP Manager. Click the pencil icon next to Change PHP version, pick Managed PHP or a version by hand, and click Confirm.
Managed PHP means SiteGround moves your site to a newer, stable version it has checked. A manual choice stays put until you change it again, so note the date and revisit it.
On Hostinger, go to Websites, open the Dashboard for your site, then go to Advanced > PHP Configuration. Pick the version under PHP version, click Update, and confirm the change.
Hostinger notes that the change affects all sites on the same plan, except sites built with its AI Builder. It also resets PHP extension values to their defaults, so check any custom extension settings after the change.
Which PHP version should you pick?
Pick PHP 8.4 or 8.5 for most sites, as of November 2026, if your theme and plugins support them.
PHP 8.4 stays in active support until 31 December 2026, with security fixes until 31 December 2028. PHP 8.5 stays in active support until 31 December 2027, with security fixes until 31 December 2029.
The PHP project gives each branch two years of active support, then two more years of security fixes only. After four years, the branch reaches end of life and gets no more fixes.
| PHP branch | Status, as of November 2026 | Security fixes until |
|---|---|---|
| 8.2 | Security fixes only | 31 December 2026 |
| 8.3 | Security fixes only | 31 December 2027 |
| 8.4 | Active support | 31 December 2028 |
| 8.5 | Active support | 31 December 2029 |
| 8.6 | Active support, released 19 November 2026 | 31 December 2030 |
PHP 8.2 loses security fixes on 31 December 2026, so do not pick it for a new site. PHP 8.1 and older already get no fixes at all, so a site on those versions should move soon.
If you are unsure about plugin support, pick PHP 8.4 first. It has the longest track record of the two active branches, and WordPress PHP compatibility explains which WordPress versions work with each PHP branch.
What should you do before you change PHP?
Back up your site first, then check that your theme and plugins support the new version.
A backup lets you restore the site in minutes if a plugin breaks on the new PHP version. Use your host backup tool or a backup plugin, and confirm the backup finished before you change anything.
Check each plugin and theme for a stated PHP requirement on its WordPress.org page. The guide to updating PHP in WordPress walks through the same safety steps in order.
Test on a staging copy when your host offers one. Change PHP on staging, click through key pages, submit a form, and place a test order if you run a store.
How do you confirm the change worked?
Go back to Tools, then Site Health, then Info, then Server, and read the PHP version row again.
The row should now show the version you picked. If it still shows the old version, wait a few minutes, clear any server cache, and check again.
Then click through your site as a visitor would. Open the home page, a post, a contact form, and the checkout page if you have one, and watch for blank pages or error text.
If a page breaks, switch PHP back to the old version in the same panel and note which plugin caused the fault, then work through the common errors one by one, starting with the plugin you changed most recently.
What mistakes should you avoid?
Do not jump from a very old PHP version straight to the newest one without checking plugin support.
A jump from PHP 7.4 to 8.5 can break old plugins that were never updated for newer PHP. Move one step at a time, such as 7.4 to 8.2, then 8.2 to 8.4, and check the site after each step.
Do not leave a phpinfo.php file on your server after you finish. It lists server settings that an attacker can use to plan an attack, so delete it the same day.
Do not change PHP on a live store during a busy period. Pick a quiet hour, warn your team, and keep the backup close so you can restore it fast.
Do not trust the command-line version alone. The php -v result can differ from the version that serves your site, so always confirm in Site Health.
Frequently asked questions
Can I change the PHP version from the WordPress dashboard?
No, WordPress shows the version but cannot change it. The change happens in your hosting panel, such as MultiPHP Manager in cPanel or PHP Manager in SiteGround Site Tools. After the change, confirm the new version under Tools, Site Health, Info, Server.
What happens if a plugin breaks after a PHP change?
Switch PHP back to the old version in the same panel, then check which plugin failed. Update or replace that plugin before you try the new version again. A staging copy lets you find the fault without breaking the live site.
Is PHP 8.3 still safe to use in late 2026?
Yes, PHP 8.3 gets security fixes until 31 December 2027, so it is safe for now. It left active support at the end of 2025, so plan a move to PHP 8.4 or 8.5 during 2027. WordPress.org still lists PHP 8.3 as its recommended minimum.
How long does a PHP version change take?
The switch itself takes a few minutes on most hosts. Bluehost says a site starts running the new version within 5 to 10 minutes of applying the change. Allow extra time to click through your pages and confirm nothing broke.
Do I need to update WordPress before I change PHP?
Update WordPress and your plugins first when you can, since newer releases support newer PHP versions. Old plugins are the most common cause of a broken site after a PHP change. If an update is not possible, pick a smaller PHP step and check the site after it.
Sources
- Requirements WordPress.org
- PHP: Supported Versions The PHP Group
- How to Update PHP Version: Manage php.ini and PHP Handlers Bluehost
- What Is Managed PHP Service and How to Enable It? SiteGround
- How to change your PHP version Hostinger
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
