How to Fix WordPress White Screen of Death — Step-by-Step WSOD Guide

To fix the WordPress white screen of death, start by enabling WP_DEBUG in wp-config.php to reveal the actual error, then disable all plugins via FTP and switch to a default theme. The wordpress white screen of death (WSOD) is almost always caused by a plugin conflict, PHP memory exhaustion, or a theme error — and every single one of those is fixable without calling a developer.

What Is the WordPress White Screen of Death?

The wordpress white screen of death is exactly what it sounds like: you load your site and get nothing. No error message. No layout. Just a blank white page staring back at you like a broken promise from your hosting provider. It can affect the front end, the admin dashboard, or both.

Since WordPress 5.2, the pure white screen has been partially replaced by the message “There has been a critical error on this website.” That’s actually progress — it means WordPress caught a fatal PHP error before it completely choked. Older installs, or errors that hit before WordPress fully loads, still produce the classic blank white screen.

According to the WordPress.org Advanced Administration Handbook, the WSOD is one of the most documented errors in the entire ecosystem. That’s cold comfort when your site is down, but it means there’s a well-worn path to fixing it.

What Causes the WordPress White Screen of Death?

The wordpress white screen of death doesn’t have one single cause — it has a hit list. Knowing which culprit is most likely saves you hours of blind troubleshooting. Here are the four most common offenders, ranked by how often they actually cause the problem.

Plugin Conflicts

Plugin conflicts are the undisputed #1 cause of the wordpress white screen of death. One bad plugin update — especially with automatic updates enabled — can throw a fatal PHP error that takes your entire site offline. The plugin doesn’t even have to be poorly coded; it just needs to conflict with another plugin, your theme, or your current PHP version.

PHP 8.x has made this worse. Strict typing in PHP 8 breaks legacy plugins that were written for PHP 7.x and never updated. If you recently upgraded your PHP version and suddenly hit the WSOD, a plugin is almost certainly the cause.

PHP Memory Exhaustion

WordPress ships with a default memory limit of 128MB. That sounds like plenty until you’re running WooCommerce, a page builder, a caching plugin, an SEO plugin, and a dozen other tools simultaneously. When PHP runs out of memory mid-execution, the wordpress white screen of death is the result.

Memory exhaustion is sneaky because it doesn’t always happen on every page load. You might see the WSOD only on specific pages — product archives, checkout, or heavily-built landing pages — while the rest of your site works fine.

Theme Errors

A syntax error in your theme’s functions.php file will trigger the wordpress white screen of death instantly. This happens most often when someone edits theme files directly in the WordPress editor without a child theme as a safety net. One missing semicolon. One mismatched bracket. Site gone.

This is exactly why we preach using a child theme — if the child theme breaks, you can delete it via FTP and your parent theme takes over. If you edited the parent theme directly, you’re in full WSOD territory with no easy rollback.

Failed WordPress Updates

A failed core update can leave truncated files on your server or — more commonly — leave a .maintenance file in your WordPress root directory. That file puts your site into maintenance mode indefinitely, which shows as a blank or near-blank screen to visitors. It’s not technically the wordpress white screen of death, but it looks identical from the outside.

Always follow a safe update process. Our guide on updating WordPress safely walks through exactly how to avoid update-triggered disasters before they happen.

How to Enable WordPress Debug Mode

Enabling debug mode is the single most important step when diagnosing the wordpress white screen of death. Without it, you’re guessing. With it, WordPress tells you exactly which file and line number caused the fatal error. Open your wp-config.php file via FTP or your host’s file manager and add these lines before the /* That's all, stop editing! */ comment:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Setting WP_DEBUG_DISPLAY to false keeps errors out of the browser (so visitors don’t see raw PHP errors) while WP_DEBUG_LOG writes them to wp-content/debug.log. Check that file immediately after triggering the white screen again. The error message will point you directly at the problem.

Our full WordPress debugging guide goes deeper into reading error logs, using Query Monitor, and advanced debugging techniques. For now, the snippet above is all you need to crack the WSOD case open.

How to Fix WordPress White Screen of Death by Disabling Plugins

If you can’t access your admin dashboard — which is common when the wordpress white screen of death hits both front end and back end — you need to disable plugins via FTP or your host’s file manager. You cannot do this from inside WordPress if WordPress won’t load.

Connect to your server via FTP and navigate to wp-content/. Find the folder named plugins and rename it to plugins_disabled. WordPress will immediately lose track of all plugins and deactivate them automatically. Reload your site — if the wordpress white screen of death is gone, a plugin was the cause.

Now rename the folder back to plugins and reactivate plugins one at a time from your dashboard. When the WSOD returns, you’ve found your culprit. Delete that plugin, find an alternative, or contact the developer with the error from your debug log.

How to Fix WordPress White Screen of Death by Switching Themes

If disabling plugins didn’t kill the wordpress white screen of death, your theme is the next suspect. Again, if you can’t access the admin panel, you’ll need FTP. Navigate to wp-content/themes/ and rename your active theme folder — something like mytheme_disabled. WordPress will automatically fall back to its default theme (Twenty Twenty-Four or whichever default is installed).

If your site loads after switching themes, the problem lives in your theme’s code. Check functions.php for syntax errors first — a missing semicolon or a bad function call is usually the culprit. If you were editing theme files directly, this is your sign to set up a child theme before you touch another line of code.

How to Increase PHP Memory Limit in WordPress

If your debug log shows a message like Fatal error: Allowed memory size of 134217728 bytes exhausted, you’ve found your WSOD cause. The fix is straightforward: increase WordPress’s PHP memory limit. Open your wp-config.php file and add this line:

define( 'WP_MEMORY_LIMIT', '256M' );

256MB handles the vast majority of WordPress setups, even heavy WooCommerce stores. If your host caps PHP memory below what you’re requesting, the wp-config.php change won’t fully take effect — you’ll need to contact your host or upgrade your plan. Some hosts also allow memory limit changes via php.ini or .htaccess.

For .htaccess, add: php_value memory_limit 256M. For php.ini, add: memory_limit = 256M. Try wp-config.php first — it’s the cleanest method and works across the widest range of hosting environments.

How to Check WordPress Error Logs

Once you’ve enabled WP_DEBUG as described above, your error log lives at wp-content/debug.log. Download it via FTP and open it in any text editor. You’re looking for lines that start with PHP Fatal error or PHP Parse error — those are the lines that caused the wordpress white screen of death.

Your server also keeps its own PHP error log, typically in your hosting control panel under “Error Logs” or in a file like /var/log/php_errors.log. If wp-content/debug.log is empty, check the server-level log — some fatal errors happen before WordPress can write to its own log file.

The Sucuri WSOD troubleshooting guide also recommends checking server access logs for 500 errors, which can reveal patterns — like the WSOD only happening on specific URLs — that point to more targeted fixes.

How to Use WordPress Recovery Mode

Since WordPress 5.2, the platform has included a built-in Recovery Mode that activates automatically when a fatal error is detected. WordPress sends an email to the admin address on file with a direct recovery link. That link lets you log into a special safe mode where you can deactivate the problem plugin or theme without needing FTP access.

If you’re dealing with the wordpress white screen of death right now, check the email inbox associated with your WordPress admin account. The subject line will be something like “Your site is experiencing a technical issue.” Click the recovery link, log in, and you’ll see a banner identifying the plugin or theme that caused the fatal error.

Recovery Mode is a lifeline, but it only works if WordPress itself loaded far enough to detect and log the fatal error. If the error happens at the server level before WordPress boots, Recovery Mode won’t fire — that’s when you need the FTP methods above.

How to Reinstall WordPress Core Files

If none of the above fixed the wordpress white screen of death, corrupted core files might be the problem. The cleanest fix is to reinstall WordPress core without touching your content. From your dashboard (if accessible), go to Dashboard → Updates and click “Re-install Now.” WordPress will download a fresh copy of core files and overwrite only the core — your themes, plugins, and database stay untouched.

If you can’t access the dashboard, do it manually. Download the latest WordPress zip from WordPress.org, extract it, and upload everything except the wp-content folder and wp-config.php via FTP. Those two are where your site lives — don’t overwrite them.

Also check your WordPress root directory for a file named .maintenance. A failed update sometimes leaves this file behind, which locks your site in maintenance mode indefinitely. Delete it via FTP and your site should come back immediately — no reinstall needed.

How to Prevent the WordPress White Screen of Death From Happening Again

Fixing the wordpress white screen of death once is painful. Fixing it three times because you didn’t change your habits is avoidable suffering. Here’s how to make sure the WSOD becomes a distant memory:

• Backup before every update. Use a solid WordPress backup strategy — automated daily backups minimum, with off-site storage.
• Test updates on staging first. Never auto-update plugins on a production site without a staging environment to catch conflicts.
• Use a child theme. Direct parent theme edits are a one-way ticket to the WSOD. Create a child theme and work there instead.
• Keep PHP version current but test first. PHP 8.x is faster and more secure, but verify plugin compatibility before upgrading on a live site.
• Monitor memory usage. Use a plugin like Query Monitor to watch memory consumption before it hits the ceiling.
• Use maintenance mode during updates. Our Maintenance Mode Toggle keeps visitors away from a potentially broken site while you update.
• Follow a safe update process. Our WordPress update guide walks through the exact workflow to update without downtime.

Frequently Asked Questions About the WordPress White Screen of Death