WordPress White Screen How to Fix: 7 Proven Methods
Fix WordPress white screen errors fast with these 7 diagnostic steps. Check memory limits, plugins, themes, and server logs to restore your site.

On this page
TL;DR — Key takeaways
- The 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 first — most white screen issues reveal themselves immediately in the PHP error log.
- Deactivate all plugins via FTP or database query when wp-admin is inaccessible, then reactivate one by one to isolate the conflict.
- Increase PHP memory_limit to 256M or 512M in wp-config.php if the error log shows memory exhaustion messages.
- Switch to a default WordPress theme by renaming your theme folder via FTP if the white screen persists after disabling plugins.
The WordPress white screen appears without warning. One moment your site works fine, the next you see nothing but blank white space. No error message, no admin bar, no content.
This is the white screen of death. In support tickets I handled, the usual culprit was a plugin conflict after an automatic update or a memory limit hit during a traffic spike. The fix is systematic: enable debug mode, check logs, isolate the component that broke, then restore normal operation. Most cases resolve in under 20 minutes once you know where to look.
What the WordPress White Screen Actually Means
The white screen is a symptom, not a diagnosis. When WordPress or PHP encounters a fatal error during page generation, the script stops executing. If error display is disabled in php.ini (the production default), the browser receives an incomplete HTTP response with no body content. That's the white screen.
Fatal errors happen for specific reasons: memory exhaustion, syntax errors in PHP files, undefined functions from missing plugins, or corrupted files. The error exists in the server log even when the screen is blank.
You might see the white screen on the front end, wp-admin, or both. Front-end-only issues usually point to theme code. Admin-only problems often involve plugin conflicts. A complete white screen across all pages suggests a core issue or memory limit.
Enable Debug Mode and Read the Error Log
Start by making errors visible. Connect via FTP or your hosting file manager and open wp-config.php in the root directory. Find the line that says:
Change it to:
Add these lines right after that existing define statement:
Save the file. Reload your site. If the white screen now shows error messages, you have your answer immediately. The error message tells you which file and line number failed.
If nothing appears on screen, check the debug.log file that WordPress just created in wp-content/. Download it and open it in a text editor. Look for the most recent timestamp and read the fatal error message. It will name the plugin or theme file that broke.
- define('WP_DEBUG', false);
- define('WP_DEBUG', true);
- define('WP_DEBUG_LOG', true);
- define('WP_DEBUG_DISPLAY', false);
Deactivate All Plugins Without Admin Access
If plugins caused the issue, you can't access wp-admin to deactivate them normally. You need to do it via FTP or database.
FTP method: connect to your site and navigate to wp-content/. Rename the plugins folder to plugins-disabled. WordPress will see no plugins directory and deactivate everything. Reload your site. If it works, rename the folder back to plugins, then rename individual plugin folders one at a time to isolate the problem plugin.
Database method: log into phpMyAdmin or your database client. Open the wp_options table (prefix might differ). Find the row where option_name equals 'active_plugins'. Edit that row and change the option_value to an empty serialized array: a:0:{}
That deactivates every plugin instantly. Reload the site. If it loads, go to wp-admin and reactivate plugins one by one until the white screen returns. That's your conflict.
Switch to a Default Theme
Theme code runs on every page load. A syntax error or missing function in functions.php can cause a white screen.
Via FTP, navigate to wp-content/themes/. Find your currently active theme folder. Rename it to something like themename-disabled. WordPress can't find the active theme anymore, so it falls back to a default theme like Twenty Twenty-Four.
Reload the site. Does it work now? Your theme was the problem. Check the theme's functions.php for recent edits or plugin dependencies. If you added custom code recently, remove it and test again.
A corrupted theme file can also cause this. Download a fresh copy of the theme from the original source, delete the broken folder via FTP, and upload the clean version.
Increase the PHP Memory Limit
Memory exhaustion is common on shared hosting. WordPress tries to load too much data or a plugin runs a heavy query, PHP runs out of memory, and the script dies.
Open wp-config.php again and add this line before the 'That's all, stop editing!' comment:
This sets the WordPress memory limit to 256 MB. For larger sites, use 512M. Save and reload.
If your host enforces a lower limit in php.ini, this won't help. Check your server error log (usually in the hosting control panel under 'Error Logs') for messages like 'Allowed memory size of X bytes exhausted'. If the limit is too low, contact support or upgrade your hosting plan.
Some shared hosts limit memory to 128M. That's barely enough for a modern WordPress install with a page builder and a few plugins.
- define('WP_MEMORY_LIMIT', '256M');
Clear All Caching Layers
Caching plugins, object cache, and CDN edge caches can serve a stale white screen even after you fix the underlying issue.
If you use a caching plugin like WP Super Cache or W3 Total Cache, delete the cache via FTP. The cache directory is usually wp-content/cache/. Delete everything in that folder.
Object cache (Redis or Memcached) can also hold bad data. If your host provides a cache flush button in the control panel, use it. Otherwise, restart the Redis or Memcached service if you have shell access.
If you use Cloudflare or another CDN, log into the dashboard and purge the entire cache. Wait 60 seconds, then test your site again in an incognito browser window to avoid local browser cache.
Check Server Error Logs for PHP Fatal Errors
WordPress debug.log might not catch everything. The server's own error log records all PHP fatal errors regardless of WordPress settings.
Log into your hosting control panel. Look for 'Error Logs', 'Logs', or 'Log Viewer'. Open the PHP error log. Sort by timestamp and find entries from the time the white screen started.
Common messages to look for: 'Call to undefined function', 'syntax error', 'Allowed memory size exhausted', 'Maximum execution time exceeded'. The log will name the exact file and line number.
If you see 'require' or 'include' errors, a file is missing or the path is wrong. If you see 'Class not found', a plugin dependency is missing or a namespace conflict exists.
Test with a Fresh WordPress Core Installation
If none of the above worked, the core files might be corrupted. Download a fresh copy of WordPress from wordpress.org matching your current version number.
Via FTP, delete these folders from your site: wp-admin and wp-includes. Do not delete wp-content or wp-config.php.
Extract the fresh WordPress download on your computer. Upload the wp-admin and wp-includes folders from the fresh copy to your site, overwriting nothing because you just deleted the old ones.
Reload the site. This replaces all core files without touching your themes, plugins, or configuration. If the white screen persists, the issue is in wp-content (your themes or plugins) or your database.
As a last resort, restore from your most recent backup and apply updates one at a time to identify what triggered the error.
Quick troubleshooting checklist
- Take a full backup of files and database before troubleshooting
- Enable WP_DEBUG in wp-config.php and check error logs
- Deactivate all plugins via FTP or database
- Switch to a default theme by renaming the active theme folder
- Increase memory_limit to 256M in wp-config.php
- Clear all caching layers (plugin cache, object cache, CDN)
- Check server error logs for PHP fatal errors
- Test with a fresh WordPress core installation if issue persists
FAQ
What causes the WordPress white screen error?
The WordPress white screen is caused by PHP fatal errors that stop page rendering. The most common triggers are memory limit exhaustion, plugin conflicts (especially after updates), syntax errors in theme functions.php, or corrupted core files. When PHP encounters a fatal error and display_errors is disabled, the browser receives an empty response and shows a blank white page.
How do I fix WordPress white screen if I can't access wp-admin?
Access your site via FTP or file manager and rename the wp-content/plugins folder to plugins-disabled. This deactivates all plugins. If the site loads, rename it back and deactivate plugins one by one by renaming individual plugin folders. If plugins aren't the issue, rename your active theme folder in wp-content/themes to force WordPress to load a default theme.
Why does increasing memory_limit fix the white screen?
WordPress and PHP plugins consume server memory during page generation. When available memory is exhausted, PHP stops execution with a fatal error. Increasing memory_limit from the default 128M to 256M or 512M in wp-config.php gives WordPress more memory to complete page rendering. Check your error log for messages like 'Allowed memory size exhausted' to confirm this is the cause.
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.