Why is my website loading a blank white page?

You open your site and, instead of your homepage, you get a completely blank white page. No text, no error, nothing. It's unnerving, especially if your site brings in customers or sales. The good news: this "white screen of death" (WSOD) doesn't appear out of nowhere, and it almost always has a clear technical cause you can track down.

In most cases, a white page means the server hit a fatal PHP error and stopped before sending any content to the browser. The usual culprit is a plugin, a theme, or an update that went wrong. In this guide I'll walk you through — one step at a time, without needless jargon — how to identify the cause and get your site back up, even if you're not technical.

What the white page actually means

A WordPress site (or any PHP-based site) works like this: the server runs code, builds the page, and sends it to the browser. When a piece of code throws a fatal error — a missing function, an incompatibility, exhausted memory — execution stops abruptly. If error display is turned off (as it should be on a public site), you don't see the error message, just the result: an empty, white page.

So the white page isn't a "disease" — it's a symptom. Somewhere behind it there's a very specific error message; we just need to surface it. Often the cause appeared right after an action: you installed a plugin, hit "Update", edited a theme. First thing I'd recommend: remember exactly what happened just before.

The most common causes

In practice, nearly every white screen comes from a handful of common sources:

• A plugin conflict or a poorly written plugin — the most frequent cause. An updated plugin becomes incompatible with another one or with your PHP version.
• A broken theme — especially after an update or a direct edit to its files.
• Exhausted PHP memory limit — the site asks for more memory than the server allows and crashes.
• An interrupted update — WordPress, a theme, or a plugin updated only halfway (dropped connection, timeout).
• An incompatible PHP version — the host switched to a new PHP version and an old plugin doesn't support it.

One useful detail: notice where the white appears. Only on the public site? Only in /wp-admin? Everywhere? That narrows the search a lot.

Step 1: make the errors visible

So you don't have to guess, have WordPress show you exactly which error occurred. Via FTP or your hosting File Manager, open the wp-config.php file and find the WP_DEBUG line. Set:

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

With WP_DEBUG_LOG on, errors get written to a debug.log file in the /wp-content/ folder. Reload the white page, then open that file. The last lines almost always name the culprit: the file and the plugin or theme that threw the fatal error.

Important: once you've fixed it, set WP_DEBUG back to false. You don't want errors visible to the public on a live site — it's a security issue too.

Step 2: disable plugins and switch the theme

If you suspect a plugin (the most likely scenario) but can't get into /wp-admin, disable them without the dashboard:

• Go into /wp-content/ via FTP or File Manager.
• Rename the plugins folder to plugins-off. WordPress will automatically deactivate every plugin.
• Check the site. If it's back, a plugin was the cause.
• Rename the folder back to plugins, then reactivate plugins one by one, checking after each. The one that brings back the white screen is your culprit.

If plugins aren't the problem, test the theme: in /wp-content/themes/ rename your active theme's folder. WordPress falls back to a default theme (Twenty Twenty-something). If the site appears, the problem is in your theme.

Step 3: PHP memory and incomplete updates

If debug.log shows something like "Allowed memory size exhausted", the site ran out of memory. Raise it in wp-config.php, before the "That's all, stop editing" line:

• define('WP_MEMORY_LIMIT', '256M');

If that's still not enough, your host can raise the actual PHP limit from the control panel. On small hosts the limit is often tight.

If the white appeared right after an interrupted update, a .maintenance file may be stuck in the site's root — delete it. And if your host just changed the PHP version, ask them (or switch it in the panel) and try a stable version supported by your theme and plugins.

How to prevent it — and when it's worth getting help

Prevention is cheaper than panic. A few simple rules:

• Back up before any update — automatically, not "when I remember".
• Test updates on a staging site, not directly on the live one.
• Keep plugins few and from serious sources; every extra plugin is extra risk.
• Don't edit theme files directly — use a child theme or ask someone who knows.

If you've tried the steps above and still see white, or you simply don't want to poke around FTP on the site you depend on, don't push until you break more. At MPO Web Studio we build and maintain sites remotely, with backups and monitoring included — and we can diagnose a white screen quickly, from a distance. A short WhatsApp message telling us what happened just before the error is often enough for us to get started.