A WordPress white screen of death shows up with zero warning. No error message, no header, no footer, just a blank white page where your site used to be. It looks catastrophic, but it’s actually one of the more predictable WordPress emergencies once you know what causes it, and most of the time it’s fixable in under ten minutes without ever touching wp-admin.
What Causes the WordPress White Screen of Death?
The WordPress white screen of death happens when PHP hits a fatal error and stops executing before the page can render. WordPress and PHP are set up by default to hide error messages from visitors as a security precaution, so instead of showing what actually broke, the browser just gets a blank page. The three most common triggers are a plugin conflict, a theme error, or the server running out of memory.
According to SmartWP, plugin conflicts alone cause roughly half of all white screen of death cases, and the six most common causes together explain about 80% of them. That ranking matters because it tells you where to start looking instead of guessing.
| Cause | How Common | Fastest Fix |
|---|---|---|
| Plugin conflict | Most common (~50%) | Disable plugins via SFTP |
| Theme conflict | Common | Switch to a default theme |
| PHP memory exhaustion | Common | Raise the memory limit |
| Corrupted .htaccess | Occasional | Rename and regenerate it |
| Failed core update | Occasional | Replace core files |
| Hosting or PHP issue | Less common | Contact your host |
Check Your Email First: WordPress Recovery Mode
Since WordPress 5.2, the platform automatically detects a fatal error caused by a plugin or theme and emails the site’s administration address a secret recovery link. If that email is sitting in the inbox, it’s the fastest fix on this entire list: click it, and WordPress logs you into a special Recovery Mode dashboard with the broken plugin or theme already paused.
The email subject line reads “Your Site is Experiencing a Technical Issue,” and it goes to whatever address is set under Settings, then General, then Administration Email. The recovery link is only valid for 24 hours by default, so check the inbox (and the spam folder) as soon as the white screen appears.
No email in sight? That usually means the site can’t send email at all, which is a separate and very common WordPress problem. It’s worth reading through why WordPress stops sending emails once the site is back up, because the same broken mail setup that hid your recovery link is also silently swallowing contact form notifications and password resets.
How Do You Fix a WordPress White Screen Without Admin Access?
Connect to the site over SFTP, SSH, or the hosting account’s file manager, then rename the entire /wp-content/plugins/ folder to something like plugins-disabled and reload the site. This is called the bisection method, and it works without ever logging into wp-admin, because a missing plugins folder forces WordPress to stop loading any plugin at all.
If the site comes back after that, a plugin caused the white screen. To find out which one:
- Rename
plugins-disabledback toplugins. Every plugin stays deactivated, because WordPress noticed the folder had gone missing. - Inside the plugins folder, rename each individual plugin’s folder one at a time, adding
-disabledto the name. - Log into wp-admin and reactivate plugins one at a time, reloading the site after each one.
- Whichever plugin brings the white screen back is the culprit. Leave it deactivated until it’s updated or replaced.
For a more systematic way to isolate a misbehaving plugin, especially on a site with dozens of them installed, the process in finding which WordPress plugin is causing a problem covers it step by step.
Rule Out the Theme Next
If disabling plugins didn’t bring the site back, the active theme is the next suspect. Rename the current theme’s folder inside /wp-content/themes/, adding -disabled to the end, and reload the site. WordPress falls back to a default theme like Twenty Twenty-Five automatically, and if the site loads, the previous theme is the problem.
If no default WordPress theme is installed, which happens on some custom builds, download the latest one from wordpress.org and upload the folder via SFTP before testing.
Raise the PHP Memory Limit
A white screen that only shows up during heavy tasks, like importing content, running a backup, or working inside a page builder, usually points to PHP memory exhaustion rather than a plugin conflict. WordPress’s default memory limits are often too low for that kind of work, and raising them is a two-line fix.
Open wp-config.php and add these lines above the line that says “That’s all, stop editing”:
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );The first line raises the front-end limit, and the second only kicks in inside wp-admin when a process needs more than that. If the increase doesn’t seem to take effect, the hosting plan likely has a hard cap below the requested value, which is a question for the host’s support team rather than something fixable from wp-config.php alone.
Still Blank? Check .htaccess and Turn On Debug Mode
A corrupted .htaccess file can break request routing on Apache and LiteSpeed hosts badly enough to cause a white screen. Rename it to .htaccess-broken via SFTP and reload the site. If that fixes it, log into wp-admin, go to Settings, then Permalinks, and click Save without changing anything. WordPress regenerates a clean default file automatically.
If none of the fixes above worked, the fastest remaining path is to see the actual PHP error instead of guessing. Add these three lines to wp-config.php, in the same spot as the memory limit lines:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the site, then open /wp-content/debug.log to see the specific fatal error, usually a missing function, a PHP version mismatch, or a class conflict between two plugins. Once the exact error is visible, the fix is usually obvious. Turn debug logging back off once the problem is resolved, since leaving it on grows the log file indefinitely.
How Do You Prevent the White Screen of Death From Happening Again?
Testing plugin and theme updates on a staging copy before pushing them to the live site prevents the majority of white screen incidents, since that’s exactly where most fatal errors first show up. Keeping the PHP version current, running regular backups, and avoiding unnecessary plugins all reduce the odds of it happening again.
- Update plugins and themes on a WordPress staging site first, then push to production once nothing breaks.
- Run automated backups so a bad update is a quick restore instead of a diagnosis project. UpdraftPlus and Duplicator are two solid options for this.
- Keep the PHP version current. Sites still running PHP 7.x are more likely to hit fatal errors when plugins target PHP 8.1 or newer.
- Avoid stacking plugins that do similar jobs. Every extra plugin is another possible source of a fatal error.
Frequently Asked Questions
A white screen of death is a completely blank page, meaning PHP started running and then hit a fatal error before producing any output. A 500 error shows the hosting company’s own error page and usually points to a server-level problem, like a broken .htaccess file or a crashed PHP process, rather than a WordPress-level PHP error.
Almost never. Renaming plugin or theme folders, editing wp-config.php, regenerating .htaccess, and replacing WordPress core files are all non-destructive changes that leave posts, pages, and the database untouched. The only way to lose content is restoring from an older backup, which would drop anything created after that backup was made.
Common reasons include a site that can’t send email at all, an incorrect or inaccessible Administration Email address under Settings, the message landing in a spam folder, or a fatal error happening before WordPress’s recovery handler even loads. Checking that the site’s outgoing email works at all is worth doing regardless, since the same failure hides other notifications too.
Yes. A crashed PHP-FPM process, a server that has run out of memory at the operating system level, or broken file permissions can all produce a blank white page that has nothing to do with a specific plugin or theme. If plugin, theme, and memory checks don’t resolve it, contacting hosting support with the exact symptoms is the next step.
Most cases resolve in under ten minutes once the cause is identified, since the fix itself (disabling a plugin, switching a theme, raising a memory limit) takes seconds. The time-consuming part is usually narrowing down which of the six common causes is responsible, which is why checking for a recovery mode email first can skip that step entirely.
Leave a Reply