WordPress White Screen of Death: Causes and Fixes

The "white screen of death" is exactly what it sounds like: you open your site or your admin dashboard and get a blank white page. No content, no error message, no explanation. Because WordPress gives you nothing to work with, it feels like the hardest error to fix. It is usually one of the easiest.

A blank screen almost always means PHP hit a fatal error and stopped before it could render anything. The most common triggers are a plugin conflict, a broken theme, or an exhausted memory limit. Work through the sections below in order. The first two fixes resolve the large majority of cases.

What the White Screen of Death Actually Is

Every WordPress page is assembled by PHP running on your server. When PHP encounters a fatal error partway through — a plugin calling a function that no longer exists, a theme file with a syntax mistake, a script that runs out of memory — it halts. On many servers the default setting is to hide that error from visitors, so instead of an error message you get an empty response: the white screen.

This tells you two useful things. First, the problem is on the server side, not in your browser, so clearing your cache alone rarely helps. Second, the real error is knowable — it is simply hidden. Most of this guide is about either removing the likely cause or unhiding the error so you can read it.

Start Here: Three Quick Checks

Is the whole site white, or just part of it?

Load a few different URLs and note the pattern:

Front end and admin both blank: a site-wide problem, usually a plugin, the theme, or memory. Keep reading.
Front end blank but /wp-admin works: the fault is almost always your active theme. Jump to the theme section.
One page blank, the rest fine: suspect a specific plugin tied to that page, or a corrupted page in the editor.

Did anything change just before it broke?

Think back to the last action before the screen went blank. A plugin update, a theme switch, a code snippet pasted into functions.php, or a WordPress core update are the usual culprits. The most recent change is your prime suspect — and often the fastest thing to undo.

Can you still reach the dashboard?

Visit yourdomain.com/wp-admin. Whether the dashboard loads decides your approach. If it loads, you can fix everything from inside WordPress. If it is also blank, you will work over SFTP or your host's file manager instead. Both paths are covered below.

Fix 1: Deactivate Your Plugins

A plugin conflict is the single most common cause, especially right after an update. The goal is to switch every plugin off, confirm that clears the screen, then turn them back on one at a time to find the guilty one.

If you can reach the dashboard

Go to Plugins, select all of them, choose "Deactivate" from the bulk actions menu, then apply. Reload your site. If it comes back, reactivate your plugins one by one, checking the site after each. When the white screen returns, the plugin you just switched on is the cause. Leave it off, then look for an update or a replacement.

If the dashboard is also blank

Connect over SFTP or open your host's file manager and navigate to wp-content/. Rename the plugins folder to something like plugins-off. That deactivates every plugin at once. Reload your site — if it works, the problem is a plugin.

Now rename the folder back to plugins. Your plugins will still show as deactivated in the dashboard. Reactivate them one at a time from Plugins to isolate the offender, exactly as above.

Fix 2: Switch to a Default Theme

If your front end is blank but the dashboard still loads, your active theme is the likely cause — a common outcome after a theme update or an edit to functions.php.

From the dashboard, go to Appearance, then Themes, and activate a default WordPress theme such as Twenty Twenty-Four. Reload your site. If it returns, your theme is at fault. Contact the theme developer, roll back to the previous version, or restore the file you edited.

If the dashboard is blank too, use SFTP or the file manager to go to wp-content/themes/ and rename your active theme's folder. WordPress cannot find it, so it falls back to an available default theme automatically. Reload and check.

A frequent trigger here is a bad edit to functions.php — one missing bracket or a stray character is enough to blank the whole site. If you edited that file just before the screen appeared, undo the change or restore the previous version of the file.

Fix 3: Raise the PHP Memory Limit

If deactivating plugins and swapping themes changes nothing, your site may be running out of memory. A page that loads on a light day can exhaust its allotment as your content, plugins, or traffic grow, and PHP stops mid-render.

Open wp-config.php in the root of your WordPress installation. Just above the line that reads /* That's all, stop editing! */, add:

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

Save the file and reload your site. If a low memory ceiling was the problem, the page returns. Some hosts cap PHP memory at the server level, so this constant has no effect on their plans. When that is the case, your host has to raise the limit — and a host that keeps WordPress on a tight memory budget is worth reconsidering.

Fix 4: Turn On Debug Logging to Read the Real Error

If you are still stuck, stop guessing and make WordPress show you the error it is hiding. Enable debug logging, reproduce the blank page, then read exactly which file and line failed.

In wp-config.php, find the line define( 'WP_DEBUG', false ); and replace it with:

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

The first line switches debugging on. The second writes every error to wp-content/debug.log. The third keeps those errors out of your visitors' view while you investigate.

Reload the blank page, then open wp-content/debug.log. The most recent lines name the exact file causing the fatal error — usually a plugin or theme file. That points you straight at the fix. When you are done, set all three values back so debugging is off on your live site.

Less Common Causes Worth Checking

If none of the four fixes above resolves it, one of these edge cases usually applies:

A stale cache. If the site works in a private browsing window but not your normal one, clear your browser cache. Then clear any caching plugin or server cache — you may be seeing a saved copy of the blank page.
A failed core update. An interrupted WordPress update can leave core files broken. Download a fresh copy of WordPress, then re-upload the wp-admin and wp-includes folders over SFTP, replacing the existing ones. Your content is untouched — those folders hold no site data.
Wrong file permissions. After a migration or a manual file transfer, permissions can end up wrong. Folders should generally be 755 and files 644. Your host can reset these if you are unsure.
An outdated PHP version. Modern plugins and themes expect a current PHP release. If your server runs an old version, raise it to a supported release in your hosting control panel.

How to Prevent It From Happening Again

Once your site is back, a few habits keep the white screen from returning:

Keep a recent backup. A current backup turns a broken update into a five-minute restore instead of an afternoon of debugging.
Test updates on staging. Apply plugin, theme, and core updates on a staging copy first, so a bad update never touches your live site.
Give PHP room. A sensible memory limit absorbs growth in content and traffic before it turns into a blank page.
Choose hosting built for WordPress. Good managed hosting ships generous memory, one-click staging, and automatic backups as standard.

When You Want Someone to Just Fix It

If you have worked through every fix and the screen is still blank — or you would rather not touch wp-config.php at all — we can take it from here. Our team has cleared this exact error on hundreds of sites. Our managed WordPress hosting is built to prevent it, with generous PHP memory, one-click staging for safe updates, and automatic daily backups.

Book a free call and we will get your site back online.