WordPress White Screen of Death: Every Cause and Fix, In Order

Last updated: August 2026

First, two quick wins

Check your email. Since WordPress 5.2, fatal errors trigger an email to the site admin with a link to log in via Recovery Mode, which lets you deactivate the exact broken plugin from a working dashboard. Half of white-screen cases end here in five minutes. Search your inbox (and spam) for "Technical Issue."

Check whether wp-admin works. If the front end is blank but /wp-admin loads, it's almost certainly the active theme failing. Switch to a default theme (Twenty Twenty-Four) and confirm.

The systematic path (when the quick wins don't apply)

Step 1, See the actual error. A white screen is an error with the message hidden. Reveal it: in wp-config.php, set WP_DEBUG and WP_DEBUG_LOG to true, reload the page, then read /wp-content/debug.log. The last lines name the failing file, and the failing file's path tells you the guilty plugin or theme. Turn debug display off again when done; error messages on a live site leak information.

Step 2, Deactivate plugins without a dashboard. Via FTP or your host's file manager, rename /wp-content/plugins to plugins-off. Site loads now? A plugin was the cause. Rename the folder back, then rename individual plugin folders one at a time until the site breaks again, that's your culprit. Replace it, roll it back a version, or contact its developer.

Step 3, Rule out the theme. Rename your theme's folder; WordPress falls back to a default theme. If that fixes it and you customized the theme directly (instead of a child theme), a theme update likely wiped or conflicted with your changes, restore from backup and move customizations to a child theme this time.

Step 4, Raise the memory limit. If the log says "Allowed memory size exhausted," add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php. If the host caps memory lower than that, this becomes a hosting conversation.

Step 5, Check PHP version compatibility. A hosting-side PHP upgrade (or downgrade) can fatal-error old plugin code overnight with no changes on your end. Your hosting panel shows the current version; try switching between 8.1/8.2/8.3 and reload.

Step 6, Corrupted core files. Rare, but real after failed updates or malware cleanup. Re-upload fresh copies of /wp-admin and /wp-includes from a downloaded WordPress zip (never touch /wp-content, that's your stuff).

The fix hierarchy in one line

Recovery email → theme test → debug log → plugins folder rename → memory → PHP version → core files. Work down the list; don't skip to reinstalling everything.

Preventing round two

White screens are almost always update accidents. The prevention stack: staging environment for testing updates, pre-update backups with one-click restore, updating plugins in small batches rather than all at once, and replacing plugins whose developers have gone quiet. This exact discipline is the "updates without breakage" half of our maintenance plans, the boring process that makes 2 a.m. white screens someone else's memory.

FAQ

My site white-screens only on some pages, why? Page-specific crashes usually mean a plugin used only on those pages (a form, slider, or booking plugin) or a page-builder template failure. The debug log for a broken page will name it.

Can I just restore yesterday's backup? Yes, and for a business site that's often the right first move, restore service, then diagnose on staging. Just don't restore and stop: whatever broke will break again on the next update if you never identify it.

wp-admin is also blank, am I stuck? No. Steps 2-6 all work through FTP/file manager without any dashboard. Recovery Mode links from the fatal-error email also bypass a broken admin.

How long does this take to fix? With server access and the log in hand: 15-60 minutes for the typical plugin/theme case. If you're stuck, this is a standard flat-rate one-time fix for us, send the symptoms and we'll quote on sight.