PHP hosting availability in 2026: what the documentation proves
Four official sources support the availability of modern PHP, but they do not certify a particular hosting account for an accounting application.
Key takeaways
Availability is a chain of claims: supported by a platform, installed by an operator, enabled for a plan and compatible with an application.
- Plesk and cPanel documentation show support for current PHP branches.
- Hostinger's documentation identifies PHP 8.3 as its new-site default but contains conflicting wording about 8.2.
- SiteGround's 2024 default announcement is historical evidence, not a current account inspection.
- PHP availability alone says nothing conclusive about MySQL 8.4, private configuration or recovery access.
Method and verification boundary
This is a representative documentation check, first recorded on 15 September and refreshed on 16 September 2026.
We read two control-panel documentation sources and two hosting-provider sources. This is a convenience sample selected to examine deployment claims, not a random sample of hosting accounts. No provider account was purchased, inspected or changed. We did not measure market share, default versions across installed servers, latency or uptime. We also did not run PHP Ledger on each named provider. The findings should be quoted with these limits.
The question is deliberately narrow: does official documentation support the proposition that PHP 8.2 and 8.3 are available in familiar hosting environments? The answer is broadly yes, with plan-level uncertainty and one documentation conflict. The separate PHP version compatibility guide explains application deployment choices. This research page concentrates on the evidence method, provenance and gaps rather than repeating installation instructions.
What did the four sources say?
The sources describe different things, so their statements should not be combined into a single market-wide default.
| Source | Observed statement | What it does not establish |
|---|---|---|
| Plesk installer version list | Lists PHP 8.2, 8.3, 8.4 and 8.5 for supported systems | That a host installed or enabled a specific handler for your account |
| cPanel EasyApache PHP documentation | Documents 8.1–8.5 availability and 8.1/8.2 in the default profile | That every operator uses that profile or grants every version to every plan |
| Hostinger PHP configuration | Names 8.3 as the new-site default; wording about selectable 8.2 conflicts | Reliable confirmation of 8.2 on an individual subscription |
| SiteGround's 2024 announcement | Describes its rollout of 8.2 as a default | That the default remained unchanged through this check date |
Why is the Hostinger wording left unresolved?
The same page describes selectable 8.2 and elsewhere labels 8.2 unavailable, so a plan-level check is necessary.
It would be misleading to choose whichever paragraph best supports a preferred minimum. The new-site section clearly names PHP 8.3 as the default. The 8.2 selection question remains unverified for an actual account because another paragraph describes 8.2 and lower as deprecated and unavailable. This is a documentation inconsistency, not evidence that the service is broken. A prospective operator should obtain confirmation for the specific subscription and verify the actual runtime before installation.
Documentation changes can also affect existing accounts differently from new ones. A screenshot in a help article may illustrate one account state rather than a universal option. Preserve the provider's answer and the measured runtime in your acceptance record. Do not attempt a configuration workaround merely to force an old version onto a plan whose supported behavior is unclear.
How do upstream security dates affect the choice?
A branch can satisfy the application's minimum while offering less remaining upstream security-support time.
The PHP supported-version schedule, checked on 16 September 2026, lists security support through 31 December 2026 for PHP 8.2 and through 31 December 2027 for PHP 8.3. These are upstream branch dates, not a promise about a provider's patch schedule or extended-support contract. They support planning an upgrade before the end of a chosen branch's maintenance period.
A runtime floor and a recommended deployment version serve different purposes. The floor defines what the application accepts. The recommendation can favor a supported version with more remaining maintenance time. Neither statement justifies running an old patch release. Use the current approved patch level for the selected deployment and retest changes in an isolated environment. Keep the web runtime and command-line runtime in the same review because providers can expose different binaries for each.
What else must be measured on the actual plan?
Check the database, extensions, routing and private storage before treating the installation as compatible.
- Identify the actual PHP version used for both web requests and command-line maintenance.
- Confirm required extensions rather than assuming they follow from the PHP version.
- Record the database product and exact version.
- Verify the public document root, HTTPS and front-controller routing.
- Confirm private configuration, session storage, backup export and restoration access.
- Assign an operator for updates and recovery.
This is an acceptance checklist, not a set of instructions to alter a hosting account. For PHP Ledger, use the package requirements and its documented preflight. A provider offering only MariaDB has not established compatibility with the validated MySQL 8.4 profile. Similar protocol support or branding does not replace an application test.
What does a useful evidence record contain?
Record the source claim and the actual measured installation separately so later readers can see the gap between them.
- Platform support
- A control panel can install or configure a particular runtime on supported systems.
- Plan availability
- The operator permits that runtime and associated requirements on the purchased account.
- Application compatibility
- The complete application and database pass the relevant checks in that actual environment.
Published platform support → plan confirmation → measured runtime → application preflight → restored trial
Keep the check date, account type, runtime output and test result with the release being evaluated. Redact credentials and private host identifiers before sharing evidence. If the application is upgraded later, a previous compatibility result remains historical rather than automatically carrying forward. Repeat the checks affected by the change, including database privileges when migrations introduce new schema objects.
When is this study not enough?
It cannot select a hosting provider or guarantee an accounting deployment without an actual plan and tested package.
We have not measured service quality, support response, pricing, tenant isolation or restore speed. No provider ranking is offered. The current PHP Ledger preview is a bounded AR/AP starter with optional one-location Inventory and manual tax; advanced workflows and regional filing remain outside its scope, so a compatible server does not establish business suitability. The FrontAccounting comparison and Dolibarr comparison illustrate why shared PHP deployment language does not imply equivalent requirements or workflows.
Questions and recommendation
Use this study to ask a provider precise questions, then verify the actual installation before depending on it.
Does this prove most shared hosts run PHP 8.3?
No. Four documentation sources are not a representative market survey, and documented availability is not installed usage.
Can a 2024 default announcement support a 2026 default claim?
Only as historical evidence unless the current state is independently confirmed. This study does not assume the default stayed unchanged.
Read the accounting-software research survey and bookkeeping evidence study for related questions about deployment and actual use. Prefer a documented, supported environment with a working recovery procedure over an unsupported claim that an application runs anywhere.
Primary source register
These official documents were checked on 16 September 2026; the provider and platform claims retain the limits stated above.
- Plesk installer version list ? platform availability.
- cPanel EasyApache PHP documentation ? supported versions and profiles.
- Hostinger PHP configuration ? default and unresolved selection wording.
- SiteGround PHP 8.2 announcement ? historical rollout.
- PHP support schedule ? upstream branch maintenance dates.