WordPress White Screen After Plugin Update? Fix It Fast
Plugin updates crash your site to a white screen? I'll show you how to fix it in minutes, even if you can't log into wp-admin.
Quick Answer
If you can still access wp-admin, disable the last plugin you updated via Plugins > Installed Plugins. If wp-admin is also white, rename the plugin folder via FTP or cPanel File Manager: /wp-content/plugins/plugin-name-here/ — just add .bak to the folder name, and your site will load. Then delete the plugin and reinstall a clean copy.
Why This Happens
The White Screen of Death (WSOD) after a plugin update is usually a PHP fatal error. WordPress runs the new code, hits a conflict with another plugin, your theme, or the PHP version on your server, and silently dies. No error message, just a blank white page. I've seen this happen most often with caching plugins, SEO plugins, and page builders like Elementor or WPBakery — especially after major version jumps. The server doesn't display errors by default on production sites, so you're left staring at nothing.
Don't worry. In 9 out of 10 cases, disabling the offending plugin brings your site back in under five minutes. Let's do that now.
Step-by-Step Fix
1. Try WordPress Recovery Mode (if you can)
WordPress 5.2+ has a built-in safety net. After a fatal error, you might get an email with a recovery link. Check your inbox (the one tied to the admin account). Click the link, and it'll put your site into recovery mode. From there, you can deactivate the problem plugin. If you didn't get an email, or the link expired, move to step 2.
2. Deactivate the Plugin via FTP or cPanel
This is the surest fix. You'll need FTP credentials (your host can give you these) or cPanel File Manager access. Here's what to do:
- Connect via FTP or open File Manager in cPanel.
- Navigate to
/wp-content/plugins/. - Find the folder for the plugin you just updated. If you're not sure which one, look for the most recently modified folder — sort by date modified.
- Rename the folder by adding
.bakto the end. For example,akismetbecomesakismet.bak. - Refresh your site. It should load normally now.
That's it. WordPress can't load the plugin if its folder name doesn't match, so it skips it entirely. Your site comes back immediately.
3. If That Didn't Work — Check Your PHP Memory Limit
Sometimes the plugin update triggers a memory exhaustion error, not a code conflict. This is more common on cheap shared hosting. Increase the memory limit by editing wp-config.php. Add this line right before the /* That's all, stop editing! */ comment:
define('WP_MEMORY_LIMIT', '256M');
Save and upload the file back. Refresh your site. If it loads, you found the issue. Your host might cap memory limits — contact them if 256M doesn't stick.
Alternative Fixes (If the Main Fix Fails)
Switch to a Default Theme Temporarily
Rarely, the new plugin version conflicts with your theme. Rename your active theme folder (inside /wp-content/themes/) to something like twentytwentyfour.bak. WordPress will fall back to a default theme (Twenty Twenty-Four or similar). If your site loads, the theme is the problem — update it or switch themes permanently.
Enable WP_DEBUG to See the Error
If you're still stuck, turn on debugging to get a real error message (instead of the white screen). Edit wp-config.php and add these lines:
define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', true);
Now load your site. You'll see a PHP error message like Fatal error: Call to undefined function or Parse error: syntax error. Google that exact error plus your plugin's name — you'll find the fix in minutes.
Prevention Tip
Stop updating plugins right before a launch or at 5 PM on a Friday. Instead, test updates on a staging site first. Most hosts offer a one-click staging environment — use it. If staging isn't an option, take a full backup (database + files) before any plugin update. I recommend UpdraftPlus or BackWPup for automatic backups. Then, if the WSOD hits again, you can restore in 60 seconds and try a different approach.
And one more thing — keep your PHP version current. Old PHP (7.0 or below) causes more plugin conflicts than outdated plugins themselves. Update to PHP 8.0 or 8.1 in your hosting control panel. Your site will run faster, and plugin updates will break less often.
Was this solution helpful?