You clicked "Update," and now your site is broken. Maybe it's a white screen. Maybe the layout is destroyed. Maybe a critical feature stopped working.

This happens more often than it should. Let's get you fixed up, and then talk about preventing it next time.

First: Identify What You Updated

Before you can roll back, you need to know what caused the problem.

  • Did you click "Update All"? If so, you have multiple suspects
  • Do you remember what was updated? Plugin, theme, or WordPress core?
  • Check your update history: Dashboard → Updates shows recent activity

If you updated multiple things at once, you'll need to do some detective work. This is exactly why we recommend updating one thing at a time—but more on that later.

Rolling Back a Plugin

Plugin updates are the most common cause of post-update problems. Here's how to roll back:

If You Can Access WordPress Admin

  1. Note which plugin version was working (check the changelog or your backups)
  2. Go to the WordPress.org plugin repository and find your plugin
  3. Click "Advanced View" to access previous versions
  4. Download the version that was working
  5. In WordPress: Plugins → Add New → Upload Plugin
  6. Upload the older version
  7. WordPress will ask if you want to replace the current version—say yes

Commercial plugins often provide access to previous versions in your account dashboard.

If You Can't Access WordPress Admin

  1. Connect via FTP/SFTP
  2. Navigate to /wp-content/plugins/
  3. Rename the problem plugin's folder (e.g., problem-plugin to problem-plugin-broken)
  4. Your site should now work (without that plugin)
  5. Upload the previous version to the plugins folder
  6. Activate it through WordPress admin once you can get in

Rolling Back a Theme

Theme rollbacks are trickier because you can't just "deactivate" your theme without consequences.

With FTP Access

  1. Navigate to /wp-content/themes/
  2. Rename your current theme folder (e.g., your-theme to your-theme-broken)
  3. Upload the previous version with the original folder name
  4. The site should load with the older theme version

Important: Child Themes

If you're using a child theme, make sure you're rolling back the right one. Parent theme updates are often the culprit, not child theme changes.

Rolling Back WordPress Core

Core updates rarely cause problems, but when they do, the issues are serious. Rolling back the core is more complicated and generally not recommended.

Better options:

  • Wait for a patch (WordPress releases fixes quickly for major issues)
  • Fix the specific incompatibility (usually a plugin or theme that needs updating)
  • Restore from a full backup

If you must roll back core, you'll need to manually replace WordPress files via FTP with files from the previous version—and this can cause database compatibility issues if the update included database changes.

When Database Rollback Is Required

Here's where things get complicated.

Most plugin updates only change files. Roll back the files, problem solved.

But some plugins—especially membership plugins, e-commerce systems, and complex form builders—make database changes during updates. New tables, new columns, modified data structures.

If you roll back the files but the database has been modified, you might end up with a mismatch: old code trying to work with a new database structure.

This is when you need a full backup restoration, not just file rollback.

This is why we emphasize backups so strongly. You need:

  • Recent backup before the update
  • Ability to restore both files AND the database
  • Ideally, a hosting provider or support partner who can do this quickly

Why This Happened

Let's be honest about what's going on. The WordPress ecosystem—plugins and themes from thousands of different developers—doesn't have perfect compatibility testing.

When you click "Update All" on 12 pending updates, each update was tested by its developer, but none were tested together. Conflicts happen.

The "Update Itch."

We call it the "update itch." WordPress constantly shows pending updates. As soon as you update, you refresh, and there are more. The counter never seems to go down.

For non-technical site owners, this feels like something's wrong. The site needs attention. So they click "Update All" to clean it up—often right before a big campaign, event, or product launch.

And then something breaks at the worst possible time.

How to Prevent This

Update One at a Time

Don't click "Update All." Update plugins individually:

  1. Update one plugin
  2. Check your site (visit key pages, test important features)
  3. If everything works, update the next one
  4. If something breaks, you know exactly which plugin caused it

Yes, this takes longer. But it takes far less time than troubleshooting a broken site when you don't know which of 12 updates caused the problem.

Know Which Updates Are Riskier

Some updates are safer to batch:

  • Plugins from established companies with solid development teams
  • Simple plugins (analytics tracking, admin tools)
  • Plugins that don't affect the front-end

High-risk updates to do carefully:

  • Membership plugins (lots of database tables)
  • E-commerce plugins (WooCommerce, Easy Digital Downloads)
  • Page builders and theme frameworks
  • Major version jumps (1.x to 2.x)

Use a Staging Environment

The real solution is to test updates on a copy of your site before applying to production. Staging environments let you:

  • Apply all updates at once
  • Verify everything works
  • Then push to production with confidence

On FatLab hosting, our SafeUpdates system does this automatically—updates run on a staging copy with automated testing before touching production.

Maintain Current Backups

If you have a backup from right before the update, recovery is simple: just restore. Make sure your backup system creates a snapshot before updates are applied.

When to Call for Help

If you're uncomfortable with FTP, unsure which update caused the problem, or need a database restoration, that's when to bring in professional help.

Rollbacks are usually fast fixes for someone with the right access. What might take you an hour of stressed Googling takes us a few minutes with proper tools and experience.

Update broke your site? Contact our support team for fast rollback and recovery.

This article is part of our WordPress Troubleshooting guide—a complete resource for diagnosing and fixing common WordPress errors.