How to Fix WordPress White Screen Fix: Practical Guide
Step-by-step guide to diagnose and fix WordPress white screen of death (WSOD). Practical troubleshooting for hosting teams and site owners.

On this page
TL;DR — Key takeaways
- WordPress white screen is typically caused by PHP memory exhaustion, plugin conflicts, or theme errors that prevent the page from rendering.
- Enable WP_DEBUG and check error logs before making changes—most white screen issues reveal their cause in PHP error messages.
- Deactivate plugins via database or file system when admin access is unavailable, then reactivate one by one to isolate the problematic component.
- Increase PHP memory limit to 256MB or higher in wp-config.php as a first step if memory exhaustion is suspected.
- Always backup your database and files before troubleshooting to ensure safe rollback if changes cause additional issues.
The WordPress white screen of death (WSOD) appears when a PHP error prevents WordPress from rendering any content, leaving only a blank white page. This issue affects both the front end and admin dashboard, blocking access to your site without warning or error messages visible to users.
This guide walks through systematic troubleshooting steps to identify and fix the root cause, whether it's a plugin conflict, theme error, memory limit, or corrupted core file. Each method includes safe testing boundaries and rollback instructions.
What Causes WordPress White Screen
WordPress white screen occurs when a fatal PHP error stops execution before any output reaches the browser. The server processes the request but fails silently, returning a 200 status code with no content.
Common triggers include PHP memory exhaustion when processing large operations, syntax errors in theme or plugin files, conflicts between incompatible plugins, and corrupted WordPress core files after failed updates.
The error remains invisible because WordPress error display is disabled by default in production environments. Enabling debug mode reveals the underlying PHP error that causes the blank screen.
Enable WordPress Debug Mode
WP_DEBUG_LOG writes errors to wp-content/debug.log without displaying them to visitors. After saving, reproduce the white screen and check debug.log for the exact error message, file path, and line number.
If debug.log shows memory exhaustion errors, proceed to increase PHP memory. If it shows plugin or theme errors, note the file path for targeted troubleshooting.
- define('WP_DEBUG', true);
- define('WP_DEBUG_LOG', true);
- define('WP_DEBUG_DISPLAY', false);
- define('SCRIPT_DEBUG', true);
Increase PHP Memory Limit
WordPress default memory limit is 40MB, which becomes insufficient for sites with many plugins, large media libraries, or complex themes. PHP memory exhaustion typically shows as 'Allowed memory size exhausted' in error logs.
Edit wp-config.php and add this line before 'That's all, stop editing':
define('WP_MEMORY_LIMIT', '256M');
For admin operations, also set: define('WP_MAX_MEMORY_LIMIT', '512M');
Save the file and refresh your site. If the white screen persists, the issue is not memory-related. If it resolves, the previous limit was too low for your site's requirements.
Verify your hosting plan supports the increased limit by checking PHP settings in your hosting control panel or phpinfo(). Some shared hosting plans enforce lower memory caps that override wp-config.php settings.
Deactivate Plugins Without Admin Access
Plugin conflicts cause white screens when incompatible code executes during page load. When admin access is blocked, deactivate all plugins via the database or file system.
Database method: Access your database via phpMyAdmin or command line. In the wp_options table, find the row where option_name is 'active_plugins'. Change option_value to 'a:0:{}' to deactivate all plugins at once.
File system method: Connect via FTP or file manager. Navigate to wp-content/plugins/ and rename the plugins folder to plugins_disabled. WordPress will not find any plugins and will load without them.
After deactivation, attempt to access your admin dashboard. If the white screen clears, the issue was plugin-related. Reactivate plugins one at a time, testing the site after each activation to identify the problematic plugin.
Once identified, leave the problem plugin deactivated and check for updates or support documentation. Many white screen issues are resolved in newer plugin versions.
Switch to Default Theme
Theme errors cause white screens when custom functions or template files contain syntax errors or call undefined functions. Switch to a default WordPress theme to test if your active theme is the cause.
Without admin access, use the database method. In wp_options, find 'template' and 'stylesheet' rows. Change both values to 'twentytwentyfour' (or another default theme installed in wp-content/themes/).
Refresh your site. If the white screen disappears, your theme contains the error. Check the debug.log for the specific file and line number, or contact your theme developer.
If using a child theme, first try switching to the parent theme. Child theme errors often stem from functions.php mistakes or incorrect template overrides.
After resolving the theme issue or switching themes, update the template and stylesheet values back to your preferred theme via the database or through the admin panel if access is restored.
Check Server Error Logs and PHP Version
Server error logs capture PHP fatal errors that WordPress cannot log internally. Access error logs through your hosting control panel, typically in Logs or Error Logs sections.
Look for entries timestamped when the white screen occurred. Common errors include 'Call to undefined function', 'Parse error', and 'Fatal error'. The log provides file paths and line numbers for precise debugging.
Verify your PHP version meets WordPress requirements. WordPress 6.0 and higher require PHP 7.4 or greater. Check your hosting panel for PHP version settings and upgrade if necessary.
After changing PHP versions, test your site. Some older plugins and themes are incompatible with PHP 8.0+ due to deprecated functions. If the white screen appears after a PHP upgrade, temporarily revert to the previous version and update your theme and plugins before trying again.
If server logs show file permission errors, reset WordPress file permissions: 644 for files, 755 for directories. Use your FTP client's recursive permission change feature or run commands via SSH if available.
Reinstall WordPress Core Files
Corrupted core files can cause white screens after failed updates or improper file transfers. Reinstalling WordPress overwrites potentially damaged files without affecting your content or settings.
Before reinstalling, backup your wp-config.php file and wp-content directory. These contain your database credentials, plugins, themes, and uploads.
Download the latest WordPress version from wordpress.org. Extract the archive and delete the wp-content folder and wp-config-sample.php from the extracted files.
Upload the remaining files to your server via FTP, overwriting existing files. This replaces wp-admin and wp-includes directories plus root files without touching your configuration or content.
After upload, visit your site. If the white screen persists, the issue is not in WordPress core files. Check plugin and theme code, or review database integrity using tools like WP-CLI or phpMyAdmin.
Quick troubleshooting checklist
- Backup database and files before making any changes
- Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php
- Check wp-content/debug.log for error messages
- Increase WP_MEMORY_LIMIT to 256M in wp-config.php
- Deactivate all plugins via database or file system
- Reactivate plugins one by one to isolate conflicts
- Switch to default WordPress theme via database
- Review server error logs for PHP fatal errors
- Verify PHP version meets WordPress requirements
- Reinstall WordPress core files if corruption suspected
- Test site functionality after each troubleshooting step
- Disable debug mode after resolving the issue
FAQ
What is the WordPress white screen of death?
The WordPress white screen of death (WSOD) is a blank white page that appears when a PHP fatal error stops WordPress from rendering content. It affects both the site front end and admin dashboard, leaving no visible error message for users or administrators.
How do I fix WordPress white screen without admin access?
Fix WordPress white screen without admin access by enabling debug mode in wp-config.php via FTP, then deactivating all plugins by renaming the plugins folder or editing the active_plugins option in the database. Switch to a default theme by changing the template and stylesheet values in wp_options table.
Why does increasing PHP memory fix WordPress white screen?
Increasing PHP memory fixes WordPress white screen when the error is caused by memory exhaustion. WordPress processes running out of allocated memory trigger fatal errors that prevent page rendering. Setting WP_MEMORY_LIMIT to 256M or higher provides enough memory for plugins, themes, and core operations to complete without crashing.
Can a plugin cause WordPress white screen even when deactivated?
No, a deactivated plugin cannot cause WordPress white screen because deactivated plugins do not execute any code. If the white screen persists after deactivating all plugins, the cause is either a theme error, WordPress core file corruption, server configuration issue, or a must-use plugin in wp-content/mu-plugins.
How do I prevent WordPress white screen in the future?
Prevent WordPress white screen by keeping WordPress core, themes, and plugins updated, testing updates on a staging site before applying to production, monitoring PHP error logs regularly, maintaining adequate PHP memory limits, and using compatible plugin combinations. Always backup before making changes to allow safe rollback if issues occur.
Related articles
- Hosting OperationsSelf-Hosted App Deployment Fails? Check DNS, SSL, Reverse Proxy, and Logs FirstTroubleshoot failed self-hosted app deployments by checking DNS, SSL, reverse proxy routing, container status, logs, and ports.
- Hosting OperationsSelf-Hosted PaaS on a VPS: What to Check Before Installing Coolify, Dokploy, or CapRoverA hosting support checklist for preparing a VPS before installing self-hosted PaaS tools like Coolify, Dokploy, or CapRover.
- Hosting OperationsLinux Server Security Lessons from the Arch Linux Malware Package IncidentPractical Linux server security checklist for VPS admins after package malware concerns, with safe checks, rollback steps, and support guidance.
- Hosting OperationsAWS Lightsail Hong Kong VPS Latency: Practical Hosting Guide for IndonesiaLearn how to test AWS Lightsail Hong Kong VPS latency, compare regions, migrate safely, and troubleshoot hosting performance.
- Hosting OperationsCloudflare Tomorrow Watchlist: A Practical Hosting Operations GuidePractical Cloudflare troubleshooting checklist for DNS, SSL, caching, WAF, origin health, safe testing, and rollback planning.
- Hosting OperationsNetwork Safety Checklist for AI Agent Skills in Hosting OperationsAudit AI agent skills safely with network checks, secret protection, sandbox testing, rollback steps, and hosting support troubleshooting guidance.