WordPress White Screen of Death: How to Fix It

You open your site and there’s nothing there — no error message, no half-loaded page, just a blank white screen. This is the WordPress “white screen of death,” and it looks a lot scarier than it usually is. In almost every case, it’s a PHP error that’s being hidden from view rather than actual data loss, and it’s fixable without touching your database.

What actually causes the white screen of death

WordPress shows a white screen when a PHP script fails badly enough to stop execution completely, but your server is configured to hide the error message from visitors (which is the correct security default — you just need to see the hidden message yourself). The most common causes, in order of likelihood:

• A plugin update that introduced a bug or conflicts with another plugin
• A theme function that references something that no longer exists
• The site running out of PHP memory mid-request
• A corrupted plugin or theme file from an interrupted upload

Step 1: Turn on error reporting to see what’s actually broken

Before you can fix anything, you need to see the actual error instead of a blank page. If you have file access (via FTP or your host’s file manager), open wp-config.php and find the line that says define( 'WP_DEBUG', false );. Change it to:

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

Reload your site. It’ll still look broken, but now the actual error gets written to a file at wp-content/debug.log. Open that file and look at the most recent entry — it’ll usually name the exact plugin or file causing the problem.

Step 2: Deactivate every plugin

If the error log points to a plugin, or you don’t have file access to check the log, the fastest fix is to deactivate everything and re-test. If you can still reach wp-admin, go to Plugins and deactivate all of them at once, then reload your site. If the white screen disappears, reactivate your plugins one at a time, reloading after each, until the white screen comes back — that last plugin is the culprit.

Can’t reach wp-admin either? Rename the wp-content/plugins folder via FTP to something like plugins-disabled. WordPress will act as if no plugins are installed, which should restore access. Rename it back and remove the broken plugin’s folder specifically once you’ve identified it.

Step 3: Switch to a default WordPress theme temporarily

If deactivating plugins didn’t fix it, the problem is likely in your theme. Via FTP, rename your active theme’s folder inside wp-content/themes. WordPress will automatically fall back to a default theme (like Twenty Twenty-Four) if one is installed, which rules the theme in or out immediately.

Step 4: Raise your PHP memory limit

Sometimes the error log will show “Allowed memory size exhausted” rather than naming a specific plugin. That means your site is running out of memory, often because of a resource-heavy plugin or theme. Add this line to wp-config.php, above the line that says /* That's all, stop editing! */:

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

This buys you breathing room, but if a specific plugin is consistently eating memory, it should still be replaced or fixed rather than permanently propped up with a higher limit.

A few mistakes that make this worse

When a site goes down, the instinct is to start changing things quickly — which is understandable, but a few common reactions actually make recovery harder rather than easier:

• Deleting and reinstalling plugins without checking the error log first. You might remove the wrong one and still have the actual problem, now with less information about what caused it.
• Restoring an old backup blindly. If you don’t know what actually broke, you might restore to a point that still has the same underlying issue, or lose recent content unnecessarily when a five-minute fix would have preserved everything.
• Changing multiple things at once. Deactivating all plugins and switching themes at the same time might fix the white screen, but you won’t know which change actually did it — which matters if you want to safely turn things back on afterward.

Change one thing, check the result, then move to the next step. It’s slower in the moment but faster overall, because you’re not undoing your own diagnostic work.

How to prevent this from happening again

White screens are rarely random — they’re almost always triggered by a specific event: an update, a new plugin install, or a hosting change. A few habits meaningfully reduce how often this happens:

• Keep a recent backup before any plugin or theme update, not just on a schedule
• Avoid installing plugins from outside the official WordPress repository unless you trust the source completely
• Update one plugin at a time when possible, rather than updating everything simultaneously and hoping
• Keep your PHP version current — very old PHP versions are more likely to choke on modern plugin code

If none of this gets you back online

Sometimes the cause is a corrupted core file, a database issue, or something specific to your hosting environment that isn’t obvious from the error log alone. If you’ve gone through the steps above and you’re still staring at a white screen — or you just don’t want to spend your afternoon digging through log files while your site is down — we fix this exact problem for $149 flat, usually within 24 hours. Send us access and a description of what happened right before it broke, and we’ll take it from there.