How to fix WordPress white screen error: Practical Guide

Understanding WordPress white screen error

The WordPress white screen error appears as a completely blank page with no content, error messages, or visual elements. Unlike other WordPress errors that display messages or warnings, WSOD provides no immediate clues about the underlying problem.

This error occurs when PHP execution fails silently, usually due to memory exhaustion, fatal errors in code, or server resource limits. WordPress attempts to load but encounters a condition that stops processing before any output reaches your browser.

The white screen can affect your entire site, only the admin dashboard, specific pages, or particular functions like post editing. The scope of the error often indicates which component is causing the failure.

• Complete site failure: usually indicates core file corruption, server misconfiguration, or critical plugin conflicts
• Admin-only white screen: typically caused by plugin conflicts in the dashboard or theme functions affecting admin pages
• Frontend-only blank pages: often related to theme issues, template file errors, or frontend-specific plugin problems
• Selective page failures: points to specific post content, shortcodes, or page-level plugin interactions

Common causes of WordPress white screen

PHP memory exhaustion is the most frequent cause of WordPress white screen errors. When WordPress or its plugins consume all available PHP memory, the script terminates without completing the page load or displaying error information.

Plugin conflicts occur when two or more plugins interact poorly, often after updates introduce incompatible code. A single poorly coded plugin can also trigger fatal PHP errors that result in white screens.

Theme issues arise from corrupted theme files, incompatible template code, or functions.php errors. Custom themes with untested code are particularly susceptible to causing white screen conditions.

Corrupted WordPress core files, database connection failures, and server-level PHP configuration problems can also trigger white screens. Hosting environment changes, such as PHP version updates or resource limit adjustments, sometimes expose latent compatibility issues.

Pre-troubleshooting preparation

Before attempting any fixes, create a complete backup of your WordPress site including all files and the database. This backup provides a rollback point if troubleshooting steps cause additional problems or data loss.

Most hosting control panels offer one-click backup tools. Alternatively, access your site via FTP and download the entire WordPress directory, then export your database using phpMyAdmin or command-line tools. Store backups outside your server environment.

Gather access credentials for FTP, SSH, database, and your hosting control panel. You'll need these to implement fixes since the WordPress admin dashboard may be inaccessible during troubleshooting.

Check your hosting account's resource usage dashboard to identify any current CPU, memory, or bandwidth limits being reached. Resource exhaustion at the hosting level can cause white screens independent of WordPress configuration.

• Full file backup via FTP, SFTP, or hosting backup tool
• Complete database export in SQL format
• FTP/SSH credentials and connection details verified
• Hosting control panel login confirmed and functional
• Current server error logs downloaded for reference

Enable WordPress debug mode

WordPress debug mode reveals hidden PHP errors that cause white screens. By default, WordPress suppresses error messages in production environments, making diagnosis difficult without enabling logging.

Connect to your site via FTP and navigate to the root WordPress directory. Download the wp-config.php file as a backup before editing. Open wp-config.php in a text editor and locate the line that reads define('WP_DEBUG', false);.

Replace that line with the following debug configuration to enable error logging without displaying errors to site visitors:

define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false); @ini_set('display_errors', 0);

Save the modified wp-config.php file and upload it back to your server, overwriting the original. WordPress now logs all errors to wp-content/debug.log. Attempt to reload the white screen page, then download and examine debug.log for error messages identifying the specific problem.

Common error messages include memory exhausted, fatal error, maximum execution time exceeded, and call to undefined function. These messages point directly to the component causing the failure.

Increase PHP memory limit

PHP memory limit defines how much server memory a single PHP script can consume. WordPress's default 64MB limit is often insufficient for sites with multiple plugins, large themes, or high traffic.

Edit wp-config.php and add this line just before the comment that says 'That's all, stop editing':

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

This increases WordPress's memory allocation to 256MB. If you have admin access issues specifically, also add:

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

Save and upload the modified file. Reload your site to check if the white screen resolves. If the error persists, the issue is not memory-related and further troubleshooting is required.

Some hosting providers enforce PHP memory limits at the server level that override wp-config.php settings. If increasing the limit in WordPress has no effect, contact your hosting provider to request a higher PHP memory_limit value in php.ini or through your hosting control panel's PHP settings.

Deactivate plugins to isolate conflicts

Plugin conflicts are resolved by deactivating all plugins, confirming the site loads, then reactivating plugins one at a time to identify the problematic component.

Since you cannot access the WordPress admin dashboard, deactivate plugins via FTP. Connect to your site and navigate to wp-content/plugins/. Rename the entire plugins folder to plugins_disabled or plugins.old.

Reload your site. If the white screen disappears, a plugin is causing the error. Create a new empty folder named plugins in wp-content/. Rename plugins_disabled back to plugins temporarily, then move plugin folders one at a time from the old plugins directory into the new one.

After moving each plugin folder, reload your site. When the white screen returns, you've identified the problematic plugin. Leave that plugin folder outside the active plugins directory, move the remaining plugins back, and your site should function normally.

Once identified, check if the problematic plugin has available updates. Developers often release fixes for bugs causing fatal errors. If no update is available, search for alternatives or contact the plugin developer with details from your debug log.

• Rename wp-content/plugins to plugins_disabled via FTP
• Reload site to confirm white screen resolves
• Create new wp-content/plugins folder
• Move plugins individually from plugins_disabled to plugins
• Test site after each plugin move to identify the conflict
• Leave problematic plugin deactivated and check for updates

Switch to a default WordPress theme

Theme issues cause white screens when template files contain syntax errors, functions.php has fatal errors, or theme code conflicts with active plugins. Testing with a default WordPress theme isolates theme-related problems.

Without dashboard access, switch themes by modifying your WordPress database directly. Access phpMyAdmin or another database management tool through your hosting control panel. Select your WordPress database and open the wp_options table.

Find the row where option_name equals 'template'. Change the option_value to 'twentytwentythree' or another default theme installed on your site. Also update the row where option_name equals 'stylesheet' to the same value.

Reload your site. If the white screen is gone, your theme is the cause. You can now access the WordPress admin dashboard using the default theme. Install a different theme or contact your original theme's developer for support.

If you need to keep your original theme, examine its functions.php file for obvious syntax errors, unclosed parentheses, or missing semicolons. Compare against a fresh download from the theme developer to identify corrupted files.

Check and repair WordPress core files

Corrupted WordPress core files occasionally cause white screens, particularly after failed updates or server issues during file transfers. Reinstalling WordPress core files over your existing installation repairs corruption without affecting your content, plugins, or themes.

Download the latest version of WordPress from wordpress.org. Extract the ZIP file on your local computer. Before uploading, delete the wp-content folder and wp-config-sample.php from the extracted files to avoid overwriting your customizations.

Using FTP, upload the remaining files from the extracted WordPress package to your site's root directory, overwriting existing files. This process replaces all core WordPress files with fresh copies while preserving your database, uploads, plugins, and themes in wp-content.

After uploading, reload your site. If a corrupted core file caused the white screen, your site should now load normally. If the error persists, the issue lies in your plugins, theme, or database configuration rather than core WordPress files.

Examine server error logs

Server error logs capture PHP errors, web server failures, and resource limit violations that WordPress's debug log might miss. These logs often reveal root causes when standard troubleshooting steps fail.

Access error logs through your hosting control panel's error log viewer, typically found in file manager or log sections. Alternatively, use FTP to download log files, usually located in the site's root directory or a logs folder. Common log filenames include error_log, error.log, or php_error.log.

Open the log file and scroll to entries timestamped around when you experienced the white screen. Look for fatal errors, memory exhausted messages, maximum execution time exceeded warnings, or segmentation fault indicators.

Search for filenames in error messages to identify which plugin, theme file, or WordPress core component triggered the failure. Resource limit errors indicate hosting environment constraints requiring plan upgrades or server configuration changes.

If logs show database connection errors, verify your database credentials in wp-config.php match your hosting control panel's database settings. Connection failures produce white screens identical to code errors but require different resolution approaches.

Prevent future white screen errors

Regular maintenance prevents most white screen errors. Update WordPress core, plugins, and themes promptly when updates are released, but test updates in a staging environment first before deploying to production sites.

Choose quality plugins and themes from reputable developers with regular update cycles and strong support records. Avoid nulled or pirated themes and plugins, which often contain malicious code or missing dependencies causing fatal errors.

Monitor your site's resource usage through your hosting dashboard. If your site consistently approaches PHP memory limits or maximum execution time settings, upgrade to a hosting plan with higher resource allocations before problems occur.

Implement automated backups that run daily and store copies off-server. When white screens or other critical errors occur, recent backups minimize downtime by allowing quick restoration to a known good state.

Use a staging site to test plugin installations, theme changes, and WordPress updates before applying them to your live site. Staging environments catch compatibility issues and white screen triggers before they affect visitors.

• Update WordPress, plugins, and themes within one week of release
• Test all updates on staging site before production deployment
• Install only reputable plugins with recent updates and positive reviews
• Monitor PHP memory usage and upgrade hosting when approaching limits
• Schedule automated daily backups with off-server storage
• Implement uptime monitoring to detect white screens immediately