You refresh the page and there’s nothing there. Not an error, not a loading icon – just white. If you’ve built or managed a WordPress site for any length of time, you already know this feeling, and you know it always seems to happen at the worst possible moment.
I’ve walked this back on client stores mid-sale, on membership sites during a launch, and on my own projects at 2am. The good news: the White Screen of Death (WSOD) is almost always a PHP fatal error hiding behind a blank page, and there’s a fixed, logical order for hunting it down. Here’s exactly how I do it.
What Actually Causes It
Since WordPress 5.2, there’s a built-in Recovery Mode that catches most fatal errors and emails the site admin a link to disable the broken component. If you’re seeing a truly blank screen with no recovery email, the error is happening even earlier – usually inside wp-config.php, a must-use plugin, or before WordPress finishes loading. That distinction matters, because it tells you where to start looking.
The usual suspects, in order of how often I actually see them:
- A plugin or theme update that introduced a PHP fatal error
- PHP memory limit exhausted (still commonly capped at 64MB or 128MB by hosts)
- A corrupted wp-config.php or .htaccess file
- Database connection failure after a migration or credential change
- A PHP version bump on the server that broke old plugin code
Fix 1: Check Your Email for a Recovery Mode Link First
Before touching any files, check the admin email inbox for a message from WordPress with a subject like “Your Site is Experiencing a Technical Issue.” That email includes a one-click Recovery Mode link that lets you log in, see exactly which plugin or theme threw the error, and deactivate it from the dashboard – no FTP required. This step alone resolves the issue in minutes for a huge share of cases, and it’s the one step most troubleshooting guides skip entirely.
Fix 2: Turn On Debug Mode
If there’s no recovery email, or you need more detail, connect via FTP or your host’s File Manager and open wp-config.php. Find this line:
define( 'WP_DEBUG', false );Change it to:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the site. WordPress will start writing detailed errors to a debug.log file inside /wp-content/. Open that file and read the most recent entry – it will usually name the exact plugin, theme, or file causing the crash. This one change turns a guessing game into a five-minute diagnosis.
Fix 3: Deactivate All Plugins via FTP
Plugin conflicts are still the single most common cause of WSOD, especially right after an update. Navigate to wp-content/plugins/ and rename the entire folder – to plugins-disabled, for example. WordPress can’t find the folder, so it deactivates everything automatically.
Reload the site. If it comes back, rename the folder back to plugins, then reactivate one plugin at a time from the dashboard, reloading after each one. The plugin that brings the white screen back is your culprit.
Fix 4: Switch to a Default Theme
If disabling plugins didn’t fix it, the theme is next. Go to wp-content/themes/ and rename your active theme’s folder. WordPress falls back automatically to a default theme like Twenty Twenty-Five. If the site loads, the problem lives in your theme – very often a broken edit inside functions.php, where even one missing semicolon can take the entire site down.
Fix 5: Raise the PHP Memory Limit
A silent memory exhaustion is one of the sneakier causes because it often shows no error at all, even with debug mode on. Add this line to wp-config.php, just above the “stop editing” comment:
define( 'WP_MEMORY_LIMIT', '256M' );Most managed hosts also let you raise the PHP memory limit directly from the hosting control panel – check there too if the wp-config.php change doesn’t fully resolve it.
Fix 6: Rule Out a PHP Version Mismatch
If your host recently auto-updated PHP in the background and your theme or a plugin hasn’t been updated to match, you can get a blank screen with no visible error at all. Check your current PHP version in the hosting panel, and if it changed recently, try rolling back to the previous version temporarily. If the site returns, you know exactly what to chase – an incompatible plugin or theme that needs updating or replacing.
Fix 7: Re-upload Core Files or Fix .htaccess
Less common, but it happens: a corrupted WordPress core file from a failed update, or a broken .htaccess after a server change. Download a fresh copy of WordPress from wordpress.org and, via FTP, overwrite only the wp-admin and wp-includes folders – never wp-content, since that’s where your actual site lives. Separately, try renaming .htaccess to .htaccess_old and regenerating it from Settings > Permalinks.
If Nothing Above Works
At this point the issue is usually server-level, not WordPress. Ask your host if there were recent server changes, check your disk quota isn’t full (a full disk causes PHP to fail silently), and review the server error log in cPanel. If you recently migrated hosts, double-check the database credentials in wp-config.php match the new environment exactly.
Keeping This From Happening Again
- Test every plugin and theme update on a staging site first, not live
- Keep a rolling backup – UpdraftPlus or your host’s native backup tool
- Update PHP versions deliberately, with a compatibility check beforehand, not by leaving it on auto
- Keep your plugin count lean; every active plugin is another point of failure
- Never edit functions.php directly on a production site
Final Word
The White Screen of Death looks like a disaster the first time you see it, but it’s rarely as bad as it looks. Nine times out of ten it’s a plugin conflict or a memory cap, and both take minutes to fix once you know where to look. Work through these fixes in order – Recovery Mode and debug mode first – and you’ll usually have an answer before you’ve finished your coffee.
If you’re dealing with something messier – a hacked site, a failed migration, or a host-level issue you can’t pin down – you can reach me at meetdaniyalsolutions.online. I’ve pulled sites back from worse.
