Why the Screen Is Blank Instead of Showing an Error
The white screen of death happens when a PHP fatal error occurs while error display is turned off — the default, safer configuration for a live site, since showing raw PHP errors to visitors is itself a security risk. The tradeoff is that you, the site owner, also don't see anything useful. The fix is the same either way: turn on error logging (not display) so the error is captured somewhere only you can see it.
Step 1: Enable Debug Logging
Via FTP or your host's file manager, open wp-config.php and add these lines just above /* That's all, stop editing! */:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reload the blank page once, then open /wp-content/debug.log. This will contain the exact PHP fatal error — typically a memory exhaustion message or a specific function call that failed in a named plugin or theme file.
Step 2: Raise the PHP Memory Limit
Memory exhaustion is one of the most common causes of a true white screen. Add this line to wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
If the site loads after this change, memory was the cause. That's a working fix, but it's worth following up by checking what's actually consuming that much memory — often a plugin doing something inefficient, or a hosting plan that's simply undersized for the site's current plugin load.
Step 3: Isolate the Plugin or Theme
If the debug log points to a plugin, or memory wasn't the issue, rename the /wp-content/plugins folder via FTP to force-deactivate every plugin at once. If the blank screen resolves, rename the folder back and reactivate plugins one at a time, reloading after each, until the white screen returns — that identifies the plugin responsible. If plugins aren't the cause, repeat the same test by renaming your active theme's folder in /wp-content/themes; WordPress will fall back to a default theme automatically.
Step 4: Check for a Syntax Error in Custom Code
If you or a developer recently edited functions.php or added a custom snippet, a single missing bracket or semicolon can cause an immediate white screen. The debug log will usually name the exact file and line — go back to the last edited file and check the syntax carefully, or restore the previous version from a backup if one exists.
Preventing It Going Forward
A blank white page is one of the least forgiving WordPress failures because it gives visitors and search engines nothing — no partial page, no error message, just nothing. It's also one of the most preventable: testing plugin, theme, and core updates on a staging environment before deploying to production catches the vast majority of white-screen causes before they ever reach a live visitor.
