Skip to content
webfixed

Guides / WordPress

WordPress white screen after an update

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1.

Short answer

Since WordPress 5.2, most PHP crashes show a critical error message or put the site in recovery mode, so a blank white page is less common. When it still happens after an update, clear every cache, rename the plugins folder to switch plugins off, check the error log for memory errors, and make sure a default theme is installed.

Symptoms

  • The site, or only the dashboard, shows a completely blank white page with no error message.
  • It started straight after a plugin, theme or WordPress update.
  • No email with the subject "Your Site is Experiencing a Technical Issue" has arrived at the site’s administration email address.
  • The page is blank for visitors but loads when you are logged in, or the other way round.
  • Heavier pages, such as page builder or WooCommerce screens, go blank while simpler pages still load.

Causes, most likely first

  1. A cache serving a broken copy

    If a page was cached while an update was installing, or during a brief fault, visitors keep getting the blank copy after the fault has gone. Caching plugins often skip logged-in users, which is why the site can look fine to you.

  2. An error after the page had started loading

    WordPress shows its critical error message only if it has not yet started sending the page. When a plugin crashes partway through a page on a live site, where PHP errors are hidden from visitors, the result is a blank or half-drawn page.

  3. PHP memory running out

    Large plugins, page builders and WooCommerce can need more memory than the site is allowed. The error log then shows a line containing "Allowed memory size of".

  4. A broken theme with nothing to fall back to

    If an update leaves the active theme broken or missing, visitors get a blank page. WordPress can only switch to a default theme if one is still installed.

  5. A fault outside WordPress’s protection

    WordPress starts its error protection after it has read wp-config.php, so a typing mistake in that file is not caught. The protection is also switched off for up to 10 minutes while updates are being installed.

How to fix it

Clear every cache

Recovery mode, added in WordPress 5.2, catches most PHP crashes and shows "There has been a critical error on this website." instead of a blank page. So when the page is completely white, rule out a cache first. A cache stores ready-made copies of pages, and it can keep serving a copy saved during the update.

  1. Open the site in a private browser window, or on a phone using mobile data, to rule out your own browser cache.
  2. If you can log in, clear the cache in your caching plugin, for example WP Rocket, LiteSpeed Cache or W3 Total Cache. The option is usually in the admin bar at the top of the screen.
  3. Clear the server cache in your hosting control panel if your host provides one.
  4. If you use Cloudflare or another content delivery network, purge its cache as well.

Rule out plugins

  1. If the dashboard works, tick the box at the top to select all plugins, choose Deactivate from the Bulk actions menu and click Apply.Menu: Plugins > Installed Plugins
  2. If the dashboard is blank, open your host’s file manager or connect by SFTP, go to wp-content, and rename the plugins folder to plugins-off. This deactivates every plugin without deleting any settings.
  3. Reload the site. If it appears, a plugin is the cause.
  4. Rename the folder back to plugins. The plugins stay deactivated.
  5. Reactivate them one at a time, reloading the site after each. When the white screen returns, the last plugin you activated is responsible. Rename that plugin’s folder to switch it off again.Menu: Plugins > Installed Plugins

Find the hidden error

On a live site PHP errors are hidden from visitors, which is correct, but it means a blank page gives no clue. The error is still recorded. Most hosting control panels have an Errors or Logs section, and your host’s support team can find the log for you. WordPress can also keep its own log. Download a copy of wp-config.php before editing it, because a typing mistake in this file takes the whole site down.

  1. Open wp-config.php, which sits in the main folder of your site, in the file manager’s editor.
  2. Find the line define( 'WP_DEBUG', false ); and change false to true.
  3. Directly underneath, add define( 'WP_DEBUG_LOG', true ); and define( 'WP_DEBUG_DISPLAY', false );
  4. Save the file and reload the blank page once.
  5. Open debug.log inside wp-content and find the most recent line marked "PHP Fatal error". The folder name in the file path shows which plugin or theme failed.
  6. When you have finished, set WP_DEBUG back to false and delete debug.log, because the log sits in a public folder.

Raise the PHP memory limit

A log line containing "Allowed memory size of" means a page needed more memory than PHP allowed. By default WordPress asks for 40MB on a single site and 64MB on a multisite network, and it can only go as high as your host permits.

  1. Download a copy of wp-config.php from the main folder of your site as a backup.
  2. Open wp-config.php in the file manager’s editor.
  3. Above the line that says "That's all, stop editing!", add: define( 'WP_MEMORY_LIMIT', '256M' );
  4. Save the file and reload the site.
  5. If the dashboard works, open the Info tab to check the result. WP_MEMORY_LIMIT is listed under WordPress Constants, and PHP memory limit under Server.Menu: Tools > Site Health

If the limit does not change, your host has fixed it. Ask them to raise memory_limit, or use the PHP settings page in your control panel if there is one. If a site keeps needing more memory, one plugin is often at fault, and the log will name it.

Rule out the theme

  1. With dashboard access, activate a default theme such as Twenty Twenty-Five, the default theme in WordPress 7.1.Menu: Appearance > Themes
  2. Without access, rename your active theme’s folder in wp-content, then themes. Visitors see a blank page until an administrator logs in and opens Appearance, then Themes.
  3. That screen shows "The active theme is broken. Reverting to the default theme." and switches to a default theme, as long as one is installed.
  4. If no default theme is installed, download Twenty Twenty-Five from wordpress.org, unzip it and upload the twentytwentyfive folder into wp-content, then themes. Then open Appearance, then Themes again.
  5. If the site works with the default theme, the fault is in your theme. Restore the previous version of the theme from a backup, or ask its developer for a fixed release.

Switching theme can move menus and widgets on some sites. Take a backup first if your host’s tools still work, and switch back as soon as you have your answer.

If that didn’t work

  1. A mistake in wp-config.php

    If wp-config.php was edited around the time of the update, compare it with a backup copy. A missing quote mark or semicolon stops the site before WordPress can show any message.

  2. A lower memory ceiling at your host

    Your host sets the real ceiling, so the WP_MEMORY_LIMIT line has no effect if the hosting plan allows less. Your host’s support can tell you what your plan allows.

  3. A fault only a backup can undo

    If nothing so far has worked, restore your host’s most recent backup from before the update, bearing in mind that a full restore loses any orders or entries received since.

When to get help

Ask for help if the screen is still blank with all plugins off and a default theme active, if the error log points to WordPress core files, the database or the server itself, or if you are not comfortable editing wp-config.php. A shop that is offline during trading hours is also a good reason not to spend long experimenting.

What a developer would check

  • The PHP error log for the fatal error and the file it names.
  • Memory use against the limit the hosting plan allows.
  • Whether the update finished, or left plugin, theme or core files half replaced.
  • Caching layers that may still hold a blank copy of the page.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Is the white screen the same as the critical error message?
They come from the same kind of fault, a PHP fatal error. Since WordPress 5.2 most of these are caught and shown as the critical error message. A blank page is what is left when the message cannot be shown, for example because the page had already started loading, or a cache kept a broken copy.
Does WordPress undo a plugin update that breaks the site?
For automatic plugin updates, yes. Since WordPress 6.6, after a plugin updates itself WordPress checks the home page for a PHP fatal error. If it finds one, it puts the previous version of the plugin back and emails the site’s administration email address.
Will I lose my website content?
No. The content lives in the database and the uploads folder, which these steps do not touch. Renaming plugin and theme folders is reversible and leaves their settings in place.

Written by Michael Broadbridge, Founder of Webgro. First published 21 September 2026. Last checked 14 November 2026 on WordPress 7.1.