WordPress White Screen After a Plugin Update: How to Fix It in 10 Minutes (and When Not To)

Claude Craft September 15, 2026 0 comments

So your site is a blank white page, wp-admin is a blank white page too, and the last thing you did was click Update on a plugin. I’m going to assume that’s you, because that’s who searches for this. You did not break anything permanent, and this is roughly a ten-minute job if you have hosting-panel or FTP access (or can get it from whoever set the site up).

Make sure it’s actually the plugin

It usually is. But “usually” has cost people an afternoon, so spend two minutes checking.

Look in the site admin’s inbox for an email from WordPress with a subject like “Your Site is Experiencing a Technical Issue.” WordPress has sent these since version 5.2 (that’s 2019, so unless your site is a museum piece, you have it). The email names the plugin that failed and includes a special login link. If it names the plugin you just updated, you’re done diagnosing. Skip to the fix.

No email? Check spam, then check the hosting error log. cPanel calls it “Errors”; on Hostinger it’s under the site’s PHP settings; on InMotion it’s a file called error_log sitting in your site root or in wp-admin. You’re looking for a line that starts with PHP Fatal error and contains a path with /wp-content/plugins/ in it. The folder name after that is your culprit.

If the log points at /wp-content/themes/ instead, it’s the theme (same fix, rename the theme folder). If it says “Allowed memory size exhausted,” the update tipped a tight PHP memory limit over the edge, and raising it in wp-config.php fixes that. Those are the other two suspects. This post is about the plugin case, which is by far the most common as far as I can tell from the tickets that reach us.

The fix, three ways, easiest first

Pick the first one you can do. You don’t need all three.

Way 1: the recovery mode link

This is the one WordPress built for exactly this situation, and almost nobody uses it, which I think is because the email goes to whatever address was typed into Settings, General back when the site was built, which was often the developer’s address, or a mailbox that was created for the launch and never opened again, so the link sits there unread while the owner is on a forum reading about FTP.

• Find the “technical issue” email and click the recovery mode link. It’s valid for 24 hours by default, so don’t sit on it.
• Log in as normal. You’ll see a “Recovery Mode Initialized” notice, and the broken plugin will be listed as paused.
• Go to Plugins, deactivate the paused one, then click “Exit Recovery Mode” in the admin bar.

The WordPress.org recovery mode page has screenshots if the admin screen looks unfamiliar.

Way 2: rename the plugin folder

No email, or the link expired. This is what I’d do anyway; it takes a minute and it’s hard to get wrong.

• Open your hosting file manager (cPanel, hPanel, whatever your host calls it) or connect with an FTP client like FileZilla.
• Go to wp-content/plugins/ and find the folder named after the plugin. It’s usually obvious: woocommerce, elementor, wordfence.
• Rename it. Add -off to the end, so elementor becomes elementor-off. Reload the site.

WordPress can’t find the plugin’s main file anymore, so it quietly deactivates it and carries on. Your site is back. Once you’ve sorted the plugin out, rename the folder back and reactivate.

Way 3: WP-CLI

Only if you have SSH access and that sentence made sense to you. If it did:

 

It’s back. Don’t walk away yet.

Clear every cache you have, in this order: the caching plugin (WP Rocket, LiteSpeed Cache, W3 Total Cache), then the hosting cache (most managed hosts have a purge button in the panel), then Cloudflare if the site runs through it. Skip this and you’ll get a call in an hour from someone still seeing the white page while you’re looking at a working site. Been there.

Then click three things. The homepage. One inner page that matters, a product page or a services page. The contact form, and actually send it. A site that renders but can’t take an inquiry is still down as far as your business is concerned.

Now the plugin. You have three options, and I’d rank them like this:

1. Roll it back to the version that worked. The WP Rollback plugin does this from the Plugins screen for anything on WordPress.org. For a premium plugin, download the previous version from the vendor’s account area and upload it over FTP.
2. Leave it deactivated and wait. If the update broke you, it broke a few hundred other people too, and there’s often a patch within days.
3. Replace it. If this is the second or third time the same plugin has done this, that’s your answer.

When you shouldn’t do this yourself

This is the part I’d rather write honestly than write well. Everything above assumes a simple case: one plugin, one update, one error. Some white screens aren’t simple, and the DIY route makes them worse.

The last one is a different problem wearing the same symptom. Renaming a plugin folder won’t help, and poking around in the file system while a site is compromised can destroy the evidence someone needs to clean it properly. That’s a security cleanup, not a maintenance job, and it’s the one case where I’d say close the FTP window and pick up the phone.

On the WooCommerce one, I’ll admit I’m more cautious than most Reddit answers. A store that stays white for twenty more minutes while a developer checks the order tables is cheaper than a store that comes back with a broken checkout nobody notices until Monday.

So it doesn’t happen again

Three habits. Nothing clever. Test the update on a staging copy first; most hosts give you one for free now. Take a backup right before you click Update, not the nightly one from twelve hours ago. And update one plugin at a time, so when something breaks you know which one did it. That’s the whole prevention plan.

Quick questions