.png&w=3840&q=75)
Websites & Hosting3 min
How to Fix "WordPress White Screen of Death" (WSOD)
NS
NameSilo Staff8/27/2026
Share
To fix the WordPress White Screen of Death (WSOD), turn on debugging by adding define('WP_DEBUG', true); to your wp-config.php file, or open the error_log file in cPanel File Manager. Review the log to identify the specific plugin or theme directory causing the fatal PHP error, then rename or delete that plugin folder to restore access.
What Is the White Screen of Death?
WSOD is a fatal PHP error masked by disabled public error display. Production servers hide error output by default, since raw PHP errors can leak file paths and other sensitive server details to visitors. When WordPress hits a fatal error and has nothing safe to show, it shows nothing at all: a blank white page.
Plugin conflicts cause the vast majority of WSOD cases. In 2025, 91% of WordPress vulnerabilities were found in plugins, compared to just 9% in themes, so a recently updated or installed plugin is almost always the first place to look.
Why It Matters: Stopping Blind Guesswork
Deactivating plugins one at a time and refreshing the page repeatedly can work, but it's slow and doesn't tell you why something broke. The debug log names the exact file and line number responsible, turning a guessing game into a two-minute diagnosis.
Method 1: Enabling WP_DEBUG Safely
Open wp-config.php via cPanel File Manager and add these three lines above the "That's all, stop editing!" comment:
define('WP_DEBUG', true);define('WP_DEBUG_LOG', true);define('WP_DEBUG_DISPLAY', false);This combination matters. WP_DEBUG_LOG writes every error to wp-content/debug.log. WP_DEBUG_DISPLAY set to false keeps those errors out of the browser entirely, protecting sensitive server information from visitors while still capturing everything for you to review. Reload the broken page, then open the log file.
After fixing the issue, revert WP_DEBUG back to false. Leaving debug mode active on a live site is a lingering security risk.
Method 2: Inspecting error_log Directly
If you'd rather skip editing wp-config.php, cPanel's File Manager often already has a plain error_log file sitting in your site's root or wp-content folder from PHP's own error logging, separate from WordPress's debug log. Open it directly and look for a line starting with PHP Fatal error:. It typically names the exact plugin folder and file path responsible.
Resolution Steps: The Rename Trick
Once the log identifies the culprit, disable it without needing WordPress admin access at all.
In cPanel File Manager, navigate to wp-content/plugins/, find the broken plugin's folder, right-click, and rename it, for example, broken-plugin to broken-plugin_old.
WordPress cannot find a plugin folder that doesn't match its expected name, so it safely skips loading that plugin entirely on the next page load, without deleting any of its data. Your site should immediately come back online. Once confirmed working, decide whether to update, replace, or permanently remove the plugin.
Common Mistakes
Deactivating everything without checking the log first: Disabling every plugin at once fixes the symptom but tells you nothing. Check the log first, when possible, so you know exactly what to fix rather than guessing which reactivation breaks the site again.
Forgetting to revert WP_DEBUG_DISPLAY: Leaving raw error output visible to the public exposes file paths and configuration details that shouldn't be public.
What This Means for You
NameSilo Hosting includes full cPanel access, giving you File Manager and error log access to fix a WSOD without touching a single line of data or losing content. Starting a new project after cleaning up? Register a new domain to go with it.
Frequently Asked Questions
What causes the WordPress White Screen of Death?
Usually a plugin or theme fatal error, or PHP running out of memory.
How do I fix WSOD in WordPress?
Enable debug logging, identify the broken plugin, then rename its folder.
How do I turn on WP_DEBUG?
Add the WP_DEBUG lines to wp-config.php via cPanel File Manager.
Where is the error_log file in WordPress?
Often in the site root, or wp-content/debug.log once logging is enabled.
How do I disable a plugin without admin access?
Rename its folder inside wp-content/plugins/ via File Manager or FTP.
Will turning on WP_DEBUG expose errors to visitors?
Not if WP_DEBUG_DISPLAY is set to false alongside it.
How do I access wp-config.php in cPanel?
File Manager, root of your WordPress installation folder.
Does NameSilo hosting offer WordPress troubleshooting tools?
Yes, via full cPanel and File Manager access on every hosting plan.
.png&w=2048&q=75)
NameSilo StaffThe NameSilo staff of writers worked together on this post. It was a combination of efforts from our passionate writers that produce content to educate and provide insights for all our readers.
More articleswritten by NameSilo
.png&w=3840&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)