WordPress Troubleshooting
Fixing the WordPress White Screen of Death, Step by Step
A completely blank white page with no error message is one of WordPress's more frustrating failures — here's how to isolate the cause and get the site back.
3
Most common causes: plugin, theme, memory limit
WP_DEBUG
Setting that reveals the hidden error
NVMe
SSD storage for fast file edits during recovery
24/7
Human support if the site stays blank
In short
The WordPress white screen of death is a blank white page with no visible error, usually caused by a PHP fatal error, a plugin or theme conflict, or the site hitting its memory limit — but WordPress hides the actual error by default. The fix is to isolate the cause methodically: enable debug mode to reveal the hidden error, deactivate all plugins (via FTP or File Manager if wp-admin is also blank) to test for a plugin conflict, and raise the PHP memory limit if the error points to memory exhaustion.
Because the white screen gives no direct clue on its own, the fastest path back is almost always turning on WP_DEBUG first, since it usually names the exact file and line causing the crash within seconds.
A blank white page is one of the more unsettling WordPress failures precisely because it offers no information — no error code, no message, nothing to search for. That blankness is intentional: production WordPress sites suppress PHP errors from public view by default, which protects against leaking sensitive file paths but also hides the one clue that would tell you exactly what broke. The fix isn't guesswork, though — it's a short, repeatable diagnostic sequence.
Whether the white screen hit only the front end, only wp-admin, or both determines where you start. If wp-admin still loads, you can deactivate plugins from the dashboard. If wp-admin is also blank, FTP or your hosting panel's File Manager becomes the only way in, since you'll be renaming plugin folders directly on the server rather than clicking through a dashboard that isn't rendering.
Step 1: Turn On Debug Mode to See the Real Error
Connect via FTP or your hosting panel's File Manager and open wp-config.php. Find the line define('WP_DEBUG', false); and change it to true, then add define('WP_DEBUG_LOG', true); on the line below it. Reload the site — instead of a blank page, WordPress now either displays the actual PHP error directly or logs it to a file at /wp-content/debug.log, depending on your other debug settings.
The error message almost always names a specific plugin file, theme file, or a memory exhaustion message directly, which turns a total guessing game into a targeted fix. Once you've identified the cause and resolved it, set WP_DEBUG back to false — displaying PHP errors publicly on a live site is a real security exposure if left on by accident.
Step 2: Deactivate Plugins to Find a Conflict
If wp-admin still loads, go to Plugins, select all, and deactivate them in bulk, then reload the front end. If the white screen clears, reactivate plugins one at a time, reloading the site after each one, until the white screen returns — that last plugin is the conflict. If wp-admin is also blank, do this via FTP or File Manager instead: navigate to /wp-content/plugins/ and rename the entire plugins folder (to something like plugins-disabled), which forces WordPress to deactivate all plugins without needing the dashboard.
Once you've isolated the specific plugin, check whether an update is available, since many white-screen plugin conflicts trace back to a plugin or the plugin's dependency falling out of sync with the WordPress or PHP version running underneath it. Update the plugin, or contact its developer if no fix exists yet, before reactivating it on the live site.
Step 3: Switch Themes to Rule Out a Theme Conflict
If plugins weren't the cause, the active theme is the next suspect. From wp-admin's Appearance > Themes, switch to a default WordPress theme temporarily. If you can't reach wp-admin, rename the active theme's folder inside /wp-content/themes/ via FTP or File Manager — WordPress automatically falls back to a default theme when its active theme folder is missing or renamed.
If switching themes clears the white screen, the previous theme has a fatal error somewhere in its code, often introduced by a recent theme update or a customization made directly to a theme file without a child theme. Restoring from a recent backup, or reapplying customizations through a child theme instead of editing the parent theme directly, avoids repeating this.
Step 4: Raise the PHP Memory Limit
If the debug log specifically mentions 'allowed memory size exhausted,' the site is running out of PHP memory rather than hitting a code conflict. Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php, above the line that says 'That's all, stop editing!', to raise WordPress's own memory ceiling. If the error persists, the server's overall PHP memory limit itself may need raising through your hosting panel's PHP configuration settings rather than just WordPress's internal limit.
A memory-related white screen tends to recur under similar conditions — importing a large amount of content, running an image-heavy plugin, or a traffic spike — until the underlying limit is addressed properly, so treat a memory fix as more permanent than a one-time patch. Hosting with generous PHP memory limits by default reduces how often this specific cause shows up in the first place.
A Blank Screen Doesn't Mean a Lost Site
The white screen of death looks catastrophic but is almost always traceable to one plugin, one theme file, or one memory limit — a methodical debug sequence finds it quickly.
Hosting Cheap's cPanel-style panel gives direct File Manager access for renaming plugin or theme folders when wp-admin itself is blank, on NVMe SSD storage that keeps file edits and reloads fast during recovery.
- File Manager and FTP access for recovery when wp-admin is blank
- PHP configuration settings for adjusting memory limits directly
- Daily backups as a fallback if a fix isn't quickly identifiable
- 24/7 human support for a second opinion on a stubborn white screen
Why Hosting Cheap
What you get
File Manager and FTP access
Rename plugin or theme folders directly on the server when wp-admin itself won't load.
PHP configuration control
Adjust the server's PHP memory limit through the hosting panel if WordPress's own setting isn't enough.
NVMe SSD storage
File edits, folder renames and page reloads during recovery stay fast even under pressure.
Daily backups
Restore to a point before the white screen appeared if the cause proves difficult to isolate.
Free managed migration
Move a repeatedly crashing WordPress install to hosting with more generous default PHP limits.
24/7 human support
Get a second opinion reading a debug log or isolating a plugin conflict causing the blank screen.
How It Works
Get set up in a few steps
Enable WP_DEBUG in wp-config.php
Reveal the hidden PHP error instead of a blank page, then check debug.log for specifics.
Deactivate plugins, then switch themes
Isolate whether a plugin or the active theme is causing the fatal error, via dashboard or FTP.
Raise the PHP memory limit if needed
Add WP_MEMORY_LIMIT to wp-config.php, or raise the server's PHP limit through the hosting panel.
Included
Everything you need, on every plan
- WP_DEBUG and WP_DEBUG_LOG enabled to reveal the actual error
- debug.log checked for a specific file, plugin, or memory message
- All plugins deactivated (via dashboard or renamed folder) to test for a conflict
- Plugins reactivated one at a time to isolate the specific conflicting one
- Active theme switched to a default theme to rule out a theme conflict
- WP_MEMORY_LIMIT raised in wp-config.php if memory exhaustion is the cause
- WP_DEBUG turned back off once the cause is fixed
- A recent backup available as a fallback restore point
FAQ
Frequently asked questions
Why is my WordPress site showing a blank white screen with no error?
WordPress suppresses PHP errors from public view by default on most hosting, so a fatal error just renders as a blank page instead of a message. Enabling WP_DEBUG and WP_DEBUG_LOG in wp-config.php reveals the actual error so you know what to fix.
How do I disable WordPress plugins if I can't access wp-admin?
Connect via FTP or your hosting panel's File Manager, navigate to /wp-content/plugins/, and rename the plugins folder to something like plugins-disabled. This forces WordPress to deactivate every plugin without needing dashboard access.
What does 'allowed memory size exhausted' mean in WordPress?
It means a PHP process ran out of the memory it was allowed to use, often triggered by a heavy plugin, large import, or traffic spike. Raising WP_MEMORY_LIMIT in wp-config.php, and if needed the server's own PHP memory limit, usually resolves it.
Can a theme update cause the white screen of death?
Yes, a theme update that introduces a PHP error, or one that conflicts with a customization made directly to theme files, is a common cause. Switching to a default theme temporarily confirms whether the active theme is responsible.
Is the white screen of death the same as a 500 internal server error?
They're related but not identical — a white screen typically means PHP hit a fatal error but display_errors is off, showing nothing at all, while a 500 error is the server's generic response to a range of failures including .htaccess issues. Enabling WP_DEBUG often turns a white screen into a visible, more specific error message.
How do I stop the white screen of death from happening again?
Keep plugins and themes updated, avoid editing parent theme files directly (use a child theme instead), and set a reasonable PHP memory limit for your site's actual needs. Regular backups mean even a repeat occurrence is a quick restore rather than a rebuild.
Ready for Hosting That Makes Recovery Easier?
Get managed WordPress hosting with File Manager access and 24/7 support, from $4.19/mo.
Get Started