How to Fix the WordPress White Screen of Death (Step by Step)
The WordPress white screen of death (WSOD) is a completely blank white page that appears instead of your website — no error message, no content, just white. The most common cause is a PHP fatal error triggered by a plugin conflict, a theme issue, or exhausted server memory. In most cases, you can fix it in under 30 minutes by deactivating plugins, switching themes, or increasing your PHP memory limit.
The WSOD is one of the most alarming WordPress errors because it gives you no information about what went wrong. Your site shows nothing — and in many cases, your WordPress admin dashboard is also blank, making it impossible to troubleshoot from the usual interface. This guide walks through every known fix, from the most common causes to the rarest, so you can get your site back regardless of what triggered the problem.
What Causes the WordPress White Screen of Death?
The WSOD is almost always caused by a PHP fatal error that crashes WordPress before it can output any HTML. The most common triggers are:
Plugin conflicts. A plugin update introduces incompatible code, two plugins conflict with each other, or a plugin is incompatible with your WordPress or PHP version. This accounts for the majority of WSOD incidents.
Theme errors. A theme update contains a PHP error, your theme’s functions.php file has a syntax mistake, or the theme is incompatible with a recent WordPress core update.
PHP memory exhaustion. WordPress runs out of the memory allocated by your hosting provider. This happens when plugins or themes consume excessive memory, or when your host’s memory limit is set too low for your site’s needs.
Corrupted core files. A failed WordPress core update leaves partially written files that cause fatal errors on load.
PHP version incompatibility. Your hosting provider upgraded PHP to a version that one of your plugins or your theme does not support.
Step 1: Enable WordPress Debug Mode
The first step is to make the error visible. By default, WordPress hides PHP errors and shows a blank page instead. Enabling debug mode tells WordPress to display the actual error message — which usually points directly to the problematic file and line number.
Access your site’s files via FTP (using FileZilla or similar), SFTP, or your hosting control panel’s file manager. Open the file wp-config.php in your WordPress root directory. Find the line that says define('WP_DEBUG', false); and change it to:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', true);
Save the file and reload your site. If a PHP error is causing the WSOD, you should now see an error message instead of a blank page. The message will typically include the file path and line number where the error occurred — for example, Fatal error: ... in /wp-content/plugins/some-plugin/file.php on line 42. This tells you exactly which plugin or theme is causing the problem.
If you still see a blank white page after enabling debug, check the debug log file at /wp-content/debug.log — the error may be logged there even if it does not display on screen. For a deeper guide, read our article on enabling WordPress debug mode.
Step 2: Deactivate All Plugins
If the error message points to a plugin file, or if you cannot determine the cause from the error message, the next step is to deactivate all plugins to see if the WSOD resolves.
If You Can Access the Admin Dashboard
Sometimes the WSOD affects only the front end of your site while the admin dashboard still works (or vice versa). If you can access wp-admin, go to Plugins → Installed Plugins, select all plugins, and choose “Deactivate” from the Bulk Actions dropdown. Reload your site. If the WSOD is gone, one of your plugins caused it.
If You Cannot Access the Admin Dashboard
Connect to your site via FTP or your hosting file manager. Navigate to /wp-content/. Rename the plugins folder to something like plugins-disabled. This effectively deactivates all plugins because WordPress cannot find them. Reload your site. If the WSOD resolves, rename the folder back to plugins — all plugins will now be deactivated (but not deleted). Reactivate them one at a time through the admin dashboard, reloading your site after each activation, until the WSOD returns. The last plugin you activated is the culprit.
For more methods, including command-line approaches, read our guide on deactivating plugins when locked out of admin. For understanding plugin conflicts in general, see our plugin conflict troubleshooting guide.
Step 3: Switch to a Default Theme
If deactivating all plugins does not resolve the WSOD, your theme is likely the cause. Switch to a default WordPress theme (Twenty Twenty-Four, Twenty Twenty-Three, or any default theme installed on your site).
Via FTP or File Manager
Navigate to /wp-content/themes/. Rename your active theme’s folder — for example, rename my-theme to my-theme-disabled. WordPress will detect that the active theme is missing and automatically fall back to the latest default theme installed. Reload your site. If it loads with the default theme, your theme was the problem.
Common theme-related WSOD causes include a syntax error in functions.php (often introduced by manual edits), a theme update that is incompatible with your WordPress version or a critical plugin, and a theme that requires a minimum PHP version your server does not meet.
Step 4: Increase PHP Memory Limit
If the error message includes “Allowed memory size exhausted” or “Fatal error: Out of memory,” your site is hitting the PHP memory ceiling.
Open wp-config.php and add this line before the line that says “That’s all, stop editing!”:
define('WP_MEMORY_LIMIT', '256M');
If this does not work, the memory limit may be enforced at the server level. You can also try adding this to your .htaccess file:
php_value memory_limit 256M
Or create/edit a php.ini file in your WordPress root with:
memory_limit = 256M
If none of these work, contact your hosting provider — some shared hosts enforce memory limits that cannot be overridden from WordPress. Read our comprehensive guide on fixing the WordPress memory exhausted error.
Step 5: Check for Corrupted Core Files
If a WordPress core update failed partway through — due to a server timeout, a network interruption, or a disk space issue — core files may be corrupted or incomplete.
Download a fresh copy of WordPress from wordpress.org. Extract it. Upload the wp-admin and wp-includes folders from the fresh download to your site via FTP, overwriting the existing folders. Do NOT overwrite wp-content (that contains your themes, plugins, and uploads) or wp-config.php (that contains your database credentials).
This replaces all core files with clean copies while preserving your content and configuration.
Step 6: Check PHP Version Compatibility
If your hosting provider recently upgraded your server’s PHP version, older plugins or themes may be incompatible. Check your PHP version in your hosting control panel. If it was recently changed, try downgrading to the previous PHP version temporarily and see if the WSOD resolves. If it does, the issue is a plugin or theme that does not support the newer PHP version — update or replace the incompatible component.
Step 7: Check for .htaccess Corruption
A corrupted .htaccess file can cause the WSOD on Apache servers. Via FTP, rename .htaccess to .htaccess-backup. Reload your site. If it works, go to Settings → Permalinks in your WordPress admin and click “Save Changes” — this regenerates a fresh .htaccess file.
Step 8: Reinstall WordPress
If none of the above steps resolve the issue, a clean WordPress reinstall may be necessary. This is a last resort that preserves your content and settings but replaces the entire WordPress core installation.
From your WordPress admin (if accessible), go to Dashboard → Updates and click “Reinstall version X.X.” If you cannot access the admin, download WordPress from wordpress.org, delete everything in your WordPress root directory EXCEPT wp-content and wp-config.php, and upload the fresh WordPress files.
How to Prevent the White Screen of Death
Keep daily backups. A recent backup means you can restore your site to a working state within minutes, regardless of what caused the WSOD. Our care plans include daily automated backups with 30–120 day retention.
Update plugins and themes regularly — but carefully. Apply updates one at a time rather than all at once. Test on a staging environment if your site is business-critical.
Use a maintenance service. Our update service applies updates daily with visual validation — automated screenshots that catch problems before visitors see them. If an update causes a WSOD, we detect it immediately, roll back, and resolve the conflict.
Monitor your PHP memory usage. If your site regularly approaches its memory limit, consider upgrading your hosting plan or optimising your plugin stack to reduce memory consumption.
Frequently Asked Questions
Can the white screen of death cause data loss?
The WSOD itself does not cause data loss. It is a display error — your database, files, and content remain intact. However, if the WSOD was triggered by a database corruption or a failed update, the underlying issue might involve data problems. This is why daily backups are essential.
Why does the WSOD only affect some pages and not others?
If only specific pages show the WSOD while others load fine, the issue is likely tied to a specific piece of content on those pages — a shortcode from a deactivated plugin, a corrupted post, or a page-specific template in your theme that contains an error.
My site shows a white screen only on mobile. What is happening?
This is rare but can occur when a plugin or theme loads different code paths for mobile devices. Try deactivating mobile-specific plugins (AMP plugins, mobile redirect plugins, responsive menu plugins) to isolate the cause.
The WSOD comes and goes intermittently. Why?
Intermittent WSOD is usually caused by PHP memory exhaustion that only occurs under specific conditions — high traffic, complex pages, or specific user interactions that consume more memory than typical page loads. Increasing your PHP memory limit and identifying memory-hungry plugins typically resolves this.
I fixed the WSOD but now my site looks different. What happened?
If you switched to a default theme to resolve the WSOD, your site will look different because it is using a different theme. Reactivate your original theme and investigate what caused the error — it may need an update, a PHP compatibility fix, or replacement if it is abandoned.
Need Expert Help? Let WP Ministry Handle It
The white screen of death is stressful — especially when it happens outside business hours, when your developer is unavailable, or when you have no idea which of the steps above to try first. Our 24/7 WordPress support team has resolved thousands of WSOD incidents and can typically restore your site within hours.
Call (901) 249-0909 for immediate assistance, or submit an emergency ticket. One-time fixes start at $199. Or choose a care plan and let our team prevent the WSOD from happening in the first place through daily updates with visual validation and proactive monitoring.
Related Articles
How to Fix WordPress 500 Internal Server Error (2026 Guide)
How to Fix “Error Establishing a Database Connection” in WordPress
How to Fix WordPress Plugin Conflicts (Troubleshooting Guide)