WordPress White Screen of Death: how to fix it

The WordPress White Screen of Death is usually a fatal PHP error caused by a plugin conflict, broken theme or exhausted memory. Enable WP_DEBUG to expose the cause and disable plugins through FTP to isolate it.

No warning, no error code: just a blank page where the site used to be. The White Screen of Death (WSOD) is so disorienting because WordPress hides the cause. This guide shows how to make the error speak and fix it quickly. It is part of the larger common WordPress errors guide.

What the White Screen of Death is

The White Screen of Death is a completely blank page shown when PHP encounters a fatal error and stops execution before rendering anything. It can affect the entire site, only wp-admin, or a single page.

The blank screen is a symptom, not the problem. WordPress hides PHP errors from visitors by default. Your first job is to turn the message back on.

Step 1 — Make the error visible (WP_DEBUG)

Before trying random fixes, edit wp-config.php before /* That's all, stop editing! */:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );      // writes to wp-content/debug.log
define( 'WP_DEBUG_DISPLAY', false ); // never expose the error publicly

Reload the site and open wp-content/debug.log. The last entry shows the exact file and line of the fatal error, usually pointing to a plugin or theme. Back up before editing any file.

Step 2 — Identify the scope

• The whole site (front end and admin): a global plugin, memory or core problem.
• Only wp-admin: an admin plugin or insufficient memory.
• Only one page or post: a theme template, shortcode or block on that page.

Step 3 — Use recovery mode (WordPress 5.2+)

Since WordPress 5.2, WordPress detects fatal errors and emails the administrator a recovery mode link. Check the admin inbox and spam folder. The link lets you enter the dashboard and identifies the plugin or theme that caused the pause.

Step 4 — Isolate the plugin through FTP

Without recovery email or dashboard access, use FTP/SFTP or the host file manager:

1. Open wp-content/.
2. Rename plugins to plugins_old.
3. Reload the site.

If the site returns, rename the folder back and disable plugins one by one until the screen goes white again. The last plugin is the likely culprit. With WP-CLI:

wp plugin deactivate --all
wp plugin activate plugin-name

Step 5 — Increase PHP memory

If debug.log says Allowed memory size ... exhausted, add this to wp-config.php:

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

If it helps, investigate the plugin, import or loop that consumed the memory. If nothing changes, the server’s php.ini limit must be raised by the host.

Step 6 — Rule out the theme

Rename the active theme folder inside wp-content/themes/. WordPress should fall back to a default Twenty Twenty theme. If the site returns, inspect functions.php, templates and PHP compatibility in the theme.

Step 7 — When none of this works

With plugins disabled, a default theme and enough memory, the remaining causes are usually corrupted core files or the server itself. Reinstall the core with wp core download --force while preserving wp-content and wp-config.php, and inspect the host’s server error log.

Redirects or an administrator you did not create may indicate a compromise. Run the WordPress malware guide before continuing. When diagnosis requires server access and PHP expertise, Pixelize handles it through WordPress Specialist.