WordPress Site Down After Plugin Update: How to Fix It

A plugin update just took your WordPress site down. You are seeing a white screen, a 500 error, or a broken layout — and every minute it stays down costs you visitors, leads, or sales.

Here is exactly how to fix it. In many cases, turning off the plugin that caused it is enough to bring the site back. For a deeper recovery walkthrough when a plugin update broke your site, that guide covers the same sequence in more detail.

Why a Plugin Update Breaks WordPress

When a plugin developer releases an update, the new version may conflict with your current theme, with another plugin, or with your version of WordPress core. WordPress fails to load and shows a blank screen, a 500 error, or a critical error message.

This is a common cause of WordPress downtime, and it is usually not a server problem. It is a compatibility conflict between code, and the fix is straightforward once you know where to look.

Step 1 — Identify the Problem Plugin

If you updated multiple plugins at once and are not sure which one caused the problem, check your WordPress update history first.

In your WordPress admin panel (if you can still access it), go to Plugins and compare each plugin's version number with the one you had before. If you use an activity log plugin, it records which plugins were updated and when.

If you cannot access the admin panel because the site is completely down, check your hosting control panel's file manager — most hosts show recent file modification dates, which will indicate which plugin folder was last changed.

If you updated only one plugin, that is your culprit. Go straight to Step 2.

Step 2 — Deactivate the Problem Plugin

The fastest fix is deactivating the plugin that caused the conflict.

If you can still access your WordPress admin panel, go to Plugins, find the plugin, and click Deactivate. Reload your site. If it loads, you have confirmed the plugin is the cause. Since WordPress 5.2, a fatal error may also trigger an email to the site admin with a recovery mode link that lets you log in and deactivate the plugin.

If you cannot access your admin panel because the site is completely down, deactivate via SFTP or your hosting file manager.

Connect via SFTP and navigate to wp-content/plugins/. Find the folder for the problem plugin — it will be named after the plugin (for example, woocommerce or contact-form-7). Rename the folder by adding -disabled to the end: woocommerce-disabled. WordPress cannot find the plugin and automatically deactivates it on next load.

Reload your site. If it comes back, the plugin is confirmed as the cause.

Step 3 — If You Updated Multiple Plugins at Once

If you updated several plugins at the same time and are not sure which one caused the problem, rename the entire plugins folder.

Via SFTP, navigate to wp-content/ and rename the plugins folder to plugins-disabled. This deactivates every plugin at once. Reload your site — if it loads, a plugin is definitely the cause.

Rename the folder back to plugins. Go to your WordPress admin panel and reactivate plugins one at a time, reloading the site after each one. When the problem returns, you have found the culprit. Rename that plugin's folder with -disabled to keep it deactivated while the rest are active.

Step 4 — Check for a Plugin Update or Rollback

Once you have identified the problem plugin, you have two options.

Check if the plugin developer has released a patch. Go to the plugin's page on wordpress.org and check the changelog for a version released after the one that broke your site. If a patch exists, update to it (via SFTP if the admin panel is still inaccessible, or through the admin panel once the plugin is deactivated and the site is back).

If no patch exists yet, keep the plugin deactivated and check the plugin's support forum on wordpress.org. Other users may already be reporting the same conflict there. Developers often patch widely reported problems quickly, but there is no guaranteed timeframe.

Report the conflict on the support forum yourself — the more reports, the faster the patch.

Step 5 — Restore From Backup if Deactivation Does Not Fix It

If deactivating the plugin does not restore your site, or if the update caused database changes that need rolling back, restore from a recent backup.

Access your backup tool (UpdraftPlus, your hosting panel, or your maintenance provider's backup system) and restore to the most recent backup taken before the update was applied. A files-only restore is faster if the plugin update only changed plugin files and did not touch the database.

After restoration, verify your site is fully functional before making any further changes. With daily off-site backups in place, this step is usually far quicker than rebuilding anything by hand.

The One Change That Prevents This Permanently

Every plugin update carries some risk of breaking your live site. The only way to eliminate that risk is to test updates on a staging environment before they go live.

A staging environment is a private copy of your WordPress site where updates are applied first. If a plugin update causes a conflict on staging, your live site keeps running normally while you resolve it. Your visitors never see an error.

From the WPOPS Perform plan up, risky updates are verified on staging before they reach your live site, so most conflicts are caught before visitors ever see them.

If your site just went down from a plugin update and you want to make sure it never happens again, get in touch via emergency support. WPOPS guarantees a response within 1 hour on every plan. We will get your site back online and set up staged update testing so this does not repeat. Ongoing WordPress maintenance under a care plan is what keeps update risk off your live site.

Frequently Asked Questions

Why did my WordPress site go down after a plugin update?

A plugin update can introduce PHP code that conflicts with your theme, another plugin, or your version of WordPress core. WordPress fails to load and shows a blank screen or 500 error. This is a common cause of WordPress downtime and is usually fixed by deactivating the problem plugin.

How do I fix WordPress after a plugin update broke it?

Deactivate the problem plugin via your WordPress admin panel (Plugins → Deactivate) or via SFTP if the admin panel is inaccessible. In SFTP, navigate to wp-content/plugins/ and rename the problem plugin's folder by adding -disabled to the end. WordPress will automatically deactivate it and your site should load again.

How do I deactivate a WordPress plugin without admin access?

Connect to your hosting account via SFTP or your hosting file manager. Navigate to wp-content/plugins/. Find the folder for the problem plugin and rename it by adding -disabled to the end (for example, rename woocommerce to woocommerce-disabled). WordPress cannot find the folder and deactivates the plugin automatically on the next page load.

My WordPress site is down but I do not know which plugin caused it

If you updated multiple plugins at once, rename the entire wp-content/plugins/ folder to plugins-disabled via SFTP. This deactivates all plugins at once. If the site loads, rename the folder back to plugins and reactivate plugins one at a time through your admin panel until the problem returns — that plugin is the cause.

How do I stop plugin updates from breaking my WordPress site?

Test plugin updates on a staging environment before applying them to your live site. A staging environment is a private copy of your site where updates are applied first. If an update causes a conflict on staging, your live site is unaffected. Staging verification is included from the WPOPS Perform plan ($59/month) up.

How long does it take to fix a WordPress site broken by a plugin update?

Once you find and deactivate the plugin that caused it, the site usually loads again on the next page load. A backup restore takes longer, depending on your site's size and your backup tool, so having a recent off-site backup ready makes a big difference.

By Manny — Founder, WPOPS