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

We’ve all been there. You go to check on your beloved WordPress site, and instead of your beautiful homepage, you’re greeted by… nothing. Just a blinding, empty, and terrifyingly blank page. This, my friend, is the infamous WordPress White Screen of Death (WSoD).

It’s the digital equivalent of a silent phone line—frustrating, scary, and it leaves you wondering what on earth went wrong. But don’t panic! The WordPress White Screen is almost always fixable. It’s usually just WordPress’s way of telling you something broke, but it’s too “sick” to even show you the error message.

This guide will walk you through the most common causes and their solutions, from the simplest fixes to the more technical ones. Let’s get your site back.

Before Troubleshooting WordPress White Screen of Death: The Essentials

Two golden rules before you start troubleshooting:

1. Don’t Make It Worse: If you can still access your WordPress admin dashboard (your /wp-admin page), don’t immediately start deactivating things. If you can’t access your admin, you’ll need an FTP client (like FileZilla) or access to your hosting account’s File Manager. This guide will assume you have that ready.
2. Back It Up: If you have a recent backup, you are in a much safer position. If you don’t, and you can’t get into your admin to make one, just be extra careful with the steps below.

Solution 1: Enable Debugging to Get Clues

The white screen is a “fatal error.” Your first step is to force WordPress to tell you what that error is. To do this, we’ll enable the debug mode.

1. Connect to your site via FTP or your host’s File Manager.
2. Find the wp-config.php file in the root directory of your WordPress install.
3. Right-click and “Edit” the file (or download, edit, and re-upload it).
4. Look for a line that says define( 'WP_DEBUG', false );.
5. Change false to true.

If that line doesn’t exist, you can add it (and the lines below) just before the line that says:

/* That's all, stop editing! Happy publishing. */

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

What this does:

• WP_DEBUG turns on the debug mode.
• WP_DEBUG_LOG saves all errors to a new file called debug.log inside your /wp-content/ folder. This is the safest way to do it, as it doesn’t print the errors on your live site for everyone to see.
• WP_DEBUG_DISPLAY keeps the errors hidden from the site’s front end.

Now, reload your website. The white screen will likely still be there, but you can now check the debug.log file. Open it, and the last few lines will almost always tell you the exact file and line number causing the problem, like:

Fatal error: Cannot re-declare some_function() in /home/user/public_html/wp-content/plugins/some-bad-plugin/some-file.php on line 123

This error message is your treasure map. If it points to a plugin or theme, you’ve found your culprit!

Solution 2: The Plugin Conflict

This is the most common cause of the WordPress White Screen. An update to a plugin, or a new plugin, conflicts with another plugin or your theme.

If your debug log pointed to a specific plugin, just go to the /wp-content/plugins/ folder and rename that plugin’s folder (e.g., change some-bad-plugin to some-bad-plugin-old).

If you couldn’t get a specific error, you’ll have to test them all at once.

1. Connect to your site via FTP.
2. Navigate to your /wp-content/ folder.
3. You will see a folder named plugins.
4. Right-click the plugins folder and rename it to something like plugins_deactivated.

This immediately deactivates all plugins on your site. Don’t worry, all your settings are safe.

Now, try to load your website. If it works (it might look broken, but it loads), you’ve confirmed the problem is a plugin.

To find the specific culprit:

1. Rename the folder back to plugins.
2. Go inside the plugins folder.
3. Rename each plugin folder one by one (e.g., elementor to elementor-off), reloading your site after each one.
4. When your site breaks again, the last plugin you renamed is the one causing the problem.

Solution 3: The Theme Conflict

If the plugins weren’t the issue, your theme might be. This often happens after a theme update or if you’ve been editing your theme’s functions.php file.

The fix is similar to the plugin fix. We’ll force WordPress to fall back to a default theme (like “Twenty Twenty-Four”).

1. Connect to your site via FTP.
2. Navigate to /wp-content/themes/.
3. Find the folder for your active theme (e.g., your-theme-name).
4. Right-click and rename that folder (e.g., your-theme-name-off).

If you have a default theme like “Twenty Twenty-Four” already installed, WordPress will automatically switch to it, and your site should come back online. If you don’t have a default theme, download one from WordPress.org and upload its folder to your /themes/ directory before doing this.

If the site loads, you know the issue is in your theme. You may need to roll back to a previous version of the theme or contact the theme developer.

Solution 4: Increase the PHP Memory Limit

Sometimes, your site just doesn’t have enough “brainpower” (memory) to run all its tasks, especially if you’re using large plugins like WooCommerce or page builders. This can result in a WordPress White Screen.

1. Connect to your site via FTP.
2. Open your wp-config.php file via FTP.
3. Just before the /* That's all, stop editing! */ line, add the following code:

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

This increases your site’s memory allowance to 256 megabytes, which is often enough to solve the problem. If your host doesn’t allow this, you may need to contact them to increase it for you.

Solution 5: Check File Permissions

This is a less common but still possible cause. If your server files have the wrong permissions, the server may be blocking WordPress from reading them.

File permissions should generally be:

• Folders: 755
• Files: 644

You can check and change these permissions using your FTP client. Right-click any folder or file and look for an option like “File Permissions.”

Warning: Be very careful with this step. Setting permissions incorrectly can make your site less secure. Never, ever set permissions to 777.

By now, one of these solutions has almost certainly fixed your site. Remember to turn off the WP_DEBUG mode in your wp-config.php file once you’re done so you aren’t logging errors (and slowing down your site) all the time.

The WordPress White Screen of Death is terrifying, but it’s just a bump in the road. A little systematic troubleshooting is all it takes to get back online.

This step-by-step video also provides a great visual guide on troubleshooting the WordPress White Screen of Death. How to Fix the WordPress White Screen of Death (Step by Step) (From: WPBeginner). This video is relevant because it visually walks you through many of the troubleshooting steps we discussed, like clearing your cache and addressing plugin issues, which can be very helpful to see in action.