Call Get help Menu
  1. ServicesWebsites, care, hosting, search and leads
  2. WorkClient sites and design concepts
  3. Learning CenterGoogle, reviews, AI answers, email and more, step by step
  4. Help CenterAsk E-3 a question, or browse the help guides
  5. AboutLarry Davis, building websites since 1999
  6. ContactStart a project, call or email

814-399-4655support@e3help.me

What PHP version should my WordPress site run?

WordPress recommends PHP 8.3 or newer. On October 31, 2026, PHP 8.4 and 8.5 get full support, 8.2 and 8.3 get security fixes only, and 8.1 and older get none. Check your version in Site Health, then upgrade on a staging copy first, because old plugins and themes can break on newer PHP.

Part of the WordPress for owners guide By Larry Davis, E-3 Design, building small-business websites since 1999 Updated October 31, 2026 · In review

The short version

  • PHP is the programming language WordPress runs on. Your host sets the version.
  • WordPress recommends PHP 8.3 or newer.
  • WordPress 7.0 and later need at least PHP 7.4, but that version is long past its end of life.
  • PHP 8.2 stops getting security fixes on December 31, 2026.
  • Test an upgrade on a staging copy before switching the live site.

What is PHP, and why does the version matter?

PHP turns your WordPress files and database into the pages visitors see. Like WordPress, it gets new versions, and old ones stop getting security fixes. A site on an old PHP version is running code nobody is patching any more, and newer plugins may refuse to install on it.

Which versions are supported right now?

From PHP’s supported versions page, as of October 31, 2026:

PHP versionStatusSecurity fixes until
8.5Full supportDecember 31, 2029
8.4Full supportDecember 31, 2028
8.3Security fixes onlyDecember 31, 2027
8.2Security fixes onlyDecember 31, 2026
8.1 and olderEnd of lifeEnded

WordPress’s requirements page recommends PHP 8.3 or greater, along with MySQL 8.0 or MariaDB 10.11 or newer. It also says WordPress works on PHP 7.4 and up, but calls those older versions end-of-life.

What changed in 2026?

WordPress 7.0, released in May 2026, dropped support for PHP 7.2 and 7.3, per the core team’s announcement. Sites on those versions stay on WordPress 6.9 until PHP is upgraded. They no longer get new WordPress releases, which is a security problem in itself. See how WordPress releases work.

How do I check my PHP version?

  1. Log in as an Administrator.
  2. Go to Tools, then Site Health.
  3. Open the Info tab and expand Server. The PHP version is listed there.

WordPress’s Site Health guide explains the screen. If your PHP is outdated, the Status tab usually flags it too. Your hosting control panel shows the version as well.

How do I upgrade safely?

  1. Take a full backup of files and database.
  2. Update WordPress, plugins and themes first. Newer versions are more likely to work on newer PHP.
  3. Make a staging copy and switch it to the new PHP version. Our answer on staging sites explains why.
  4. Test the pages that matter: home, contact form, booking, store checkout, login.
  5. Switch the live site in your hosting control panel.
  6. Check again, and keep the old version noted in case you need to switch back.

Go one step at a time if you’re far behind. Moving from 7.4 to 8.3 in one jump can surface several problems at once.

Why do hosts send PHP warnings?

Hosts don’t want to run versions that no longer get security fixes. They usually email a deadline, then upgrade sites themselves. A forced upgrade without testing is when sites break. Act on the first email, not the last one.

What are the common mistakes and edge cases?

  • Old, unmaintained plugins. These are the usual cause of breakage on newer PHP. Replace them before the upgrade. See how many plugins is too many.
  • Custom theme code. Older custom themes may use functions newer PHP removed. A developer needs to check them.
  • Upgrading straight to the newest version. Pick a version your plugins say they support. 8.3 or 8.4 is a safe target for most sites in late 2026.
  • Deprecation notices on screen. These are warnings, not errors, but they shouldn’t show to visitors. Ask whoever maintains the site to turn off on-screen errors.

What if the upgrade broke my site?

Switch back to the previous PHP version in your hosting control panel; the site should return. If it shows “There has been a critical error,” WordPress emails a recovery link to the site’s admin address; see what a critical error means. Then find the plugin or theme at fault on staging.

How long does it take?

The switch takes minutes. Testing takes an hour or two on a typical small-business site, longer if a plugin needs replacing.

How does E-3 handle this?

For hosted sites we look after through website care, monitoring tracks each site’s PHP version alongside waiting updates and known plugin vulnerabilities. Speed fixes and other bigger changes are tested on a staging copy first.

Sources

  1. Requirements (WordPress.org)
  2. Dropping support for PHP 7.2 and 7.3 (Make WordPress Core, January 2026)
  3. Supported versions (PHP.net)
  4. Site Health screen (WordPress.org Documentation)

Next step

Still stuck? Ask E-3 for an answer from our help guides.

Rather we handled wordpress for owners for you?

It’s part of what we do every week for small businesses, as part of website care. Start with a free check of your site and profile, or call and ask.

Free website check Call 814-399-4655

Ask E-3

Suggestions appear as you type. Use the up and down arrows to choose one, or press Enter to ask.

Quick actions

Top questions

Topics

EmailWebsite editsSite downDomainsStoreGoogle

Get support