How to fix WordPress white screen error: Troubleshooting Checklist

Common Symptoms and Failure Patterns

The WordPress white screen error manifests in several distinct patterns, each pointing to different underlying causes. Understanding which areas are affected helps narrow down the troubleshooting scope.

Frontend-only white screens typically indicate theme issues or frontend-specific plugin conflicts. Admin-only white screens often result from admin-heavy plugins or database connection problems. Site-wide white screens usually point to core WordPress issues, severe plugin conflicts, or server resource exhaustion.

Partial white screens that appear only on specific pages or post types suggest conflicts with custom post type plugins or page builders. White screens after updates indicate compatibility issues between the new version and existing plugins or themes.

Initial Diagnostic Checks

Before making any changes, check your server error logs to identify PHP fatal errors. Most hosting control panels provide error log access under error logs or similar sections. Look for recent entries containing 'Fatal error', 'Parse error', or 'allowed memory size exhausted'.

Verify server resources by checking available disk space and current memory usage. WordPress requires at least 64MB of PHP memory, though modern sites typically need 256MB or more. Insufficient resources cause white screens during resource-intensive operations like plugin updates or image processing.

Test whether the white screen affects the entire site or specific areas. Try accessing /wp-admin, the homepage, and individual posts. If you can access wp-admin but not the frontend, the issue is theme-related. If wp-admin is also white, the problem is likely plugin or core-related.

Plugin Conflict Isolation

Plugin conflicts are the most common cause of WordPress white screens. A single incompatible or poorly coded plugin can crash the entire site. The standard isolation method involves disabling all plugins, then reactivating them individually to identify the culprit.

Since you cannot access wp-admin during a white screen, use FTP, SFTP, or your hosting file manager to disable plugins. Navigate to /wp-content/ and rename the 'plugins' folder to 'plugins-disabled'. This immediately deactivates all plugins. Refresh your site to see if it recovers.

If the site loads after disabling plugins, rename the folder back to 'plugins', then rename individual plugin folders one at a time. Start with recently updated or installed plugins. After renaming each plugin folder, check if the white screen returns. When you find the problematic plugin, keep it disabled and contact the plugin developer or find an alternative.

For critical plugins that you cannot disable, check the plugin's support forum or changelog for known issues and compatibility patches. Sometimes updating to a newer version or rolling back to a previous version resolves the conflict.

Theme Troubleshooting

Theme issues cause white screens when template files contain PHP errors, when child themes reference missing parent theme functions, or when themes are incompatible with the current WordPress version. Theme problems typically affect only the frontend while leaving wp-admin accessible.

Switch to a default WordPress theme using the file system. Navigate to /wp-content/themes/ and rename your active theme folder. WordPress automatically falls back to an available default theme like Twenty Twenty-Four. If the site loads, the original theme has a problem.

For child themes, verify that the parent theme exists and is not corrupted. Check that functions.php in the child theme correctly references the parent theme. A missing or incorrectly named parent theme causes immediate white screens.

If you must restore your original theme, create a fresh copy from the theme developer and upload it with a temporary different folder name. Activate it from wp-admin to ensure it works before removing the problematic version. Always keep a working theme as a fallback.

Memory and Resource Limits

PHP memory exhaustion is a frequent white screen trigger, especially on shared hosting or sites with many plugins. The error occurs when WordPress attempts an operation that exceeds the allocated memory limit, causing a fatal error that produces no output.

Increase the PHP memory limit by editing wp-config.php in your WordPress root directory. Add this line before the comment that says 'That's all, stop editing':

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

For admin operations that require more memory, add a separate admin memory limit:

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

If increasing memory in wp-config.php has no effect, your server-level PHP configuration may be restricting it. Contact your hosting provider to increase the php.ini memory_limit value. Shared hosting plans often cap this at 128MB or 256MB.

Check maximum execution time limits if white screens occur during long operations like imports or large media uploads. Add set_time_limit(300); to the problematic operation or ask your host to increase max_execution_time in php.ini.

Debug Mode and Error Logging

WordPress debug mode reveals hidden error messages that help identify the exact cause of white screens. By default, WordPress suppresses error output to prevent exposing sensitive information. Enabling debug mode makes these errors visible.

Edit wp-config.php and modify the WP_DEBUG settings. Replace the existing WP_DEBUG line (or add these lines if they do not exist) before the 'stop editing' comment:

define('WP_DEBUG', true);

define('WP_DEBUG_LOG', true);

define('WP_DEBUG_DISPLAY', false);

This configuration logs errors to /wp-content/debug.log without displaying them on the frontend. After enabling debug mode, reproduce the white screen error, then check debug.log for specific error messages indicating which file and line number caused the failure.

Common logged errors include 'Call to undefined function', 'Class not found', 'Parse error', and 'Maximum execution time exceeded'. Each error message points to the problematic plugin, theme, or WordPress core file. Once you identify the source, disable or fix that component.

Always disable debug mode on production sites after troubleshooting. Leaving it enabled exposes system paths and can create large log files that consume disk space. Set WP_DEBUG back to false when finished.

Advanced Recovery Methods

If standard troubleshooting does not resolve the white screen, check for corrupted WordPress core files. Download a fresh copy of your WordPress version from wordpress.org and replace the /wp-includes and /wp-admin directories via FTP. Do not replace wp-config.php or the /wp-content directory.

Database corruption occasionally causes white screens, particularly affecting wp-options or wp-posts tables. Use phpMyAdmin to repair database tables. Select all tables, choose 'Repair table' from the dropdown, and execute. WordPress also has a built-in repair mode: add define('WP_ALLOW_REPAIR', true); to wp-config.php, then visit yoursite.com/wp-admin/maint/repair.php. Remove this line after repairs complete.

Check file and directory permissions if white screens appear after a server migration or manual file changes. WordPress requires 755 for directories and 644 for files in most hosting environments. Incorrect permissions prevent PHP from reading required files. Use your FTP client or hosting file manager to set permissions recursively on /wp-content.

For persistent white screens after exhausting all options, restore from a recent backup. Most hosting providers offer automatic daily backups accessible through the control panel. Restoring to a known working state is faster and safer than continued troubleshooting when the cause remains unclear.

PHP version incompatibility can cause white screens, especially after server-side PHP updates. WordPress 6.0+ requires PHP 7.4 or higher, but some older plugins and themes require specific PHP versions. Check your hosting control panel's PHP version selector and test different versions. Start with PHP 7.4 if unsure.