WordPress White Screen of Death: How to Diagnose and Fix a Blank Page

WordPress White Screen of Death: How to Diagnose and Fix a Blank Page

The WordPress white screen of death is a PHP fatal or memory error that leaves a blank white page with no error message. Fix it by turning on WP_DEBUG to read the real error, deactivating plugins, switching to a default theme, raising the PHP memory limit, or using Fatal Error Recovery Mode (over FTP if you cannot reach wp-admin).

Few WordPress problems feel as alarming as loading your site and getting nothing back: no content, no error message, just an empty blank screen. This is the WordPress white screen of death (WSOD), and despite the dramatic name your WordPress site is almost always recoverable without losing any data. This guide walks through what the white screen of death is, what causes it, and a clear, ordered set of fixes you can run to fix the white screen whether or not you still have access to your dashboard.

What Is the WordPress White Screen of Death?

The white screen of death is a state where WordPress fails to render a page and returns a blank white screen instead of your site or a readable error message. It can hit the whole site, only the front end, or only wp-admin. Because there is no visible error message, the blank white screen gives you nothing to work with on the surface, which is what makes the WSOD feel harder to troubleshoot than other failures.

It helps to separate two similar situations. Modern versions of WordPress often show a “There has been a critical error on this website” page instead of a pure blank screen. That message page is covered in our guide to how to fix the WordPress critical error. The white screen error is the older, message-free symptom: same family of underlying problems, but the page itself stays empty. The diagnostic steps below apply to both, and they map onto the broader workflow in our WordPress troubleshooting guide.

What Causes the White Screen of Death?

Almost every WordPress white screen of death traces back to PHP halting before the page can finish. The causes of a WordPress white screen nearly always fall into one of these buckets:

• A PHP fatal error: a plugin, theme, or custom snippet calls a function that does not exist or breaks at runtime, and PHP stops.
• Memory exhaustion: the script runs past its memory limit and PHP logs an “allowed memory size exhausted” message before dying.
• A plugin conflict: two plugins clash, or one plugin breaks after an update, taking the site down.
• A theme conflict: a faulty or half-updated theme triggers the blank screen.
• A syntax error in code: an edit to functions.php or another file introduces a typo that PHP cannot parse.
• Corrupted WordPress core files: an interrupted update leaves WordPress core in a broken state.

The fixes below are ordered to surface the real error first, then rule out each cause quickly.

First Checks Before You Change Anything

Spend two minutes scoping the problem before you edit anything. Check whether the blank screen affects the whole site or only the WordPress admin: if the front end works but wp-admin is blank, the culprit is usually a plugin or theme that only loads in the dashboard. Next, clear your browser cache and any site or hosting cache, because a stale cached page can keep showing a blank white screen after the real fault is already gone. Finally, note the last thing that changed: a plugin update, a theme switch, or a code edit is your prime suspect when you troubleshoot.

Fix 1: Turn On WP_DEBUG to See the Real Error

The fastest way to fix a white screen error is to make WordPress show you the hidden error message. Edit the wp-config.php file in your site root and change the debug constants:

1. Open wp-config.php through your hosting File Manager or over FTP.
2. Find define('WP_DEBUG', false); and set it to true.
3. Add define('WP_DEBUG_LOG', true); so PHP writes problems to /wp-content/debug.log.
4. Reload the page, then open the error log to read the exact file and line that failed.

That single error message usually names the plugin, theme, or function causing the problem, so you can jump straight to the right fix. For the full list of constants, see the WordPress reference on debugging in WordPress. Turn WP_DEBUG back off once the site is healthy.

Fix 2: Raise the PHP Memory Limit

If the error log shows “allowed memory size exhausted,” PHP ran out of memory. Raise the limit by adding this line to the wp-config.php file, just above the “stop editing” comment:

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

If that is not enough or your host overrides it, increase memory_limit in php.ini or add php_value memory_limit 256M to .htaccess. The PHP memory_limit reference explains the directive in detail. Memory exhaustion can also be a symptom of an inefficient plugin, so if the white screen of death returns, read our deeper walkthrough on how to fix the WordPress memory exhausted error.

Fix 3: Deactivate All Plugins

A plugin conflict is the single most common cause, so deactivate plugins as a group and test. If you can still log in:

1. Go to Plugins in wp-admin, select all, and choose Deactivate.
2. Reload the site. If the blank screen is gone, a plugin was the problem.
3. Reactivate your plugins one by one, checking the site after each, until the white screen returns and exposes the plugin causing the problem.

If you cannot reach the dashboard, do the same thing over FTP. Connect with an FTP client or your host File Manager, open /wp-content/, and rename the plugins folder to something like plugins-off. That forces WordPress to deactivate every plugin at once. Rename the folder back, then disable each plugin individually by renaming its own subfolder to find the offender.

Fix 4: Switch to a Default Theme

If plugins are not the cause, test the theme. From the dashboard, activate a default theme such as Twenty Twenty-Four. Without admin access, use FTP: open /wp-content/themes/ and rename your active theme folder. WordPress cannot find the active theme, so it falls back to a default theme automatically. If the white screen clears, your theme was at fault, and you can troubleshoot it from there. Our guide on how to fix a broken theme in WordPress covers the next steps, including a likely syntax error in the theme files.

Fix 5: Use Fatal Error Recovery Mode

Since WordPress 5.2, the platform ships with a built-in safety net. When a fatal error would trigger the white screen of death, WordPress emails the site admin email a special recovery-mode link. Open that email, click the link, and you enter the dashboard in recovery mode with the failing plugin or theme paused. From there you can deactivate the faulty component cleanly and keep the rest of the site running. If the email never arrives, confirm the admin email address is correct and that your host is sending mail, then fall back to the FTP methods above.

How to Fix the White Screen Without Admin Access

When wp-admin itself is a blank white screen, every fix above still works through FTP or your hosting File Manager:

1. Edit the wp-config.php file to enable WP_DEBUG and read the error log.
2. Rename the /wp-content/plugins folder to deactivate all plugins.
3. Rename the active theme folder to force a default theme.
4. Raise the PHP memory limit in wp-config.php, php.ini, or .htaccess.

If none of that clears the WSOD, contact your hosting provider. On managed WordPress hosting the support team can check server error logs, restore a backup, or repair corrupted core files quickly. You can also bring it to our WordPress support team if you would rather not work in the files yourself.

Confirm the Fix and Clear Cache

Once the site loads again, clear every layer of cache (browser, caching plugin, and any server or CDN cache) so visitors see the recovered site rather than a cached blank screen. Reload a few key pages, log in to wp-admin, and set WP_DEBUG back to false. If you renamed any folder over FTP, make sure the names are restored and only the genuinely faulty plugin or theme stays deactivated.

How to Prevent the White Screen of Death

Most white screen incidents are preventable. Test plugin and theme updates on a staging copy before pushing them to your live site. Keep comfortable memory headroom (256M is a safe baseline for most business sites) so a single heavy request cannot exhaust PHP. Update plugins and themes deliberately rather than all at once, and keep recent backups so recovery is a restore rather than a rebuild. Adding uptime and error monitoring means you hear about a blank screen before your customers do. The WordPress reference on common WordPress errors is a useful companion as you harden the site.

Frequently Asked Questions

What is the WordPress white screen of death?

It is a failure where WordPress returns a blank white screen with no error message instead of your page. The WSOD is usually caused by a PHP fatal error or memory exhaustion that stops the page from rendering. Your content is still in the database, so the site is almost always recoverable.

What causes the WordPress white screen of death?

The usual causes are a plugin conflict, a theme conflict, PHP memory exhaustion, a syntax error in custom code, or corrupted WordPress core files after an interrupted update. Each one halts PHP before the page finishes, which produces the blank screen. Turning on WP_DEBUG reveals which one is to blame.

What is the first thing I should do when I see the white screen?

Clear your browser and site cache to rule out a stale page, then check whether the blank screen affects the whole site or only wp-admin. After that, enable WP_DEBUG in the wp-config.php file so WordPress shows the real error message and points you at the exact file causing the problem.

How do I fix the white screen without admin access?

Use FTP or your hosting File Manager. Edit wp-config.php to turn on debugging, rename the /wp-content/plugins folder to deactivate all plugins, and rename the active theme folder to force a default theme. These are the same fixes as the dashboard route, just performed in the files instead of wp-admin.

What does “allowed memory size exhausted” mean?

It means a PHP script tried to use more memory than the configured limit allows, so PHP stopped and produced the white screen. Raise the limit with define('WP_MEMORY_LIMIT', '256M'); in wp-config.php, or adjust memory_limit in php.ini. If it keeps recurring, an inefficient plugin is usually the underlying cause.

What is WordPress Fatal Error Recovery Mode?

Recovery mode is a built-in feature (since WordPress 5.2) that catches a fatal error and emails the site admin email a link to a protected dashboard. The faulty plugin or theme is paused, so you can log in, deactivate it, and restore the site without touching FTP or the wp-config.php file.

Will I lose my website data or content from a white screen error?

No. The white screen of death is a rendering failure, not data loss. Your posts, pages, and settings stay safe in the database while PHP is unable to display them. Once you remove the faulty plugin, theme, or memory limit, the same content renders normally again.

Can a hacked site cause the white screen of death?

It can. Malware sometimes injects broken or malformed PHP that triggers a fatal error and the blank white screen. If debugging points to unfamiliar code or files you did not add, treat it as a security incident: scan the site, restore a clean backup, and contact your hosting provider or a WordPress security specialist before bringing it back online.