This is a research guide based on cited documentation. It is not a report of firsthand testing. Our editorial method

The upstream calendar

Every host policy hangs off PHP's own support calendar. As of 30 October 2026, php.net lists four supported branches. 8.2 is in its final security-only period and reaches end of life on 31 December 2026. 8.1 reached end of life on 31 December 2025, 8.0 on 26 November 2023 and 7.4 on 28 November 2022.

For a course site this matters because LMS plugins track the same calendar. LifterLMS says it supports all PHP versions receiving active and security support and recommends PHP 8.3. A site on 8.2 today has about two months before upstream security fixes stop.

PHP branchActive support untilSecurity support until
8.231 Dec 202431 Dec 2026
8.331 Dec 202531 Dec 2027
8.431 Dec 202631 Dec 2028
8.531 Dec 202731 Dec 2029
8.1End of life31 Dec 2025
7.4End of life28 Nov 2022

Host-by-host policy

The table summarises each host's documentation. Where a page does not state a default or a notice period, the table says so rather than guessing.

HostVersions documentedEnd-of-life handlingNotice describedOpt-out
Kinsta7.4, 8.0, 8.1, 8.2, 8.3, 8.4, 8.5; oldest officially supported is 8.1Automatically upgrades to the latest supported version when a version reaches end of lifeMyKinsta notification when the update completes; advance notice period not statedChoosing an LTS version disables automatic updates; LTS versions get security patches only
WP Engine7.4, 8.2, 8.4; 8.4 beta support only for WordPress 6.7 and newerRemoves end-of-life versions and upgrades all sitesTechnical contacts emailed several times before the changeNone: automatic upgrades cannot be deferred; temporary extended support offered for 7.4
SiteGroundNot listed on the pages reviewed; check Site Tools > Devs > PHP ManagerManaged PHP periodically moves sites to a new server default once SiteGround considers it matureSchedule and notice not statedSelect a PHP version manually or switch Managed PHP off per site
Liquid Web managed VPS (cPanel, Plesk, InterWorx)Whatever is installed on your server; docs point to php.net's timelineNo automatic end-of-life migration describedNot statedYou change versions in EasyApache 4 and MultiPHP Manager, Plesk or InterWorx
KnownHostWeb hosting lists 5.6 through 8.5; WordPress plans list 8.2WordPress hosting page says KnownHost handles PHP updatesNot statedNot stated

What forced upgrades mean in practice

WP Engine is the clearest case. Its supported list includes 8.2, its policy upgrades every site when a version reaches end of life, and upstream security support for 8.2 ends on 31 December 2026. A course site on 8.2 at WP Engine should therefore plan to be on 8.4 soon, whether or not it chooses the date. WP Engine has not published a date for this on the pages reviewed; the inference comes from combining its policy with php.net's calendar.

Kinsta's auto-upgrade is on by default and goes to the latest supported version, not the next one. A jump from an old branch straight to the newest is a bigger compatibility step than most site owners would choose, which is why some pick an LTS version, accepting security-only patches and the reduced performance Kinsta warns about.

SiteGround's Managed PHP is gentler: it moves the server default and leaves sites with a manually selected version alone. The risk there is the opposite one: a pinned version that nobody revisits.

Testing tools each host offers

WP Engine's PHP Test Driver previews the site on another PHP version for your browser only, while visitors keep the live version, and each environment can run its own version, so staging can be upgraded first. Kinsta lets you change PHP per site or in bulk across sites including staging, and an update usually takes about three minutes. On a Liquid Web cPanel VPS, MultiPHP Manager assigns versions per domain, so you can run a staging domain on the new version alongside production and roll back the same way.

  • Upgrade staging first and walk through enrolment, checkout, a lesson, a quiz and certificate generation.
  • Check the PHP error log for deprecation warnings from the LMS, membership and payment plugins.
  • Confirm every premium plugin's changelog lists the target PHP version.
  • Keep the host's technical contact email current so upgrade notices reach someone.
  • Book the production change for a low-traffic window, not the morning of a cohort start.

Who should care most

Sites with older premium add-ons, custom code or abandoned plugins are most exposed to forced upgrades, because a version jump can break them without warning to students. If that describes your stack, prefer a host that lets you test on staging with the target version and gives advance notice, and do the upgrade yourself before the host does it for you. Sites running current plugins on 8.3 or 8.4 can mostly let automatic upgrades happen, provided staging tests run first.

Questions before you decide

When does PHP 8.2 reach end of life?

php.net lists security support for PHP 8.2 until 31 December 2026. Active support ended on 31 December 2024.

Can I stop WP Engine from upgrading PHP?

No. WP Engine says that when a PHP version reaches end of life it automatically upgrades all websites and that automatic PHP upgrades cannot be deferred. It emails technical contacts several times beforehand.

Does Kinsta upgrade PHP automatically?

Yes, by default. Kinsta says that when a PHP version reaches end of life it upgrades the site to the latest supported version, and that selecting a Long-Term Support version disables automatic updates.

How do I stop SiteGround changing my PHP version?

SiteGround says Managed PHP can be switched off per site in Site Tools, and that if you manually select a PHP version it will not be updated automatically.

Sources & verification

Product details and prices can change. Check the linked provider before buying.

  1. PHP: supported versions Accessed 30 Oct 2026
  2. PHP: unsupported branches Accessed 30 Oct 2026
  3. Kinsta docs: PHP Accessed 30 Oct 2026
  4. Kinsta docs: restart and update PHP Accessed 30 Oct 2026
  5. WP Engine: PHP version guide Accessed 30 Oct 2026
  6. WP Engine: PHP on WP Engine Accessed 30 Oct 2026
  7. SiteGround KB: what is Managed PHP Accessed 30 Oct 2026
  8. SiteGround KB: check which PHP version is running Accessed 30 Oct 2026
  9. Nexcess documentation (Liquid Web): PHP versions and why they matter Accessed 30 Oct 2026
  10. KnownHost: compare web hosting plans Accessed 30 Oct 2026
  11. KnownHost: compare WordPress hosting plans Accessed 30 Oct 2026
  12. KnownHost: WordPress hosting Accessed 30 Oct 2026
  13. LifterLMS: minimum system requirements Accessed 30 Oct 2026

Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.

Your decision at a glance

Compare the options

Full comparison

Documentation-based guidance. No tested ranking or performance score.

Hosting

Liquid Web

Consider it for
Use Liquid Web when the job is a defined managed-server responsibility and the quoted plan lists which server tasks they own versus yours.
Starting cost
Quote-dependent; VPS commonly $10–$100 and managed configurations can exceed $100 per Liquid Web's cost explainer (2026-09-15)
Before you choose
Not a fit until the failing component is identified. Management does not include application debugging unless the written scope says so.

Checked 15 Sep 2026 · Pricing source

View Liquid Web plans

Direct provider link; no affiliate tracking added by this publication. Link disclosure

Managed WordPress

Kinsta

Consider it for
Use Kinsta Single 20GB, listed at $35/month, when a WordPress course site needs published PHP-capacity controls and a staging rehearsal.
Starting cost
Single 20GB listed $35/month on 2026-09-15; first-month promotions and annual billing change the cash invoice
Before you choose
Do not treat visitor allowances as class concurrency. No plan here is verified for a specific learner count.

Checked 15 Sep 2026 · Pricing source

View Kinsta plans

Direct provider link; no affiliate tracking added by this publication. Link disclosure

Managed WordPress

WP Engine

Consider it for
Use WP Engine Essential when the quoted plan covers your plugin stack, membership cache rules, and an isolated staging copy.
Starting cost
Essential 1-site card displayed $336/year on 2026-09-15 with promotional first-year pricing; confirm undiscounted checkout
Before you choose
Skip if you cannot rehearse membership access and payments at the destination. No measured speed advantage is claimed.

Checked 15 Sep 2026 · Pricing source

View WP Engine plans

Direct provider link; no affiliate tracking added by this publication. Link disclosure

Shared hosting

SiteGround

Consider it for
Use SiteGround StartUp, advertised at $2.99/month for a prepaid first 12 months then $17.99/month, when one WordPress site needs shared hosting rather than a server you administer.
Starting cost
StartUp first-term $2.99/mo prepaid 12 months, renews $17.99/mo on 2026-09-15 (world page: ex. VAT); 1 website, 10GB, ~10,000 visits marketing estimate
Before you choose
Visit marketing estimates are not class concurrency. Renewal is $17.99/mo after the prepaid term. No course-capacity test is claimed.

Checked 15 Sep 2026 · Pricing source

View SiteGround plans

Affiliate link: we may earn a commission on an eligible purchase. Link disclosure