the wordpress white screen of death, and how to fix it

A completely blank white page — no error, no clue, nothing — is WordPress's most panic-inducing failure. It is also, more often than not, one of the quickest to fix once you know the handful of things that cause it. The blankness is the point: something failed so early that WordPress could not render anything, including its own error message.

First, see the actual error

The white screen is hiding a real error. Turn debugging on and it will usually appear. In wp-config.php, find WP_DEBUG and set it to true:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

With DEBUG_LOG on, the error is written to wp-content/debug.log rather than shown to visitors. Reload the page, then read that file. Nine times out of ten the last line names the exact plugin, theme file and line number that failed. That single line tells you everything the rest of this guide helps you act on.

Rule out a plugin

A plugin conflict is the most common cause, usually right after an update. If you can still reach wp-admin, deactivate plugins one at a time until the site returns. If you cannot reach the admin — the white screen covers that too — do it over the files:

1. 01Connect over SFTP or the file manager and open wp-content.
2. 02Rename the plugins folder to plugins-off. This deactivates every plugin at once.
3. 03Check the site. If it is back, the cause was a plugin.
4. 04Rename the folder back to plugins, then deactivate plugins one by one in wp-admin to find the culprit.

Rule out the theme

If disabling plugins did not help, the theme is the next suspect — again, often after an update. Switch to a default theme to test. Over files, rename your active theme's folder inside wp-content/themes; WordPress falls back to a default theme automatically. If the site returns, the theme is at fault.

Raise the memory limit

If the debug log mentions 'allowed memory size exhausted', the site ran out of PHP memory — common on heavier sites and page builders. Raise it in wp-config.php:

define('WP_MEMORY_LIMIT', '256M');

If that line has no effect, the limit is capped lower at the server level, and this is where hosting matters: a host that lets you run 256MB or more solves this class of problem outright, while one that caps PHP memory tightly leaves you fighting it repeatedly.

When it is a half-finished update

If the white screen appeared during an update — the browser closed, the connection dropped — WordPress may be stuck in maintenance mode or left with mismatched files. Look for a file named .maintenance in the site root and delete it. If core files are genuinely corrupted, re-uploading a fresh copy of WordPress over the top (leaving wp-content and wp-config.php alone) replaces them without touching your content.

How to stop it happening again

• Update on staging first. A staging copy is where a bad update should reveal itself, not on the live site — one click to test, and nothing public breaks.
• Take a restore point before updates, so a bad one is a rollback rather than a debugging session.
• Give the site enough PHP memory. Most white screens that recur are a memory ceiling nobody raised.
• Keep fewer, better plugins. Every plugin is a thing that can fail during an update.

None of these are exotic. They are what managed WordPress hosting is supposed to give you as standard — staging, restore points and enough memory — which is why the white screen is far more common on hosting that treats those as extras.