RegisterLogin
WordPress Troubleshooting

How to Fix the WordPress White Screen of Death (WSoD)

A comprehensive technical guide to diagnosing and fixing the dreaded WordPress White Screen of Death (WSoD) by debugging PHP limits, plugins, and themes.

Nextgen Support•
How to Fix the WordPress White Screen of Death (WSoD)

The WordPress White Screen of Death (WSoD) is one of the most frustrating errors you can encounter as a website owner. Unlike standard errors that provide a helpful numerical code (like a 500 Internal Server Error or a 404 Not Found), the WSoD typically presents exactly what its name implies: a completely blank, white screen with absolutely no output.

Because there is no visible error message, diagnosing the root cause can feel like searching for a needle in a haystack. In this guide, we will walk you through the precise technical steps to force WordPress to reveal the error and safely bring your site back to life.

What Causes the White Screen of Death?

The WSoD almost always boils down to a fatal PHP error or a memory exhaustion issue. When a PHP script fails catastrophically, and error reporting is disabled (which is the default security setting on live servers), the server simply stops executing the code and returns an empty HTML response.

The most common culprits include:

  1. Memory Limits: A heavy script (often a page builder or a backup plugin) tries to consume more RAM than your server allows.
  2. Plugin/Theme Conflicts: A recent update caused a fatal incompatibility between two plugins.
  3. Corrupted Core Files: An interrupted WordPress core update left your core PHP files in a broken state.

Step 1: Force WordPress to Reveal the Error (Enable Debugging)

Before blindly deactivating things, the smart approach is to look at the server error logs. We can force WordPress to write the fatal error into a hidden text file.

Connect to your server via FTP or your host’s File Manager and open the wp-config.php file in the root directory. Look for this line:

define( 'WP_DEBUG', false );

Change it to true, and add the following two lines immediately below it:

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

What this does: It prevents errors from displaying publicly to your visitors (WP_DEBUG_DISPLAY, false) but logs the exact fatal error to a file located at wp-content/debug.log.

Reload your blank white website once to trigger the error, then open wp-content/debug.log. You will likely see a line starting with Fatal error: ... which will explicitly name the plugin or theme causing the crash!

Step 2: Increase the PHP Memory Limit

If your debug.log shows an error like: Fatal error: Allowed memory size of 33554432 bytes exhausted, your WordPress site has run out of RAM.

You can attempt to increase the memory limit by adding this line to your wp-config.php file (just above the ‘That’s all, stop editing!’ line):

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

If you are on a cPanel server, you may also need to update the memory_limit directive inside your MultiPHP INI Editor.

[!NOTE] If you are on a cheap shared hosting plan, your hosting provider may actively block you from increasing the PHP memory limit beyond 64MB or 128MB. If you are constantly hitting memory limits, it is time to upgrade to Nextgen WordPress Hosting or a dedicated VPS Server where you have full control over server resources.

Step 3: Deactivate All Plugins (The Manual Way)

If the issue isn’t memory-related and you can’t access your wp-admin dashboard to turn off plugins, you have to do it at the file system level.

  1. Connect to your site via FTP or File Manager.
  2. Navigate to the wp-content folder.
  3. Locate the plugins folder.
  4. Rename the plugins folder to plugins_deactivated.

This hard-stops WordPress from loading any plugins. Now, try to load your website. If it comes back online, you know a plugin was the culprit.

To find out which one, rename the folder back to plugins. Your site won’t instantly crash because WordPress marked them all as inactive in the database when it couldn’t find the folder. Now, log into your wp-admin dashboard and reactivate your plugins one by one until the site crashes again. The last one you activated is the broken plugin.

Step 4: Revert to a Default Theme

If disabling plugins didn’t fix the WSoD, the issue might be within your theme’s functions.php file (especially if you recently added custom code snippets).

Navigate to wp-content/themes/ and rename your active theme’s folder (e.g., rename twentytwentyfour to twentytwentyfour_old). WordPress will detect the missing theme and automatically fall back to the default WordPress theme, resolving the white screen if the theme was responsible.

Recover instantly from fatal errors with built-in daily backups on Nextgen’s WordPress shared hosting.