WordPress White Screen of Death: My Site Will Not Load

You open your site and get a completely blank page. No error, no warning, nothing. You try the admin panel and that is blank too. This is known as the white screen of death, and it is less frightening than it looks — because the cause is almost always one of four things.

The white screen is in fact an error screen; the error message is simply hidden from you. The server suppresses technical detail so visitors do not see it, and a blank page is what remains. So the first job is not to find the error — it is to make the error visible.

The Four Common Causes

1. Plugin or theme conflict. The most frequent cause by far. A plugin updated and now clashes with another plugin or with the theme.
2. Memory limit exhausted. As a site grows, or a heavy plugin is added, the memory allocated to PHP runs out and execution stops mid-request.
3. PHP version mismatch. The host upgraded PHP and an old theme or plugin does not work on the new version. Hosting providers sometimes do this without notice.
4. Corrupted files or a half-finished update. The connection dropped mid-update and files were left incomplete.

There is a fifth possibility: a compromise. If the blank screen comes with redirects or files you do not recognise, follow the recovery process instead of the steps below.

Step by Step: Finding Out Which One

1. Make the error visible

Enabling the debug setting in the configuration file replaces the blank page with the real error message, which usually names the offending file and line number. That single line solves half the problem. When you enable it, send errors to a log file rather than to the screen — visitors should never see a stack trace.

2. Can you reach the admin panel?

If the front end is blank but the admin loads, the problem is most likely in the theme or in a plugin that only runs on the front end. If the admin is blank too, it is deeper: memory, PHP version or core files.

3. Disable all plugins at once

If you cannot log in, you can still do this from the files: renaming the plugins directory temporarily disables all of them. If the site comes back, a plugin is the culprit. Rename the folder back and reactivate plugins one at a time until it breaks again. Tedious, but conclusive.

4. Switch to a default theme

If plugins are innocent, the theme is next. If the site loads on a default theme, the problem is yours — usually in the theme's own code or in a mismatch between the theme and the PHP version.

5. Check the memory limit

A line like "allowed memory size exhausted" in the error log points straight at memory. You can raise the limit, but that usually just suppresses the symptom. The real question is why this site needs that much memory, and the answer is normally a heavy plugin or an unoptimised query.

6. Check the PHP version

Dropping PHP back one version in the server panel often brings the site up instantly. It is not a fix, though — old PHP versions stop receiving security updates. The correct path is to make the theme and plugins compatible with the current version.

When to Stop

• You have no backup. Without a way back, every intervention is a gamble. Take a copy of the current broken state first.
• The site trades. On a site taking orders, trial and error is lost revenue.
• The log points at core files. If the problem is in the system itself rather than your code, a partial fix makes things worse.

How We Handle It

We never work directly on the live site in white screen cases. A copy is moved to a separate environment, the logs are read there, the faulty component is identified and the fix is tested before it touches production. Visitors see a maintenance notice throughout and search rankings are unaffected.

Most white screen incidents trace back to an update applied without testing. Running the update on a copy first and exercising the critical flows — forms, payment, search — prevents almost all of them. That is exactly why our maintenance subscription never updates straight into production.

Locked Out of the Admin: Diagnosing from the Files

The most awkward version of a white screen is one where the admin panel is unreachable too. Then the only route is the files and the server:

1. Open the server error log, usually under "error log" in your hosting panel. The last lines normally name the offending file outright.
2. Look at recently modified files. Sort by modification date and the file at the top is very often the source.
3. Rename the plugins directory temporarily. That disables all plugins at once; if the site returns, you have your culprit.
4. Force the default theme by renaming the theme directory, which makes the system fall back.
5. Check the configuration file. If it was hand-edited, a single stray character at the end can stop the entire site.

All of these are reversible and none delete data. Still, copying the files before each step is a good habit.

When It Is Not a White Screen at All

• Blank page but content in the source: the problem is on the front end, not in PHP — most likely a JavaScript error or content hidden by CSS.
• Only one page is blank: the fault is in that page's template or a shortcode it uses. The rest of the site is healthy.
• Blank only on mobile: caching or a mobile-specific plugin is involved.
• Sometimes blank, sometimes fine: that is a resource problem rather than a code bug; the server cannot complete the request at certain moments. See 502 and 504.
• Blank after logging in: the session or permissions layer, commonly a security plugin.

Correct diagnosis halves the work. On its own, "the site will not load" carries no information until these distinctions are made.

What Would It Cost If We Fixed It?

You do not have to guess, and you do not have to ask us. Tick the items you need in the calculator on our site and the total appears instantly. No forms, no waiting for a quote.

Calculate your price in one minute →