A WordPress site down after update recovers in three steps: get back into wp-admin, deactivate the plugin you just updated, then roll that one plugin back to its previous version. Your content is almost certainly fine. Do not restore a backup yet, because that undoes everything since the backup was taken.
Three separate businesses posted this exact emergency on one job board in a single day last week. One had a fatal error on an Elementor update. Another went down the moment a plugin upgrade finished. The third got a warning email from WordPress, then found the site broken when they checked.
It feels catastrophic. In reality the cause is almost always a conflict between the new version and something else on your site, and conflicts are recoverable without a developer.
Work through this in order. The first question decides everything that follows.
Start here: can you still log into wp-admin?
Try yoursite.com/wp-admin right now. The answer splits this into two completely different repairs, and most guides mix them together.
If the dashboard loads, even with warnings, you have the easy version. Skip to the next section.
If you are locked out, check your admin email inbox first. When WordPress hits a fatal error it emails the site administrator a private Recovery Mode link, which looks like yoursite.com/wp-login.php?action=enter_recovery_mode&rm_token=. That link logs you in with the broken plugin paused, so you can deactivate it normally. This has been built into WordPress since version 5.2, and the official Recovery Mode documentation covers how it behaves.
The email often names the exact plugin that caused the crash. That single line saves you the entire diagnosis.
If no email arrived, jump to the locked-out section below.
If you can still log in
Deactivate the plugin you just updated. That is it for the first move, and it fixes most cases immediately.
Go to Plugins, find the one you updated, and deactivate it. Reload your site in a private browsing window so you are not looking at a cached copy. If the site returns, you have your culprit.
If deactivating that plugin changes nothing, deactivate all of them. When the site comes back, reactivate them one at a time, checking the front end after each. The one that breaks it again is your answer. Sometimes the plugin you updated is innocent and it simply stopped tolerating a conflict that already existed, which is why testing them one by one beats guessing. Our guide to fixing a plugin that is not working covers that isolation process in more detail.
Once you know which plugin is responsible, keep it deactivated and move to the rollback section. Do not just leave it off and hope, because most sites need that plugin doing its job.
If you are locked out of wp-admin
Rename the plugins folder. This deactivates every plugin at once and almost always restores access.
Open your host’s file manager or connect over FTP. Open wp-content and rename the folder plugins to plugins_old. WordPress cannot find any plugins, so it deactivates all of them, and your dashboard should load.
Now rename the folder back to plugins. Your plugins stay deactivated because WordPress already recorded them as off, so you can log in and reactivate them one at a time to find the culprit.
To disable a single plugin instead, rename just its own folder inside wp-content/plugins. WordPress deactivates that one plugin and leaves the rest running. That is the safer move when you already suspect which plugin broke things.
Nothing here deletes your content. Plugin settings live in your database and survive all of this.
No recovery email? That tells you something
If WordPress never emailed you, your site probably cannot send mail at all.
That is a separate problem hiding behind this one. WordPress sends through PHP’s mail function by default, which many hosts block, so admin notifications, form notifications and password resets all fail silently. You have possibly been missing those emails for months. Our guide to WordPress emails not sending fixes it properly once the site is back up.
The other possibility is that the error was not fatal enough to trigger Recovery Mode. Either way, use the locked-out method above and deal with mail delivery afterwards.
Why WordPress’s automatic rollback did not save you
This confuses people, and the answer is a real limitation rather than a bug.
WordPress 6.3 added a rollback feature for plugin and theme updates. Reading the headline, most owners assume the site is now protected from bad updates. It is narrower than that. The official core announcement explains that the rollback triggers when the update process itself fails, restoring the previous version so the site stays available.
Your situation is different. The update succeeded, the files installed correctly, and the process reported success. Trouble started once the new version began running, usually by conflicting with another plugin, your theme, or your PHP version.
That gap is exactly where a site down after update lands, and no built-in feature covers it. You have to roll back manually.
How to roll the plugin back properly
Return the plugin to its previous version rather than deleting it. Two routes, depending on your access to the dashboard.
From the dashboard: install the free WP Rollback plugin, then use the Rollback link that appears under any plugin from the WordPress.org directory. Pick the previous version and confirm. It takes two clicks.
By hand: open the plugin’s page on WordPress.org, scroll to Advanced View, and choose the previous version from the Previous Versions dropdown. Download that zip. Deactivate and delete the broken version, then upload the older zip through Plugins, Add New, Upload Plugin. Reactivate it.
Deleting a plugin sounds alarming and is safe here, because the plugin’s settings live in your database rather than in its files. They come back when you reinstall.
Two things to handle afterwards. Turn off auto-updates for that plugin until the developer ships a fix, or you will repeat this next week. And check whether the plugin’s changelog or support forum already mentions the conflict, since a fix is often days away.
Premium plugins are the awkward case, because they are not in the WordPress.org directory and WP Rollback cannot reach them. Log into the vendor’s account area, download the previous release, and install it the manual way above.
Before you restore a backup, read this
Restoring a backup is the option every guide offers first, and on a business site it is often the most expensive one.
A restore returns your entire site to how it looked when the backup ran. That means you also lose everything that happened since: new orders, form submissions, comments, posts, customer accounts, inventory changes. On a WooCommerce store backed up nightly, restoring at 4pm can erase a day of orders you have not fulfilled and cannot recover.
So treat a restore as the last resort, not the first. Try Recovery Mode, then deactivation, then a plugin rollback. Those three fix the large majority of post-update failures and none of them touch your data.
If you do have to restore, export anything new first where you can. Orders, form entries and recent posts can often be exported from the dashboard before you roll back. Our WordPress backup guide covers keeping restore points frequent enough that this decision stops being painful.
Stuck on “briefly unavailable for scheduled maintenance”
Delete the .maintenance file in your site’s root folder. WordPress creates it during an update and removes it afterwards, so a stuck message means the update was interrupted before it finished.
Use your file manager or FTP, find .maintenance in the same folder as wp-config.php, and delete it. The site returns immediately.
If the site then shows a different error, that is progress. Match the symptom to the right guide: a blank page is the white screen of death, a server error is a 500 internal server error, and our roundup of common WordPress errors covers the rest.
How to stop this happening again
Update on a copy of your site, not on the live one. That single habit removes almost all of this risk, and everything else on this list supports it.
- Test updates on a staging site before they touch production, especially for stores and booking sites
- Update in small batches rather than clicking Update All, so a break identifies itself immediately
- Take a backup before you update, not after something goes wrong
- Turn off auto-updates for plugins that touch checkout, payments or forms, and leave them on for security-focused plugins
- Delete plugins you do not use, since every one is another update that can conflict
- Avoid updating on a Friday afternoon, which is not a technical rule but has saved more weekends than any technical rule
The honest tradeoff is that testing takes time, and updating straight to live is faster on the days nothing breaks. The value of that trade depends on what an hour of downtime costs you. For a store, it rarely is.
Key takeaways
A WordPress site down after update is usually a conflict rather than a corrupted site, and your content is almost always intact. Answer the first question before anything else: can you reach wp-admin, or are you locked out? Those are two different repairs.
If you are locked out, check your admin email for a Recovery Mode link, and rename the plugins folder if the email never came. If you can log in, deactivate the plugin you updated, then reactivate one at a time if that is not enough.
Roll the guilty plugin back to its previous version rather than leaving it off. And keep a backup restore as the last resort, because it erases every order and form entry recorded since the backup ran.
Frequently asked questions
Why did my site go down right after a plugin update?
Almost always a conflict. The new version expects something your theme, another plugin, or your PHP version no longer provides, and the mismatch throws a fatal error. Less often, the update was interrupted and left corrupted files. Both are recoverable, and neither one damages your posts, pages or settings.
How do I fix a WordPress site if I am locked out of wp-admin?
Rename the plugins folder inside wp-content using your host’s file manager or FTP. WordPress deactivates every plugin, which normally restores dashboard access. Rename the folder back afterwards, then reactivate plugins one at a time to find the culprit. Nothing is deleted and settings stay in your database.
Can I roll back a plugin to the previous version?
Yes. The free WP Rollback plugin does it in two clicks for anything from the WordPress.org directory. Manually, download the previous version from the plugin’s page under Advanced View, delete the broken version, then upload the older zip. Premium plugins need the previous release from the vendor’s account area.
Should I restore a backup after a bad update?
Only as a last resort. A restore returns the whole site to the backup point, so you lose orders, form entries, comments and posts recorded since then. Try Recovery Mode, plugin deactivation and a rollback first, since those fix most cases without touching your data.
Why did I not get a recovery mode email from WordPress?
Usually because your site cannot send email. WordPress uses PHP’s mail function by default and many hosts block it, so admin notifications never arrive. The other possibility is that the error was not fatal enough to trigger Recovery Mode. Use the file manager method instead, then fix mail delivery afterwards.
Site still down and you need it back now?
If you have worked through this and the site is still broken, or the thought of renaming folders over FTP makes you nervous, hand it over rather than making it worse. Survyc is an AI-first digital agency that recovers broken WordPress sites for agencies and businesses, and we work white label so your own client sees your name on the fix. You get a scoped answer before any work starts, and our guide to what a WordPress repair costs explains how we price it. Tell us what happened or email info@survyc.com. If you would rather this never happened again, our WordPress care plans run updates on staging first.
