WordPress guide
How to Fix the WordPress White Screen of Death
Quick answer: a WordPress white screen is almost always a hidden PHP error or a memory problem. Clear every cache first, then turn on the debug log to see the error. If you cannot reach the dashboard, rename the wp-content/plugins folder over FTP or your host's File Manager to disable all plugins, switch to a default theme, and raise the PHP memory limit. Then re-enable plugins one at a time to find the cause.
The "white screen of death" is exactly what it sounds like: you open your site and get a blank white page. No error, no menu, nothing to click. Because WordPress hides PHP errors from visitors by default, the page simply stops. Here is how to find out why and get the site back.
Why WordPress Shows a White Screen
- A PHP error in a plugin, theme or custom code, often right after an update.
- Not enough PHP memory for a heavy page, common with page builders and WooCommerce.
- A cached blank page that keeps being served after the real problem is gone.
- A failed update that left WordPress core, a plugin or a theme half installed.
- Wrong file permissions after a migration or a server change.
Newer WordPress versions usually show "There has been a critical error on this website" instead of a blank page. If that is what you see, follow the WordPress critical error guide. The steps below cover the white screen.
First, Check Where the White Screen Appears
- The whole site and the admin: most likely a plugin, the theme or memory. Start with step 3.
- Only the front end, the admin works: usually the theme or a front-end plugin, or a cached page.
- Only some pages: a page builder layout, a shortcode or a widget on those pages.
- Only the Elementor or block editor: usually memory or a plugin conflict in the editor. See the Elementor expert page if it is an Elementor site.
How to Fix the White Screen, Step by Step
-
Clear every cache
Clear your caching plugin (LiteSpeed Cache, WP Rocket, W3 Total Cache and so on), your host's cache, any CDN such as Cloudflare, and your browser. Then test in a private window. If the site comes back, a blank page was cached while something was briefly broken.
-
Look for the recovery mode email
Check the admin email inbox, including spam, for "Your Site is Experiencing a Technical Issue". Its recovery mode link lets you log in and deactivate the plugin or theme that caused the problem.
-
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 white page and open
wp-content/debug.log. The line starting withPHP Fatal errortells you which file failed, and the folder in its path names the plugin or theme. Remove these lines when you are done. -
Disable all plugins without the dashboard
In your hosting File Manager or FTP, rename
wp-content/pluginstoplugins-off. If the site loads, a plugin was the cause. Rename the folder back toplugins; WordPress will show them as deactivated. Reactivate them one at a time and reload the site after each one until the white screen returns. -
Switch to a default theme
Rename your active theme's folder in
wp-content/themes. WordPress switches to an installed default theme such as Twenty Twenty-Five. If the site works with the default theme, the problem is in your theme or child theme, often a recent edit tofunctions.php. -
Raise the PHP memory limit
If the log mentions
Allowed memory size ... exhausted, add this towp-config.php:define( 'WP_MEMORY_LIMIT', '256M' );If your host limits memory at the server, increase
memory_limitin the hosting panel or ask support to raise it. -
Clear a stuck update
If an update was interrupted, look for a file named
.maintenancein the main WordPress folder and delete it. Then reinstall WordPress core from Dashboard → Updates → "Re-install version", or upload freshwp-adminandwp-includesfolders from wordpress.org. This does not touch your content orwp-content. -
Check file permissions
After a migration, wrong permissions can stop PHP from reading files. The usual settings are 755 for folders and 644 for files, with
wp-config.phpoften stricter. Your host can reset them for you. -
Read the server error log, or restore a backup
Your hosting panel has an error log that catches problems WordPress cannot log itself. If you still cannot find the cause, restore the latest backup from before the white screen appeared.
Safety first: before renaming folders or editing wp-config.php, download a copy so you can undo any change in seconds.
How to Prevent the White Screen of Death
- Update plugins, themes and PHP on a staging copy first, and keep daily backups.
- Remove unused plugins and keep the ones you need up to date.
- Choose hosting with enough PHP memory for your theme, builder and store.
- Let a WordPress maintenance plan handle updates, backups and monitoring for you.
Still Looking at a Blank Page?
Send me the problem and I will fix it for you for $25 per bug, tested before I hand the site back. Bigger issues get a clear quote first.
White Screen of Death FAQs
What is the WordPress white screen of death?
A blank white page with no error message, shown instead of your website or the WordPress admin. It usually means a PHP error or a memory problem stopped the page from loading, and error messages are hidden from visitors.
Is the white screen of death the same as the critical error?
They usually have the same causes. Since WordPress 5.2, most fatal errors show "There has been a critical error on this website" instead of a blank page, but a white screen can still appear, for example when a cached blank page is served or the error happens before WordPress can show its message.
Can my hosting cause the white screen of death?
Yes. A low PHP memory limit, an outdated or newly changed PHP version, wrong file permissions or a server that is out of resources can all produce a white screen. Your hosting error log usually shows which one it is.
Related guides: how to fix the WordPress critical error and WooCommerce checkout not working.