AmaarDev.
Hire Me

How to Fix the White Screen of Death in WordPress (2026 Guide)

Developer troubleshooting the white screen of death WordPress error on a laptop

You open your site and see… nothing. Just a blank, empty page staring back at you. No error message, no clues, no way into wp-admin. That is the white screen of death WordPress users dread — and unlike most errors, it tells you absolutely nothing about what went wrong.

I have fixed this exact problem on client sites more times than I can count. The good news: the white screen of death is almost always one of five things, and you can work through them in under 30 minutes with nothing more than your hosting file manager. This guide walks you through each step in order, from the most common cause to the least.

What Causes the White Screen of Death?

The white screen of death in WordPress is almost always a PHP fatal error that PHP is configured not to display. Instead of an error message, the browser gets an empty response. The usual suspects are:

  • A plugin conflict — one plugin updated and clashed with another, with your theme, or with the PHP version on your server. This is the most common cause by far.
  • A theme problem — usually right after switching or updating a theme, or after editing functions.php.
  • Exhausted PHP memory — a script asked for more memory than your host allows, so PHP died silently.
  • A stuck core update — a failed WordPress update left a .maintenance file behind.

Work through the steps below in order. Stop as soon as your site comes back.

Before You Touch Anything: Check Your Email

Since WordPress 5.2, core tries to help you. When a plugin or theme throws a fatal error, WordPress pauses the offending code and emails the admin address a message titled “Your Site is Experiencing a Technical Issue.” That email contains a link to Recovery Mode — a special wp-admin session where you can deactivate the broken plugin or theme directly, without FTP.

So step zero: check the inbox of your site’s admin email address. If that email is there, click the Recovery Mode link, deactivate the culprit, and you are done. If it is not there — or the white screen affects every page including wp-login — keep reading.

Step 1: Enable WordPress Debug Mode

Your first goal is to replace the blank screen with an actual error message. Open wp-config.php in your site’s root folder (via your host’s File Manager or FTP) and find this line:

define( 'WP_DEBUG', false );

Replace it with:

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

WP_DEBUG_DISPLAY set to false keeps errors off the public-facing page — important if your site is live — while WP_DEBUG_LOG writes every error to wp-content/debug.log, which you can open and read.

Reload the broken page, then open wp-content/debug.log. You will usually see a fatal error naming the culprit directly, something like:

PHP Fatal error: Uncaught Error: Call to undefined function my_plugin_load()
in /home/user/public_html/wp-content/plugins/broken-plugin/broken-plugin.php on line 42

That path tells you exactly which plugin or theme is crashing. Fix or remove it (steps below), and the white screen goes away.

Important: turn debug mode back off when you are finished. Leaving WP_DEBUG on in production can expose paths and details to attackers. Edit wp-config.php again and set it back to false — you can leave WP_DEBUG_LOG on if you like, it is harmless and useful. WordPress documents the full set of debug constants in its official debugging guide.

Step 2: Deactivate All Plugins at Once

If you cannot reach wp-admin to deactivate plugins normally, you can do it at the file level. Connect via your host’s File Manager or FTP, go to wp-content/, and rename the plugins folder to plugins-disabled.

WordPress looks for wp-content/plugins on every load. When it cannot find the folder, it silently deactivates every plugin. Nothing is deleted — renaming is fully reversible.

Reload your site. If the white screen of death is gone, a plugin caused it. Here is the cleanup:

  1. Rename the folder back to plugins. All your plugins come back, but WordPress leaves them deactivated — your settings are preserved.
  2. Go to Plugins > Installed Plugins in wp-admin and reactivate them one by one, reloading the site after each one.
  3. When the white screen of death returns, the plugin you just activated is the culprit. Leave it deactivated and contact the plugin developer or find an alternative.

Start with whichever plugin you most recently updated or installed — it is the culprit more often than not.

Step 3: Switch to a Default Theme

If disabling plugins did not help, your theme is next. Via File Manager or FTP, go to wp-content/themes/ and rename your active theme’s folder — for example, rename mytheme to mytheme-broken.

When WordPress cannot find the active theme, it falls back to a default theme (Twenty Twenty-Four or Twenty Twenty-Five) if one is installed. If the site loads, your theme — or something in it, often a bad functions.php edit or an outdated template file — was the problem.

Practical advice: never edit a parent theme’s functions.php or template files directly. That is exactly what child themes are for — they survive updates and keep a single broken edit from taking down your whole site.

Step 4: Increase the PHP Memory Limit

Sometimes the white screen means a script ran out of memory. This is common on shared hosting with restrictive defaults, or on sites running several heavy plugins (page builders, security suites, and multilingual plugins together are classic offenders).

In wp-config.php, right before the line that says “That’s all, stop editing!”, add:

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

Save and reload. WordPress defaults to 40MB, and hosts often cap it low — 256M resolves memory-exhaustion white screens on most shared plans. If your host overrides this value at the server level, you will need to ask their support to raise it instead.

Worth knowing: raising the limit fixes the symptom, not the cause. If a plugin routinely eats 256MB, that plugin has a bug or your site has outgrown the plan. Check Tools > Site Health in wp-admin afterward — it flags memory pressure and outdated PHP versions clearly.

Step 5: Check for a Stuck .maintenance File

If the white screen appeared right after clicking “Update” on WordPress core, the update may have failed halfway. WordPress creates a .maintenance file in your site’s root folder during updates and deletes it when finished. If the update died mid-process, the file stays — and every visitor sees nothing while it is there.

Open your site’s root folder in the File Manager (enable “show hidden files” — files starting with a dot are hidden by default), and if you see .maintenance, delete it. Then check Dashboard > Updates to make sure core actually completed the update; re-run it if needed.

When to Call Your Hosting Support

If you have worked through all five steps and the screen is still white, the problem is below WordPress — at the server level. Common server-side causes include corrupted core files, a PHP version incompatible with your WordPress install, or a full disk quota. A good host can spot these from server logs in minutes. Check your host’s error logs in the control panel first, then open a support ticket with the debug.log output attached — you will save everyone time.

How to Prevent the White Screen of Death

Fixing the white screen of death is satisfying; never seeing it again is better:

  • Back up before every update. One-click restores turn a disaster into a 5-minute detour. My complete WordPress backup guide covers how to set this up properly.
  • Update in the right order: plugins and themes first, then WordPress core, then check the site between each batch.
  • Keep PHP current. WordPress 6.x runs best on PHP 8.1 or newer; running PHP 7.x with modern plugins is asking for fatal errors.
  • Test on staging. Most decent hosts offer one-click staging — run updates there first.
  • Keep a recent backup off-site so a worst-case restore never depends on the same server that just failed. (See the migration guide for how to move a site safely when your host is part of the problem.)

Wrapping Up

The white screen of death WordPress throws at you looks terrifying, but it is a mechanical problem with a mechanical fix: get an error message with debug mode, eliminate plugins, eliminate the theme, check memory, check for a stuck update. Work the list in order and you will find it.

If your site is showing a white screen right now and you do not have time to debug it yourself, get in touch — I troubleshoot and repair broken WordPress sites, usually within a day.