WordPress White Screen of Death: How to Recover

What the White Screen Means (Fatal Error)

A white screen means PHP hit a fatal error it could not recover from — the request dies mid-execution before any HTML renders. The recovery ladder:

1. Enable WP_DEBUG — edit wp-config.php: define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); then read wp-content/debug.log for the actual fatal.
2. Raise memory — define('WP_MEMORY_LIMIT', '256M'); in wp-config.php; exhaustion is the most common cause.
3. Disable plugins by rename — rename wp-content/plugins to plugins.old; site returns? Rename back and bisect.
4. Switch theme — rename the active theme's folder; WordPress falls back to a default.
5. Front-end only vs wp-admin — admin-only whites point at admin-specific plugins and functions.

The full error-reading discipline lives in the PHP error logs guide, and the sibling failure mode in the WordPress 500 error guide.

Step 1: Enable WP_DEBUG to See the Real Error

On white screen of death (WSOD), the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 2: Raise the PHP Memory Limit

Step two: raise the PHP memory limit when the log or the symptom pattern says exhaustion. WordPress works within PHP's memory_limit; busy plugins — page builders, importers, WooCommerce with large catalogs — exceed 64–128 MB defaults on ordinary days. Three places to raise it, in order of preference: wp-config.php with define('WP_MEMORY_LIMIT', '256M'); (WordPress-level), cPanel → MultiPHP INI Editor setting memory_limit (server-level, where the panel permits), or php.ini on VPS-class servers.

Verify the change landed via Site Health → Info → Server. If the white screen persists at 256M, memory was not the cause — return to the debug log, because guessing past this point wastes the afternoon the log would have saved.

Step 3: Disable Plugins via FTP Rename

On memory_limit exhaustion, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Step 4: Switch to a Default Theme

Switch to a Default Theme. Update plugins and themes on a copy or straight after a backup, one at a time if the site is a shop. A white screen after an update is usually one plugin: rename its folder via the file manager to disable it. Remove plugins you do not use — they are unpatched code.

Front-end Only vs wp-admin White Screens

On theme functions.php errors, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Prevention: Staging Updates and Backups

A backup you have never restored is a hope, not a backup. Keep a copy off the same server that hosts the site, and restore files and the database together so they match. On WebJi®, free migration of an existing site is available subject to terms and approval — open a ticket before the old host deletes the account.