The WordPress white screen of death (WSOD) is a blank page that appears when PHP errors aren’t displayed, usually caused by memory exhaustion, plugin conflicts, or PHP version mismatches. Fix it by enabling debugging, increasing memory limits, or deactivating plugins through FTP—most issues resolve within minutes once the root cause is identified.
The WordPress white screen how to fix is critical knowledge because WSOD affects approximately 30% of WordPress sites at some point during their lifecycle, according to WordPress hosting provider Kinsta’s 2025 downtime analysis. When your site goes blank, you lose traffic, revenue, and user trust instantly. Unlike other errors that show messages, the white screen provides zero feedback, making diagnosis difficult without proper troubleshooting steps. Understanding the root causes saves hours of frustrated debugging and keeps your site operational.
The white screen appears when WordPress encounters a fatal PHP error but has error reporting disabled—a security practice on production sites. Common culprits include exhausted PHP memory limits (the most frequent cause), conflicting plugins that break on update, incompatible PHP versions, corrupted .htaccess files, and third-party code with syntax errors.
Memory exhaustion happens because WordPress loads plugins, themes, database queries, and media processing simultaneously. A poorly coded plugin might create infinite loops or load massive datasets into RAM. PHP’s default 40MB limit often isn’t enough for modern WordPress installations running WooCommerce, Advanced Custom Fields, or image optimization tools.
Plugin conflicts occur when two plugins hook into the same WordPress action and one breaks before the other runs, causing a fatal error that halts page rendering. This typically happens after updates when plugin versions become incompatible.
Debug mode reveals the hidden error messages causing the white screen. Edit your wp-config.php file (located in your WordPress root directory) and add these lines before the line that says “That’s all, stop editing!”:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'SCRIPT_DEBUG', true );This configuration writes errors to /wp-content/debug.log instead of displaying them publicly. Access your site via SFTP or file manager, navigate to /wp-content/, download debug.log, and read it to identify the exact error. Once you’ve found and fixed the issue, set WP_DEBUG back to false to improve performance and security.
There are three ways to increase PHP memory. The most reliable is editing wp-config.php by adding this line before “That’s all, stop editing!”:
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );If that doesn’t work, edit your .htaccess file in the WordPress root and add:
php_value memory_limit 256MFor shared hosting where .htaccess modifications are blocked, contact your host and request a memory limit increase (most providers allow up to 256MB or higher). If you manage a VPS or dedicated server, edit php.ini directly and change the memory_limit value, then restart PHP-FPM. Start with 256MB; if the white screen persists, increase to 512MB. WordPress and most plugins run comfortably at 256MB unless you’re running heavy image processing or large database operations.
When the white screen prevents admin access, you need file-level control. Use SFTP or your hosting control panel’s file manager to navigate to /wp-content/. Rename the /plugins/ folder to /plugins-old/. This disables all plugins instantly without deleting them. Refresh your site. If it comes back online, rename the folder back to /plugins/, then deactivate plugins one at a time through WordPress admin to find the culprit.
If the white screen persists after disabling plugins, you’ve found a different root cause. Move on to theme troubleshooting by renaming your active theme folder in /wp-content/themes/ to something like /theme-old/. WordPress will fall back to a default theme. If the site returns, your theme has a fatal error—consider updating it or switching to a new one.
Check your PHP version compatibility. WordPress 6.4+ requires PHP 7.2.26 minimum, but PHP 7.4+ is recommended. Many hosts still run PHP 7.0 or 5.6, which causes fatal errors with modern WordPress code. Ask your hosting provider to upgrade your PHP version or switch your site in the control panel. This single change resolves 15-20% of WSOD issues on older shared hosting accounts.
Verify your .htaccess file isn’t corrupted. A malformed .htaccess causes parsing errors that trigger the white screen. Rename your .htaccess to .htaccess-old via SFTP, then go to WordPress Settings > Permalinks and click “Save Changes” to regenerate it. If your site returns, the old .htaccess was the problem.
Check for WordPress core file corruption by comparing your wp-includes/ and wp-admin/ folders against a fresh WordPress download. A compromised server, incomplete update, or database sync issue can corrupt these files. Re-upload them from a clean WordPress installation if you suspect corruption.
Establish these preventive practices: enable WordPress automatic updates to keep core, plugins, and themes current. Use a staging environment to test major updates before applying them to production—most quality hosts provide one-click staging. Install a health-check plugin like Health Check & Troubleshooting (recommended by WordPress.org) to monitor PHP compatibility and identify problematic plugins before they break your site.
Monitor your server resources with your hosting control panel’s metrics. If memory usage consistently approaches your limit, upgrade your plan or optimize your setup. Set up log monitoring to catch errors early—tools like WP Activity Log or hosting-native options send alerts when errors spike.
Consider managed WordPress hosting (like WP Engine, Kinsta, or Pagely) where the provider handles PHP updates, memory management, and plugin compatibility testing automatically. According to Kinsta’s 2025 hosting reliability report, managed WordPress hosts experience 60% fewer white screen incidents than unmanaged shared hosting because they optimize the stack specifically for WordPress.
The white screen of death (WSOD) is a completely blank page—nothing renders, no error messages appear, just whitespace. It occurs when a fatal PHP error halts WordPress before it can output any HTML. It’s different from a 500 error or blank page with an error message because the server sends HTTP 200 (success) but serves no content.
On production sites, PHP error display is intentionally disabled for security. Showing errors to visitors exposes your server structure and file paths to attackers. WordPress stores errors in a log file instead, which you can read privately through your file manager or SFTP.
Most hosting control panels (cPanel, Plesk, DirectAdmin) include a file manager accessible through a web browser. Use it to navigate to wp-content/plugins/, rename the plugins folder, or edit wp-config.php. If your host provides neither SFTP nor a file manager, contact support and request emergency access or ask them to disable plugins for you.
Most white screen issues resolve in 5-15 minutes once you enable debug logging and identify the error. Memory limit increases take seconds. Plugin deactivation works instantly. Theme issues usually resolve in minutes. Only database corruption or server misconfigurations require hours of troubleshooting.
No. Increasing PHP memory from 40MB to 256MB won’t impact performance because you’re only allocating what’s available—unused memory doesn’t burden the system. If anything, it prevents the memory-exhaustion errors that currently crash your site. However, if memory usage is constantly at 90%+, that indicates you need more resources or code optimization, not just a higher limit.