Walkthrough · Beginner · 10 minutes
How to Change Your PHP Version
How to move your sites onto a quicker, still-supported PHP release without anything falling over, without the guessing — the steps in order, the snag ahead of time, and the tip our support team repeats daily.
The short answer
One line covers it: move your sites onto a quicker, still-supported PHP release without anything falling over — a beginner-level job of roughly 10 minutes.
Below are the precise steps, the classic stumble, and one tip from the support desk. Wherever the platform already does a step for you, the guide says so rather than handing you a machine's chores.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Experience required
5
Stages, start to finish
Free
Support included
Proven
On the platform itself
No prior knowledge assumed — a hosting account, a browser and 10 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.
First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.
The whole job in one view
Set out end to end, the route is: check the current version for each domain, make sure your software is ready, change the version, then browse the site, roll back if something objects and fix whatever complained, then try again.
Every stage is a few minutes of unhurried clicking — the total depends mostly on how well you already know the control panel. The detailed instructions are further down; read the whole path once before you begin.
One caution before you click anything
Sitting on an end-of-life PHP build because nothing appears broken. Once support ends the security patches stop, so the stability you think you are protecting is the stability of unpatched vulnerabilities.
It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.
A habit worth borrowing
Measured in speed per pound, nothing in hosting is better value than moving up a PHP release. WordPress benchmarks appreciably faster on 8.x than on 7.4, and the whole job is one dropdown and a walk through your pages.
A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.
Where this platform takes work off you
Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.
Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.
Why this job is shorter on our plans
Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.
Order an annual plan and the first year of the name's registration is on us.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
The snag, flagged up front
The classic error for this particular task is named before step one, which is how 10 minutes stays 10 minutes.
Jargon never charges you
Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.
Honest about how big it is
Move your sites onto a quicker, still-supported PHP release without anything falling over is a beginner-level job — set aside 10 minutes, with the platform-absorbed steps marked.
The dull parts automated
SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Quick Start
Order placed to site online
- 1
Check the current version for each domain
The PHP selector in the panel shows what each domain runs. Sites brought in from elsewhere are often several releases behind where they could comfortably sit.
- 2
Make sure your software is ready
Current WordPress core copes with modern PHP perfectly well; the exposure is in ageing plugins and themes. Read their tested-up-to notes, or simply lean on the next step.
- 3
Change the version, then browse the site
Pick the new release and click through the pages that matter. It takes effect immediately, so anything incompatible complains inside a couple of minutes.
- 4
Roll back if something objects
Reversing it takes the same dropdown and the same few seconds. A failed attempt costs two minutes, which is exactly why testing beats a year of hesitation.
- 5
Fix whatever complained, then try again
The error message names the component that could not cope. Update or replace it, run the version change again, and see it through.
Built In
Fitted to every plan
- Money back within 30 days on hosting plans, 7 on reseller
- Spam and virus screening on every mailbox by default
- The name's first year included when you order annually
- A renewal figure identical to the one you registered at
- People on the support desk every hour of every day
- NVMe SSD storage on every tier, not only the dear ones
- Your existing site brought across by our engineers, at no charge
- A daily copy, with restores you run yourself from the panel
- DDoS filtering absorbed at the network edge
- SSH, Git and Composer on the developer plans
Frequently Asked
The questions that come up most
How likely is a PHP change to break my site?
On a well-maintained site, very unlikely. The danger sits in abandoned plugins and elderly themes. Since the selector reverts instantly, the practical test is to switch and click around, though an online shop should rehearse on staging first.
Can different sites on one account run different PHP releases?
They can. PHP is set per domain, so one stubborn legacy site can stay put while the rest move on. Treat that as a bridge towards upgrading it rather than a permanent home for stragglers.
Do plans include copies I can restore myself?
Yes — every plan gets a daily copy, and the restore runs from your panel in minutes: files, databases or both, at three in the morning with no ticket queue in the way. Keeping a further copy offsite is still a sound habit, and nothing here stops you.
Does hosting include mail?
Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.
Keep reading
How to Move a Website to a New Domain
Rebrand onto a new domain while keeping the rankings and the returning visitors — intermediate level, about an afternoon plus monitoring.
How to Migrate Email to a New Host
Relocate mailboxes to a new host with full history preserved and zero losses — intermediate level, about 1–2 hours, or one support ticket.
PHP (Glossary)
The plain-English definition this page rests on, with a worked example.
Drupal Hosting
Drupal with Composer, Drush and per-site PHP control to hand.
PHP Hosting
Set the PHP version per site, on quick NVMe hardware.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
The name is waiting.
NVMe hosting with SSL and the migration included, people answering at any hour, and a price that stays where it was.
View Drupal Hosting plans