You clicked the blue “Update” button on a plugin, the spinner went for a few seconds, and then your entire site went white. No error code, no rollback option, just a blank page on every URL including wp-admin. If a plugin update just killed your WordPress site, this is a 5-step fix path that gets you back online without losing any content.
The trick is to disable the broken plugin from outside WordPress, restore the previous plugin version, and then put your site into a state where you can update safely going forward. You do not need to be a developer. You only need cPanel or FTP access.
Why a plugin update causes WSOD
A plugin update can throw a fatal PHP error for three common reasons. The new version may require a higher PHP version than your host runs. It may use a function from another plugin that you do not have installed. Or the update files may have arrived corrupted, so half the plugin’s PHP files are missing or empty.
Whatever the trigger, WordPress hits the bad code, PHP dies silently, and the page output is empty. Your visitors see white. Your wp-admin is locked behind the same broken plugin so you cannot deactivate it through the normal UI. That is what makes this error feel so trapped, but the way out is straightforward.
Step 1: Identify the plugin you just updated
If you triggered the update yourself, you already know which plugin caused the crash. If WordPress was set to auto-update, check your email. WordPress sends an “Auto-update complete” notification listing every plugin or theme it touched. The most recent email is your suspect. If you have no email logs, check the file modification dates inside /wp-content/plugins/ through your File Manager. The folders updated in the last hour are your candidates.
Step 2: Disable that single plugin via FTP
Log in to your hosting File Manager (or use FileZilla over SFTP) and go to /wp-content/plugins/. Find the folder of the plugin you suspect. Rename it from something like woocommerce to woocommerce-off. WordPress sees the folder is gone, deactivates the plugin automatically, and your site starts loading again. Try wp-admin in a fresh browser tab. The dashboard should appear within seconds.
If it does not, the broken plugin is a different one. Rename the folder back, then repeat with the next-newest folder until the dashboard returns. Within five minutes you will have isolated the offender.
Step 3: Roll back to the previous plugin version
Now that wp-admin works, you need a working version of the broken plugin back. The cleanest tool for this is the free WP Rollback plugin from the WordPress repository. Install it from Plugins → Add New, search “WP Rollback”, and activate. Go to your Plugins screen, find the broken one, and you will see a new “Rollback” link. Pick the version from before the update (usually one number lower) and click Rollback. Your previous working version reinstalls in about 20 seconds.
If the plugin is a premium one not on wordpress.org, log in to the developer’s site, download the previous version zip from your account area, and upload it through Plugins → Add New → Upload Plugin. Most premium plugin vendors keep at least the last 3 versions available.
Step 4: Find out why the new version broke
Before you re-update, you want to know what made the new release crash. Three quick checks:
- PHP version: Open Tools → Site Health → Info → Server. If your PHP is below 7.4, modern plugins increasingly break. Upgrade to 8.1 or 8.2 from your hosting control panel before retrying.
- Plugin changelog: On the plugin’s WordPress.org page, click “Development” then “View changelog”. The new version often lists a “requires PHP X” or “breaking change” note.
- Conflict with another plugin: Read the support forum for the plugin. If many users posted issues in the last 48 hours, the release itself is buggy and a patch is usually within a week.
Step 5: Update safely on a staging copy
Once you know the cause is fixed (PHP upgraded, conflict patched, or new plugin version released), do not update directly on production. Use a staging site. Hostinger, Cloudways, SiteGround, and Kinsta all offer one-click staging on their cheapest WordPress plans. Clone your live site, run the update on staging, click around for 10 minutes, then push to live. This 10-minute habit prevents 99 percent of repeat WSOD events.
What if I cannot access File Manager or FTP?
Some hosts only give you a limited control panel. If you cannot reach plugin folders directly:
- Open a support ticket. Hostinger and Bluehost will rename the plugin folder for you in under 15 minutes.
- Use phpMyAdmin instead. Inside the
wp_optionstable, edit theactive_pluginsrow and remove the broken plugin’s entry from the serialised list. This is fiddly but works. - Restore yesterday’s automatic backup. Most shared hosts in India keep daily backups for 7 days.
How to make sure this never happens again
Three habits keep your site safe from update-driven white screens:
- Turn off plugin auto-updates on production. Manual updates let you control timing and keep a backup right before.
- Run a backup right before any update. UpdraftPlus and BlogVault can take a 30 second backup on demand.
- Update one plugin at a time and reload your site after each one. If something breaks, you immediately know which plugin did it.
FAQ
Will I lose posts or settings if I rename the plugin folder?
No. Renaming only deactivates the plugin. All posts, pages, comments, and plugin settings stay safely in the database. When you reactivate, your settings return as they were.
How do I know which plugin caused the WSOD if I updated several at once?
Rename the entire plugins folder to plugins-off first to confirm a plugin is the cause. Then rename it back and rename each plugin folder one at a time, reloading wp-admin between each. The plugin you rename when the white screen returns is the broken one.
Can I just delete the bad plugin and re-install the same version?
That reinstalls the broken version. Use WP Rollback or upload an older version zip instead. Re-installing the same broken release will only crash your site again.
Is auto-update worth keeping on after this?
Auto-update is fine for security and minor releases. Major version updates and any plugin you depend on heavily (WooCommerce, page builders, membership plugins) should stay manual. The 30 seconds you save is not worth a midnight site crash.
Should I switch to a managed WordPress host after this?
If WSOD keeps happening, yes. Managed hosts like Cloudways, Kinsta, and Hostinger Cloud run automatic compatibility checks and one-click rollbacks. The extra ₹500 to ₹1,000 per month is worth the peace of mind for a business site.
How long should a normal plugin update take?
Most plugin updates finish in 5 to 30 seconds. If an update sits at “Updating” for over 2 minutes, your server may have hung halfway through, leaving corrupt files. That is a common WSOD trigger. Cancel the page, FTP in, and check.
Final word
A plugin update WSOD is one of the most beginner-unfriendly errors in WordPress, but the actual fix is simple once you know the FTP rename trick. Work through these five steps in order, get your site back online today, then enable staging and pre-update backups so the next plugin update is a non-event. If you also want a complete recovery kit, see our main WordPress white screen of death guide for every other cause beyond plugin updates.