You open your site and get nothing. No error, no header, no “something went wrong”. Just a white page. WordPress people call this the white screen of death, and it’s one of the most unnerving problems you can run into, because it gives you no clue at all.
The good news is that it’s almost always fixable, and your content is almost always fine. A white screen means WordPress stopped before it could draw the page. Your posts, pages and orders are still sitting safely in the database.
First, which white screen do you have?
“White screen” covers a few different problems. Spend a minute working out which one is yours, because the fix depends on it.
- The whole site is blank, front end and wp-admin. Something crashes WordPress on every page. Usually a plugin or theme, sometimes a server limit.
- The front end is blank, but wp-admin works. The problem is in something that only runs on public pages: your theme, a page builder, or a plugin that adds things to the front end.
- Only wp-admin is blank, or only one admin screen. Often a plugin that adds an admin page, or a JavaScript error.
- Only one page or post is blank. Look at what’s on that page: a shortcode, a block from a plugin, an embedded form.
- Only the block editor is blank or shows “The editor has encountered an unexpected error”. This is nearly always JavaScript, and nearly always a plugin that extends the editor.
Also check the page in a private window, or on your phone with Wi-Fi off. If it works there, you might be looking at a cached copy of a broken page. Clear your caching plugin, your host’s cache and your browser cache before going further.
Why the screen is white instead of an error
Since WordPress 5.2, most crashes show an error message instead of a blank page (in current versions it reads “There has been a critical error on this website”), and WordPress emails you a link to fix it. If that’s what you’re seeing, our guide to the critical error message is the one you want.
A truly blank page still happens, though. Typical reasons:
- PHP runs out of memory before WordPress’s error handling can kick in.
- Error messages are hidden. Most live sites are set not to show errors to visitors, which is correct, but it means a crash can look like an empty page.
- The error happens very early, for example in a must-use plugin or a drop-in file like
object-cache.php. - The page is built by JavaScript, and that script fails. The server sent a perfectly good page; your browser just couldn’t finish it.
Step 1: Find the error message
The white screen hides an error message somewhere. Finding it is the fastest route to the cause.
Check your email. WordPress may have sent “Your Site is Experiencing a Technical Issue” to the admin address. It names the plugin or theme that crashed and includes a recovery link.
Check the browser console. Press F12, open the Console tab and reload. Red errors here mean a JavaScript problem, and the file path often contains /wp-content/plugins/plugin-name/, which tells you who to suspect.
Turn on the debug log. Open wp-config.php with your host’s file manager or FTP, and just above the line that says “That’s all, stop editing!”, add:
define( 'WP_DEBUG', true );define( 'WP_DEBUG_LOG', true );define( 'WP_DEBUG_DISPLAY', false );Reload the blank page, then open wp-content/debug.log. Look for a line starting with “PHP Fatal error”. It usually ends with a file path, and that path tells you whether a plugin, your theme or something else is to blame. Remove these lines again once you’re done.
Ask your host. If you can’t edit files, your host’s support team can look at the PHP error log for you. It’s a two-minute job for them.
Step 2: Fix what the error points to
If it’s out of memory, the error says something like “Allowed memory size of 134217728 bytes exhausted”. Ask your host to raise the PHP memory limit, or add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php. But treat that as first aid. If a plugin suddenly needs far more memory than before, it may have a bug, and the white screen will come back.
If it names a plugin, and you can reach wp-admin, deactivate that plugin. If you can’t, rename its folder in wp-content/plugins/ (for example, add -off to the end) with your file manager or FTP. WordPress then skips it and the site should come back.
If it names your theme, rename the theme’s folder in wp-content/themes/. WordPress falls back to a default theme, as long as one is installed.
If it names a file in mu-plugins or a drop-in, talk to your host first. These are often installed by them, for caching or security.
Step 3: When there’s no clear error
Sometimes the log is empty, or the error points to WordPress itself rather than a plugin. Then you need to test.
Switch plugins off and see whether the white screen goes away. If it does, a plugin is involved, and you can narrow it down by turning them back on in halves. Our guide on finding which plugin is breaking your site explains how.
On a live site, though, switching every plugin off means your visitors get a broken site too. Culprit Finder does the same testing in your browser only, so visitors keep the normal site. It also catches the frustrating case where two plugins only crash together. If the white screen covers wp-admin as well, you can still use it by starting from WordPress’s recovery mode, as explained in when the whole site is down.
If the white screen stays with every plugin off, look at your theme, must-use plugins and server settings instead.
Afterwards
Once the site is back:
- Remove the debug lines from
wp-config.php, or at least make sureWP_DEBUG_DISPLAYis false. - Rename any folders back, or delete the plugin if you’ve decided to replace it.
- Report the bug to the plugin or theme author, with the exact error line from the log.
- Set up backups and a staging site, if you don’t have them yet. The next update you’re unsure about can be tested there first.
A white screen looks like the end of the world. In practice it’s usually one line in a log file, pointing at one plugin.