WordPress White Screen of Death: Causes and How to Fix It

Picture of Ivan Predojev
Ivan Predojev

Writer

Table of Contents

You open your website and there is nothing there. No header, no menu, no error message, just an empty white page staring back at you. If you have run a WordPress site for any length of time, you have probably met the WordPress white screen of death at least once, and it rarely shows up at a convenient moment. The good news is that a blank page is almost never a sign that your content is gone. It is a symptom, and like most symptoms, it points to a cause you can track down. In this guide we will walk through what the blank screen actually means, how to get WordPress to tell you what went wrong, and the fixes that bring most sites back within minutes.

What the White Screen Actually Means

A blank white page usually means that PHP, the language WordPress is built on, ran into a problem it could not recover from and stopped before it sent any HTML to the browser. Because nothing was printed, your browser has nothing to show. Behind the scenes, the server often returns an HTTP 500 Internal Server Error, but many hosts hide the details for security reasons, so visitors simply see white.

In most cases the trigger is a fatal error: a plugin calling a function that no longer exists, a theme written for an older PHP version, a typo from a quick edit, or a script that ran out of memory. Everything after the error never gets a chance to run.

Newer versions of WordPress have softened this experience. Since version 5.2, WordPress includes a fatal error handler that catches many of these crashes and shows a short message saying there has been a critical error on the website, instead of a totally blank page. You will still see the classic white screen, though, when the error happens too early for that handler to load, when the handler has been turned off, or when something outside WordPress, such as a caching layer or server configuration, is serving the empty response.

It also helps to notice where the blank page appears. If only the front end is white while wp-admin still works, look at the theme or a front-end plugin. If only the dashboard breaks, suspect an admin-only plugin or a memory spike. If both are blank, the problem loads very early, often from a plugin, a broken core file, or the server itself.

The WordPress overview of common WordPress errors covers this blank page and its close relatives. With the basics in place, the first thing to check is something WordPress may already have sent you.

Start with the Recovery Mode Email

When the built-in error handler catches a crash, WordPress tries to email the site’s administrator address. That message names the plugin or theme that caused the problem and includes a special link that opens recovery mode. Inside recovery mode you can log in to the dashboard even though the public site is still broken, and the faulty extension is paused only for your session so you can deactivate it, update it, or replace it. The feature was introduced in WordPress 5.2, and the original announcement of fatal error recovery mode explains how it works under the hood.

Check your inbox, including spam, before you touch any files. If the email arrived, click the link, deactivate the named plugin or switch away from the broken theme, and reload. If no email came, perhaps because the admin address is outdated, the next step lets you see the exact error yourself.

Turn On Debugging to See the Real Error

Guessing at the cause of a blank page wastes time. By enabling WP_DEBUG, you tell WordPress to report PHP errors, warnings, and notices instead of hiding them. Pairing it with WP_DEBUG_LOG writes those messages to a file, which is far safer on a live site than printing them for every visitor.

These settings live in wp-config.php, the file in the root folder of your WordPress install. Connect with FTP, SFTP, or your hosting file manager, open the file, and look for the line that defines WP_DEBUG. Replace it, or add the lines below above the comment that says to stop editing. The official guide to debugging in WordPress lists every option.

ConstantSuggested ValueWhat It Does
WP_DEBUGtrueTurns on error reporting inside WordPress
WP_DEBUG_LOGtrueSaves errors to wp-content/debug.log
WP_DEBUG_DISPLAYfalseKeeps errors off the public page
SCRIPT_DEBUGfalse (unless debugging scripts)Loads unminified core CSS and JavaScript

Once the constants are saved, reload the broken page so the error happens again, then open wp-content/debug.log. Scroll to the bottom and look for a line that starts with “PHP Fatal error.” It will usually include a file path, and that path is your best clue. If it points inside wp-content/plugins/some-plugin, you have found the plugin. If it points inside wp-content/themes, the theme is the culprit. A message about “Allowed memory size exhausted” tells you to look at the memory limit instead.

When the site is fixed, set WP_DEBUG back to false and delete the debug.log file. Leaving logging on forever can fill up disk space and, if the file is publicly reachable, expose details about your server. With the error message in hand, you will usually find that it points to one of the most common causes of all.

When Plugins and Themes Collide

Most white screens trace back to a plugin conflict or a theme that no longer plays well with the rest of the site. A plugin update might rely on a newer version of another plugin, two plugins might declare the same function, or a theme might call a feature a plugin removed. The more extensions a site runs, the more chances there are for a clash.

If you can still reach the dashboard, deactivate plugins one at a time and reload the site after each one. When the page comes back, the last plugin you turned off is the cause. If the dashboard is also white, you will need to work at the file level. Open wp-content through FTP or the file manager, and rename the plugins folder to something like plugins-off. WordPress cannot find any plugins, so it deactivates all of them at once. Reload the site; if it works, rename the folder back to plugins and then rename individual plugin folders one by one until the white screen returns.

Themes work the same way. If the error log points to your theme, or if disabling plugins did not help, rename your active theme’s folder inside wp-content/themes. WordPress will try to fall back to a default theme, such as one of the yearly Twenty-something themes, as long as one is installed. If none is present, upload a fresh copy of a default theme first. A site that loads with the default theme confirms that your theme, or a child theme customization, needs repair.

Once the guilty extension is identified, you can roll back to the previous version, check for a patch, send the developer the exact error from your log, or replace the plugin with a better maintained alternative. Sometimes, though, every plugin and theme looks innocent, and the problem sits one layer deeper in the server’s resources.

Memory Limits and PHP Version Problems

Two server-side settings cause a surprising share of blank pages. The first is the PHP memory limit, which caps how much memory a single request can use. The second is the PHP version your site runs on, which decides which functions and syntax your code is allowed to use. Here is how each one tends to show up:

  • Memory exhaustion: the log says “Allowed memory size of X bytes exhausted.” Large page builders, image processing, and imports are frequent triggers.
  • Too old a PHP version: a recently updated plugin uses newer syntax and crashes on an outdated server.
  • Too new a PHP version: an older plugin or theme uses functions that were removed in a later PHP release.
  • Missing extensions: a plugin expects a PHP extension, such as one for images or XML, that the server does not have enabled.

To raise the memory available to WordPress, you can define WP_MEMORY_LIMIT in wp-config.php, for example setting it to 256M. That value cannot exceed the server-level memory_limit setting in PHP. If your host caps memory lower, you will need to raise it in the control panel or ask your host to do it.

Symptom in the LogLikely CauseFirst Thing to Try
Allowed memory size exhaustedMemory limit too low or a runaway scriptRaise WP_MEMORY_LIMIT, then find the heavy plugin
Call to undefined functionRemoved or missing function, or missing extensionCheck PHP version and enabled extensions
Syntax error, unexpected tokenCode written for a newer PHP version, or a typoUpdate PHP or revert the last file edit
Cannot redeclare functionTwo plugins or a plugin and theme clashingDeactivate plugins one by one

PHP versions move on a regular schedule, and each release eventually stops receiving security fixes. You can check which branches are still maintained on the official PHP supported versions page, and compare that with the WordPress server requirements. Upgrading PHP is good practice, but do it on a staging copy first so you can catch any plugin that is not ready for the change.

If memory and PHP version both check out, the blank page might not be an error at all. A few quieter causes are worth ruling out next.

Smaller Culprits: Caching, Permissions, and Stuck Updates

Not every white screen comes from a crash. Sometimes the site is fine and something in front of it, or a leftover file from an interrupted process, causes the blank result. These are quick to check before you restore anything:

  • Cached blank pages: if a page crashed once, your caching plugin, server cache, or CDN may have stored the empty response. Clear every cache layer and test in a private browser window.
  • Wrong file permissions: if the web server cannot read key files, it may return a blank page. Folders are typically set to 755 and files to 644; the guide to changing file permissions explains safe values.
  • A stuck .maintenance file: during updates WordPress creates a file named .maintenance in the root folder. If an automatic update fails partway, that file can remain and leave the site blank or stuck in maintenance mode. Delete it and reload.
  • Half-finished core updates: a timed-out update can leave core files missing or mismatched. Re-uploading fresh copies of the wp-admin and wp-includes folders usually fixes it.
  • Hidden file edits: a stray space or character added to functions.php or wp-config.php can break the whole site. Undo the last edit if you made one.

A failed auto-update deserves special attention, because it often happens overnight with nobody watching. If the white screen appeared without anyone touching the site, check for a .maintenance file and the modified dates on recently updated plugins.

When none of these quick checks help, it is time to look at a full example of how the pieces fit together in real life.

A Real-World Example

Picture a small agency that manages a client’s online store. On a Tuesday morning the client calls: the homepage is completely white, and so is the dashboard. Nobody on the team made changes the day before. The account manager checks the client’s inbox and finds no recovery mode email, because the admin address still belongs to a former employee.

The developer connects through SFTP and finds a .maintenance file in the root folder, with several plugin folders carrying the same overnight timestamp. That points to an automatic update. She deletes the file and reloads, but the page is still white, so the update did more than get stuck.

Next she turns on WP_DEBUG and WP_DEBUG_LOG, reloads the homepage, and opens debug.log. The last line is a fatal error pointing to a shipping plugin, complaining about a call to an undefined function. The plugin’s new version relies on a feature from a newer release of the store plugin, which had not updated because it was excluded from automatic updates. The two versions simply could not work together.

She renames the shipping plugin’s folder, and the site loads instantly. She then updates the store plugin on a staging copy, confirms the shipping plugin works against it, and repeats the update on the live site. Finally, she fixes the admin email address so the next recovery mode message reaches the right person, and turns debugging off.

The lesson is not that automatic updates are bad. It is that a predictable process, starting with the error log instead of random clicks, turns a scary blank page into a routine repair. Sometimes, though, the fastest path is to roll back entirely.

When to Restore a Backup

If you cannot find the cause, or the damage is wider than a single plugin, restoring a recent backup is often the quickest way back. This is especially true after a hack, a corrupted database, or an update that changed many files at once. A clean restore puts files and the database back to a known good state, and you can investigate the original problem later on a staging copy without customers staring at a white page.

A restore is only as good as the backup behind it, so make sure yours include files and the database, live off the server, and are recent enough to protect new orders and posts. The WordPress guide to WordPress backups covers what to include and how often to run them. Of course, many site owners would rather not handle any of this alone, which is where a support team comes in.

How Webueno Handles a White Screen

At Webueno, our troubleshooting service is built for exactly this kind of problem. It covers PHP error debugging and fixes after updates, which is where most white screens begin. We follow the same logic described above: read the errors, isolate the cause, fix it safely, and confirm the site is stable. Several parts of our platform help:

  • Daily Backups add-on: daily, offsite backups of files, database, and configuration, available as an option on a per-site basis.
  • Staging and live on one server: Webueno hosting runs staging and live sites on the same server, so fixes can be tested before they touch the real site.
  • Per-site PHP versions: each site on Webueno hosting can run its own PHP version, which makes compatibility problems easier to solve without affecting other sites.
  • Uptime Monitoring add-on: checks your site every 3 minutes and sends an alert after 3 failed pings, roughly 9 minutes after an outage begins.

Support work is billed in credits. One credit equals one hour of work and costs $42, and credit bundles are available with discounts of up to 21%. For ongoing care, our maintenance plans run through the Webueno Care Assistant plugin:

Maintenance PlanPrice per Site
Daily$60
Weekly$20
Monthly$10

Together, these tools mean a white screen is caught early, diagnosed from real error data, and fixed with a backup ready if anything goes sideways. That turns an emergency into a short, well-documented ticket.

Get Your Site Back Online

A blank page feels alarming, but it almost always has a clear cause: a plugin or theme conflict, a memory limit, a PHP version mismatch, a stuck update, or a cached empty response. Work through the steps in order, starting with the recovery email and the error log, and most sites recover quickly.

If you would rather hand the problem to people who fix these every week, or you want monitoring and backups in place before the next one happens, create your Webueno account and send us a ticket. We will find the error, fix it, and keep your WordPress site running.

Frequently Asked Questions

Here are short answers to the questions site owners ask most often about blank WordPress pages.

Is My Content Lost When I See the White Screen of Death?

Almost never. Your posts, pages, and settings live in the database, and a white screen usually means PHP stopped before it could display them. Once the underlying error is fixed, your content reappears exactly as it was.

Why Do I See a Critical Error Message Instead of a Blank Page?

Since WordPress 5.2, a built-in fatal error handler catches many crashes and shows a short critical error notice instead of an empty screen. It is the same underlying problem, just with a friendlier message. Check the admin email inbox for a recovery mode link that names the plugin or theme involved.

How Do I Fix the White Screen if I Cannot Log In?

Use FTP, SFTP, or your host’s file manager. Rename the wp-content/plugins folder to disable all plugins, or rename your active theme’s folder so WordPress falls back to a default theme. Enabling WP_DEBUG_LOG in wp-config.php will also show you the exact error.

Can a Caching Plugin Cause a White Screen?

Yes. If a page crashed even briefly, a caching plugin, server cache, or CDN may keep serving that blank version after the problem is gone. Clear all cache layers and test in a private window before assuming the site is still broken.

What Should I Do if a WordPress Update Caused the Blank Page?

First, look for a .maintenance file in the root folder and delete it if the update was interrupted. Then check the error log to see which plugin, theme, or core file is failing. If the damage is widespread, restore a recent backup and repeat the update on a staging copy.

How Can I Prevent the White Screen of Death in the Future?

Keep plugins, themes, and PHP up to date, but test major updates on staging first. Run regular offsite backups and use uptime monitoring so you hear about outages quickly. A maintenance plan takes most of this routine work off your plate.

You may also like

Illustration of a first byte of data traveling from a server to a browser with a stopwatch measuring the delay, representing Time to First Byte (TTFB) server response time in WordPress.
How to Reduce Server Response Time (TTFB) in WordPress

Ready to Move Your Website and Business Forward?

No contracts. No unnecessary complexity. Just reliable execution and real results.