WordPress white screen of death: how to find the cause and fix it
A blank WordPress page usually means a PHP fatal error. How to read the error log, disable plugins and themes, raise the memory limit, and get the site back.
· 6 min read · By the Spot Downtime team
You load your WordPress site and get a completely blank page. No error, no theme, nothing. This is the “white screen of death” (WSoD). It nearly always means PHP hit a fatal error and, because error display is off on production sites, printed nothing.
The cure is to make the hidden error visible, then fix what it names. Most of the time that is a plugin, a theme or a memory limit.
What you are looking at
WordPress is a PHP application. When PHP stops mid-request, the web server sends whatever output exists, which is often an empty body. Depending on the setup the status code is 500 or, less helpfully, 200 with nothing in it. That second case matters for monitoring, covered below.
Typical triggers:
- A plugin or theme update with a coding error or a PHP version incompatibility.
- A PHP upgrade by your host that an older plugin cannot run on.
- The PHP memory limit being exhausted.
- A half-finished update that left core, plugin or theme files incomplete.
- A syntax error from editing
functions.phpor another file by hand.
Step 1: check your email and recovery mode
Since WordPress 5.2, a fatal error caused by a plugin or theme triggers an email to the site admin address with the subject mentioning a technical issue and a special recovery mode link. Open it, log in, and WordPress will tell you which plugin or theme crashed and let you deactivate it. If that email never arrived, go on to the next step.
Step 2: turn on the error log
Edit wp-config.php in the site root. Add these lines above the comment that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the page, then read wp-content/debug.log. The last lines name the file and line that failed:
PHP Fatal error: Uncaught Error: Call to undefined function foo() in
/var/www/html/wp-content/plugins/some-plugin/includes/bar.php:42The path tells you the culprit: a folder under plugins/ is a plugin, one under themes/ is a theme. Your host's own PHP error log, usually in the control panel or /var/log, works too. Turn WP_DEBUG back off when you are done, and keep WP_DEBUG_DISPLAY false on a live site so visitors never see error text.
Step 3: disable the plugin or theme
If the log named one, turn it off. If you cannot get into the dashboard, do it from the file system.
Rename the folder
cd wp-content/plugins
mv some-plugin some-plugin.disabledWordPress treats a plugin whose folder is missing as deactivated. If you do not know which plugin it is, rename the whole plugins folder to disable all of them, then rename it back and re-enable plugins one at a time:
mv wp-content/plugins wp-content/plugins.off
mkdir wp-content/pluginsUse WP-CLI
If you have shell access, WP-CLI is quicker and safer:
wp plugin deactivate --all
wp plugin activate woocommerce # re-enable one by one
wp theme list
wp theme activate twentytwentyfour # fall back to a default themeIf the site returns after switching to a default theme, the problem is in your theme, often a recent edit to functions.php.
Step 4: check the memory limit
If the log says Allowed memory size of 134217728 bytes exhausted, PHP ran out of memory. Raise WordPress's limit in wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );This cannot exceed the limit your host sets in php.ini (memory_limit). If it still fails, ask the host to raise it or look for the plugin that uses so much. A runaway import or backup plugin is a frequent cause.
Step 5: repair core files and PHP version
- Corrupt core files. After an interrupted update, verify and replace WordPress itself without touching your content:
wp core verify-checksums
wp core download --force --skip-content- PHP version mismatch. If the host recently changed PHP, the error usually mentions a removed function or a syntax problem in an old plugin. Update the plugin, or switch the PHP version back in your hosting panel while you do.
- Stuck maintenance mode. A
.maintenancefile left in the site root after a failed update shows a maintenance message. Delete it.
Back up first
wp-content and a database export. Most WSoD fixes are harmless, but a backup makes them reversible.Why uptime monitoring often misses a white screen
A basic check that only looks for a 200 response can pass while the page is blank, because some setups return 200 with an empty body. To catch it, add a keyword check for text that must appear on the page, such as your site name or a footer phrase. If the keyword is missing, the monitor counts as down even though the server answered 200.
Spot Downtime's website monitoring supports keyword checks and confirms failures from three regions before alerting, so a single network blip does not wake you. The website down checklist covers what to do in the first minutes of any outage.
- Use recovery mode or turn on
WP_DEBUG_LOGto see the real error. - Disable the plugin or theme named in the log.
- Raise
WP_MEMORY_LIMITif memory ran out. - Verify core files and check the PHP version.
- Add a keyword check so a blank page triggers an alert.
Get new guides by email
Practical posts on monitoring, outages, error fixes and on-call, when they're published. No spam.
Keep reading
- Troubleshooting · HTTP errorsEvery website error message explained: HTTP codes, browser errors and email bouncesAn index of the errors you'll meet running a website, sorted by the layer that failed: DNS, network, HTTPS, HTTP 4xx and 5xx, Cloudflare 52x and email bounces, each with a full guide and a free tool to check it.October 5, 2026 · 4 min read
- HTTP errors · Troubleshootingnginx 502 Bad Gateway: fixing "connect() failed" to PHP-FPM and other upstreamsnginx logs connect() failed (111), (2) or (13) when it can't reach your app. What each errno means, and how to fix PHP-FPM sockets, ports, permissions and SELinux.November 13, 2026 · 7 min read