WordPress White Screen of Death: 9 Fixes Ordered by Probability (2026)

Quick answer: The WordPress white screen of death (WSOD) happens when a PHP fatal error stops WordPress before it can render. Fix it in 5 minutes: enable WP_DEBUG to see the real error, deactivate all plugins via FTP/file manager, switch to a default theme, and increase memory limit to 256M. These steps resolve ~90% of cases. If diagnostics reveal malware or corrupted database, you'll need deeper fixes or host support.

Step 1: Enable WP_DEBUG to See the Actual Error

The white screen hides the real error message. Force WordPress to show it:

1. Access your site files via FTP (FileZilla) or your host's file manager (cPanel → File Manager on Bluehost).
2. Open wp-config.php in the root directory.
3. Find the line define('WP_DEBUG', false); and change false to true.
4. Add this line directly below: define('WP_DEBUG_LOG', true);
5. Save the file and reload your site.

You'll now see the actual PHP error instead of a blank screen. Common patterns:

• Fatal error in /wp-content/plugins/[plugin-name]/ → Plugin conflict (see Fix #2)
• Fatal error in /wp-content/themes/[theme-name]/ → Theme error (see Fix #3)
• Allowed memory size exhausted → Memory limit (see Fix #4)
• Parse error: syntax error → Code typo (see Fix #5)

Important: Set WP_DEBUG back to false after fixing — leaving it on exposes sensitive paths to visitors.

Step 2: Deactivate All Plugins (~40% of Cases)

If WP_DEBUG shows a plugin error or you can't see the error, deactivate all plugins without wp-admin access:

1. Navigate to /wp-content/ via FTP or file manager.
2. Rename the plugins folder to plugins-disabled.
3. Reload your site. If it works, a plugin was the culprit.
4. Rename the folder back to plugins.
5. Now rename each plugin folder inside plugins one-by-one (e.g., akismet-disabled) and reload after each rename until you identify the problem plugin.

Once identified, delete the broken plugin folder entirely, then reinstall a fresh copy from WordPress.org or find an alternative.

Step 3: Switch to a Default Theme (~20% of Cases)

If plugins aren't the issue, test your theme:

1. Navigate to /wp-content/themes/
2. Rename your active theme's folder (e.g., custom-theme → custom-theme-disabled).
3. WordPress automatically falls back to a default theme (Twenty Twenty-Five or similar).
4. Reload your site. If it loads, your theme has a fatal error.

Fix: Check the theme's functions.php for syntax errors, re-download a fresh copy of the theme, or contact the theme developer.

Step 4: Increase PHP Memory Limit (~15% of Cases)

If WP_DEBUG shows memory exhausted, increase the limit:

Add this line to wp-config.php (before the /* That's all, stop editing! */ comment):

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

If that doesn't work, create/edit .htaccess in the root and add:

php_value memory_limit 256M

Still not working? Your host caps the limit — contact support or check your hosting control panel (Bluehost: cPanel → MultiPHP INI Editor).

Step 5: Check for Syntax Errors in functions.php (~8% of Cases)

If you recently edited functions.php or added a code snippet:

1. Access /wp-content/themes/[your-theme]/functions.php via FTP.
2. Look for missing semicolons, unclosed brackets , or PHP opening tags without closing tags.
3. Common culprit: a space or blank line before <?php or after ?>.
4. Re-upload a fresh copy of functions.php from a theme backup.

Step 6: Check Error Logs for Hidden Clues

If WP_DEBUG doesn't reveal the issue:

• cPanel hosts (Bluehost, HostGator): cPanel → Metrics → Errors → view recent PHP errors.
• SiteGround: Site Tools → Statistics → Error Logs.
• File system: Check /wp-content/debug.log (created when WP_DEBUG_LOG is true).
• PHP logs: Look for error_log or php_errors.log in the root directory.

Step 7: Re-upload WordPress Core Files (~10% of Cases)

If a core file is corrupted:

1. Download fresh WordPress from wordpress.org.
2. Extract the ZIP file.
3. Via FTP, upload wp-admin and wp-includes folders (overwrite existing).
4. DO NOT overwrite wp-content or wp-config.php.
5. Reload your site.

Step 8: Restore from Backup (When All Else Fails)

If nothing works and you have a recent backup:

• Bluehost: cPanel → Backup → restore a previous backup, or use Bluehost's automated backups tool.
• Plugin backups: If you used UpdraftPlus, BackupBuddy, etc., restore via their recovery process.
• Manual backup: Re-upload your wp-content folder and import your database via phpMyAdmin.

Pro tip: After restoring, immediately enable automatic backups to prevent future panic.

Step 9: Contact Your Host (Last Resort)

If you've tried everything and still see a white screen:

• Server-side issue — PHP version incompatibility, server misconfiguration, resource limits.
• Database corruption — your host can repair database tables via phpMyAdmin or command line.
• Malware infection — host-level security scan can identify injected code.
• Account suspension — rare, but check if your hosting account is suspended for non-payment or TOS violation.

Good hosts (Bluehost, SiteGround, WPX) will diagnose server-side issues in minutes.

Prevent Future White Screens

• Use a staging site — test plugin/theme updates before pushing to production (built into Bluehost, SiteGround, WP Engine).
• Automatic backups — daily minimum, before any update.
• Disable auto-updates for major plugins — WooCommerce, page builders should be updated manually on staging first.
• Monitor uptime — get alerted immediately if your site goes down (see best uptime monitors).
• Increase memory preemptively — set WP_MEMORY_LIMIT to 256M before you need it.
• Quality hosting matters — budget hosts with oversold servers cause more WSODs from resource exhaustion.

Related errors: fix "critical error" message, 500 internal server error, database connection error, memory limit exhausted, stuck in maintenance mode.