Walkthrough · Intermediate · 20–40 minutes
How to Fix the WordPress White Screen
Identify what's producing the blank page and clear it step by step — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: identify what's producing the blank page and clear it step by step — a intermediate-level job of roughly 20–40 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
Intermediate
Skill rating
20–40 minutes
Time budget
5
Steps in total
24/7
Support on call
No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.
A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.
The outline first, then the detail
Over the whole job, you will get the hidden error on screen, begin with the last thing you changed, turn the plugins off from outside, fall back to a stock theme and rule out the dull explanations.
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
Changing three things at once and hoping. The site comes back, nobody knows which change did it, the real fault is still there, and it returns punctually at the next update.
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.
What we tell every customer
The error log turns twenty minutes of guessing into thirty seconds of reading. The logged line names the file and the function, and that file's folder names the plugin responsible.
A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.
What a Hosting & Domains plan spares 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.
A quick platform makes for a short guide
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
NVMe storage and LiteSpeed caching sit under every tier, the smallest plan included — that is the floor here, not an upgrade.
- 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 dull parts automated
SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Works exactly as printed
Every step is proven on the platform we run — none of the 'your host may vary' hedging.
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
Taken from real tickets
These guides came out of the support queue, so every snag flagged is one people genuinely hit.
Quick Start
Order placed to site online
- 1
Get the hidden error on screen
Set WP_DEBUG and WP_DEBUG_LOG to true inside wp-config.php, or go and read the server error log in cPanel. A white screen is a fatal error with its message suppressed, so the first job is reading that message.
- 2
Begin with the last thing you changed
A blank page nearly always follows an action: an update, a new plugin, a template edit. Whatever you did most recently stays the prime suspect until the log clears it.
- 3
Turn the plugins off from outside
Rename wp-content/plugins in File Manager and every plugin drops at once. Site back? Rename it again and reactivate them one by one until the guilty one owns up.
- 4
Fall back to a stock theme
Plugins ruled out? Rename the active theme's folder so WordPress falls back to a bundled default. A fatal error inside a theme looks identical from the outside.
- 5
Rule out the dull explanations
PHP memory exhausted, a mangled .htaccess, an update that died halfway. Raise the memory limit, rebuild .htaccess by re-saving permalinks, or run the update again, in that order.
Built In
Fitted to every plan
- WordPress and 400+ further applications installed in one click
- A daily copy, with restores you run yourself from the panel
- WebP image optimisation built in, at no extra charge
- Upgrades applied in place, with no migration when you change plan
- 99.9% uptime as the target, watched around the clock
- No set-up charge at any point, and no joining fee
- Softaculous included for one-click application installs
- Spam and virus screening on every mailbox by default
- Mailboxes that answer at the name you hold
- Money back within 30 days on hosting plans, 7 on reseller
Frequently Asked
The questions that come up most
Why is there nothing on screen instead of an error?
Production PHP hides error output on purpose, since error text shows your stack to anybody watching. The fatal error occurred all the same, with its message routed to the log instead of the browser. Debug mode simply sends it somewhere you can read.
I cannot get into the dashboard — can this still be fixed?
Everything in this guide happens outside WordPress. cPanel's File Manager renames plugin folders, edits wp-config.php and opens the error log without a dashboard anywhere in sight. Being locked out changes your tools, not the method.
Is there a safe place to try changes?
Yes — plans with staging let you copy the live site, work on the copy, then publish it once it behaves. That turns 'hope the update works' into 'know it works' before a single customer meets it.
Can I transfer in a name I already own?
Yes, and it is routine. Unlock the name at your current registrar, take the auth code, and start the transfer from your client area. Whatever registration time remains carries over, and DNS keeps resolving the whole way through.
Keep reading
How to Connect a CDN
Serve assets from close to your visitors, in the cases where that genuinely pays — intermediate level, about an hour.
How to Install WordPress
Have WordPress live and answering on your domain within ten minutes — beginner level, about 10 minutes.
Best Hosting With WordPress Toolkit
The same call put as a buyer's guide: what to verify, what to ignore, and the plan we would sign.
Drupal Hosting
Drupal with Composer, Drush and per-site PHP control to hand.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.
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.
Put the site on ground you own.
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