The WordPress white screen of death is almost always a PHP fatal error that is hidden from view. To fix it, check your admin email for the Recovery Mode link, turn on the debug log to see the real error, then disable the plugin or theme it names. If the log mentions memory, raise the PHP memory limit to 256M.
- A blank white page means PHP stopped before it could print anything. Your content is still safe in the database.
- Newer WordPress versions show “There has been a critical error” instead of a blank page. It is the same problem.
- The debug log turns a mystery into one clear line naming the file and plugin at fault.
- Clear every cache (plugin, server and CDN) after the fix or you may keep seeing the white page.
What is the WordPress white screen of death?
Imagine a wedding photographer who edits a single line in her theme’s functions.php to add a tracking code. She clicks Update File and the whole site, dashboard included, turns plain white. No message, no menu, nothing to click.
That blank page appears when PHP hits a fatal error and error display is turned off, which is the correct setting for a live site. WordPress cannot finish building the page, so the browser receives nothing. Since WordPress 5.2 most sites show a “critical error” message instead, but on some setups you still get pure white.
What causes a white screen in WordPress?
- A plugin conflict or a broken plugin update. The most common cause by far.
- Theme code errors, often a typo in functions.php or a theme update that needs a newer PHP version.
- PHP memory exhausted. Page builders and WooCommerce on cheap hosting can run out of memory.
- Incompatible PHP version after the host upgrades PHP or you switch it in the panel.
- Failed auto-update that left WordPress core files half replaced.
- Corrupted cache serving an empty page even after the real problem is fixed.
How do you fix the white screen of death step by step?
- Check the admin email. Look for a message titled “Your Site is Experiencing a Technical Issue”. It names the plugin or theme and includes a Recovery Mode login link. Log in, then deactivate or update the named item.
- Turn on the debug log. Edit wp-config.php through your host’s File Manager and set
define('WP_DEBUG', true);,define('WP_DEBUG_LOG', true);anddefine('WP_DEBUG_DISPLAY', false);. Reload the white page and open wp-content/debug.log. The last “PHP Fatal error” line shows the file path, and the folder name in that path is the culprit. - Disable plugins without the dashboard. Rename wp-content/plugins to plugins-off. If the site returns, rename it back and disable plugins one by one.
- Switch the theme. Rename the active theme folder in wp-content/themes. WordPress falls back to a default theme if one is installed.
- Raise memory. Add
define('WP_MEMORY_LIMIT', '256M');above the line that says “That’s all, stop editing!”. - Clear caches. Purge your caching plugin, the host’s server cache and any CDN such as Cloudflare.
- Reinstall core if needed. If debug.log points to wp-admin or wp-includes, upload fresh copies of those two folders from wordpress.org. Never overwrite wp-content.
Share the error or a screenshot and get a free diagnosis. Most WordPress errors are fixed the same day, with a backup taken first.
What if only the dashboard or only one page is white?
A white wp-admin with a working front end usually means an admin-only plugin (a page builder add-on, an SEO plugin or a backup plugin) is failing. A single white post often means a shortcode or block from a removed plugin, or a very long page hitting the memory limit. The debug log still tells you which one.
How do you prevent the white screen from happening again?
- Never edit theme files from Appearance, Theme File Editor on a live site. Use a child theme or a code snippets plugin with error protection.
- Update plugins in small batches and keep a backup from the same day.
- Test PHP version changes on a staging copy first.
- Keep your hosting PHP memory at 256M or more for page builders and WooCommerce.
- Remove plugins you do not use.
If your error is different, the guide to common WordPress errors and fixes covers 500 errors, database errors and redirect loops.
Frequently asked questions
Is the white screen of death the same as the critical error message?
Yes. Both come from a PHP fatal error. Newer WordPress versions show a critical error message instead of a blank page, and email the admin a Recovery Mode link.
Did I lose my posts?
No. Posts, pages and settings live in the database, which a white screen does not delete. Back up before you start fixing anyway.
Why is my site still white after I fixed the plugin?
A cache is still serving the old blank page. Purge the caching plugin, the server cache and any CDN, then reload in a private window.
Can a hack cause the white screen?
Sometimes. If the debug log points to unknown files or the site redirects to spam, treat it as a hacked site and clean it properly.
How long does it take to fix?
With the debug log on, most white screens are fixed in 10 to 30 minutes. Database or core file damage can take longer.
Sources
Share the error or a screenshot and get a free diagnosis. Most WordPress errors are fixed the same day, with a backup taken first.
More WordPress guides
Rather have an expert run your WordPress site?
Tanvir H is a Bangladesh-based WordPress and Elementor web designer with 7+ years of experience, 650+ projects and a 4.9 client rating. New websites, redesigns, fixes, speed, security and SEO, handled by one expert who explains everything in plain English and works with clients worldwide.
