You open your site and instead of your homepage, there’s just… nothing. A blank white page. The first time this happens to a client, they usually message me in a bit of a panic, and I get it — it looks like the site’s gone forever. It almost never is. This is the White Screen of Death, and it’s one of the more common emergencies I fix, usually inside half an hour once I can actually get into the site.

Why it happens

WordPress goes blank when a PHP error is serious enough to stop the page rendering, but the server isn’t configured to show you what that error actually was. In roughly the order I see them:

A plugin conflict or a bad update is the most common cause by a wide margin. A theme error, often right after a theme update. The PHP memory limit getting exhausted — the site’s trying to do more than the hosting plan allows. Corrupted core files from a WordPress update that got interrupted halfway. Or a syntax error in custom code somebody added to functions.php, sometimes months ago, that only breaks under specific conditions.

First: back up whatever you can reach

If you’ve got any access at all — FTP, hosting file manager, anything — grab a copy of wp-content and export the database before you start poking around. If something goes sideways during troubleshooting, you want a way back.

How I actually work through it

Step one is always turning on debug mode so I can see the real error instead of a blank page. Add this just above the “that’s all, stop editing” line in wp-config.php:

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

That writes the actual error to a log file at /wp-content/debug.log, and that log almost always tells you exactly which plugin or file is the problem — no more guessing.

If I can’t even reach wp-admin, I connect via FTP, go to /wp-content/, and rename the plugins folder to something like plugins-disabled. WordPress treats every plugin as deactivated at that point. If the site comes back, I rename it back and turn plugins on one at a time from wp-admin until I find the one that breaks it.

Still blank? I rename the active theme’s folder inside /wp-content/themes/, which forces WordPress to fall back to a default theme like Twenty Twenty-Four. If that fixes it, the problem was in the theme’s code all along, not a plugin.

Sometimes it’s just memory. Adding define('WP_MEMORY_LIMIT', '256M'); to wp-config.php fixes it outright — a lot of hosts cap this lower by default than a site with several active plugins or a page builder actually needs.

And if none of that works, I’ll re-upload fresh copies of the wp-admin and wp-includes folders from wordpress.org (never wp-content, that’s where all your actual content and uploads live) to fix corruption left over from an interrupted update.

How to stop this from happening again

Never update plugins, themes, and WordPress core all at once — do them one at a time and check the site in between each. Use a staging site to test anything major before it touches the live site. Keep automatic backups running daily, at minimum, so there’s always a recent point to roll back to. And keep your plugin count down — fewer moving parts genuinely means fewer conflicts, this isn’t just a platitude, I see it play out constantly.

When it’s worth calling someone

If the site makes you money or generates leads, every hour it’s down has a real cost, and troubleshooting blind can turn what should be a ten-minute fix into a lost afternoon. If you’re staring at a white screen right now, reach out — most of these get fixed same day, often within the hour.