The WordPress white screen of death is one of the most unnerving problems you can hit, precisely because it tells you nothing. You load your site — or your dashboard — and get a plain white, blank page. No error, no message, no clue. The nickname is dramatic, but the reality is usually mundane: something in your site’s code hit a fatal error and WordPress simply stopped rendering. In most cases it’s a quick fix once you know where to look.
The blank screen almost always comes from one of three things: a plugin, your theme, or the server running out of memory. We’ll turn on WordPress’s error reporting first so you’re not working blind, then check each cause in turn.
Step 1: Turn on debug mode so you can see the real error
Before guessing, make WordPress show you what actually went wrong. Open your wp-config.php file (WordPress’s main settings file) over SFTP (a secure way to connect to your site’s files) or your host’s file manager and find the line that says define('WP_DEBUG', false);. Replace it with these three lines:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
Now reload the page. Instead of nothing, WordPress writes the error to a file at wp-content/debug.log. Open it and read the last few lines — you’ll usually see something like “Fatal error… in /wp-content/plugins/some-plugin/file.php”. That single line often names your culprit and saves you the rest of this guide. When you’re finished troubleshooting, set WP_DEBUG back to false so errors aren’t logged forever.
Step 2: Suspect the last thing you changed
White screens rarely appear out of nowhere. Think back: did you just update or install a plugin, switch or edit a theme, or did an automatic update run overnight? Whatever changed last is your first suspect, and undoing it is often the whole fix.
Step 3: Deactivate all plugins
Plugins are the most common cause. If you can still reach your dashboard, deactivate them all at once, then reactivate one at a time, reloading the site after each. The one that brings the white screen back is your problem plugin.
If the white screen has locked you out of the dashboard too, do the same thing over SFTP: rename the wp-content/plugins folder to something like plugins-off. That deactivates every plugin instantly. If your site returns, rename the folder back to plugins — your plugins will still be there, just deactivated — and re-enable them one by one to find the bad one.
Step 4: Switch to a default theme
If plugins aren’t the cause, a broken theme is the next candidate — especially if you (or a developer) recently edited functions.php. A single stray character in that file will white-screen the whole site. Temporarily switch to a stock theme like Twenty Twenty-Four. If you’re locked out, rename your active theme’s folder in wp-content/themes over SFTP; WordPress falls back to a default theme automatically. If the site loads, the theme is the answer.
Step 5: Raise the PHP memory limit
Sometimes there’s no bad plugin or theme — the site simply ran out of memory mid-page and gave up, leaving a blank screen. Give it more headroom by adding this line to wp-config.php:
define('WP_MEMORY_LIMIT', '256M');
If that fixes it, note the lesson: a site constantly bumping against a low memory ceiling is a site being squeezed by an underpowered plan. On bargain hosting, memory is often capped low to fit more customers on one server.
Step 6: Check for a corrupted WordPress file
Rarely, one of WordPress’s own files gets corrupted during a failed update. The safe fix is to re-upload fresh copies of the wp-admin and wp-includes folders from a clean download of WordPress (never touch wp-content or wp-config.php — that’s your content and settings). If you’re not comfortable doing this, it’s a good moment to call for help rather than risk a wrong move.
When the fix is the host, not the file
Two of the most common white-screen causes — running out of memory and failed automatic updates — are really hosting problems wearing a technical costume. A good host gives your site enough memory to breathe, and applies updates carefully instead of letting a half-finished one corrupt a file.
That’s the everyday difference with managed WordPress hosting. Our plans include generous resources so memory ceilings aren’t a daily fight, and updates are automatic and verified — every time we update your site, we check that it still looks and works right, so a bad plugin update gets caught and rolled back before it ever white-screens your live site. It’s the difference between “an update broke my site” and never hearing about it because it was handled.
If all else fails: roll back to a working version
If you can’t find the cause, or a fix made things worse, stop editing and restore. A recent clean backup returns your entire site to the last moment it was working — no detective work required. Our guide on how to restore WordPress from a backup walks through it, and every plan we run keeps off-site backups 3 times a day so a clean copy is always a request away.
The short version
- Turn on debug logging and read
debug.log. - Undo whatever you changed last.
- Deactivate plugins (rename the folder if you’re locked out).
- Switch to a default theme.
- Raise the PHP (the programming language WordPress runs on) memory limit.
- Re-upload WordPress files, or restore from backup.
If the white screen won’t budge — or you’d rather not edit live config files while your business is offline — hand it over. Fixing blank screens is routine work for our US-based team, and if it keeps happening, moving to hosting with real resources usually ends it. For the neighboring symptoms, see our emergency troubleshooting checklist and our fix for the database connection error.