How to Fix the WordPress White Screen of Death
A blank WordPress page is almost always a hidden PHP fatal error. Make it visible, find the plugin or theme behind it and get the site back step by step.
· updated · 9 min read
In this article8 sections
The WordPress white screen of death is almost always a PHP fatal error that WordPress is not showing you. Make the error visible with debug logging, read the last fatal error, and it will usually name the plugin, theme or file that broke the site.
This guide goes through that process in a sensible order: confirm what kind of failure you actually have, get the error out of hiding, isolate plugins and themes, and only then look at memory, PHP versions, caches and core files. You need SFTP, SSH or your host's file manager. WP-CLI makes several steps faster, so commands are included where they help.
First, find out what kind of failure you have
A blank page and a broken page are not the same thing, and the exact symptom saves you time. Before you change anything, check these:
- A completely blank page with no text at all. Classic white screen. Usually a fatal error with error display turned off, or an error that happens before WordPress can render anything.
- "There has been a critical error on this website." This is the modern version of the white screen. Since WordPress 5.2, fatal error protection catches the crash and shows this message instead of a blank page.
- "Error establishing a database connection." Different problem. Check the database credentials in
wp-config.phpand whether the database server is up. The WordPress database repair guide covers that path. - "Briefly unavailable for scheduled maintenance." An update was interrupted and left a
.maintenancefile in the WordPress root. Delete it and reload. - Only wp-admin is blank, or only one page. Points to code that runs in a specific context, like an admin-only plugin feature, a page builder template or a shortcode on that page.
Then open the site in a private window and check the HTTP status in the network tab of your browser's developer tools (the DevTools tips article shows where). A 500 means PHP crashed. A 200 with an empty body can mean a cached blank page, so clear caches before you go hunting for code.
Use recovery mode when WordPress offers it
When fatal error protection catches a crash, WordPress emails the site's admin address with a link to recovery mode. That link logs you in with the broken plugin or theme paused, so you can deactivate it, update it or roll back. Only you see the paused state. Visitors still get the error until you fix it.
Check the spam folder before you give up on the email. Many sites never get it, because the server has no working mail setup or the admin address is an old inbox nobody reads. If the email is not there, move on to the logs.
Turn on debug logging and read the error
Connect to the server and open wp-config.php in the WordPress root. Add these lines above the comment that tells you to stop editing (it starts with "That's all"):
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
WP_DEBUG turns on error reporting, WP_DEBUG_LOG writes errors to wp-content/debug.log, and the last two lines keep errors off the screen so visitors never see file paths. Reload the broken page, then open debug.log and search for the most recent PHP Fatal error. A typical line looks like this:
PHP Fatal error: Uncaught Error: Call to undefined function example_helper() in /var/www/html/wp-content/plugins/example-plugin/includes/loader.php:42
The path is the answer most of the time. Here the culprit sits in plugins/example-plugin. If the message says Allowed memory size of ... bytes exhausted, you have a memory problem instead, covered further down.
Two warnings. First, wp-content/debug.log is publicly reachable by default on many servers, and it can contain paths and data you do not want indexed. WP_DEBUG_LOG also accepts a file path, so you can write the log outside the web root, for example define( 'WP_DEBUG_LOG', '/home/user/logs/wp-debug.log' );. Second, turn debugging off again when you are done. The official Debugging in WordPress page lists the other debug constants.
If no debug.log appears, the error probably happens before WordPress loads its configuration, or PHP cannot write to wp-content. Look in your host's PHP error log instead. On shared hosting it is often in the control panel, on a VPS it is in the PHP-FPM or web server logs.
Isolate the plugin or theme
If the log names a plugin or theme, start there. If it does not, or you cannot get a log, you isolate by elimination.
Without dashboard access
Rename the folder of the suspected plugin in wp-content/plugins, for example from example-plugin to example-plugin.off. WordPress cannot find the plugin and skips loading it. If the site comes back, you have your answer.
If you have no suspect, rename the whole plugins folder to plugins.off. If the site loads, a plugin is the cause. Rename the folder back and then disable plugins one at a time, or in halves, until the site breaks again. With twenty plugins, halving gets you to the culprit in about five rounds instead of twenty.
With WP-CLI
WP-CLI is faster and does not leave half-renamed folders behind. Save the list of active plugins first, because deactivating everything throws that list away:
wp plugin list --status=active --field=name > active-plugins.txt
wp plugin deactivate example-plugin
wp plugin deactivate --all
wp theme activate twentytwentyfive
If WP-CLI itself crashes because of the same fatal error, add --skip-plugins --skip-themes to the command so WordPress loads without them. The WP-CLI command reference has the full list.
Do not forget the less obvious places
Renaming the plugins folder does not touch everything that runs PHP on a WordPress site. Also check:
- Must-use plugins in
wp-content/mu-plugins. They load automatically and do not show up as normal plugins. Hosts often put their own code here. - Drop-ins like
advanced-cache.php,object-cache.phpanddb.phpdirectly inwp-content. A caching plugin that was removed without cleanup can leave a drop-in behind that still runs. - The theme, and especially a child theme's
functions.php. A single syntax error added through the theme editor is enough. Rename the active theme folder and WordPress falls back to a default theme, if one is still installed.
Memory limits and PHP version changes
If the log shows memory exhaustion, raise the WordPress memory limit in wp-config.php:
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
WP_MAX_MEMORY_LIMIT applies to admin tasks like image processing and imports. Your host's PHP memory_limit is the ceiling, and WordPress cannot go above it. If the site still runs out of memory at a generous limit, something is looping or loading far too much data. Raising the limit further only hides that.
A PHP upgrade on the server is another common trigger, especially when nobody on your side changed anything. Hosts move sites to newer PHP versions, and old plugins that call functions removed in PHP 8 crash immediately. Check which PHP version the site runs in your hosting panel or under Tools, Site Health. If an upgrade lines up with the crash, switch back temporarily, update or replace the plugin, and then upgrade again.
Caches, file permissions and core files
When the code looks fine but the page stays blank, work through the layers around WordPress:
- Clear every cache. Page cache plugin, server cache, CDN and OPcache. A blank page can be cached and served long after the error is gone. Restarting PHP-FPM, or the host's "clear cache" button, resets OPcache.
- Check the object cache. If
object-cache.phppoints at Redis or Memcached and that service is down, the site can fail on every request. - Check file permissions. Files should usually be
644and folders755. Wrong ownership after a migration or a manual upload can stop PHP from reading files. - Verify core files. Run
wp core verify-checksumsto compare core files with the official release. If something is modified or missing, reinstall core withwp core download --force --skip-content. Without WP-CLI, replace thewp-adminandwp-includesfolders with fresh copies of the same version. Never overwritewp-contentorwp-config.php.
If checksums fail on files you never touched, treat it as a possible compromise. The WordPress security hardening guide covers what to do next.
Make the next one boring
You cannot prevent every fatal error, but you can make them rare and quick to fix:
- Test updates on staging first, at least for big plugin updates and PHP upgrades. The staging environment guide shows how to set one up.
- Update in small batches. Updating fifteen plugins at once turns a five minute fix into a guessing game.
- Keep backups you have restored at least once. A backup you have never restored is one you cannot count on.
- Monitor page content as well as uptime. A white screen can return a
200status. An uptime check that looks for a known word on the page catches it. - Keep error logs on and private. Log to a file outside the web root, with display turned off, so the next fatal error is already written down when you need it.
Frequently asked questions
Why is my WordPress site showing a blank white page?
Almost always a PHP fatal error with error display turned off, most often caused by a plugin update, a theme change or a PHP version upgrade on the server. Turn on WP_DEBUG_LOG and read wp-content/debug.log to see the exact file and line.
How do I fix the white screen of death without admin access?
Use SFTP or your host's file manager. Enable debug logging in wp-config.php, then rename the suspected plugin folder or the whole plugins folder to disable plugins without logging in. WP-CLI over SSH does the same thing faster.
Can a plugin update cause the white screen of death?
Yes, it is the most common cause. An update can require a newer PHP version than your server runs, or conflict with another plugin or the theme. Recovery mode or renaming the plugin folder gets the site back while you roll back or wait for a fix.
Is it safe to leave WP_DEBUG on in production?
Leave it on only with WP_DEBUG_DISPLAY set to false and the log written outside the web root. Otherwise visitors can see errors, and the default debug.log file can be read by anyone who knows the path.
Why is only my WordPress admin showing a white screen?
Some plugins only run code in the dashboard, so they can crash wp-admin while the front end works. The fix process is the same: read the debug log, then disable the plugin it names.
Will I lose my content because of the white screen of death?
Usually not. Posts, pages and settings live in the database, and a fatal error in PHP code does not delete them. Take a fresh backup of files and database before you start changing things, just in case.
- WordPress
- Debugging
- PHP
- WP-CLI

Written by Pontus Henriksson
Co-founder and CEO of Walldy in Sundsvall. I have built for the web since I was fourteen, tested games for studios like Netflix and Bungie since 2021, and write about what I use in real projects.
Liked this? Get the next one.
New Claude skills, kits and what I learn building AI for small businesses. Not often, only when it is worth sending. Unsubscribe with one click.