You open your WordPress site and see… nothing. A blank white page, no error, no menu, sometimes not even the admin dashboard. Or newer WordPress versions show a short message: “There has been a critical error on this website.” This is the famous White Screen of Death (WSoD).
It looks scary, but your content is almost never lost. The white screen simply means PHP, the code WordPress runs on, hit an error and stopped before it could show the page. In most cases, the fix takes 10 to 20 minutes.
What usually causes it
- A plugin, often one you just installed or updated (the most common cause).
- Your theme, especially after an update or a code edit.
- A memory limit: the site needs more PHP memory than your host allows.
- A PHP version mismatch: an old plugin or theme that breaks on a newer PHP version, or the reverse.
- A failed or interrupted update.
- A small typo in a file you or a developer edited, like functions.php.
Before you start
- Check whether it’s the whole site or just one page. Open the homepage, a post and /wp-admin/. If only one page is blank, the problem is in that page’s content or a block, not the whole site.
- Clear your cache. Try a private browser window, and clear your caching plugin or host cache if you can reach it. Sometimes you’re looking at an old cached error.
- Take a backup if you can. Your host’s backup tool works even when WordPress doesn’t. See how to back up and restore a WordPress site.
- Know how to reach your files. You’ll need your hosting dashboard’s File Manager (or an FTP app like FileZilla) for the steps below.
Step 1: Check your email for WordPress recovery mode
Since version 5.2, WordPress catches most fatal errors and emails the site’s admin address with the subject “Your Site is Experiencing a Technical Issue”. The email names the plugin or theme that caused the error and includes a special recovery mode link.
- Check the admin email inbox, including spam.
- Click the recovery mode link and log in.
- WordPress shows you which plugin or theme failed. Deactivate it, then exit recovery mode.
- Reload your site. If it works, update that plugin, replace it, or contact its developer.
No email? Move on to Step 2.
Step 2: Turn off all plugins
Because plugins cause most white screens, test them first.
If you can reach wp-admin: go to Plugins, select all, choose Deactivate, then reload the site. If it works, turn the plugins back on one at a time, reloading each time, until the white screen returns. The last one you activated is the culprit.
If you can’t reach wp-admin:
- Open your host’s File Manager and go to public_html → wp-content.
- Rename the plugins folder to plugins-off. WordPress can no longer find any plugins, so it deactivates them all.
- Reload your site. If it works, a plugin was the problem.
- Rename the folder back to plugins. Then rename each plugin’s folder inside it, one at a time, until you find the one that breaks the site. Delete or replace that plugin.
Step 3: Switch to a default theme
If disabling plugins didn’t help, test your theme.
If you can reach wp-admin: go to Appearance → Themes and activate a default WordPress theme such as Twenty Twenty-Five.
If you can’t reach wp-admin:
- In File Manager, go to wp-content → themes.
- Rename your active theme’s folder, for example yourtheme to yourtheme-off.
- WordPress falls back to a default theme, if one is installed. If none is, upload a fresh copy of a default theme from wordpress.org into this folder first.
- Reload your site. If it works, the problem is in your theme. Undo any recent code edits, reinstall the theme from a clean copy, or contact its developer.
Using a custom-built theme? Keep the last working version as a zip file, so you can reinstall it in a minute if an edit goes wrong.
Step 4: Turn on debugging to see the real error
If you still don’t know the cause, ask WordPress to write the error to a log file.
- In File Manager, open wp-config.php in your site’s main folder, and download a copy first as a backup.
- Find the line define( ‘WP_DEBUG’, false ); and replace it with:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );
- Save the file and reload your site once.
- Open wp-content → debug.log. Look at the last lines for a “PHP Fatal error”. It names the exact file and line, for example /wp-content/plugins/some-plugin/file.php on line 120, which tells you which plugin or theme to fix.
- When you’re done, set WP_DEBUG back to false and delete debug.log. Leaving debugging on can expose information about your site.
Step 5: Raise the memory limit or check the PHP version
If the log mentions “Allowed memory size exhausted”, your site ran out of PHP memory.
- Add this line to wp-config.php, just above the line that says “That’s all, stop editing!”:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
- If that doesn’t work, your host’s limit is lower. Raise memory_limit in the host’s PHP settings (often under Select PHP Version → Options in cPanel), or ask support.
If the log mentions deprecated or undefined function errors after a PHP upgrade, an old plugin or theme isn’t compatible. Temporarily switch back to the previous PHP version in your hosting dashboard, then update or replace the plugin before upgrading PHP again. Most current plugins support PHP 8.x.
Other quick fixes
| Symptom | Likely cause | Fix |
| White screen right after an update | Interrupted update left a .maintenance file | Delete the .maintenance file from the main WordPress folder |
| Only wp-admin is blank | A plugin or theme loads badly in the dashboard | Follow Steps 2–3 using File Manager |
| Only one page or post is blank | A broken block, shortcode or very long content | Edit the page, remove recent blocks, or restore an earlier revision |
| White screen after editing functions.php | A typo in the code | Re-upload the original file or undo your edit via File Manager |
| Nothing helps | Damaged files or a deeper server problem | Restore your latest backup, or ask your host’s support to check the error logs |
If your site shows “Error establishing a database connection” instead of a white screen, that’s a different problem, related to your database details or server, not plugins or themes.
How to prevent it next time
- Back up before every update. A backup turns a white screen into a five-minute restore. Use automatic daily backups from your host or a plugin.
- Update one plugin at a time, and check the site after each. If something breaks, you’ll know exactly what caused it.
- Delete plugins you don’t use. Fewer plugins means fewer conflicts and a faster site. See how to speed up a slow WordPress site.
- Never edit theme files live. Use a child theme, or test changes on a staging site first. Many hosts offer one-click staging.
- Keep PHP current, carefully. Before switching PHP versions, check that your plugins and theme support the new one.
- Choose a host with good support. When nothing else works, a host that can read the server error logs for you saves hours. Compare options in our guide to the best web hosting for small business websites.
From my own experience ★
I’ve faced the white screen myself while building this site. The first time, the problem was the theme. Reinstalling a clean copy of the theme brought the site straight back, which is why I now always keep the last working version saved before I upload any change.
The second time was messier. Before settling on a design, I tried many different themes one after another, and the leftover settings and files from all of them started causing error after error. Instead of chasing each problem, I reset the site to a clean WordPress install and moved to a new custom theme. It felt drastic at the time, but it was the right call: the site has been stable ever since.
My lesson: if one theme or plugin breaks your site, fix that one thing using the steps above. But if you’ve installed and removed so many themes and plugins that you can’t tell what’s causing what, a clean start with one well-built theme can save you days.
Related guides: WordPress Troubleshooting: How to Fix the Most Common Errors · How to Fix the “500 Internal Server Error” in WordPress
FAQ
What is the WordPress White Screen of Death?
It’s a blank white page, or the message “There has been a critical error on this website”, shown when PHP hits a fatal error and stops loading the page. It’s usually caused by a plugin, a theme, a memory limit or a PHP version problem.
Will I lose my content?
Almost never. Your posts and pages are stored in the database, which is untouched by a white screen. Once you fix the plugin, theme or setting, everything reappears.
Can I fix it without access to wp-admin?
Yes. Use your host’s File Manager or FTP to rename the plugins or theme folder, and edit wp-config.php to turn on debugging or raise the memory limit. You don’t need the dashboard for any of the five steps.
Why is only my admin dashboard white?
Usually a plugin that loads only in the dashboard is failing, or the admin area needs more memory than the front end. Rename the plugins folder (Step 2) and raise the memory limit (Step 5).
When should I ask my host for help?
If none of the steps work, you can’t access File Manager, or the debug log shows server errors you don’t understand. Hosts can see server-level error logs that you can’t, and many will fix the problem for free.
Final word
The WordPress White Screen of Death almost always has a simple cause. Work through the five steps in order: check the recovery mode email, turn off plugins, switch to a default theme, read the debug log, and raise the memory limit or check the PHP version. Most sites are back within 20 minutes.
Then protect yourself for next time: back up before updates, update one plugin at a time, and keep a clean copy of your theme ready to reinstall.


