WordPress White Screen of Death: Causes and Fixes

Why the Screen Is White

The WordPress White Screen of Death (WSOD) is a PHP fatal error that kills the page before WordPress can render anything — including an error message. You see a blank white page, or sometimes a brief “This page isn’t working” browser error. The server sent back an empty response because PHP died mid-execution.

On WordPress 5.2+, most fatal errors trigger the “critical error” handler instead of a white screen. If you’re seeing a true blank page, it usually means the error is so severe that even WordPress’s error recovery system couldn’t catch it, or your WordPress version predates that feature.

The Usual Suspects

Plugin or Theme Conflict

This is the cause in roughly 70% of WSOD cases. A plugin update introduces a bug, two plugins conflict, or a theme update breaks compatibility with an active plugin.

The fastest test: rename your wp-content/plugins folder to plugins-disabled via SFTP. If the site comes back, a plugin is the culprit. Rename the folder back, then rename individual plugin folders one by one until you find which one breaks the site.

For themes: rename your active theme’s folder. WordPress switches to a default theme automatically. If that fixes it, the theme is the problem.

PHP Memory Exhaustion

WordPress has a default memory limit that’s often set too low. When a page requires more memory than allowed — large page builder layouts, WooCommerce with many products, image-heavy pages — PHP runs out and dies silently.

Check by adding this to wp-config.php:

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

If this fixes the white screen, you were hitting the memory ceiling. But this is a band-aid — you should figure out what’s consuming so much memory. Likely culprits: bloated page builder layouts, unoptimized database queries from plugins, or loading too many posts at once.

PHP Version Mismatch

Your host upgraded PHP (say, from 7.4 to 8.1) and a plugin or theme uses deprecated functions. PHP 8.x is stricter about types and removed functions that 7.x tolerated.

If the WSOD started right after a server change you didn’t initiate, ask your host if PHP was updated. Most hosts let you switch PHP versions in the control panel — temporarily rolling back to the previous version will confirm if this is the cause.

Corrupted Core Files

Less common but not rare: WordPress core files got corrupted during an update, a failed migration, or a security breach. The fix is straightforward — download a fresh copy of WordPress from wordpress.org, extract it, and upload the wp-admin and wp-includes folders via SFTP, overwriting the existing ones. Don’t overwrite wp-content — that’s where your themes, plugins, and uploads live.

The Debug Sequence

Work through this in order:

1. Enable WP_DEBUG. Edit wp-config.php, set define('WP_DEBUG', true); and define('WP_DEBUG_LOG', true);. Check wp-content/debug.log for the actual error.
2. Check server error logs. Your hosting control panel (cPanel, Plesk) has an error log section. PHP fatal errors show up here even when WordPress can’t catch them.
3. Disable all plugins. Rename the plugins folder. If the site loads, re-enable one at a time.
4. Switch to default theme. If disabling plugins didn’t help, rename your theme folder.
5. Increase memory limit. Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php.
6. Reinstall WordPress core. Upload fresh wp-admin and wp-includes from a clean download.

When the White Screen Keeps Coming Back

A WSOD that recurs after fixing usually points to a systemic issue: the hosting environment can’t reliably support what the site is trying to do, or there’s malware injecting code that periodically causes failures.

If you’re chasing the same white screen repeatedly, the underlying setup needs examination — not just the symptom. That might mean migrating to better hosting, reducing the plugin stack, or doing a security audit to rule out compromise.

Parameter’s emergency diagnostic is built for exactly this scenario. We get access, identify the root cause, and give you a clear action plan — typically within 2 hours. The $250 diagnostic fee credits toward an annual Protect plan if you want ongoing monitoring so the WSOD doesn’t come back.