How to Fix the WordPress White Screen of Death Fast

You click "Update" on a plugin, the page reloads, and your whole clan site is a blank white page. No error, no menu, not even the admin bar. The WordPress white screen of death looks terrifying because it tells you nothing, but in my experience about nine times out of ten it comes down to one of four causes, and most of them can be fixed in under 20 minutes without a developer.

This guide walks through the order I use on fan sites and community blogs: find out what broke, get the site back up, then fix the actual cause so it does not happen again next Tuesday.

What causes the WordPress white screen of death

A white screen means PHP hit a fatal error and WordPress was told not to show it. Since WordPress 5.2, the core software usually catches these and shows "There has been a critical error on this website", plus an email to the admin address. You only get a truly blank page when that safety net fails or when error display is switched off on the server. The usual culprits are:

A plugin update or conflict. By far the most common. One plugin calls a function another one removed, or needs a newer PHP version than your host runs.
A theme problem. A broken functions.php, often after someone pasted a snippet from a forum into the theme editor.
PHP memory limit. Heavy page builders and gallery plugins can exceed a 64 MB or 128 MB limit, especially on cheap shared hosting.
PHP version mismatch. Your host upgraded from PHP 7.4 to 8.2 and an old plugin uses code that 8.x no longer accepts.

Step one: check the recovery email and the error log

Before you touch anything, open the inbox for your site's admin email. WordPress sends a message titled "Your Site is Experiencing a Technical Issue" that names the plugin or theme at fault and includes a special recovery mode link. That link lets you log in with the broken plugin paused, so you can deactivate it from the normal Plugins screen. If the email is there, you may be done in two minutes.

No email? Log in to your hosting panel and look for an error log. On cPanel it is usually under Metrics, then Errors, or as a file called error_log in your site folder. The last few lines will say something like "PHP Fatal error: Uncaught Error: Call to undefined function" followed by a file path. The folder name in that path, such as wp-content/plugins/old-gallery/, tells you who to blame.

If there is no log at all, switch on debugging. Open wp-config.php in your host's file manager and change the debug line to:

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

Reload the white page once, then open wp-content/debug.log. Turn these settings back to false when you are finished, because a public debug log can reveal file paths to anyone who guesses the address.

Step two: disable plugins without the dashboard

If you cannot reach wp-admin, you can still turn plugins off. Using the file manager or an FTP client, go to wp-content and rename the plugins folder to plugins-off. WordPress cannot find any plugins, so it deactivates them all. Reload the site.

If it comes back, rename the folder to plugins again. Everything stays deactivated, so now reactivate plugins one at a time from the dashboard, reloading the front page after each one. When the screen goes white again, you have found the culprit. On a site with 25 plugins this takes about 10 minutes. Our longer guide on finding a WordPress plugin conflict covers the trickier cases where two plugins only break when both are active.

Step three: rule out the theme and memory limit

If plugins were not the problem, test the theme. In wp-content/themes, rename your active theme folder. WordPress will fall back to a default theme such as Twenty Twenty-Four if one is installed. If the site loads, the issue is in your theme, usually a recent edit to functions.php. This is exactly why custom code belongs in a child theme for your fan site rather than in the parent theme, where one typo takes everything down.

For memory, add this line to wp-config.php above the "That's all, stop editing" comment line:

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

If the site returns, you have bought time, but treat it as a warning. Something on the site is using far more memory than a normal blog needs, and you should find out what.

Why rolling back is not always the right fix

The common advice after a white screen is "just roll back the plugin to the old version". I understand the appeal, and plugins like WP Rollback make it one click. But I push back on making it the default.

A lot of plugin updates on gaming sites are security patches. Rolling back a forum, membership or form plugin to dodge a fatal error can reopen a hole that bots are already scanning for, sometimes within 48 hours of the patch being published. The better order is: pause the plugin, read its changelog and support forum, and check whether the update simply needs a newer PHP version. Many white screens after an update are solved by asking your host to move you from PHP 7.4 to 8.1 or 8.2, which takes a dropdown change in most panels.

Roll back only as a short bridge, with a reminder in your calendar to update again within a week.

Preventing the next white screen

You will not prevent every fatal error, but you can make them cheap. Three habits help most:

Test updates on staging first. Most hosts include a one click staging copy. Update there, click through five key pages, then push to live.
Keep a fresh backup before every update session. A restore point from this morning beats a careful diagnosis at midnight.
Trim plugins you do not need. Every inactive or abandoned plugin is another thing that can break when PHP changes.

Update in small batches of two or three plugins, not all 20 at once. If something breaks, you know where to look.

Frequently asked questions

Why is my WordPress site showing a blank white page?

A blank white page almost always means a PHP fatal error with error display turned off. The most common trigger is a plugin or theme update that conflicts with something else or needs a newer PHP version. Check the admin email and your server error log to see which file caused it.

Can I fix the white screen of death without wp-admin access?

Yes. Use your host's file manager or FTP to rename the wp-content/plugins folder, which deactivates every plugin. If that does not work, rename your active theme folder so WordPress falls back to a default theme.

Does the white screen of death delete my content?

No. Your posts, pages and comments live in the database, which a fatal error does not touch. Once you fix or remove the broken code, everything reappears exactly as it was.