The WordPress “white screen of death” is a completely blank page where your website should be. It usually means a PHP error stopped WordPress before it could display anything, but error messages are hidden. The most common causes are a faulty plugin or theme, a PHP version change or the site running out of memory. You can usually fix it by finding and switching off whatever broke.
Key takeaways
- A blank white page is usually a hidden PHP error, not lost content.
- Newer WordPress versions often show “There has been a critical error” instead, with a recovery email.
- Start with whatever changed most recently: a plugin, theme or PHP update.
- The debug log tells you exactly which file failed.
- If only the admin area is white, the cause is often a plugin that loads only in the admin area.
What is the WordPress white screen of death?
It’s a nickname for a blank page with no error message. WordPress tried to build the page, hit a fatal error and stopped. Because error messages are switched off on live websites (as they should be), visitors see nothing at all.
Since WordPress 5.2, many fatal errors show “There has been a critical error on this website” instead of a white page. If that’s what you see, follow our guide to the critical error message. A pure white screen still happens when the error occurs before WordPress can catch it, or when the problem is a memory limit.
What causes a white screen?
- Plugin conflicts, often straight after an update.
- Theme errors, including small edits to the theme’s code.
- PHP version changes by your host, which older plugins can’t handle.
- Memory limits, when a page needs more memory than PHP is allowed to use.
- Failed updates, which leave a mix of old and new files.
- Caching, where a cached blank page keeps being served after the fault is fixed.
How do I fix the white screen of death?
Take a backup first if you can, then work through these in order.
1. Check the admin area and the email
Visit /wp-admin. If it loads, go to Plugins and deactivate whatever you updated last. Also check the admin email inbox for a message titled “Your Site is Experiencing a Technical Issue”. It contains a recovery link that lets you log in with the faulty plugin paused.
2. Clear every cache
If you use a caching plugin, a CDN or server caching, clear them all. Then load the site in a private browser window. Sometimes the fault is gone but a blank copy is still being served.
3. Switch off all plugins
If you can’t reach the admin area, use your host’s file manager or SFTP. Rename wp-content/plugins to plugins-off. If the site appears, rename it back, then rename individual plugin folders one by one until the white screen returns. That plugin is the cause.
4. Switch to a default theme
If plugins aren’t the cause, rename your active theme’s folder in wp-content/themes. WordPress falls back to a default theme, such as Twenty Twenty-Five, if one is installed.
5. Turn on the debug log
Add these lines to wp-config.php, above “That’s all, stop editing”:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reload the page, then read wp-content/debug.log. The last error names the file and line that failed. The WordPress debugging guide explains each option. Turn debugging off afterwards.
6. Raise the memory limit
If the log says “Allowed memory size exhausted”, add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php. If that doesn’t work, your hosting plan may cap memory. Ask your host.
What if only some pages are white?
That points to something used only on those pages: a particular form, page builder element, shop page or template. Check the debug log while loading that page. If only the admin area is white, look at plugins that add admin features, such as SEO, security or backup plugins.
If you’re stuck on the login page instead, our guide to fixing WordPress login problems will help. A browser message about “too many redirects” is a different issue again, covered in our ERR_TOO_MANY_REDIRECTS fix.
How do I stop it happening again?
- Back up before every update, with a copy stored off the server.
- Test updates on a staging copy before the live site.
- Update regularly. Small, frequent updates break less than big jumps.
- Remove unused plugins and themes. Patchstack found 91% of new WordPress vulnerabilities in 2025 were in plugins (Patchstack).
- Monitor uptime, so you hear about problems first.
That’s what our website maintenance plans do every month. When something does break, our fast WordPress repairs team fixes it, and our website support line puts you through to a real person in Australia.
Frequently asked questions
Is my website content gone?
Almost certainly not. Your content is stored in the database, which a white screen doesn’t touch. Once the fault is fixed, everything returns.
Why is my WordPress admin a white screen but the site works?
A plugin that only runs in the admin area is the likely cause. Rename plugin folders one at a time to find it.
Can a hack cause the white screen of death?
Yes. Malware can break files when it injects code. If you find unknown admin users or strange files, treat it as a security incident.
Does increasing the memory limit always fix it?
Only if memory is the cause. Check the debug log first. If it mentions memory, raise the limit. Otherwise, look for the failing plugin or theme.
Will my host fix a white screen for me?
Some hosts help, but many treat it as a website problem, not a server problem. A maintenance plan covers this kind of repair.
Sources
- Debugging in WordPress, WordPress Developer Resources
- Fatal Error Recovery Mode in 5.2, Make WordPress Core, April 2019
- Common WordPress errors, WordPress Developer Resources
- State of WordPress Security in 2026, Patchstack