WordPress White Screen of Death: A Senior Developer’s Fix Walkthrough

A blank white page with no error, no menu, nothing. It’s one of the most unnerving things WordPress does, because it tells you exactly zero about what went wrong. WordPress hides fatal PHP errors on purpose so visitors don’t see sensitive paths, which is sensible right up until you’re the one staring at the void. Since WordPress 5.2, that same fatal error more often shows the there has been a critical error message instead, though the white screen still turns up on older setups and certain failures.

I’ve cleared this on hundreds of sites for agencies who handed us a project that went dark mid-build or mid-update. The fix is almost never guesswork. You read the error, then you change one thing. Here’s the order I work in, fastest and most common causes first.

How do you find what’s causing the white screen before changing anything?

Turn on debug logging so WordPress writes the fatal error to a file instead of hiding it. Open wp-config.php over FTP or your host’s file manager, and just above the line that says /* That's all, stop editing! */, add three constants. Reload the broken page, then read wp-content/debug.log. The last line names the exact file and line number that crashed.

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

Setting WP_DEBUG_DISPLAY to false keeps the error out of the live page while still logging it, so you’re not flashing a stack trace at visitors. The log entry usually looks like PHP Fatal error: ... in /wp-content/plugins/some-plugin/file.php on line 212. That one line tells you whether you’re chasing a plugin, the theme, or your own code. Most people skip this step and start disabling things at random. Read the log. It saves an hour.

If the front end is blank but /wp-admin still loads, that points at the theme or a front-end plugin. If the admin is white too, it’s deeper: a plugin loaded everywhere, a memory ceiling, or a corrupted core file.

How do you fix the white screen after a plugin update?

Deactivate plugins to confirm one of them is the cause, then re-enable them one at a time to find the culprit. A plugin conflict is the most common reason for a true blank screen, and it spikes right after auto-updates run overnight. If you can still reach the dashboard, deactivate all plugins under Plugins, All Plugins. Screen comes back? Reactivate them one by one until it breaks again. That last one is your problem.

When the admin is locked out too, do it over FTP. You don’t need command line for this. Connect with an FTP client (FileZilla, Cyberduck) or your host’s file manager, open wp-content/, and rename the plugins folder to something like plugins-off. WordPress can’t find the folder, so it deactivates every plugin at once and the site loads.

Now rename it back to plugins, then go inside and rename individual plugin folders one at a time, reloading after each, until the screen goes white again. The folder you just renamed holds the broken plugin. Leave it deactivated, roll it back to the previous version, or replace it with a fresh copy from the developer. Don’t just delete it blindly if it stores data you need.

What if disabling plugins didn’t fix it?

Switch to a default theme to rule out a theme conflict. A bad theme update, or a broken edit to functions.php, can white-screen the whole front end while the admin stays fine. If you can reach the dashboard, go to Appearance, Themes, and activate a default like Twenty Twenty-Four. If the site comes back, your theme is the cause.

Locked out of the admin? Over FTP, open wp-content/themes/ and rename your active theme’s folder. WordPress falls back to a default theme automatically as long as one is installed, so the site loads and you’ve confirmed the theme. If renaming the theme does nothing, the theme isn’t your problem, put the name back and keep going.

How do you fix a syntax error in functions.php?

If your debug log points at a line in functions.php, you’ve got a PHP syntax error, usually from a snippet pasted in with a missing brace or semicolon. This is the classic “I added one little code snippet and the whole site died” white screen. The log will read something like PHP Parse error: syntax error, unexpected ... in /wp-content/themes/yourtheme/functions.php on line 84.

Open that file over FTP, go to the line number in the error, and remove or fix the offending code. The most common mistakes: an extra closing ?> at the bottom of the file, a missing semicolon, or a stray copy of <?php in the middle. If you’re not sure which edit broke it, delete the snippet you added last. Always work on a copy of the file so you can revert. And this is exactly why you edit theme code in a child theme, not the parent, a core update would wipe a parent-theme edit anyway.

How do you increase the PHP memory limit to fix the white screen?

Add WP_MEMORY_LIMIT to wp-config.php to give WordPress more headroom when a process runs out of memory. By default WordPress tries to allocate just 40 MB to PHP on a single site and 64 MB on multisite, per the WordPress wp-config documentation. A heavy plugin, a big import, or a page builder can blow past that and trigger a blank screen.

In wp-config.php, above the “stop editing” line, add:

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

Reload the site. If it comes back, memory was the wall you were hitting. One honest caveat: some hosts cap PHP memory at the server level, so this constant gets ignored. If 256M changes nothing and the debug log still shows an “allowed memory size exhausted” error, the limit is set in php.ini or your hosting panel, and you’ll need to raise it there or ask your host to bump it.

What if none of that works, could it be a corrupted core file?

Replace WordPress core to rule out a corrupted or half-written file from a failed update. If the debug log points at a file inside /wp-includes/ or /wp-admin/, or an update timed out partway through, a core file is likely damaged. This one’s rare, but it does happen on flaky connections during manual updates.

Download a fresh copy of WordPress from WordPress.org, unzip it, and delete the wp-content folder and wp-config.php from that download so you don’t overwrite your site’s content or settings. Then upload the remaining files over FTP, letting them overwrite the existing wp-admin and wp-includes folders and the root files. This refreshes core without touching your themes, plugins, uploads, or database. Always take a full backup before you do this.

Work through those in order and you’ll clear the vast majority of white screens without a developer. The blank screen is one of a handful of errors that take down WordPress sites, and we cover the rest in our rundown of 8 common WordPress problems and how to fix them.

Sometimes the log points at something nasty: a core file mismatch that hints at malware, a conflict buried three plugins deep, or custom code nobody on the team wrote. That’s the “no one else could solve it” category. We’re the senior bench agencies hand those to. Our white-label WordPress team fixes the hard stuff under your brand, your client never knows we exist. If a site’s down right now and you need it back fast, send us the details and we’ll dig into the actual error, not a checklist.

Frequently asked questions

Tried every step above and still staring at a blank screen? If the site is down and you would rather hand it to a senior developer than keep guessing, we can take it over and get it back. Send us the broken site and we will diagnose the real cause and give you a fixed quote to fix it.