The “white screen of death” is a blank page where your WordPress site should be. It is almost always caused by a PHP error that stops the page from loading and, because error display is off on production sites, you see nothing at all. The good news is that it is usually a quick fix once you find which plugin, theme or setting caused it.
Before you start
- Check your email. Since WordPress 5.2, a fatal error often triggers a message to the admin address with a recovery mode link.
- Make sure you have access to your files by SFTP or your host’s file manager, and take a backup if you can.
Step 1: turn on debug logging
Edit wp-config.php and add these lines above the “That’s all, stop editing” comment:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reload the page, then open wp-content/debug.log. The last “Fatal error” line names a file and often the plugin or theme at fault. Remove the debug lines when you are done.
Step 2: disable all plugins
If the log is unclear, or you cannot reach it, rename the plugins folder. Using SFTP, rename wp-content/plugins to plugins-off. If the site returns, a plugin is the cause. Rename the folder back, then rename or remove plugin folders one at a time until you find the culprit.
Step 3: switch to a default theme
Rename your active theme’s folder inside wp-content/themes. WordPress falls back to a default theme if one is installed. If the site loads, the theme (or a recent edit to its functions.php) is the problem.
Step 4: raise the memory limit
Add this to wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
If this fixes it, find out why the site needs so much memory. A heavy plugin or a very large import is a common cause. Your host may also cap memory regardless of this setting.
Step 5: check PHP and the server log
- Check which PHP version your site is using. A plugin that needs a newer or older version can fail after a PHP change.
- Look at your host’s PHP error log. It may show errors that WordPress did not write to its own log.
Step 6: restore from backup
If a code edit or failed update broke the site and you cannot identify the cause, restore the last working backup and reapply your changes one at a time.
How to prevent it
- Test updates and code changes on a staging site first.
- Do not edit theme files in the dashboard editor; use a child theme or a code snippets plugin with safe mode.
- Keep automatic backups and a recovery plan.
Final thoughts
A blank page is a message with the volume turned down. Turn on logging, check plugins, then the theme, then memory, and the log will usually point straight at the cause.
Frequently asked questions
Is the white screen of death caused by a hack?
Rarely. It is usually a plugin, theme or code error. If you also see unfamiliar files or admin users, scan the site for malware.
Why do I only see the white screen on some pages?
Only certain templates or plugin features may trigger the error. The debug log will name the file and line responsible.



