How to Fix the WordPress White Screen of Death

Few things are more alarming than visiting your WordPress website and seeing nothing but a blank white page. No error message, no content — just white. This is what the WordPress community calls the White Screen of Death (WSOD), and while it sounds catastrophic, it is almost always fixable once you know where to look.

The WSOD typically indicates a PHP fatal error that WordPress is suppressing rather than displaying. The most common causes are a plugin or theme conflict, a PHP memory limit being exceeded, or a syntax error introduced by a code edit. This guide walks you through a systematic process to identify and fix the cause.

Immediate steps: enable debugging and check error logs

Your first step is to find out what the actual error is. Connect to your server via FTP or your host’s file manager and open wp-config.php. Find the line that reads `define('WP_DEBUG', false);` and change false to true. Also add `define('WP_DEBUG_LOG', true);` and `define('WP_DEBUG_DISPLAY', false);` on the lines below. This writes errors to a debug.log file in wp-content rather than displaying them publicly.

Once debug logging is enabled, reload the white-screen page, then check wp-content/debug.log for error messages. The log will typically show you the exact file and line number causing the fatal error. If the error points to a plugin file, you know which plugin to deactivate. If it points to a theme file, you know to switch themes. Turn debugging off again once you have resolved the issue.

Deactivating plugins and switching themes

If the white screen appeared after installing or updating a plugin, deactivating that plugin via FTP is the fastest fix. In wp-content/plugins, find the folder for the suspect plugin and rename it by adding -disabled to the end. WordPress will no longer load it, which should restore your site immediately. Rename it back to re-enable it once the developer releases a fix.

If you cannot identify the specific plugin, deactivate all plugins at once by renaming the entire wp-content/plugins folder to plugins-disabled. This eliminates plugins as the cause. If your site reappears, rename the folder back to plugins and reactivate them one at a time to find the culprit. If the WSOD affects only the front end but the dashboard is accessible, the problem is almost certainly your active theme. Switch to a default WordPress theme such as Twenty Twenty-Four to confirm.

PHP memory limits and other common causes

The WordPress WSOD is sometimes caused by a script exceeding the PHP memory limit. Add `define('WP_MEMORY_LIMIT', '256M');` to wp-config.php to increase the limit WordPress requests from PHP. If your host’s server-level PHP memory limit is lower than this value, you may need to increase it via your hosting control panel or ask your host to do so.

Other causes include a corrupt .htaccess file (rename it to .htaccess-old and let WordPress regenerate it via Settings > Permalinks), a PHP version incompatibility (check that your PHP version meets the requirements of your plugins and theme), and a syntax error introduced by editing PHP files directly. If you recently edited a PHP file, restore it from your backup or from the original plugin/theme source.