TL;DR: Fastest Safe Fix

To fix the WordPress White Screen of Death, first check whether you can access wp-admin. If the dashboard is unavailable, use your hosting File Manager or SFTP to rename the wp-content/plugins folder and disable all plugins temporarily. If the site loads, one plugin is the cause. If that does not work, switch to a default theme, enable private debug logging in wp-config.php, check the error log, increase memory if needed, and verify your PHP version.

What Is the WordPress White Screen of Death?

The WordPress White Screen of Death, often called WSOD, is when your website shows a blank white page instead of your normal content. Sometimes the whole site is blank. Sometimes only the admin dashboard, a single post, checkout page, login page, or Elementor/page builder editor is affected.

Unlike the “There has been a critical error on this website” message, the white screen may not show any visible explanation. That usually means a PHP error, memory problem, server-side issue, or broken WordPress component stopped the page from rendering before WordPress could display a friendly error screen.

Common signs of the issue include:

• Your homepage loads as a blank white page.
• wp-admin shows a blank screen.
• Only one page or post is blank.
• The site works for logged-out users but not admins.
• The site breaks after updating a plugin, theme, WordPress, or PHP.
• The page returns HTTP 500 but shows no readable error.
• Your browser shows a white page with no source content.

What Usually Causes the White Screen of Death?

A blank WordPress screen usually means something failed silently. The cause can be simple, but you need to isolate it carefully.

The most common causes are:

• Plugin conflict: A plugin update, abandoned plugin, security plugin, cache plugin, page builder, WooCommerce extension, or custom plugin may trigger a fatal error.
• Theme issue: A broken theme file, child theme edit, template override, or functions.php mistake can stop the site from loading.
• PHP memory exhaustion: WordPress may run out of memory during updates, imports, backups, page builder edits, or WooCommerce actions.
• PHP version mismatch: Old plugins may fail on newer PHP versions, while modern plugins may not work well on outdated PHP versions.
• Failed update: An incomplete WordPress, plugin, or theme update can leave missing or corrupted files.
• Custom code error: A bad snippet added through a code snippets plugin, theme editor, or custom functionality file can break the site.
• Server or cache issue: Object cache, page cache, CDN cache, PHP-FPM, LiteSpeed, Apache, or Nginx configuration can sometimes hide the real problem.

Before You Start: Protect the Site First

Do not start deleting plugins, themes, or database tables randomly. The safest approach is to pause the broken component, check logs, and make targeted fixes.

Do this first:

• Take a full backup if your hosting panel still allows it.
• Write down what changed recently.
• Check whether only the frontend, backend, or one page is affected.
• Clear browser cache, but do not clear server logs yet.
• Use File Manager or SFTP instead of editing files blindly from wp-admin.
• Avoid restoring an old database on WooCommerce, LMS, booking, or membership sites unless you understand the data loss risk.

If the white screen happened after a recent update, also read this related FyrePress guide: Fix WordPress Issues Fast: Rollback Guide.

Fix 1: Check Your Admin Email for Recovery Mode

If WordPress detects a fatal error, it may send a recovery mode email to the site administrator. This email usually includes a secure link that lets you access the dashboard and deactivate the broken plugin or theme.

Steps:

1. Open the email inbox connected to your WordPress admin account.
2. Search for emails from WordPress about a technical issue.
3. Click the recovery mode link if available.
4. Log in to your WordPress dashboard.
5. Deactivate the plugin or theme WordPress identifies.
6. Update, roll back, or replace the broken component.

If you do not receive the email, do not stop here. Many hosts block or delay WordPress emails, and some fatal errors prevent recovery mode from helping. Continue with the manual fixes below.

External reference: WordPress introduced Fatal Error Recovery Mode to help administrators access the backend after fatal errors. You can read the official Make WordPress explanation here: Fatal Error Recovery Mode in WordPress.

Fix 2: Disable All Plugins Manually

Plugins are one of the most common reasons for a WordPress white screen. If you cannot access wp-admin, you can disable all plugins through your hosting File Manager, SFTP, or SSH.

How to disable plugins without wp-admin:

1. Log in to your hosting control panel.
2. Open File Manager or connect using SFTP.
3. Go to your WordPress installation directory.
4. Open the wp-content folder.
5. Rename plugins to plugins-disabled.
6. Reload your website in a private browser window.

wp-content/plugins
wp-content/plugins-disabled

If the site loads after renaming the plugins folder, one of your plugins is causing the white screen. Rename the folder back to plugins, then disable individual plugin folders one by one until the site works again.

How to find the broken plugin:

1. Rename plugins-disabled back to plugins.
2. Open the plugins folder.
3. Rename one plugin folder at a time.
4. Reload the site after each rename.
5. When the site starts working, the last renamed plugin is likely the cause.

Once you find the plugin, do not immediately reinstall the same version. Check its changelog, support forum, PHP compatibility, WordPress compatibility, and recent update history.

Related FyrePress guide: WordPress Plugin Compatibility Checklist.

Fix 3: Switch to a Default WordPress Theme

If disabling plugins does not fix the white screen, your active theme may be responsible. This is common after editing functions.php, updating a premium theme, changing a child theme, or adding custom PHP code.

If you can access wp-admin:

1. Go to Appearance → Themes.
2. Activate a default WordPress theme.
3. Reload the broken page.

If you cannot access wp-admin:

1. Open File Manager or SFTP.
2. Go to wp-content/themes.
3. Rename your active theme folder.
4. Reload the site.

If a default WordPress theme is installed, WordPress may fall back to it. If the site works after disabling the active theme, the issue is likely inside the theme, child theme, template file, custom hook, or theme function.

Related FyrePress guide: Create a WordPress Staging Site Before Updates.

Fix 4: Enable WordPress Debug Logging

If plugins and themes do not clearly reveal the problem, turn on private debug logging. This helps you see the actual PHP error without exposing technical details to visitors.

Open wp-config.php and add these lines before the final comment that says That's all, stop editing!:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

After adding the code, reload the white screen page once. Then check:

• wp-content/debug.log
• PHP error logs in your hosting panel
• LiteSpeed, Apache, Nginx, or PHP-FPM logs
• WooCommerce logs if the issue affects checkout or scheduled actions
• Security plugin logs if the blank page appears after login or form submission

Example error clue:

PHP Fatal error: Uncaught Error: Class "Example_Class" not found
in /wp-content/plugins/example-plugin/includes/class-main.php on line 42

In this example, the path points to example-plugin. That means you should disable, update, roll back, or replace that plugin instead of guessing.

External reference: WordPress provides official debugging constants such as WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY. You can review the official documentation here: Debugging in WordPress.

Fix 5: Increase the WordPress Memory Limit

If the white screen appears during plugin updates, media uploads, imports, backups, WooCommerce actions, Elementor editing, or admin tasks, your site may be hitting the PHP memory limit.

Add these lines to wp-config.php before the final stop-editing comment:

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

If your hosting server has a lower PHP memory cap, WordPress cannot always override it. In that case, raise the memory limit from your hosting control panel, php.ini, .user.ini, or ask your host to increase it.

Important: increasing memory can restore access, but it is not always the final fix. If a plugin, import, query, cron job, or builder process keeps exhausting memory, you still need to find and fix the real cause.

Fix 6: Check Your PHP Version

A PHP version change can trigger a WordPress white screen. This often happens after a hosting migration, server upgrade, control panel change, or manual switch from one PHP version to another.

What to check:

• Was PHP changed recently?
• Does the error log mention syntax errors, type errors, deprecated functions, or missing classes?
• Do your plugins support your current PHP version?
• Does your active theme support your current PHP version?
• Did the site break immediately after switching PHP?

If the site broke after changing PHP, temporarily switch back to the previous working version from your hosting panel. Once the site is accessible, update or replace the incompatible plugin, theme, or custom code.

Related FyrePress guide: WordPress PHP Requirements Explained.

Fix 7: Clear Cache Carefully

Sometimes the issue is fixed, but a cache layer keeps showing a blank page. This can happen with WordPress cache plugins, LiteSpeed Cache, object cache, CDN cache, browser cache, or server-level cache.

Clear these cache layers after making a fix:

• WordPress cache plugin cache
• Server cache from your hosting panel
• CDN cache such as Cloudflare
• Object cache such as Redis or Memcached
• Browser cache

Do not clear cache before checking logs if the issue is still active. Logs are more useful while the error is fresh.

Fix 8: Reinstall WordPress Core Files

If the white screen started after a failed WordPress update and plugins/themes are not the cause, WordPress core files may be incomplete or corrupted.

If wp-admin works:

1. Go to Dashboard → Updates.
2. Click Re-install for the current WordPress version.
3. Clear cache and test the site.

If wp-admin does not work:

1. Download a fresh copy of WordPress from WordPress.org.
2. Extract the files on your computer.
3. Upload fresh WordPress core files through SFTP or File Manager.
4. Do not overwrite wp-config.php.
5. Do not overwrite the wp-content folder.

This step is more advanced. If you are not comfortable replacing files manually, ask your hosting provider or developer for help.

Fix 9: Disable Custom Code Snippets

Many WordPress white screen issues come from small custom snippets added to a theme file, code snippets plugin, custom functionality plugin, or must-use plugin.

Check these locations:

• wp-content/themes/your-theme/functions.php
• wp-content/themes/your-child-theme/functions.php
• wp-content/mu-plugins
• Custom plugin folders
• Code snippets plugin entries

If the white screen appeared after adding code, remove the last snippet or comment it out. A missing semicolon, wrong hook, duplicate function name, or unsupported PHP syntax can break the whole site.

Best Fix Method by User Type

The best recovery method depends on how much access you still have.

For beginners

Start by checking your admin email for a recovery mode link. If that fails, contact your host and ask them to check the PHP error log for the exact fatal error.

For site owners with File Manager access

Rename the plugins folder first. If the site loads, isolate the broken plugin. If it does not, rename the active theme folder and test again.

For developers

Enable private debug logging, reproduce the white screen once, read the first fatal error, and fix the exact plugin, theme, autoloaded file, hook, class, function, or PHP compatibility issue named in the stack trace.

For WooCommerce, LMS, and membership sites

Avoid full database restores unless absolutely necessary. Restoring an old database may remove new orders, users, subscriptions, form entries, course progress, or bookings. Target the broken plugin, theme, or code first.

How to Prevent the White Screen of Death

The best fix is prevention. A safe update workflow makes WordPress white screen issues much less likely and easier to recover from.

Prevention checklist:

• Use a staging site before major WordPress, plugin, theme, or PHP updates.
• Keep full file and database backups before updates.
• Update plugins and themes in small batches.
• Check plugin compatibility before updating WordPress.
• Use a child theme for custom theme edits.
• Avoid adding untested PHP snippets to a live site.
• Remove abandoned plugins and unused themes.
• Keep debug display disabled on production sites.
• Review PHP error logs after major changes.
• Test login, checkout, forms, search, mobile pages, and admin editing after updates.

Related FyrePress guide: Safely Update WordPress Without Issues.

Final Recommendation

The fastest safe way to fix the WordPress White Screen of Death is to isolate the failing component. Start with recovery mode if available, then disable plugins, test the active theme, enable private debug logs, check memory, verify PHP compatibility, and clear cache only after making a real fix.

Do not treat the white screen as a random problem. It almost always leaves a clue in the error logs. Once you find the file path or fatal error, you can fix the issue directly instead of guessing.

Frequently Asked Questions

What causes the WordPress White Screen of Death?

The most common causes are plugin conflicts, theme errors, PHP fatal errors, memory limit issues, failed updates, incompatible PHP versions, custom code mistakes, or server-side problems.

Can I fix the White Screen of Death without wp-admin?

Yes. You can use hosting File Manager, SFTP, or SSH to rename the plugins folder, disable the active theme, edit wp-config.php, enable debug logging, and check server error logs.

Will renaming the plugins folder delete my plugins?

No. Renaming the plugins folder only stops WordPress from loading plugins temporarily. It does not delete plugin files or plugin settings from the database.

Why is only my WordPress admin dashboard white?

If only wp-admin is blank, the cause may be an admin-only plugin, security plugin, custom dashboard code, memory issue, or PHP error triggered only for logged-in users.

Should I restore a backup to fix the white screen?

Restore a backup only when targeted troubleshooting fails or the site is severely damaged. For WooCommerce, membership, booking, or LMS sites, database restores can overwrite new orders, users, payments, or submissions.

How do I find the exact error behind the white screen?

Enable private debug logging in wp-config.php, reload the broken page once, then check wp-content/debug.log or your hosting PHP error log. The first fatal error usually points to the plugin, theme, or file causing the problem.

How can I prevent the White Screen of Death in the future?

Use staging before updates, keep verified backups, update plugins carefully, check PHP compatibility, avoid abandoned plugins, test custom code before publishing, and monitor error logs after major changes.