Few things are more alarming than opening your WordPress site and seeing a blank white page or the message “There has been a critical error on this website.” This problem, often called the White Screen of Death (WSoD), usually happens because of a PHP error caused by a plugin, theme, memory limit or recent change. The good news is that it is usually fixable without losing content.
This guide walks you through a calm, step-by-step troubleshooting process.
Common Causes
| — | — |
|---|---|
| Failed update | Interrupted core, plugin or theme update |
| Code edits | Mistake in functions.php or custom code |
Step 1: Check if the Problem Affects Everything
Visit both the front end and /wp-admin. If only certain pages show errors, the cause may be a specific plugin feature or template. If the entire site and admin are blank, a fatal error is likely.
Step 2: Use Recovery Mode
When WordPress detects a fatal error, it often emails the site administrator a special recovery mode link. Recovery mode lets you log in and deactivate the problematic plugin or theme. Check the admin email inbox and spam folder.
Step 3: Deactivate Plugins
From the dashboard
If you can access wp-admin, deactivate all plugins and reactivate them one by one to find the culprit.
Without dashboard access
- Open your hosting file manager or connect via FTP
- Go to wp-content
- Rename the “plugins” folder to “plugins-disabled”
- Check if the site loads
- Rename it back, then rename individual plugin folders one at a time to identify the problem plugin
Step 4: Switch to a Default Theme
If deactivating plugins does not help, the theme may be the issue. Rename your active theme’s folder in wp-content/themes. WordPress will fall back to a default theme if one is installed.
Step 5: Increase PHP Memory Limit
Memory exhaustion can cause blank screens. You can increase the WordPress memory limit by adding a line to wp-config.php or ask your host to raise the PHP memory limit.
Step 6: Enable Debugging
Turn on WordPress debugging in wp-config.php to log errors to a debug.log file inside wp-content. The log usually names the file and line causing the error, pointing directly to the plugin or theme responsible. Disable debugging and delete the log after fixing the problem, as logs can expose sensitive information.
Step 7: Check PHP Version
If the error appeared after your host upgraded PHP, an old plugin or theme may be incompatible. Temporarily switching PHP versions through the hosting panel can confirm this, but the long-term fix is updating or replacing incompatible code.
Step 8: Fix Recent Code Changes
If you edited functions.php or added a code snippet, undo the change through the file manager. A missing semicolon or bracket can break the entire site.
Step 9: Clear Caches
Sometimes the site works but cached error pages remain. Clear plugin, server and CDN caches.
Step 10: Restore a Backup
If troubleshooting fails, restore a recent backup from your host or backup plugin. Then apply updates carefully to find the cause.
Troubleshooting Summary
| — | — |
|---|---|
| “Allowed memory size exhausted” | Increase memory limit |
| Error after editing functions.php | Undo the code change |
Preventing Future Errors
- Take regular backups
- Test updates on a staging site
- Keep plugins and themes updated and compatible
- Avoid editing theme files directly; use child themes or snippet plugins
- Remove abandoned plugins
- Monitor uptime and error logs
Real-World Example
After an automatic plugin update, a blog displayed “There has been a critical error on this website.” The owner found a recovery mode email, logged in and saw that a gallery plugin had caused the error. She deactivated it, the site returned immediately and she replaced the plugin with a maintained alternative after testing on staging.
Frequently Asked Questions
Will I lose my content?
Usually not. Posts and pages are stored in the database, which remains intact in most WSoD cases.
What if only one page is blank?
A specific plugin, shortcode or template on that page may be causing the problem.
Is it safe to rename plugin folders?
Yes. It simply deactivates the plugin. Rename it back after troubleshooting.
How do I find the debug log?
After enabling logging, look for debug.log in the wp-content folder.
Should I contact my host?
Yes, if you cannot access files or the issue relates to server settings, memory or PHP versions.
Can caching cause a white screen?
Rarely, but stale cached error pages can make the problem appear to persist.
Conclusion
The WordPress white screen of death is frightening but usually fixable. Use recovery mode, deactivate plugins, switch themes, increase memory, read debug logs and undo recent changes. Keep backups and test updates on staging to prevent future surprises.
