WordPress White Screen of Death: How to Fix It and When to Recover

The WordPress white screen of death is a blank page where your site should be: no error message, no design, sometimes not even the admin area. It almost always means PHP hit a fatal error and stopped before it could print anything. In most cases your posts, pages and settings are still safe in the database, and the fix is to find the plugin, theme or setting that crashed and switch it off. Only when files or the database have really been lost does the job turn into a recovery.

This guide takes you through the checks in a safe order, from the quick recovery-mode link to manual fixes over SFTP, and explains what to do if the white screen turns out to be the visible sign of a site that is genuinely gone.

What causes the WordPress white screen of death

WordPress builds every page with server-side code. When that code meets an error it cannot continue past, it stops. If error display is switched off, which is correct on a live site, the visitor gets an empty page instead of a message. The usual triggers are:

• A plugin update or a new plugin that conflicts with another plugin, with the theme, or with the server software version.
• A theme update or a broken edit to functions.php, often a missing bracket or a pasted code snippet.
• Memory exhaustion. Page builders, large WooCommerce catalogues and import jobs can run past the memory limit set by the host.
• A server upgrade by the host. Old plugins and themes written for PHP 7 can fail on version 8 and later.
• Failed or interrupted updates that leave core, plugin or theme files half written, sometimes with a .maintenance file left behind.
• Missing or damaged files after a migration, a hack, a cleanup by a security tool, or a hosting problem.

The first five are fixable in minutes once you know which one it is. The last one is where data loss can be involved, so it is worth ruling it out early.

First, check what is actually blank

Before you change anything, spend two minutes narrowing the problem down. Each answer points to a different fix.

• Is the whole site blank, or only some pages? One blank page usually means a template, shortcode or block on that page. A completely blank site points to a plugin, the theme or the server.
• Does /wp-admin/ load? If the dashboard works but the front end is blank, the theme is the prime suspect. If both are blank, think plugins, memory or PHP version.
• Is it blank for everyone? Open the site in a private window and on mobile data. A cached blank page in a CDN or caching plugin can outlive the original fault.
• What changed recently? Updates, a new plugin, a code snippet, a host migration or a server upgrade notice in your hosting email are the strongest clues you have.

Step 1: Look for the recovery mode email

Since WordPress 5.2, fatal error protection catches many plugin and theme crashes. Instead of a blank page you may see “There has been a critical error on this website”, and WordPress emails the site’s administrator address with a subject like “Your Site is Experiencing a Technical Issue”. That email names the plugin or theme that failed and includes a special recovery-mode login link.

Use that link to log in, deactivate the plugin or switch the theme it names, and then exit recovery mode. Check the spam folder, and check the inbox of whichever address is set as the site’s admin email; on agency-built sites it is often the developer’s address rather than the owner’s. Recovery mode does not catch every error. Problems in core files, server configuration or memory before WordPress loads can still produce a plain white page with no email.

Step 2: Turn on debugging to see the real error

A blank page hides the message you need. You can bring it back safely by writing it to a log file instead of the screen. Connect with SFTP or your host’s file manager, open wp-config.php in the site root, and above the line that says “That’s all, stop editing” set:

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

Reload the blank page, then open /wp-content/debug.log. The last “PHP Fatal error” line usually names a file path. A path inside /wp-content/plugins/plugin-name/ tells you which plugin to disable; a path in /wp-content/themes/ points at the theme; “Allowed memory size exhausted” points at memory. The WordPress developer handbook explains these settings in its guide to debugging in WordPress. Switch debugging off again when you have finished, because the log can expose server paths.

How to read the most common log lines

Log entries look intimidating, but you only need three parts of each line: the type of error, the message and the file path. Typical examples:

• “Allowed memory size of 134217728 bytes exhausted” means the request ran out of memory (that number is 128 MB). The file path tells you which code was running at the moment, not necessarily the culprit; raise the limit first, then look for the heavy plugin.
• “Call to undefined function” usually appears when one plugin depends on another that is missing or deactivated, or when a theme calls a function removed in a newer WordPress release. The path names the code making the call.
• “syntax error, unexpected” followed by a line number means a file was edited by hand and a bracket, quote or semicolon is missing. Open that file at that line, or put back the original copy.
• “Cannot redeclare” means two plugins, or a plugin and the theme, define the same function. Disable one of the two named in the message.

Note the time stamp on each entry. The log keeps old errors too, so match the newest entry to the moment you reloaded the blank page.

Step 3: Disable plugins without the dashboard

If the log names a plugin, or you cannot get a log at all, disable plugins from the file system. In /wp-content/, rename the plugins folder to something like plugins-off. WordPress will treat every plugin as missing and deactivate them. If the site comes back, rename the folder back to plugins, then rename individual plugin folders one at a time until the white screen returns. The last one you re-enabled is the cause.

Leave the faulty plugin off and check for an update, a known conflict on its support forum, or a compatible alternative. Do not delete it straight away if it stores settings or content you need; deactivation is enough to get the site back.

Step 4: Switch to a default theme

If plugins are not the cause, test the theme. In /wp-content/themes/, rename the active theme’s folder. WordPress falls back to a default theme such as Twenty Twenty-Five if one is installed. If the site loads, even in the wrong design, the theme or a child theme edit is at fault. Undo the last change to functions.php, restore the theme files from a backup, or reinstall a clean copy of the theme from its developer.

Step 5: Raise the memory limit and check the server version

For “Allowed memory size exhausted” errors, add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php. Your host may cap memory below that, in which case ask them to raise it or look for the plugin that is using so much. If the white screen started right after the host moved you to a newer PHP version, you can usually switch back temporarily in the hosting control panel while you update the plugin or theme that is not compatible. Treat that as a short-term measure; old PHP versions stop receiving security fixes.

Step 6: Clear caches and stuck maintenance files

Once the cause is fixed, clear every cache layer: the caching plugin, the host’s server cache and any CDN such as Cloudflare. If the white screen appeared during an update, look for a file called .maintenance in the site root and delete it. If core files were interrupted mid-update, re-upload fresh copies of the wp-admin and wp-includes folders from the same WordPress version, leaving wp-content and wp-config.php untouched.

When the white screen hides missing files

Occasionally the checks above turn up something worse than an error: the wp-content folder is empty, the uploads are missing, or the theme folder has vanished. Then the blank page is a symptom of lost files, and repeated fixes will not help. Stop editing the server so nothing else is overwritten, ask your host for its most recent copy before its retention window closes, and gather any local or staging copies. Our guide to recovering when the WordPress database is lost but the files remain covers the opposite case. If WordPress shows “Error establishing a database connection” rather than a white page, use our guide to fixing an error establishing a database connection, and if the whole site has vanished rather than gone blank, start with why a WordPress site disappears.

White screen on a single page, post or editor screen

When most of the site works and only one URL is white, the cause is almost always something on that page:

• A shortcode or block from a disabled plugin. Some plugins crash when their shortcode runs with missing settings. Open the page in the editor, remove or replace the shortcode, and preview again.
• A custom page template. If the page uses a template file from the theme, switch it to the default template in the page settings to test.
• A very long page or a huge gallery. Pages with hundreds of images or a large table can hit memory or execution time limits on their own. The memory fix in step 5 often solves it.
• The block editor itself is white. A white editor screen, while the public page is fine, usually comes from a plugin that adds editor panels or from browser extensions. Test in a private window, then disable editor add-on plugins one by one.

White screen only in the admin area

If visitors see the site normally but /wp-admin/ is blank, look at plugins that load only in the dashboard: page builders, SEO plugins, backup tools and security plugins. The debug log usually names one of them. A white login page after a security plugin update can also come from a firewall rule blocking your own IP address; the security plugin’s documentation explains how to disable it by renaming its folder. Avoid clearing out the wp-admin folder; a fresh copy of the same WordPress version is the safe way to rule out damaged admin files.

Quick reference: symptom, likely cause, first fix

How to stop the white screen coming back

• Update plugins one at a time on busy sites, and read the changelog for new minimum requirements first.
• Test major plugin, theme and server upgrades on a staging copy before the live site.
• Keep the admin email address current so recovery-mode messages reach a real person.
• Put custom code in a child theme or a snippets plugin that can be switched off, never straight into a live theme functions file.
• Remove plugins and themes you no longer use; abandoned code is the most common source of fatal errors after server upgrades.

If you cannot bring the site back yourself

If the files or database are gone and there is no usable backup, the public side of the site can often still be rebuilt. Our WordPress restoration service recreates pages, posts, images and menus on a clean WordPress install from archived captures and any partial copies you have. It cannot bring back data that was never public, such as user accounts, orders or form entries, and we will tell you what is missing before any work starts. You can check whether your site has enough archived material with our free restoration check.

Frequently asked questions

Is my content lost if I see the WordPress white screen of death?

Usually not. A white screen is normally a code error, and posts and pages stay in the database while the site is blank. Fix the plugin, theme or memory problem and they appear again. Content is only at risk if files or the database were actually deleted.

Why is there no recovery mode email?

Recovery mode only catches certain plugin and theme errors, and the email goes to the site’s admin address, which may be an old or a developer’s mailbox. Errors that happen before WordPress fully loads, such as some memory or core file problems, do not trigger it.

Can I fix the white screen of death without FTP?

Often yes. Most hosts have a file manager in the control panel where you can rename folders and edit wp-config.php, and many have a one-click option to change the PHP version. Some managed hosts can also disable plugins for you through support.

Will restoring a backup fix it?

Restoring a backup from before the problem started will usually remove the white screen, but it also removes anything added since. If you can find the cause with the steps above, fixing it directly keeps your latest content.