How to Update the PHP Version in Plesk (Safely, Per

Why Outdated PHP Is a Security Risk

Security first, speed and features second.

PHP versions live roughly two years of active support plus one of security-only patches — after that, nothing, ever. Every unpatched CVE in an EOL version is public, weaponised and scanned for at industrial scale; running PHP 7.4-class code in 2026 is hosting a known target.

The secondary costs compound: each generation brings measurable performance gains (JIT, engine optimisations) — sites routinely report 20–40 percent faster on current PHP with zero code changes — and modern frameworks require 8.x floors, so old PHP blocks the tools you will want next.

The test-before-you-trust sequence below makes the upgrade a five-minute risk instead of a gamble: compatibility check, change, verify, one-click rollback.

Big jumps deserve a rehearsal — the staging guide sets one up.

Step 1: Check Plugin and Theme Compatibility

Three steps, with a rollback path:

1. Check compatibility — inventory plugins and themes first: note anything old or unmaintained; WordPress sites get a plugin health scan.
2. Change PHP — Plesk → Websites & Domains → PHP Settings for the domain → select a current 8.x version from the dropdown → OK. The change applies to that domain only.
3. Test and roll back if needed — front and inner pages, wp-admin, forms and checkout; any white screen and the same dropdown puts the old version back in seconds.

Plesk's per-site PHP is the upgrade superpower: the store runs 8.5 while a legacy site keeps its older version until its rebuild. The Plesk hosting plans ship current PHP lines ready per domain.

Step 2: Change PHP in Plesk PHP Settings

On PHP 8.x versions, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 3: Test and Roll Back if Needed

Test and Roll Back if Needed. Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Running Mixed PHP Versions Across Sites

Two practical notes on per-site PHP selection: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.