Hitting the White Screen of Death (WSOD) after updating WordPress is a critical issue that stops your site dead in its tracks. This definitive guide provides a clear, step-by-step action plan to diagnose the root cause and get your website back online—fast. Follow these proven methods to resolve most white screen issues within 30 minutes.

60-Second Triage: 3 Immediate Fixes to Try First

Before deep-diving, attempt these quick solutions that resolve over 50% of cases:

1. Force Refresh & Clear Cache: Press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) for a hard refresh. Clear your browser cache.
2. Disable All Plugins: Via FTP or your host's file manager, rename the /wp-content/plugins folder to plugins_old. Refresh your site. If it works, a plugin conflict is the cause.
3. Switch to a Default Theme: Via FTP, rename your active theme folder inside /wp-content/themes/. This forces WordPress to load a default theme (e.g., Twenty Twenty-Five).

If the white screen persists, proceed with systematic troubleshooting below.

Step 1: Enable Debug Mode to Find the Exact Error

When your site shows a blank screen, enabling debugging makes it reveal the specific error.

1. Access your site's root directory via FTP (e.g., FileZilla) or your hosting file manager.
2. Edit the wp-config.php file.
3. Find the line define('WP_DEBUG', false); and replace it with:php

   define('WP_DEBUG', true);
   define('WP_DEBUG_LOG', true); // Errors are saved to a log file
   define('WP_DEBUG_DISPLAY', false); // Hides errors from public visitors
   @ini_set('display_errors', 0);

4. Save the file and refresh the broken page.
5. Now, check the /wp-content/debug.log file via FTP. This log will pinpoint the fatal error. Common examples:
   • Fatal error: Allowed memory size exhausted → Out of PHP memory.
   • Parse error: syntax error → Coding error in a plugin or theme.
   • Fatal error: Cannot redeclare class... → Conflict between plugins/themes.

Step 2: Apply the Targeted Fix Based on the Error

Use the debug log to choose the right solution from these six core fixes.

Fix 1: Increase PHP Memory Limit

If the error mentions "memory size exhausted," WordPress needs more resources.

• In wp-config.php: Add these lines before /* That's all, stop editing! */:php

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

• Contact Your Host: If it fails, the server's php.ini limit is too low. Ask your host to increase memory_limit.

Fix 2: Repair Corrupted WordPress Core Files

An incomplete update can break core files. Reinstall them safely.

• Download the same version of WordPress from wordpress.org.
• Unzip it and delete the wp-content folder and wp-config-sample.php file from the download.
• Upload all other files via FTP to your root directory, overwriting existing ones. (Your content, themes, and plugins remain untouched.)

Fix 3: Reset the .htaccess File

A corrupted .htaccess file often causes WSOD, especially if only the homepage or admin is blank.

• Via FTP, find .htaccess in your root directory.
• Rename it to .htaccess.backup.
• Refresh your site. If it works, go to WordPress Admin > Settings > Permalinks and click "Save Changes" to generate a new, clean file.

Fix 4: Update Your PHP Version

WordPress requires newer PHP versions. Old PHP (like 7.2) can cause a white screen after an update.

• Go to your hosting control panel (cPanel, Plesk, etc.).
• Find "PHP Version" or "PHP Selector".
• Switch to a supported version like PHP 8.1 or 8.2.
• Save and test your site.

Fix 5: Clear All Caches

Old cached files can conflict with updated code.

• Plugin Cache: Temporarily rename your caching plugin's folder via FTP (e.g., change wp-rocket to wp-rocket_off).
• Server Cache: Contact your host to clear Varnish, Redis, or Memcached caches.
• CDN Cache: Purge the cache in your CDN service (e.g., Cloudflare).

Fix 6: Repair the Database

Update processes can sometimes corrupt database tables.

• In wp-config.php, add this line: define('WP_ALLOW_REPAIR', true);
• Visit: https://yourdomain.com/wp-admin/maint/repair.php
• Click "Repair Database".
• Crucial: Remove the added line from wp-config.php after repair for security.

Step 3: Advanced Scenarios & Last-Resort Recovery

• Only Admin Area is White (Frontend Works): The fault likely lies in your theme's functions.php or an admin-specific plugin. Check the functions.php file of your active theme via FTP for errors.
• Nothing Works – Restore from Backup: If you have a pre-update backup, use your backup plugin (e.g., UpdraftPlus) or hosting panel to restore both files and the database. This is your ultimate safety net.

How to Prevent Future White Screens After Updates

1. Always Backup First: Use a reliable plugin to create a full backup (files + database) before any update.
2. Test on a Staging Site: Apply updates first on a staging or local copy of your site to check for conflicts.
3. Maintain Compatibility: Keep your PHP version updated and use plugins/themes from trusted developers that are regularly maintained.
4. Update in Order: Follow this sequence: Backup > Update Plugins > Update Theme > Update WordPress Core.

Final Summary: Fixing the post-update White Screen of Death is a logical process: Enable debug logging to identify the error → Isolate the cause (plugin/theme) → Apply the specific fix (memory, core files, PHP, etc.). By following this structured approach, you can systematically restore your site and implement practices to avoid future downtime.

Complete Vertical Flowchart