Few WordPress problems are as unsettling as the WordPress white screen of death. You load your site and get nothing — no error message, no admin panel, just a completely blank white page staring back at you. The silence of it is the hardest part. Unlike an error that tells you what went wrong, the WordPress white screen of death gives you nothing to work with on the surface. I have fixed this on dozens of sites over the years and the pattern is consistent: the WordPress white screen of death is almost always caused by a PHP error that WordPress has suppressed, a plugin conflict, or a memory limit being hit. Every case I have encountered was fixable without data loss, and this guide walks through every fix in the order that resolves it fastest. For the bigger picture, our WordPress Errors Complete Guide pulls everything together.
Quick check before anything else: The WordPress white screen of death sometimes affects only the front end, only the admin, or both. Visit
yoursite.com/wp-admin/and note whether that loads or also shows blank. This tells you whether the issue is site-wide or isolated, which narrows down the cause immediately.
Enable WordPress Debug Mode to See What Is Actually Wrong
The single most useful first step when dealing with the WordPress white screen of death is turning on WordPress debug mode. By default, WordPress suppresses PHP errors and displays nothing — which is why you see a blank white page instead of an error message. Enabling debug mode makes WordPress show you exactly what failed and where, turning the silent WordPress white screen of death into a specific, actionable error message.
Connect to your server via FTP or file manager and open wp-config.php. Find this line:
define( 'WP_DEBUG', false );
Change it to:
define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', true );
Save the file and reload your site. If debug mode works, the blank white page is replaced by a PHP error message identifying the exact file and line number causing the WordPress white screen of death. The error message will typically point to a specific plugin, theme file, or — less commonly — a WordPress core file. With that information, the fix is usually straightforward: deactivate the named plugin, switch themes, or restore the corrupted file. Once you have fixed the underlying issue, return to wp-config.php and set WP_DEBUG back to false — debug mode should never be left active on a live site as it exposes code details publicly.
If changing WP_DEBUG does not produce an error message and the WordPress white screen of death persists, check the debug log at wp-content/debug.log via FTP. Errors that do not display on screen are often written there, and the log will give you the same file-and-line information to work from.
How Plugin Conflicts Cause the WordPress White Screen of Death
A buggy or incompatible plugin is the most common cause of the WordPress white screen of death. When a plugin has a PHP fatal error — a code problem so serious that PHP cannot continue executing — WordPress has nothing to render and displays blank. Plugin-caused WordPress white screen of death issues typically appear immediately after installing or updating a plugin, which makes the culprit obvious. But they can also appear after a WordPress core update makes an older plugin incompatible, with no obvious recent change triggering the problem.
If you can access the admin panel, go to Plugins → Installed Plugins and deactivate all plugins at once using the bulk action dropdown. If the WordPress white screen of death clears, a plugin is responsible. Reactivate them one at a time, reloading after each activation, until the blank screen returns — the last plugin you reactivated is the problem.
If the admin panel is also blank, plugin deactivation must go through FTP. Navigate to wp-content/plugins/ and rename the entire folder to plugins_off. WordPress treats the folder’s absence as all plugins being deactivated. If the WordPress white screen of death clears after this rename, rename the folder back to plugins and then rename individual plugin folders one at a time until the error returns. The renamed folder that causes the blank screen to reappear belongs to the conflicting plugin. Delete or replace that plugin’s files with a fresh download from the WordPress plugin repository.
Theme Issues Behind the WordPress White Screen of Death
After plugins, a broken or incompatible theme is the second most common source of the WordPress white screen of death. A theme with a PHP syntax error — even a single misplaced semicolon — produces a fatal error that WordPress cannot recover from, resulting in the same blank white page. Custom theme edits, theme updates that break child theme compatibility, and poorly coded premium themes are the typical culprits.
To test whether a theme is causing the WordPress white screen of death, connect via FTP and navigate to wp-content/themes/. Rename your active theme’s folder — for example, rename mytheme to mytheme_off. WordPress falls back to its default theme (Twenty Twenty-Four or whichever bundled theme is installed) when the active theme cannot be found. Reload your site.
If the WordPress white screen of death clears, your theme contains the problem. A fresh download of the theme from its source replaces any corrupted or incorrectly edited files. If you recently made manual edits to theme files, check functions.php specifically — syntax errors in this file reliably trigger the WordPress white screen of death and are one of the most common theme-related causes. Restore the file from a backup or from the theme’s original download.
Memory Limits and the WordPress White Screen of Death
PHP memory exhaustion is a less obvious but very real cause of the WordPress white screen of death. When a PHP process runs out of allocated memory mid-execution, it terminates abruptly and outputs nothing — producing a blank white screen. Sites with a low PHP memory limit, or sites running memory-heavy plugins like page builders or WooCommerce with large product catalogues, hit this ceiling regularly.
The fix is to increase the PHP memory limit. In wp-config.php, add this line before “That’s all, stop editing!”:
define( 'WP_MEMORY_LIMIT', '256M' );
If that does not resolve the WordPress white screen of death, try increasing further to 512M. You can also set the memory limit in .htaccess by adding php_value memory_limit 256M, or in php.ini if your hosting environment allows it. On managed hosting platforms, the memory limit is often controlled by the host’s server configuration and may require a support ticket to increase beyond what wp-config.php changes can achieve.
The WordPress White Screen of Death After a Failed Update
A WordPress core update that does not complete successfully can leave core files in a half-updated state that produces the WordPress white screen of death. This is less common than plugin and theme issues, but it happens — particularly on shared hosting with tight execution time limits where large updates time out mid-process.
If your site is stuck in maintenance mode alongside the WordPress white screen of death, start by deleting the .maintenance file from your WordPress root directory via FTP. WordPress creates this file at the start of an update and removes it on completion — a failed update leaves it in place and keeps the site in maintenance mode indefinitely.
After removing .maintenance, if the WordPress white screen of death persists, replace the core files manually. Download the current version of WordPress from wordpress.org, extract it, and upload the wp-admin and wp-includes directories to your server, overwriting the existing versions. Leave wp-content and wp-config.php untouched. A clean set of core files eliminates file-level corruption from the failed update and resolves the WordPress white screen of death in most post-update scenarios.
Increase PHP Execution Time If Nothing Else Works
A PHP script timing out mid-execution produces the WordPress white screen of death in certain scenarios — particularly during imports, batch operations, or plugin processes that run longer than the server’s max_execution_time allows. Unlike a memory error, a timeout produces no error message even with debug mode enabled, making it harder to identify.
Add this to wp-config.php to increase the execution time limit:
set_time_limit(300);
Or add php_value max_execution_time 300 to your .htaccess file. 300 seconds is sufficient for virtually all standard WordPress operations. If the WordPress white screen of death was caused by a timeout during a specific operation, the operation now has enough time to complete without aborting. After confirming the site is working correctly, identify what process was timing out and address its root cause — a plugin performing a very long database query on every page load, for example, needs to be optimised or replaced rather than just given more execution time.
Our guide on fixing WordPress plugin conflict errors covers plugin debugging in more depth, including how to identify which specific plugin within a large library is causing compatibility problems. Our guide on how to enable WordPress debug mode safely covers the full debug configuration options and how to use the debug log effectively without exposing error details to site visitors. The WordPress developer documentation on debugging is the authoritative reference for debug mode configuration and the full range of diagnostic constants available. Related: WordPress Admin Menu Order.
