Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Explainer

What Causes the WordPress White Screen of Death?

Short answer

A WordPress white screen of death is almost always a PHP fatal error that stops the page before any HTML loads. The most common causes are a plugin conflict, a theme or code error, an exhausted memory limit, or a broken update. Since WordPress 5.2, the same error often shows a short critical-error message instead, and WordPress emails the site admin a Recovery Mode link.

Key takeaways

  • A white screen of death is a PHP fatal error that stops the page before any HTML loads.
  • Since WordPress 5.2, many fatal errors show a critical-error message and send a Recovery Mode email instead of a blank page.
  • The debug log at wp-content/debug.log names the file and line where PHP stopped.
  • Renaming the wp-content/plugins folder switches all plugins off at once when the dashboard is out of reach.
  • Raise the memory limit only when the log shows an exhausted-memory error.

What is the WordPress white screen of death?

The white screen of death is a blank white page that appears when PHP hits a fatal error and stops before sending any HTML to the browser.

Learn WordPress calls it a generic error with a number of possible causes, and names plugin or theme compatibility issues as the most common ones. Read the Troubleshooting Basics lesson on Learn WordPress for the official list.

Your content is usually still safe in the database, since the error stops the page from loading rather than deleting anything.

This guide explains how to work out which cause you have. For the step-by-step repair, see How to Fix the WordPress White Screen of Death in WordPress.

Why does WordPress show a blank page instead of an error?

WordPress hides PHP errors on live sites by default, so a fatal error leaves the browser with nothing to show.

WordPress.org's debugging guide says PHP only displays fatal errors or shows a white screen when errors are reached, and that WP_DEBUG_DISPLAY controls whether those messages appear in the page. See Debugging in WordPress.

Since WordPress 5.2, the fatal error handler usually replaces the blank page with a short message: "The site is experiencing technical difficulties. Please check your site admin email inbox for instructions." WordPress.org's wp-config guide records that wording in Editing wp-config.php.

A pure white page still appears when the error happens before WordPress can load its handler, or when error display is off and no log is running.

A 500 error is a close cousin of the white screen, and the same log-first method finds its cause. See How to Fix the 500 Internal Server Error in WordPress.

What are the most common causes of a white screen?

Six causes cover almost every white screen: a plugin conflict, a theme or code error, low memory, a broken update, a PHP version mismatch, or damaged core files.

The trigger usually tells you where to look first. A white screen that starts right after a change points at that change.

CauseTypical triggerWhat the log usually says
Plugin conflictA plugin is installed or updatedFatal error in wp-content/plugins/plugin-name/
Theme or code errorA theme change or an edit to functions.phpParse error in wp-content/themes/theme-name/functions.php
Memory exhaustionImports, page builders, or large catalogsAllowed memory size of N bytes exhausted
Broken updateAn update stops midwayFailed opening required file in wp-includes/
PHP version mismatchA plugin needs a newer PHP versionCall to undefined function
Damaged core filesA failed upload or a bad editFailed opening required file in wp-admin/

WordPress.org recommends PHP 8.3 or greater as of November 2026, so an old PHP version is worth checking early. See the Requirements page on WordPress.org.

Check the full version list in WordPress Minimum Requirements (Current) before you blame a plugin.

How can you tell a plugin caused the white screen?

A plugin is the likely cause when the white screen appears right after you install, update, or change a plugin.

Learn WordPress advises deactivating plugins by renaming the wp-content/plugins folder to plugins-old over FTP, which switches them all off at once. The Troubleshooting Basics lesson gives the exact folder steps.

If the site returns, rename the folder back and reactivate plugins one at a time until the white screen comes back. The last one you switched on is the cause.

The debug log often names the plugin folder in the fatal error line, which saves the one-by-one check.

For the full isolation method, see How to Fix Plugin Conflicts in WordPress.

How can you tell the theme or custom code caused it?

The theme or custom code is the likely cause when the white screen follows a theme change or an edit to a PHP file such as functions.php.

A parse error in the log names the file and line number, which points at the exact edit that broke the site.

Learn WordPress advises renaming the active theme folder over FTP, which makes WordPress fall back to an installed default theme. The Troubleshooting Basics lesson covers this switch.

If the site returns with the default theme, the fault sits in your theme or in a snippet it loads.

A syntax error from a pasted snippet is the most common form of this cause. Remove the snippet, clear the error, and add code through a child theme or a code snippets plugin instead.

How can you tell the site ran out of memory?

Memory is the likely cause when the log says the allowed memory size was exhausted, or when the white screen hits heavy pages such as imports.

The PHP manual says memory_limit sets the most memory a script may use, and lists 128M as the default value. See Description of core php.ini directives in the PHP manual.

WooCommerce's server recommendations ask for a WordPress memory limit of 256 MB or greater as of November 2026, which is double the PHP default. See WooCommerce Server Recommendations.

Raise the limit only when the log shows an exhausted-memory error. Raising it for other causes hides nothing and fixes nothing.

See How to Fix “Allowed Memory Size Exhausted” in WordPress for the exact setting to change.

How can you tell an update or a broken file caused it?

An update is the likely cause when the white screen starts during or right after a WordPress, plugin, or theme update.

An update that stops midway can leave half-written files, and the log then names a missing or damaged file in wp-includes or wp-admin.

A page that says “Briefly unavailable for scheduled maintenance” is a different fault: a leftover .maintenance file, not a white screen.

Damaged core files are fixed by replacing wp-admin and wp-includes with fresh copies from the same WordPress version, without touching wp-content.

WordPress also rolls back a plugin or theme automatically when an automatic update causes a fatal error, so check whether the update already reverted itself before you start repairs.

What does the debug log tell you about the cause?

The debug log names the exact file and line where PHP stopped, which usually points straight at the cause.

Add three lines to wp-config.php above the “stop editing” comment, then reload the blank page once.

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

WordPress.org's debugging guide says WP_DEBUG_LOG needs WP_DEBUG enabled, and that the log is saved to wp-content/debug.log. See Debugging in WordPress.

Read the last “PHP Fatal error” line first. The folder name in its path tells you whether a plugin, a theme, or core broke.

WordPress.org warns that debug tools are meant for local and staging sites, so set WP_DEBUG back to false and delete debug.log after the fix.

How do you check whether Recovery Mode caught the error?

Recovery Mode catches many fatal errors since WordPress 5.2, so check your admin email for its login link before you touch any files.

WordPress.org's wp-config guide says Recovery Mode shows an error message instead of a white screen when a plugin causes a fatal error. See Editing wp-config.php.

The email names the plugin or theme and the file and line, and its link logs you in with that extension paused for your session only.

If no email arrived, check spam, then confirm the admin email address under Settings, then General is current.

The same screen is covered in How to Fix “There Has Been a Critical Error on This Website” in WordPress.

What if the white screen only hits wp-admin?

A white screen that hits only wp-admin, while the public site still loads, usually points at a plugin that runs in the dashboard.

Use Recovery Mode first, since its link opens the dashboard with the faulty plugin paused for your session.

If Recovery Mode did not trigger, rename the plugins folder over FTP, then switch plugins back on one at a time from the dashboard.

A white screen on every page, front and back, points at the theme, a must-use plugin, or a core file instead.

How do you tell a database problem from a white screen?

A database problem usually shows a message, not a white page, so a pure white screen rarely means the database is down.

WordPress shows “Error establishing a database connection” when it cannot reach the database, which is a different fault with its own repair.

If the debug log shows database errors, WordPress.org's wp-config guide notes that database errors are printed only when WP_DEBUG is true. See Editing wp-config.php.

Check the database login details in wp-config.php only after the log points at the database, since guessing there wastes time.

What mistakes should you avoid?

The most common mistake is changing several things at once, which hides the real cause and makes the fix hard to repeat.

  • Leave WP_DEBUG on after the fix. Turn it off and delete debug.log, since the log sits in a public folder.
  • Raise the memory limit before reading the log. Memory only helps when the log shows an exhausted-memory error.
  • Edit wp-config.php without a backup. One typo there can break the whole site, including the dashboard.
  • Reinstall WordPress before checking the log. A reinstall rarely helps when a plugin or theme is the cause.

Work through one cause at a time: read the log, name the cause, fix that one thing, then reload the page.

Frequently asked questions

Can a white screen delete my content?

No. The white screen means PHP stopped before the page could load, but your posts, pages, and media stay in the database. Once you remove the plugin, theme, or code that caused the fatal error, the same content loads again. Keep a backup before you edit files, so a wrong change never puts that content at risk.

Why does my site show a critical error message instead of a white screen?

Since WordPress 5.2, the fatal error handler catches many plugin and theme errors and shows a short critical-error message instead of a blank page. It also emails the site admin a Recovery Mode link. A pure white page still appears when the error happens before WordPress can load that handler.

How long should I leave WP_DEBUG on?

Leave it on only while you diagnose the fault. Once the site loads again, set WP_DEBUG back to false in wp-config.php and delete wp-content/debug.log. The log file sits in a public folder, so leaving it there can expose file paths and error details to anyone who finds it.

What if the debug log is empty after a white screen?

An empty log usually means the error happened before WordPress loaded, or that WP_DEBUG was not set before you reloaded the page. Check that the three debug lines sit above the stop-editing comment in wp-config.php, reload the blank page once, then read the log again. If it stays empty, ask your host to check the server PHP error log.

Do I need a developer to fix a white screen?

Often no. Plugin, theme, and memory causes are fixed by renaming a folder, removing a snippet, or raising a limit, and the debug log names the cause. Call your host or a developer when the log points at server settings, when the error sits in wp-config.php itself, or when the site stays blank after the common causes are ruled out.

Sources

  1. Debugging in WordPress WordPress Developer Resources
  2. Editing wp-config.php WordPress Developer Resources
  3. Troubleshooting Basics Learn WordPress
  4. Requirements WordPress.org
  5. Description of core php.ini directives PHP Manual
  6. WooCommerce Server Recommendations WooCommerce

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test