WordPress White Screen of Death Fix

Updated March 11, 2026 • Expert Guide • Prime AI Tech Solutions

Looking for the best solutions? Compare top options and get expert advice tailored to your needs.

Explore Top Recommendations ›

Introduction: The Dreaded WordPress White Screen of Death (WSoD)

The WordPress White Screen of Death (WSoD) is one of the most unsettling and common issues WordPress users encounter. It's a blank white page where your website should be, offering no error messages, no navigation, just an empty void. This can be particularly alarming because it leaves you with no immediate clues as to what went wrong, effectively shutting down your online presence. While it appears formidable, the WSoD is almost always fixable with a systematic, step-by-step approach. This comprehensive guide will equip you with the expert knowledge and actionable steps needed to diagnose and resolve the WSoD, restoring your WordPress site to full functionality.

Understanding the WordPress White Screen of Death (WSoD)

The WSoD typically indicates a critical PHP error or an exhaustion of your server's memory limit. Because WordPress is built on PHP, any severe issue in a theme, plugin, or even the core files can cause PHP to crash, resulting in a blank page instead of the usual error report. The absence of an error message is often due to server configurations that suppress error display for security reasons. Understanding these underlying causes is the first step towards an effective resolution.

  • Plugins: The most frequent culprit. A newly installed or updated plugin, or an incompatibility between plugins, can trigger a WSoD.
  • Themes: Similar to plugins, a corrupted or poorly coded theme, or a conflict after an update, can cause the issue.
  • PHP Memory Limit: If your WordPress site, plugins, or themes demand more memory than allocated by your hosting provider, PHP will crash.
  • Corrupted Core Files: Less common, but sometimes WordPress core files can become damaged during an update or due to server issues.
  • Syntax Errors: Manually editing PHP files (e.g., functions.php) and introducing a syntax error will immediately break the site.
  • Server Issues: Rarely, the problem might stem from your hosting environment itself, though this is usually accompanied by other server-side errors.
WordPress White Screen of Death (WSoD) technical error screen with troubleshooting elements

The Ultimate Step-by-Step Guide to Fixing the WSoD

Before you begin, always attempt to create a full backup of your website if you have any backend access (e.g., via your hosting control panel or a previous backup plugin). If not, proceed carefully, knowing that changes are reversible.

Step 1: Enable WordPress Debugging

This is the absolute first and most critical step. Enabling debug mode will force WordPress to display any PHP errors on the screen, providing invaluable clues. If your screen remains white even after enabling debug, it suggests a more fundamental PHP configuration issue or a memory limit problem.

  1. Connect to your website via FTP/SFTP (using a client like FileZilla) or through your hosting provider's File Manager.
  2. Navigate to your WordPress root directory (where wp-config.php is located).
  3. Open the wp-config.php file for editing.
  4. Look for the line: define( 'WP_DEBUG', false );
  5. Change false to true: define( 'WP_DEBUG', true );
  6. To log errors to a file instead of displaying them publicly (recommended for live sites), add the following lines *after* the WP_DEBUG line: 
    define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  7. Save the wp-config.php file and upload it back to your server.
  8. Refresh your website. If an error message now appears, it will point you directly to the problematic file and line number. If WP_DEBUG_LOG was enabled, check the wp-content/debug.log file.

Step 2: Increase PHP Memory Limit

A common cause of WSoD is your WordPress site exceeding the allocated PHP memory. This is especially true for sites with many plugins, complex themes, or heavy traffic.

  1. Via wp-config.php: Open your wp-config.php file (as in Step 1) and add the following line *above* the /* That's all, stop editing! Happy publishing. */ comment: 
    define( 'WP_MEMORY_LIMIT', '256M' );
    (You can try 128M or 512M if 256M doesn't work, but 256M is generally a good starting point.)
  2. Via php.ini: If you have access to your server's php.ini file (often through cPanel's MultiPHP INI Editor or PHP Selector options), find the line memory_limit and change it: 
    memory_limit = 256M;
  3. Via .htaccess: As a last resort, you can try adding this line to your .htaccess file (located in the root directory): 
    php_value memory_limit 256M
  4. Save changes and check your site.

Step 3: Deactivate All Plugins

Plugins are the most frequent cause of WSoD due to conflicts or poor coding. This step helps isolate if a plugin is the culprit.

  1. Connect via FTP/SFTP or File Manager.
  2. Navigate to wp-content/.
  3. Rename the plugins folder to something like plugins_old. This will automatically deactivate all plugins on your site.
  4. Refresh your website. If your site returns, a plugin was the problem.
  5. To find the specific plugin: Rename plugins_old back to plugins. Then, inside the plugins folder, rename each individual plugin folder one by one (e.g., plugin-name to plugin-name_old) and refresh your site after each rename. The plugin whose renaming brings your site back is the problematic one. Delete or replace it.

Step 4: Switch to a Default WordPress Theme

Similar to plugins, a problematic theme can cause the WSoD.

  1. Connect via FTP/SFTP or File Manager.
  2. Navigate to wp-content/themes/.
  3. Locate your currently active theme folder. Rename it (e.g., mytheme to mytheme_old).
  4. WordPress will automatically fall back to a default theme (like Twenty Twenty-Four, Twenty Twenty-Three, etc.) if one is present. Ensure you have at least one default WordPress theme installed in your themes folder.
  5. Refresh your website. If it comes back, your theme was the issue. You'll need to investigate the theme for errors, contact the developer, or choose a different theme.

Step 5: Clear Cache (If Applicable)

If you're using a caching plugin or your host has server-side caching, a cached version of your site might be serving the WSoD. If you can access your WordPress admin, clear the cache through your plugin's settings. If not, you might need to clear it via your hosting control panel or by temporarily deactivating the caching plugin (as per Step 3).

Step 6: Check File Permissions

Incorrect file permissions can block WordPress from accessing necessary files, leading to a WSoD.

  • Connect via FTP/SFTP.
  • Right-click on your WordPress root directory and select "File Permissions..." (or similar).
  • The recommended permissions are:
    • Directories: 755
    • Files: 644
  • Apply these permissions recursively to all subdirectories and files.

Step 7: Replace Corrupt Core Files

Rarely, core WordPress files can become corrupted. This step effectively reinstalls WordPress without affecting your content.

  1. Go to wordpress.org/download/ and download a fresh copy of WordPress. Ensure it's the exact same version as your current installation.
  2. Unzip the downloaded file on your computer.
  3. Connect via FTP/SFTP.
  4. Upload the wp-admin and wp-includes folders from the fresh download to your server's root directory, overwriting existing files.
  5. Do NOT upload or overwrite the wp-content folder or the wp-config.php file! These contain your unique content and database connection details.
  6. Refresh your site.

Step 8: Check for Syntax Errors

If you recently edited a PHP file directly (e.g., functions.php in your theme), a simple missing semicolon or bracket can cause a WSoD. Debugging (Step 1) should pinpoint this. If it does, correct the error in the specified file and line number.

Step 9: Review Your .htaccess File

A corrupted or misconfigured .htaccess file can also cause internal server errors that manifest as a WSoD.

  1. Connect via FTP/SFTP or File Manager.
  2. In your root directory, rename the .htaccess file to something like .htaccess_old.
  3. Refresh your site. If it comes back, the .htaccess file was the problem.
  4. To regenerate a clean .htaccess file, log into your WordPress admin (if you can now), go to Settings > Permalinks, and simply click "Save Changes" without making any modifications. This will generate a new default .htaccess file.

Step 10: Contact Your Web Host

If none of the above steps resolve the WSoD, it's time to contact your hosting provider. Provide them with all the troubleshooting steps you've already taken, any error messages you found (especially from debugging logs), and details about when the issue started. They have server-side logs and tools that can often identify deeper problems.

Common Mistakes to Avoid During WSoD Troubleshooting

  • Panicking: Stay calm and follow a systematic approach. Haphazard changes can complicate diagnosis.
  • Not Backing Up: Always try to back up your site before making significant changes, even if it's just copying files via FTP.
  • Skipping Debugging: This is the most crucial step. Without error messages, you're troubleshooting blind.