How to Fix a WordPress White Screen of Death

The White Screen of Death is exactly what it sounds like: your site loads a completely blank page, no error text, no styling, nothing, on the front end, in wp-admin, or both. It's alarming precisely because it gives you nothing to work with. But it's also one of the more mechanically predictable WordPress failures once you know where to look.

What's actually causing the blank page

A white screen almost always means a fatal PHP error occurred while WordPress was building the page, and the server is configured to hide error output rather than display it, which is normal and correct behavior for a live site. The error is happening, you just can't see it yet. The fix isn't guessing at what broke, it's turning on visibility into that hidden error long enough to identify it, then turning it back off.

Step 1: Turn on WordPress debug mode

Connect to the site over SFTP or your hosting file manager and open wp-config.php in the site's root folder. Find the line that reads define('WP_DEBUG', false); and change it to true, and add define('WP_DEBUG_LOG', true); just below it. Reload the blank page. Instead of a white screen, you should now see the actual PHP error, or find it logged to a file at wp-content/debug.log, naming the specific file and line where the failure happened.

Reading the log file instead of displaying errors on the page

If you'd rather not display raw PHP errors on a live page even briefly, keep define('WP_DEBUG_LOG', true); in place but pair it with define('WP_DEBUG_DISPLAY', false);, which logs the error to a file without showing it on the page itself. Reload the site to trigger the error, then open wp-content/debug.log through SFTP or your file manager to read exactly what failed, without exposing anything to whoever happens to load the page while you're still diagnosing it.

Step 2: Read what the error actually names

The error text almost always points to a specific plugin or theme file, something like a fatal error in a file inside wp-content/plugins/some-plugin-name. That's your answer: that plugin is the immediate cause, whether from an update that introduced a bug, a compatibility issue with your current PHP version, or a conflict with another active plugin.

Step 3: If you can reach wp-admin, deactivate from there

If the white screen only affects the front end and wp-admin still loads, go to Plugins and deactivate the one named in the error. If several plugins seem implicated, deactivate all of them and reactivate one at a time, reloading the site after each, until the white screen returns and tells you exactly which one caused it.

Step 4: If wp-admin is also blank, deactivate over SFTP instead

When the admin area is blank too, you can't click anything, so the fix happens through file access instead. Connect over SFTP or your host's file manager, navigate to wp-content, and rename the plugins folder to something like plugins-disabled. WordPress will detect that its active plugins are missing and deactivate all of them automatically, without deleting anything. Reload the site to confirm it comes back.

• Rename the plugins folder rather than deleting it, so nothing is lost
• Reload the site once renamed to confirm the white screen clears
• Rename the folder back to plugins once confirmed
• Reactivate plugins individually from wp-admin, watching for the one that reintroduces the error

A faster path when you already suspect one plugin

If a specific plugin update happened right before the white screen appeared, you often don't need to disable everything at once. Navigate directly to that plugin's folder inside wp-content/plugins and rename just that one folder, leaving every other plugin active. This isolates the test to your actual suspect first, and is faster than deactivating and individually re-enabling an entire plugin list when you already have a reasonably strong guess about the cause.

What to do if it's the theme, not a plugin

If disabling every plugin doesn't clear the white screen, the theme itself may be the cause, particularly after a theme update or a direct edit to a template file. Switch to a default WordPress theme temporarily, again through wp-admin if reachable, or by renaming the active theme's folder over SFTP if not, which forces WordPress to fall back to a default theme automatically.

When it traces back to a memory limit instead

If the debug log specifically mentions "allowed memory size exhausted," the immediate cause is a PHP memory ceiling rather than a bug in the plugin's code itself. Raising the limit with define('WP_MEMORY_LIMIT', '256M'); in wp-config.php can clear the immediate symptom, but if a specific plugin is what's driving memory usage that high, it's worth identifying and addressing that plugin directly rather than only raising the ceiling.

Preventing the next one

• Keep a recent backup before updating plugins or themes, not just after something breaks
• Test major plugin or theme updates on a staging copy of the site when one is available
• Avoid installing plugins that haven't been updated in a long time or lack recent reviews
• Keep WP_DEBUG_LOG enabled quietly in the background on a staging site so issues surface early

A white screen feels catastrophic mostly because it hides its own cause. Once debug logging shows you the actual error, fixing it is usually a matter of deactivating one plugin or theme, not rebuilding anything. The blank page is a symptom, and the log file underneath it almost always names the real problem directly.