WordPress white screen of death: how to fix it

What the WordPress white screen of death means

The "white screen of death" is the informal name for a WordPress page that returns no useful visible content or error message. In PHP terms, a fatal error may have stopped execution while error display is disabled, so the browser receives a blank or nearly blank response.

Modern WordPress can show a critical error screen or trigger Recovery Mode for some fatal errors, but not every failure produces that interface. A blank front end with a working admin area can indicate a theme or front end plugin problem. A blank front end and blank admin area points more strongly to a plugin, theme, PHP or server wide failure.

Common causes of a WordPress white screen

Plugin and theme faults are common, particularly after an update, a PHP version change or a new code deployment. PHP 8.x is stricter about some programming errors than older PHP releases, so outdated custom code can fail after a server upgrade even when WordPress itself is current.

Memory exhaustion can also terminate a request before a page is produced. Imports, page builders, ecommerce tasks, backup jobs and image processing can increase memory use. A broken or incomplete update may leave mismatched files, while syntax errors in custom PHP can stop execution immediately.

The fastest diagnosis comes from timing and logs. If the blank page started directly after one change, reverse or isolate that change first. If it appeared without a visible change, inspect the PHP or WordPress error log before altering several components.

How to fix the white screen of death safely

Before editing files or the database, take a full backup of both website files and the database. Then use the least invasive checks first.

1. Check the administrator email for a WordPress Recovery Mode message. If it names a plugin or theme, disable that component and retest.
2. If wp-admin is unavailable, use SFTP or your host file manager to rename the suspected plugin folder inside wp-content/plugins. If there is no clear suspect, temporarily disable plugins using the WordPress documented folder rename method, then restore the folder name and reactivate plugins individually.
3. If the front end alone is blank, test with a current default WordPress theme if you can do so safely.
4. Enable logging briefly in wp-config.php without displaying errors to visitors:

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

Reload the affected page, read wp-content/debug.log, then turn debugging off. If the log reports an exhausted memory limit, fix the process using the memory rather than treating a larger limit as the only solution.

When to get help with a blank WordPress site

Stop troubleshooting if you cannot identify the failing component, the log points to custom PHP you do not maintain, the site is taking orders or payments, or changes are making the fault less predictable. Repeatedly renaming folders or changing PHP settings without a clear test can obscure the original cause.

Web Support Services offers an Emergency Fix for £249 per incident, with a response within 2 working hours. If you want routine updates, backups and monitoring, care plans start from £59 a month.