The WordPress White Screen of Death (WSOD): how to fix it step by step, without a developer

It's the kind of morning you never want: you open your site and, instead of your homepage, you get a completely blank white screen. No text, no error, no admin. Nothing. It's called the "White Screen of Death" (WSOD) and, alarming as it looks, most of the time it has a simple, fixable cause.

The good news: you don't necessarily need a developer to get through the first wave of panic. You need a calm plan, in the right order, so you don't make things worse. Below are exactly the steps a professional follows when this kind of emergency call comes in - from the simplest to the most technical. Work through them one by one and, very likely, your site comes back.

What WSOD actually is and why it happens

A white screen almost always means the PHP that builds your page stopped with a serious error (a "fatal error"), and WordPress never got to display anything. For security reasons the error message is hidden from the public - hence the empty page.

The most common causes are few and they repeat:

• a plugin or theme conflict, especially right after an update;
• a PHP memory limit that's been exceeded;
• a code error in a manually edited file (often functions.php);
• rarely, a server or database problem.

The key is not to guess, but to eliminate suspects one at a time. Before anything else, if you can, make a backup of your files and database. A backup before you intervene saves your nerves if something goes wrong.

Step 1: turn on error messages so you can see the cause

A white screen tells you nothing - but you can make it talk. You'll need file access via FTP, the File Manager in cPanel, or your hosting panel.

Open wp-config.php in your site's root and find the line:

`define('WP_DEBUG', false);`

Replace it with:

`define('WP_DEBUG', true);`

`define('WP_DEBUG_LOG', true);`

`define('WP_DEBUG_DISPLAY', false);`

Reload the site. Errors will be written to a file called debug.log inside the wp-content folder. Open it and read the last lines: they usually tell you exactly which plugin or file failed, with its name and line number. This is the single most valuable clue in the whole operation. Once you've fixed things, set WP_DEBUG back to false so visitors never see errors.

Step 2: disable plugins and switch the theme

The most frequent culprit is a plugin. If you can still reach the admin (wp-admin), deactivate plugins one by one and reload after each, until the site returns.

If you can't get into the admin at all, do it through files:

• enter wp-content via FTP or File Manager;
• rename the plugins folder to something like plugins-off;
• check the site.

If it comes back, a plugin was the cause. Rename the folder back to plugins, then deactivate plugins one at a time (by renaming their subfolders) until you find the guilty one.

If the problem persists, test the theme: rename the active theme's folder in wp-content/themes. WordPress will fall back to a default theme (like Twenty Twenty-Something) and, if that fixes it, your theme was the problem.

Step 3: raise the PHP memory limit

If debug.log shows a message like "Allowed memory size exhausted", your site ran out of memory. This is a simple fix.

In wp-config.php, add this before the line that says "That's all, stop editing":

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

If that's not enough, or you're not allowed to change it from WordPress, you can raise the limit in php.ini or from your hosting panel (many hosts have a PHP setting where you pick the memory value directly in the interface).

If you don't have access to these settings, this is the right moment to message your hosting support: it's a common request and they'll sort it quickly. Low memory shows up often on cheap hosting plans, especially on sites with many plugins or a WooCommerce store.

Step 4: roll back to the last good version, and when to ask for help

If everything started after an update or a manual edit, the cleanest move is to return to the state before it. That's why the backup matters: with a recent copy, you restore the files and database and the site is online again in minutes.

If you edited functions.php by hand and got the white screen, you most likely left an extra bracket or semicolon. Open the file and remove the last change you made.

Ask a professional when: you can't find the files, the errors point to database problems, or the site earns you money and every hour down costs you. At MPO Web Studio we work remotely across the country and can take on this kind of emergency fast - message us on WhatsApp, give us access, and we get it back online. And for new clients we build sites with a clean structure and a ready-made demo before you pay, precisely so scares like this stay rare.