A blank white page after an update usually means a plugin, theme, or core update caused a PHP fatal error, or WordPress got stuck in maintenance mode. Clear your caches, delete any leftover .maintenance file, then turn on debug logging and disable the plugin or theme the log names. Restore a backup if nothing else works.

Many business owners describe the same moment (this is a composite of common cases). A bakery owner clicks “Update all” on a quiet Sunday evening, refreshes her homepage, and sees nothing. No menu, no products, no error, just a white page. She has heard the phrase WordPress white screen of death before, and now she fears her online orders and five years of photos are gone. On her first call with a web team, she apologizes for not knowing what PHP or FTP means. The developer explains that her content sits safely in the database and that one update almost certainly caused the crash. She realizes the problem has a clear order of steps.

What Is the WordPress White Screen of Death?

The WordPress white screen of death is a blank page that appears when PHP stops running before WordPress can draw your site. A fatal error from a plugin, theme, or core file usually causes it, and visitors see no message at all.

A white screen after an update means WordPress crashed while loading, not that it deleted your content. Your posts, pages, and orders stay in the database. Finding and disabling the code that crashed brings the site back.

White Screen vs “There Has Been a Critical Error”

Since WordPress 5.2, the built-in error handler often shows “There has been a critical error on this website” instead of a blank page. Both screens point to the same kind of fatal error. A pure white screen usually appears when the error happens before that handler loads, or when your host or a cache plugin serves an empty page.

Why Updates Trigger It

Here are the most common triggers after an update:

  • A plugin conflict between a freshly updated plugin and another plugin or your theme
  • A plugin or theme that needs a newer PHP version than your server runs
  • An update that stopped halfway and left files incomplete
  • A heavy plugin that needs more PHP memory than your server allows

What Should You Check First?

Check your caches and test the site in a private browser window first, because a cache can keep showing a broken page after the real problem has gone. Then confirm which part of the site actually fails.

Start with these quick checks:

  • Open the site in a private or incognito window.
  • Clear your browser cache. Our guide explains what browser cache is and why clearing it helps.
  • Purge your caching plugin and any CDN cache from your hosting panel.
  • Note which part fails: only the homepage, only wp-admin, or the whole site.

If the site fails to load at all, with a timeout or a hosting error instead of a white page, see our list of fixes for a WordPress site that will not load as well.

How Do You Fix WordPress Stuck in Maintenance Mode?

Delete the .maintenance file in your site’s root folder to fix WordPress stuck in maintenance mode. WordPress creates that file during every update and removes it when the update finishes, so a leftover file means an update stopped early.

The official WordPress common errors guide shows the message visitors see: “Briefly unavailable for scheduled maintenance. Please check back in a minute.” Open your hosting file manager or an FTP client, find the folder that holds wp-config.php, and delete .maintenance. WordPress also ignores the file once it is more than 10 minutes old, so a message that lasts longer than that usually points to a separate problem. After you delete the file, rerun the update that failed from Dashboard, then Updates.

How Do You Find the Cause With WordPress Debug Mode?

WordPress debug mode writes the exact fatal error to a log file, including the file path of the plugin or theme that crashed. Turning it on takes one edit to wp-config.php and removes most of the guesswork.

Add three lines to wp-config.php: set WP_DEBUG to true, WP_DEBUG_LOG to true, and WP_DEBUG_DISPLAY to false. Reload the site, open wp-content/debug.log, and read the last “PHP Fatal error” line. The folder name in that line tells you which plugin or theme to disable.

Add the lines above the “That’s all, stop editing!” comment, and turn them off once you finish.

Also check your admin inbox for an email titled “Your Site is Experiencing a Technical Issue.” That email holds a recovery link that logs you in with the faulty code paused. If the link fails, our guide to fixing Recovery Mode not initialized explains why and what to do next.

How Do You Fix a WordPress Update That Broke Your Site?

Fix a WordPress update that broke your site by disabling the plugin or theme the debug log names. Without a clear log entry, disable all plugins at once and test the theme next.

Work through these fixes in order:

Disable Plugins via FTP or File Manager

Go to wp-content/plugins and rename the faulty plugin’s folder, for example from woocommerce-addon to woocommerce-addon-off. WordPress deactivates any plugin it cannot find. To test every plugin at once, rename the whole plugins folder to plugins-off, reload the site, then rename it back and reactivate plugins one by one from the Plugins screen.

Switch to a Default Theme

If the log names your theme, rename that theme’s folder in wp-content/themes. WordPress then falls back to an installed default theme such as Twenty Twenty-Five, so keep one installed.

Raise the PHP Memory Limit

A log line that says “Allowed memory size exhausted” means a script ran out of memory. Add define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); to wp-config.php. Your host’s server limit still caps this number, so ask support if the error returns.

Fix a 500 Internal Server Error

A 500 internal server error after an update often comes from a corrupted .htaccess file. Rename .htaccess to .htaccess_old, then open Settings, then Permalinks, and click Save Changes to create a fresh file. If the screen instead says “Error establishing a database connection,” follow our guide to repairing the WordPress database connection.

How Do You Roll Back a WordPress Update Safely?

Roll back a WordPress update safely by restoring the previous version of only the plugin or theme that failed, after you take a fresh backup. A full site restore works too, but it also removes any orders, comments, or form entries from after the backup.

Here is how the main options compare:

  • WP Rollback plugin: The free WP Rollback plugin on WordPress.org lets you pick an earlier version of any plugin or theme from the WordPress.org directory. It does not cover premium plugins in its free version.
  • Manual rollback: Upload the older version through FTP in place of the new folder.
  • Host backup: Restore yesterday’s backup from your hosting panel when several parts of the site broke at once.

To stop the next update from breaking things, update one plugin at a time, test changes on a staging site, and keep daily backups. Ongoing website maintenance handles plugin, theme, and core updates for you and fixes errors as they appear.

Conclusion

A white screen after an update looks frightening, but your content stays safe in the database. Start with the fast checks: clear every cache and delete any leftover .maintenance file. Then turn on debug logging, read the last fatal error, and disable or roll back the plugin or theme it names. For the future, update one item at a time and keep a recent backup ready.

If you would like a hand getting your site back online, contact our team and we will walk through it with you in plain language.

Frequently Asked Questions

Does a white screen delete my content?

No. The white screen means PHP stopped before WordPress could display your site. Your posts, pages, products, and orders stay in the database. Once you disable or replace the plugin or theme that crashed, everything appears again. Take a backup before you start fixing anyway.

Why is only my wp-admin dashboard white?

A blank dashboard with a working front end usually means a plugin that loads only in the admin area crashed, often a page builder, an SEO tool, or a security plugin. Turn on debug logging, reload wp-admin, and check wp-content/debug.log for the plugin name. Then rename that plugin’s folder through FTP or your file manager.

How long does WordPress stay in maintenance mode?

WordPress normally stays in maintenance mode for a few seconds while an update runs. WordPress ignores a .maintenance file once it is older than 10 minutes, so a longer outage usually means another problem. Delete the file from your site’s root folder, reload the site, and rerun the update that failed from Dashboard, then Updates.

Should I update all plugins at once?

Updating all plugins at once saves time, but it makes a failure hard to trace because you cannot tell which update caused it. Update one plugin at a time on important sites, check the site after each one, and test major updates on a staging copy first.