Create Accountor Login
WordPress

WordPress White Screen of Death: Find the Fatal Error

· 10 min read

Laptop with a blank white screen on a dark table
Photo by KATRIN BOLOVTSOVA on Pexels

Where the Blank Page Comes From

The WordPress white screen of death is a PHP fatal error with the message hidden. The page is blank because PHP stopped before WordPress printed anything. So you do not guess which plugin it was. You make the error visible, read the one line that names the file, and act on that line.

This is for whoever is staring at a white browser window right now, with or without dashboard access. The first half covers what a blank page can be and how to tell the versions apart. The second half is the sequence that gets the site back without breaking something else on the way.

A White Screen Is PHP Stopping Halfway

PHP builds your page from the top and streams it out. On a fatal error it stops. If that happens early, before any HTML has gone out, the browser gets an empty body and shows nothing. If it happens later, you see half a page: a header, a menu, then a void.

Where the page cuts off is a clue, so read it first. A completely empty page points at something that loads very early, which in practice means the main configuration file, a must-use plugin, or a plugin near the front of the queue. Half a page points at whatever was rendering when it died, usually a theme template or a shortcode.

Recovery Mode May Already Have Emailed You a Way In

Current WordPress does not always lock you out. After a fatal error, recovery mode emails the admin and super admin address with a secret link. Following it opens a dashboard where the plugins and themes behind the fatal error are paused for you.

Check that mailbox before you reach for SFTP. Two details decide whether the email helps. It goes to the address in Settings, then General, and on a site somebody else built that is often a mailbox nobody reads, though the RECOVERY_MODE_EMAIL constant can override it. The link also expires, and the recovery_mode_email_link_ttl filter sets how long, so an email from last Tuesday will not help today. Recovery mode rides on a cookie in your browser, not on your user account, which is why it does not follow you to a different browser.

Only the Debug Log Names the Cause

Everything else here is inference. The log is evidence. WordPress ships the switches and leaves them off: WP_DEBUG defaults to false, and define( 'WP_DEBUG', true ); turns on debug mode throughout WordPress.

On a live site you want the log without the output. Per the debugging documentation, that is three lines in wp-config.php above the stop editing comment:

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

Errors then land in debug.log in the content directory, usually wp-content/debug.log, and stay off the page where a customer or a search engine could read them. WP_DEBUG_DISPLAY defaults to true, which is why you have seen sites with warnings printed above the logo. If wp-content is not writable, WP_DEBUG_LOG also takes a file path in place of true. Save, reload the broken page once, and open the log.

Tired man pinching the bridge of his nose at a laptop
Photo by Tima Miroshnichenko on Pexels

Memory Exhaustion Is the Classic Silent Version

If the screen is white and the log is empty, or holds a single allowed memory size line, this is almost always the cause. WordPress raises PHP's memory itself. By default it tries to lift the allocation to 40MB for a single site and 64MB for multisite, using code at the top of wp-includes/default-constants.php.

Those numbers are floors, and a site with a page builder, a store, and thirty plugins will pass them. Raise the limit in wp-config.php with define( 'WP_MEMORY_LIMIT', '96M' );. For the dashboard specifically there is WP_MAX_MEMORY_LIMIT, which defaults to 256MB and matters during imports and updates. The configuration reference says both must be set before wp-settings.php is included, which is what the stop editing comment marks. If your host caps PHP memory below what you ask for, it ignores the constant, and the number in your config file is decoration.

White in the Dashboard and White on the Front Point Different Ways

Find out which surfaces are broken first, since the answer shortens the list a lot. A blank front end with a working dashboard usually means the theme or a front-end plugin. A blank dashboard with a working front end usually means an admin-side plugin, and the front end is being served from a cache and is not healthy at all.

If both are blank, something loads on every request: the configuration file, a must-use plugin in wp-content/mu-plugins, a dropin such as object-cache.php, or a PHP version change under the whole site. One blank page on an otherwise working site is the memory and timeout case, because that page does more work than the rest.

A Blank 500 and a Blank 200 Are Different Problems

Open the browser's network tab, or send a headers-only request from the command line, and read the status code on the blank page. People skip this and lose an hour guessing.

An empty body with a 500 is PHP dying, and that is what this post covers. An empty body with a 200 is something that ran to the end and chose to send nothing: a cache that stored an empty response, a redirect loop that resolved to nothing, a maintenance or coming soon plugin, or a theme template with no output. With a 200 the log stays empty because there was no error. Look at caching and at plugins that intercept output.

Your Browser Can Keep Showing a Page That Is Already Fixed

Once a blank response has been cached, it keeps coming back after the fault is gone, and people undo a correct fix because of it. Full page caching plugins, the host's own cache, and a CDN edge can each hold one.

Test with a cache buster, meaning any unused query string on the end of the URL, or open a private window. A device on a different network is better still. If the URL with a query string loads and the plain one does not, the site is fixed and you are looking at a stored copy. Purging the cache is the last step, not the first.

Person checking a phone in front of a laptop
Photo by Jakub Zerdzicki on Pexels

Getting the Site Back in the Right Order

The instinct is to start deactivating plugins. That works in the end, costs an hour, and leaves half the site switched off while you do it. The order below is quicker and makes less mess.

Read the Last Lines of the Log First

With logging on and the broken page reloaded once, open wp-content/debug.log and scroll to the bottom. A PHP fatal error line gives the message, the file, and the line number, and the path is the answer. wp-content/plugins/some-plugin/includes/class-thing.php names the plugin to disable and spares everything else.

Read the message as well as the path. Calling an undefined function or method usually means a plugin expecting a companion plugin or a newer core version. A class not found often means a failed or partial update. Allowed memory size exhausted is the memory case above. A syntax error means somebody edited a file, and when that file is in a theme, the dashboard's built-in file editor is the usual culprit, which is why define( 'DISALLOW_FILE_EDIT', true ); is worth adding once the site is up.

Deactivate Plugins from the Command Line

With shell access this takes one command. The WP-CLI plugin deactivate command accepts a named plugin or the whole set, and the exclude option makes it usable on a real site:

wp plugin deactivate --all --exclude=woocommerce

Reload. If the white screen is gone, reactivate in small groups, not one at a time. Halving the list finds the offender in far fewer reloads than walking it. Write down which plugins were active before you start, because deactivating everything does not remember the list for you, and a store with a dozen extensions is not something to rebuild from memory.

Rename the Plugins Folder When You Have No Shell

Without WP-CLI, do the same over SFTP or your host's file manager. Rename wp-content/plugins to plugins-off and reload. WordPress finds no plugins, deactivates all of them in the database, and the fatal error disappears if a plugin caused it.

Rename the folder back to plugins afterward. The plugins reappear in the dashboard deactivated, and you switch them on in groups. On a store during business hours you have just turned off checkout, so if the site is taking orders, accept the outage on purpose or wait for a quiet hour. Delete nothing at this stage. A renamed folder can be reversed, and a deleted one takes its settings along.

Switch Themes Only After Plugins Are Ruled Out

Theme faults are rarer than plugin faults, so this is step two. If every plugin is off and the screen is still white, rename your active theme's folder in wp-content/themes. WordPress falls back to a default theme when the active one is missing, and that is enough to get you into the dashboard.

If the front end returns, the fault is in the theme. The usual suspects are a child theme calling something the parent dropped in an update, or a function added to functions.php by hand. Check whether the theme was updated recently and whether a child theme exists at all, because an update that replaced a parent theme's files calls for a different repair than a bad edit.

Laptop showing code in a dark room
Photo by Nemuel Sereti on Pexels

Raise the Memory Limit and Know When That Is the Wrong Fix

When the log says allowed memory size exhausted, raise the memory constant and reload. For large imports, big media libraries, or a store with many variations, that is a legitimate fix for a legitimate need.

It is the wrong fix when the number keeps needing to go up. Memory that climbs month after month is usually one plugin loading everything into an array, or a query with no limit, and a higher ceiling buys a few weeks before the same white screen returns on a bigger page. Ask whether you set it once and forgot it, or set it three times in a year. The second pattern is a performance problem being paid for with memory.

A PHP Version Bump Is the Cause People Miss

Nothing changed on the site, and it went white anyway. Almost always, something changed underneath it. A host moving you to a newer PHP release, or someone switching the version in a hosting panel, can turn code that used to emit a deprecation notice into code that throws a fatal error.

The tell is timing. There is no update in the plugin log, but the break lines up with a maintenance window or a panel change. Do not revert PHP and leave it there, because the old version stops getting security fixes and the next forced move breaks the same thing again. Go back one version to get the site up, update the plugin or theme that cannot handle the new one, test on a copy, and move forward. Check forms and receipts after any PHP move, since mail sent through the server's default mailer fails without leaving a trace on the site. That is the argument for a real sending path such as Email Delivery for Cloudflare.

Keeping It from Happening Again

Every fix above gets done under pressure, which is the expensive way to do any of them. The cheap way is prepared in advance: SFTP or shell credentials somebody currently has, an admin email address somebody reads so recovery mode can reach you, logging configured before you need it, and a copy of the site where an update can fail harmlessly. Most white screens arrive with an update, and an update applied to a staging copy first turns an outage into a Tuesday afternoon.

That is the shape of managed WordPress maintenance. Each update is reviewed, applied at the right time, watched, and rolled back if it misbehaves; updates are tested in staging against your site first, and site error monitoring and daily form submission testing run alongside, so a page that loads perfectly and is still broken gets noticed. Managed PHP upgrades are part of it too, which is the version of this problem most providers will not touch. On managed WordPress hosting the same work has more room: free one-click staging, a restore point before risky changes, automated daily backups kept 14 days, and rollbacks handled by our team rather than by you at eleven at night. If you are weighing that against doing the upkeep yourself, the maintenance comparisons lay the options out, and the wider managed WordPress page shows where the pieces meet.

Two neighboring posts are worth a look. Maintenance mode is the screen people confuse with this one, and it protects far less than its name suggests. And a missed publish schedule is the same lesson from the other side: the parts of a WordPress site with no browser attached are the parts nobody is watching.

Keep Reading

WordPress WordPress Maintenance Mode: What It Does and Does Not CoverMaintenance mode is a holding page and nothing more. Why sites get stuck in it, how to clear the .maintenance file, and what it does not protect you from.Read the article WordPress WordPress Missed Schedule: Why WP-Cron Skipped Your PostMissed schedule means WP-Cron never ran the job that publishes your post. Why it happens, how to check the queue, and the cron fix that holds.Read the article WordPress WordPress Security Checklist: What to Fix Once and RecheckWhich WordPress security settings to fix once and which checks to repeat: updates, logins, wp-config.php, backups, scans, and a one-hour quarterly review.Read the article WordPress WordPress MCP: How to Connect an AI Assistant SafelyWordPress MCP explained: the Abilities API, the official MCP adapter, and how to connect Claude or ChatGPT with OAuth and a staging copy first.Read the article WordPress WordPress Email Not Sending: Find the Break in OrderWhy WordPress reports success while email never arrives, and the order to check the sender address, bounces, authentication, and the mail route.Read the article WordPress Why Is My WordPress Site So Slow? Find the Cause FirstWhy is your WordPress site so slow? Work out whether the server, the images, or a plugin is the cause, then fix it in the order that usually pays off first.Read the article WordPress WordPress Maintenance Checklist: What to Do and How OftenA practical WordPress maintenance checklist: what to check weekly, how to order updates, how to test backups, and when to hand the work off.Read the article WordPress Update PHP in WordPress: Test First, Switch, Roll BackChange your WordPress PHP version safely: find your current version, pick a supported target, test on staging, switch, and roll back fast.Read the article Zoho Zoho Deluge: What It Is, Where It Runs, and How It Fails QuietlyDeluge is the scripting language built into Zoho. What a Deluge script is, where it runs across your apps, and why it fails without anyone noticing.Read the article

Ask Us Anything

We’d love to hear from you!