Your hosting panel shows PHP 7.4, 8.1, 8.2, 8.3, and 8.4. WordPress says it supports "modern PHP." Your oldest plugin says "tested up to 7.4." Picking a version should not feel like roulette, but for a lot of site owners it does.
Here is how we think about PHP for WordPress in 2026: what to run, what to avoid, and how to upgrade without breaking checkout on a Tuesday.
What WordPress actually needs today
Current WordPress releases expect a supported PHP branch. Running end-of-life PHP (7.4 and older in 2026) means no security patches from the PHP project. Hosts may force upgrades or leave you exposed.
WordPress.org compatibility targets move forward each year. In practice, PHP 8.2 or 8.3 is the sensible default for production sites in 2026. They are mature, widely supported by plugins, and still receive security fixes.
PHP 8.4 is the newest line. Some hosts offer it already. WordPress core may run fine, but the long tail of plugins and themes lags. Treat 8.4 as "test on staging first," not "flip on live because the dropdown exists."
Why PHP version matters beyond speed
Newer PHP is often faster. That is a nice bonus. The bigger reasons to upgrade:
- Security patches stop on EOL versions
- Hosts deprecate old runtimes and surprise you at renewal
- Modern plugins drop support for PHP 7.x entirely
- Compliance and insurance questionnaires ask what you run
We wrote about the risk side in PHP end of life and your live website. Waiting until the host forces an upgrade is the painful path.
How to choose for your specific site
Standard WordPress + popular plugins (WooCommerce, Yoast, major builders): PHP 8.2 or 8.3 on production after a staging test.
Legacy custom plugin or old theme: Check with the developer before jumping. Scan error logs on staging for deprecated function notices.
High-traffic WooCommerce: 8.2/8.3 plus object cache and opcode cache (OPcache). Version choice matters less than fixing autoload bloat if the database is a mess.
Multisite or agency stack with mixed ages: Upgrade the worst plugin or client site first on staging. One ancient mu-plugin can block the whole network.
The staging test (non-negotiable)
Clone production. Switch PHP version in cPanel or MultiPHP. Then:
- Load homepage, shop, cart, checkout, account login
- Submit contact and order forms
- Open wp-admin, save a post, run a backup
- Check debug.log if WP_DEBUG_LOG is enabled on staging
- Run critical cron or import jobs
Watch for white screens, deprecation warnings turned fatal, and session/cookie issues on PHP 8.x. Fix or replace offending code before touching live.
Common breakage patterns on PHP 8+
- Plugins using removed curly-brace array/string syntax (rare now, still on abandoned code)
- Passing null to internal functions that no longer accept it
- Old serialization or custom session handlers
- Encoding assumptions in ancient themes
Deprecation notices in logs are warnings today and hard failures tomorrow. Do not ignore a staging log full of "Deprecated:" lines.
What about PHP 8.4 specifically?
Early adopters get performance and language improvements. They also get to discover which niche plugins have not caught up. If your stack is boring (core, WooCommerce, Elementor, mainstream security plugin), 8.4 may be fine in late 2026. If you run vertical software (membership, LMS, industry-specific), stay on 8.3 until vendors say otherwise.
When in doubt, 8.3 is the conservative modern choice. 8.2 is still acceptable if a vendor has not certified 8.3 yet, but plan to move before 8.2 approaches end of life.
Hosting panel tips
cPanel MultiPHP lets you set version per domain or directory. Useful when one old subdomain cannot upgrade yet. Do not forget CLI PHP for cron and WP-CLI may differ from web PHP. Run php -v over SSH and match versions intentionally.
After changing PHP, restart PHP-FPM if your host requires it (some panels do this automatically). Clear opcode cache if odd behavior persists.
Bottom line
For WordPress in 2026, run a supported PHP branch (8.2 or 8.3 for most sites), test on staging, fix plugin debt, and treat 8.4 as opt-in when your stack is ready. Staying on 7.4 is not a stability strategy. It is a countdown.
Not sure what your site can handle? Talk with Swift Host. We will check plugin ages, run staging upgrades, and pick a PHP version that matches your actual code, not just the newest number in the dropdown.
