WordPress white screen of death - where it comes from and how to clear it

A white screen is a fatal error with no message - the site crashed and WordPress did not even get to say why. The jargon term is “the white screen of death”: instead of a site you get an empty white page, sometimes only on some pages, sometimes everywhere, occasionally including the admin dashboard. The mechanics are the same as with a critical error that does show a message - PHP execution stopped - except this time you get no recovery email and no hint on screen. Newer WordPress versions usually display a message; pure white most often means an older install, error reporting switched off, or a crash so early that the engine never started.

Your data - posts, products, orders - lives in the database and this error does not touch it. The job is to find out what exactly broke, and then switch it off.

The quick checks first

Before you go into the files, three things that take 2 minutes:

1. Does /wp-admin work? If it does, the error is front-end only; almost certainly the theme or a plugin that renders the page is to blame. Go to Appearance → Themes and switch to a default theme for a moment
2. Is the white screen everywhere, or on one page? One page points to a specific element (a form, a gallery, a plugin used only there); everywhere points to something global
3. What happened just before? An update, a new plugin, an edit to a theme file, a PHP version change on the hosting? That is your prime suspect - crashes rarely come out of nowhere

Turn the message on instead of the blankness

The biggest problem with a white screen is the lack of information. One line changes that: in wp-config.php (the site’s main directory, edit over FTP or the hosting file manager) find the WP_DEBUG line and set it to true - and if it is not there, add it before the “That’s all, stop editing” comment:

define( 'WP_DEBUG', true );

Refresh the page. Instead of blankness you should get a concrete error with a file name - for example wp-content/plugins/plugin-name/... - and that is your answer about who is at fault. After the fix, set it back to false, because error messages on a live site are a gift to attackers.

What helps: if you are nervous about editing wp-config.php, the same information sits in the PHP error logs in your hosting panel - the “Logs” section. The last entries around the time of the crash point to the culprit without touching a single file. It is the same technique I describe for error 500.

Switch off the culprit

From here the procedure is identical to a fatal error. In short:

1. The plugin named in the error: in wp-content/plugins rename its folder - the site comes back immediately
2. The error points to the theme: in wp-content/themes rename the active theme’s folder; WordPress falls back to the default
3. A “memory exhausted” error: PHP ran out of memory - in the hosting panel raise memory_limit (256 MB is a sensible minimum for a site with a store)
4. None of the above: possibly damaged files after an interrupted update - WordPress core files can safely be overwritten with a fresh copy from wordpress.org (without the wp-content folder)

A white screen only sometimes, or only in the dashboard

Two special variants. Blankness in the admin dashboard only (the front end works) is usually a conflict with a plugin that runs only in the back end, or a memory limit that is too low - the dashboard can need more than the front end. Blankness now and then - under heavier traffic, after the nightly backup - is a symptom of server resources running out rather than broken code; diagnosing that needs logs over a longer period, and it is a typical thing monitoring catches under ongoing support before customers start hitting an empty page.

Frequently asked questions

How is a white screen different from a critical error? They are the same family of failure. A “critical error” is a newer WordPress that managed to catch the problem and show a message (plus send a recovery email). A white screen is the same kind of crash with no information at all - which is why the first step is getting a message out of it, through debug mode or the logs.

Do visitors see the same thing I do? Usually yes, but check in a private browser window - caching (yours or a cache plugin’s) can show one person a white page and another a normal one. If you use a cache plugin, clear it after the fix, otherwise the blankness will keep haunting you for hours.

How long does the fix take? With the error message in hand - usually hours. Without access to FTP and the hosting panel neither a specialist nor anyone else can do much, so the first thing worth gathering is credentials. I give the quote in writing after looking at the site.

Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.