How to Fix the WordPress White Screen of Death
What you're seeing
- A completely blank white page with no error text
- The front end, the wp-admin dashboard, or both fail to load
- An HTTP 500 error, or the page that just hangs and never finishes
- It started right after a plugin/theme update, a new install, or an edit to a code file
- Sometimes only certain pages are blank while others still work
What causes it
A plugin conflict or faulty update
A single plugin throwing a fatal error will take the whole page down, and the most common trigger is a plugin that was just updated or activated. Two plugins that don't get along can do the same thing. This is the first thing to suspect when the screen went white right after an update.
A broken or incompatible theme
A corrupted theme file, a bad edit to functions.php, or a theme that isn't compatible with your PHP version can produce a fatal error and a blank screen. Switching temporarily to a default theme like Twenty Twenty-Four quickly tells you whether the theme is the culprit.
PHP memory limit exhausted
WordPress, your plugins, and your theme all consume PHP memory, and when they exceed the allotted memory_limit the script is killed mid-render, leaving a blank page. Heavy plugins, large media operations, or a low host default (like 64M) are common reasons. Raising the limit in wp-config.php often resolves it.
A PHP version mismatch
If your host upgraded PHP (say from 7.4 to 8.2), older plugins or themes that use deprecated syntax can fatal-error on the new version. The site was fine yesterday and blank today with no changes on your end. The fix is updating the offending code or temporarily reverting the PHP version in your hosting panel.
A corrupted core file or failed update
An interrupted WordPress update, a bad file upload, or a damaged .htaccess file can leave core files in a broken state. This is less common but does happen after timeouts or server hiccups during an update. Replacing core files or regenerating .htaccess usually clears it.
A caching layer serving a stale broken page
Sometimes the underlying error is already fixed, but a page cache or your browser is still serving the blank version. This makes a resolved problem look like it's still broken. Clearing the cache and hard-refreshing rules this out before you go deeper.
How to fix it yourself
These steps are ordered from safest to most involved — take a full backup before changing any files, and stop if anything feels out of your depth.
Turn on WP_DEBUG to see the real error
Edit wp-config.php and set define('WP_DEBUG', true); along with define('WP_DEBUG_LOG', true); to write errors to wp-content/debug.log instead of guessing. The log will usually name the exact file and line that failed, which points straight at the guilty plugin or theme. Set WP_DEBUG_DISPLAY to false so visitors don't see raw errors, and turn debugging back off once you're done.
Check your host's PHP error log
Your hosting control panel (cPanel, Plesk, or your host's dashboard) almost always has an error log that records the fatal error with a timestamp and file path. This is the single most useful clue and requires no code changes at all. If you can read which plugin or theme is named, you've found the cause.
Deactivate plugins to isolate the conflict
If you can still reach wp-admin, deactivate all plugins, confirm the site loads, then reactivate them one at a time until it breaks again. If you're locked out, rename the wp-content/plugins folder to plugins-off via SFTP or your host's file manager to disable them all at once. This is safe and reversible — renaming back restores everything exactly as it was.
Switch to a default theme
If plugins aren't the cause, rename your active theme's folder in wp-content/themes; WordPress will fall back to a default theme like Twenty Twenty-Four. If the site comes back, the problem is in your theme — most often a recent edit to functions.php. Editing theme code directly is riskier, so don't paste in fixes you don't fully understand.
Raise the PHP memory limit
If the logs point to memory, add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php above the "That's all, stop editing" line. Some hosts cap this at the server level, so if it doesn't take effect you may need to raise it in php.ini or ask your host. This is a safe change, but if the site still blanks, memory wasn't the real problem.
Rather not risk it? We'll fix it for you.
If the logs don't make sense, the site is still blank after isolating plugins and the theme, or you simply can't risk breaking your live site further, that's exactly what we're here for. Our Emergency Rescue takes a full backup first, finds the real root cause from the error logs, fixes it cleanly, and documents exactly what was wrong — usually within hours, with a money-back guarantee. You don't have to keep editing live files on a hunch.