The WordPress White Screen of Death, Explained
Get your site back from the WordPress white screen of death: turn on the debug log, read the last fatal line, and rename the plugin folder it names.
The white screen of death is a PHP fatal error that nobody printed. WordPress hit an error it could not recover from, PHP stopped, and the page came back empty instead of showing the reason. The fix starts the same way every time: turn on the debug log, open wp-content/debug.log, and read the last fatal line. It names the file at fault, nearly always a plugin or theme, and that one line tells you what to rename.
TL;DR: (1) Turn on WP_DEBUG and WP_DEBUG_LOG in wp-config.php over SFTP. (2) Reload the broken page once, then read the last line of wp-content/debug.log. (3) Rename the plugin or theme folder that line names (some-addon to some-addon.off). (4) Turn WP_DEBUG back off. Clearing cache, raising memory and reinstalling core come later, if at all, because none of them tell you which file failed.
Why the screen is blank
PHP has a setting called display_errors. PHP’s built-in default is on, but the php.ini-production file that hosts start from switches it off, and the PHP manual says it should never be on for a site connected to the internet. So on a live host a fatal error (a call to a function that no longer exists, a class that isn’t loaded, a typo in an update) stops PHP and prints nothing.
Since WordPress 5.2 there is also a fatal error handler, WP_Fatal_Error_Handler. WordPress registers it in wp-settings.php before it loads must-use plugins, plugins or the active theme. When it can, it replaces the blank page with “There has been a critical error on this website” and an HTTP 500 status. That covers most fatals, syntax errors included. In our Playground test on 2026-11-10 (WordPress 7.1.4, PHP 8.3.36, Playground CLI 3.1.63), a parse error in an active plugin and in a must-use plugin both returned a 500 error page from WordPress, and both were written to debug.log.
So if you see a short sentence instead of an empty page, you are on a different problem. The critical-error message has its own guide, and a page that says only Error establishing a database connection is a failed database connection, not a PHP crash.
When WordPress shows nothing at all
A truly blank page means the handler did not run, or ran and was not allowed to print. These are the cases we found. The behaviour is read from the WordPress 7.1.4 source unless a test is named.
| What happened | Why there is no message | What you get |
|---|---|---|
A typo or syntax error in wp-config.php | This file runs before WordPress registers its handler or turns on its log | PHP’s own error if display_errors is on, otherwise an empty page. Our 2026-11-10 test logged nothing to debug.log; check the host’s PHP error log |
| A fatal after part of the page was already sent (a template or a hook that runs mid-page) | The handler only prints its message in wp-admin or if no output has gone to the browser yet | A page that stops partway, which often looks blank. Our 2026-11-01 test (WordPress 7.1.4, PHP 8.3.33, Playground) ran out of memory inside the wp_body_open hook and returned status 200 with the page cut off and no critical-error message |
WP_DISABLE_FATAL_ERROR_HANDLER is true in wp-config.php | The handler is never registered | Plain PHP behaviour: an empty page, or the raw error if display_errors is on |
| A fatal during an update, on the request doing the update | The handler stands down while the .maintenance file is less than 10 minutes old | The update screen stops partway or comes back empty. Other visitors see “Briefly unavailable for scheduled maintenance. Check back in a minute.” |
The active theme’s folder is missing, or it has none of index.php, templates/index.html or the older block-templates/index.html | WordPress only explains a broken theme to users who can switch themes | Logged-out visitors get an empty page with no error at all |
| PHP crashed or was killed (the host’s own memory cap, for example), or the web server gave up waiting for it | WordPress’s message never reaches the browser | A server error page or an empty response, and an entry in the server’s log, not WordPress’s |
The cause is written down somewhere in every row except the theme one, and that one has a fix of its own in step 3.
Fix it, in order
1. Turn on the log
Edit wp-config.php over SFTP (what the file does and how to edit it safely). WordPress’s wp-config-sample.php already defines WP_DEBUG once, as false. PHP keeps the first value of a constant. A second define( 'WP_DEBUG', true ) below it changes nothing and adds a “Constant WP_DEBUG already defined” warning. We checked this with a two-line PHP script on PHP 8.3.33 and PHP 8.5.10 (2026-10-31). Both kept the first value, and PHP 8.5 adds that this will be an error in PHP 9. So find the existing line and change false to true, then add the other lines above /* That's all, stop editing! */:
define( 'WP_DEBUG', true ); // change the EXISTING line
define( 'WP_DEBUG_LOG', true ); // add
define( 'WP_DEBUG_DISPLAY', false ); // add
@ini_set( 'display_errors', 0 ); // add
WP_DEBUG_DISPLAY false keeps the errors off the public page while WP_DEBUG_LOG writes them to wp-content/debug.log. If you’d rather not type it, the WP_DEBUG code generator builds the same block. For what each constant does and how to switch them off again, see how WordPress debug mode works. Reload the broken page once to write a fresh entry.
2. Read the last fatal
Open wp-content/debug.log and look at the bottom. If it isn’t there, where WordPress writes debug.log covers custom paths and hosts that move it.
tail -n 30 wp-content/debug.log
You’re looking for a line like this. It is a real entry from our test site (2026-11-01, WordPress 7.1.4, PHP 8.3.33, WordPress Playground), where a test plugin called a function that does not exist:
[01-Nov-2026 16:57:07 UTC] PHP Fatal error: Uncaught Error: Call to undefined function some_addon_missing_helper() in /wordpress/wp-content/plugins/some-addon/some-addon.php:6
Stack trace:
#0 /wordpress/wp-includes/class-wp-hook.php(353): {closure}('')
#1 /wordpress/wp-includes/class-wp-hook.php(377): WP_Hook->apply_filters(NULL, Array)
#2 /wordpress/wp-includes/plugin.php(523): WP_Hook->do_action(Array)
#3 /wordpress/wp-includes/template-loader.php(23): do_action('template_redire...')
#4 /wordpress/wp-blog-header.php(19): require_once('/wordpress/wp-i...')
#5 /wordpress/index.php(17): require('/wordpress/wp-b...')
#6 {main}
thrown in /wordpress/wp-content/plugins/some-addon/some-addon.php on line 6
The path names the culprit: plugins/some-addon. On a live host the path starts with your own document root (for example /var/www/html/ or /home/user/public_html/) instead of /wordpress, which is just where the test server keeps WordPress. If the trace is long or the message is cryptic, paste it into the WordPress error log decoder. It picks out the plugin or theme the path points to and explains the error type.
The words after PHP Fatal error: (or PHP Parse error: for a syntax error) usually point at one of a handful of causes:
| Log message contains | Likely cause | Fix |
|---|---|---|
Call to undefined function | A plugin calls a function from another plugin, WooCommerce or a theme that isn’t active or loaded yet | Activate the missing dependency, or deactivate the plugin that calls it |
Allowed memory size of N bytes exhausted | A script ran out of PHP memory | Raise the limit, the one case where more memory is the real fix. Fixing the allowed memory size exhausted error covers both WordPress’s constant and the host’s memory_limit |
Cannot redeclare | The same class or function is loaded twice, often a duplicated plugin or two plugins bundling one library | Rename one of the two conflicting plugins |
Parse error: syntax error | A plugin or theme file has a typo, often from a half-finished upload | Re-upload the named file, or roll back to the last working copy |
Uncaught Error: Class "X" not found | A plugin was removed but other code still expects its class | Reinstall the missing plugin, or remove the code in the file the log names |
This table is a guide to common patterns. The log’s own wording wins over it, and the decoder reads the exact line for you.

wp-content/debug.log on our test site. The path after wp-content/plugins/ names the plugin at fault.3. Deactivate the named plugin or theme
You can’t reach /wp-admin, so do it over SFTP. Rename the plugin’s folder, for example some-addon to some-addon.off. WordPress can’t load a folder it can’t find, so the plugin stops running and the site comes back.
If the log points at your theme, rename the active theme’s folder the same way. That stops the fatal and brings /wp-admin back, but it does not switch the front end to a working theme. The function that does, validate_current_theme(), runs from two places in WordPress 7.1.4: the Appearance → Themes screen and the Customizer. The Dashboard and other admin screens don’t call it. So log in, open Appearance → Themes once, and WordPress switches to Twenty Twenty-Five (the WP_DEFAULT_THEME in 7.1.4), or to the newest bundled default theme you still have. If no bundled default theme is installed, it has nothing to switch to, so upload one first. Until then, logged-out visitors see an empty page, which is the theme row in the table above.
4. If the log won’t write
Either wp-content isn’t writable, or the error happened before WordPress turned logging on (the wp-config.php and server rows above). Check the host’s PHP error log instead:
find . -name "error_log" -newermt "-1 hour"
That command finds any file named error_log changed in the last hour. It holds the same kind of line in a different file. If it finds nothing, check PHP’s error_log setting (phpinfo() lists it, or ask the host). When that setting is empty, the PHP manual says errors go to the server’s own logger, for example Apache’s error log.
What not to do
Don’t just raise the memory limit. Bumping WP_MEMORY_LIMIT to 256M or 512M fixes the blank page only if the log says Allowed memory size of N bytes exhausted. If the error is Call to undefined function, more memory changes nothing. Read the log first; if it does name memory, the memory exhausted guide explains which limit to raise.
Don’t treat clearing the cache as a diagnosis. The white screen is PHP stopping on the server. A stale cached file can’t cause it, though a broken caching plugin can, and the log will name it. Purge the page cache after the fix, though: a cache or CDN that stored the blank page can keep serving it after the site works again.
Don’t edit or reinstall core WordPress. The fatal is rarely in wp-includes or wp-admin. It’s in the plugin or theme the log points to, and reinstalling core treats a cause you haven’t confirmed.
Don’t disable every plugin and re-enable them one by one before you read the log. Bisecting works, but it’s slow. The log names the folder in one step. Keep the switch-everything-off method for when there’s no readable error at all.
Don’t leave debugging on, and don’t forget the log file. Once the site is back, set WP_DEBUG back to false. wp-content/debug.log sits inside the public web root, so on many hosts anyone can read it at yoursite.com/wp-content/debug.log even after WP_DEBUG is off. Delete it, or block direct access to *.log files, once you’re done.
Still stuck?
If the log names a plugin but renaming it doesn’t clear the screen, there’s a second fatal underneath. Reload, read the new last line, and repeat. If the site loads but only the post editor is blank, that is a different fault, usually JavaScript: see a blank block editor instead of a blank site. If the message itself is the problem, the error log decoder translates the error type and file path.
Sources
- WordPress Advanced Administration: Debugging in WordPress
- WordPress 7.1.4 source: wp-settings.php, class-wp-fatal-error-handler.php, template-loader.php, theme.php (validate_current_theme)
- PHP manual: Runtime configuration for errors (display_errors, error_log)
- PHP manual: memory_limit
William Lopez is the founder of Odie Themes. He builds the free WordPress tools and themes on this site and has been on WordPress.org since December 2019.
FAQ
Questions
Why is my WordPress site showing a blank white page?
Almost always a PHP fatal error that nothing printed. Since WordPress 5.2 most fatals show "There has been a critical error on this website" instead, so a page that is truly blank usually means a case the handler cannot cover: an error in wp-config.php, a fatal after part of the page was already sent, or the handler switched off. The reason is still recorded. Turn on the debug log, open wp-content/debug.log, and read the last fatal line.
Where is the WordPress debug.log file?
WordPress writes it to wp-content/debug.log, but only once logging is switched on. wp-config.php already defines WP_DEBUG once, as false. If you add a second define() for it, PHP keeps the first value and raises a "Constant WP_DEBUG already defined" warning, so change the existing line to true instead. Then add WP_DEBUG_LOG as true and WP_DEBUG_DISPLAY as false so errors stay off the public page, and reload the broken page once to write a fresh entry.
How do I deactivate a WordPress plugin when I can't access wp-admin?
Rename the plugin's folder over SFTP, for example some-addon to some-addon.off. WordPress cannot load a folder it cannot find, so the plugin stops running and the site comes back. If the log points at your theme instead, renaming the theme folder stops the fatal and brings wp-admin back, but the front end stays broken until you open Appearance > Themes or the Customizer once. Those are the screens that run validate_current_theme() and switch you to a bundled default theme. The Dashboard and other admin screens do not.
Does increasing the memory limit fix the WordPress white screen of death?
Only if the log says Allowed memory size of N bytes exhausted. If the error is something else, such as Call to undefined function, raising WP_MEMORY_LIMIT to 256M or 512M does nothing. Read the log first, then raise memory only if memory is the stated problem.
What does "There has been a critical error on this website" mean?
It is the message from the fatal error handler added in WordPress 5.2. The handler is registered before plugins and the theme load, so it catches most fatal errors, including syntax errors in plugin files, that used to leave a blank page. When the error comes from a plugin or theme and happens in wp-admin or on the login screen, it also emails a Recovery Mode link to the admin address. A blank page instead of that message means the handler could not run or could not print, for example after a typo in wp-config.php.