The WordPress white screen of death (WSOD) is a critical error that renders your site completely blank without any visible error messages, affecting both the frontend and admin dashboard. This issue typically stems from exhausted PHP memory limits, plugin or theme conflicts, corrupted core files, or server misconfigurations. The most effective troubleshooting approach involves systematic elimination of potential causes, starting with the least invasive methods before progressing to deeper technical fixes.

Key findings from the search results reveal:

• Plugin conflicts are the most common cause, with Jetpack specifically identified as a culprit in multiple cases ^[2][3]
• Memory limits frequently trigger WSOD, with solutions requiring edits to the wp-config.php file to increase allocation ^[1][8]
• Debug mode (WP_DEBUG) is essential for identifying hidden PHP errors that cause the blank screen ^[2][10]
• File access via FTP/SSH becomes necessary when locked out of the admin dashboard, particularly for plugin deactivation ^[4]

Systematic troubleshooting for WordPress white screen of death

Plugin and theme conflict resolution

The majority of WSOD cases originate from plugin or theme incompatibilities, particularly after updates. A Reddit user confirmed that "in my experience that white screen is generally caused by a plug-in or theme," with Jetpack specifically identified as problematic in their case ^[2]. The systematic approach requires isolating the culprit through controlled deactivation.

Start by attempting to access WordPress Recovery Mode if available (appears when WordPress detects a fatal error). This built-in feature allows plugin deactivation without direct admin access ^[1]. For complete lockouts:

• Connect via FTP/SSH and navigate to /wp-content/plugins/
• Rename the plugins folder to plugins_deactivated (creates a new empty plugins folder)
• Check if the site reappears - if yes, the issue lies with a plugin
• Reactivate plugins one by one by moving them back to the plugins folder ^[4]

For theme conflicts:

• Switch to a default theme (Twenty Twenty-Four, etc.) by renaming your current theme folder in /wp-content/themes/ via FTP
• Kinsta's guide emphasizes this as the second most effective method after plugin checks ^[3]
• If the site loads with a default theme, your original theme contains fatal errors

Critical notes:

• Always create a full backup before making these changes ^[1][10]
• The WordPress.org support forum shows users successfully resolving WSOD by renaming plugin folders when unable to log in ^[4]
• Cloudways reports that 60% of WSOD cases they handle stem from plugin conflicts ^[10]

Memory limit adjustments and server-level fixes

Insufficient PHP memory is another primary cause, with WordPress.com noting this is particularly common in self-hosted installations ^[8]. The default memory limit (often 32MB-64MB) may be inadequate for complex sites. To address this:

Edit your wp-config.php file (located in the root directory) and add this line before the "That's all, stop editing!" comment:

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

This increases the limit to 256MB, which Hostinger identifies as sufficient for most WordPress installations ^[9]. For persistent issues, you may need to edit the server's php.ini file:

memory_limit = 256M

Additional server-level solutions:

• Enable debug mode by adding these lines to wp-config.php:

define('WPDEBUG', true);
define('WPDEBUGLOG', true); define('WPDEBUG_DISPLAY', false);

• Check file permissions - incorrect permissions (often 777) can cause WSOD. Hostinger recommends:
• 755 for directories
• 644 for files
• 440 for wp-config.php ^[9]

• Failed update recovery: If WSOD appears after an auto-update failure, delete the .maintenance file in your root directory via FTP ^[10]

• PHP version compatibility: WordPress StackExchange highlights cases where WSOD occurred due to PHP not being properly enabled in Apache servers ^[6]

For advanced server issues:

• Check PHP error logs (location varies by host, typically in /var/log/php_error.log)
• Verify Apache/Nginx configuration files for syntax errors
• Contact hosting support if issues persist after basic troubleshooting ^[4]