Fix the WordPress White Screen of Death: A 5-Step Guide
Facing the dreaded WordPress white screen of death? Don't panic. Our step-by-step guide helps you diagnose and fix the issue in minutes, from plugin conflicts to memory limits.
What is the White Screen of Death (and Why It Happens)?
The WordPress White Screen of Death (WSOD) is exactly what it sounds like: a completely blank, white screen where your website should be, with no error message. It’s one of the most common and alarming WordPress errors because it offers no clues about the cause. The good news is that it’s almost always fixable. This issue typically stems from a PHP code error or a database connection problem, most often triggered by a poorly coded plugin or a conflicting theme update. It's not a virus, and your content is almost certainly safe; your site is just failing to render properly.
Think of it as a critical failure in the instruction manual your server reads to build your site. If one step is broken or conflicts with another, the server simply stops, leaving you with a blank page. This can affect your entire site or just a single page, and it frequently locks you out of the WordPress admin area as well. Our approach will be to systematically rule out the most common culprits, starting with the easiest and most likely problems first, so you can get your site back online without breaking a sweat.
Step 1: Check for a Simple Plugin Conflict
More than 90% of the time, the White Screen of Death is caused by a single rogue plugin. To test this theory, you need to deactivate all your plugins simultaneously. Since you probably can't access your admin dashboard, you’ll have to do this manually via your hosting control panel's File Manager or an FTP client like FileZilla. Navigate to your WordPress installation folder, find the `wp-content` directory, and locate the `plugins` folder inside.
Instead of deleting anything (never delete files while troubleshooting!), simply rename the `plugins` folder to something like `plugins_old` or `plugins_deactivated`. This action immediately deactivates every plugin on your site. Now, try to load your website. If it comes back to life, you've confirmed a plugin is the problem. To find the specific offender, rename the folder back to `plugins`, then log into your WordPress admin and reactivate each plugin one-by-one, reloading your site after each activation, until the white screen returns.
Step 2: Rule Out a Faulty Theme
If deactivating your plugins didn't solve the problem, the next likely suspect is your active theme. A recent theme update, a custom code snippet, or an incompatibility with a new version of WordPress can all trigger the WSOD. The fix is similar to the plugin method: you need to force WordPress to fall back to a default theme. WordPress comes packaged with default themes like 'Twenty Twenty-Three' or 'Twenty Twenty-Four', which are stable and reliable for testing.
Using your File Manager or FTP client again, navigate to `wp-content/themes`. Find the folder for your currently active theme and rename it just as you did with the plugins folder. This will automatically force WordPress to revert to the latest default theme. Check your site again. If it loads (albeit looking different), you know your theme was the issue. At this point, you can try reinstalling a fresh copy of your theme or contacting the theme developer for support.
Step 3: Enable Debug Mode and Check Logs
When the simple fixes don't work, it's time to gather more intelligence. WordPress has a built-in debugging feature that can reveal the specific PHP error causing the site to crash. To enable it, you'll need to edit your `wp-config.php` file, which is located in the root directory of your WordPress installation. Before editing this critical file, always download a backup copy to your computer.
Open `wp-config.php` and find the line that says `define( 'WP_DEBUG', false );`. Change `false` to `true`. You may also want to add the following two lines below it to log errors to a private file instead of displaying them on your site: `define( 'WP_DEBUG_LOG', true );` and `define( 'WP_DEBUG_DISPLAY', false );`. Now, reload your site. Instead of a white screen, you should see an error message indicating the exact file and line number causing the problem. This is invaluable information for fixing the issue or for sending to your host or a developer for help.
Step 4: Increase Memory Limits and Final Checks
Sometimes, the white screen isn't caused by a code conflict but by resource exhaustion. A script or plugin might be trying to use more memory than your server allocates to PHP, causing it to crash. You can resolve this by increasing the PHP memory limit. Again, in your `wp-config.php` file, add the following line just before the `/* That's all, stop editing! */` comment: `define('WP_MEMORY_LIMIT', '256M');`. This raises the limit to 256 megabytes, which is often sufficient to resolve memory-related issues.
If you've tried all these steps and the blank screen persists, the issue might be more complex. A failed automatic WordPress core update could leave behind corrupted files, which can be fixed by manually reinstalling WordPress. In other rare cases, it could be a server-level issue. This is the point where it's wise to lean on your hosting provider's support team. Provide them with the error logs you generated from debug mode, and they should be able to investigate server-side problems or help you restore your site from a recent backup.
Questions readers ask about this topic
Can the white screen of death affect my admin dashboard too?
Will I lose my data if I rename the plugins folder?
Is the WordPress white screen of death a security issue?
What if I can't access my site's files via FTP or File Manager?
Where to go next on Hostilo
One email a month. Hosting deals, new reviews, no fluff.
The WordPress performance checklist that actually works
Twelve changes that move real Core Web Vitals numbers, ranked by impact, not popularity.
How to speed up WordPress: the only checklist you need
Ten changes that actually move the needle on WordPress speed — ranked by impact, not by what plugin authors want you to install.