WordPress Update Failed or Broke Your Site? How to Recover

You clicked Update, and now something is wrong. Maybe the update failed with “Update failed” or “Could not create directory”. Maybe it finished, but the site now shows an error, a broken layout, or a feature that no longer works. Updates are the most common moment for a WordPress site to break, and in most cases the problem can be undone.

This guide covers both situations: updates that failed to install, and updates that installed but broke the site.

Step 1: Work out what changed

Write down which updates ran and when. If you updated several plugins at once, the problem is almost certainly one of them. Check:

• Dashboard → Updates and the Plugins page for recently updated items.
• Your email inbox. WordPress sends a message after automatic updates, and after a fatal error it sends a “Your site is experiencing a technical issue” email that usually names the plugin or theme and includes a recovery mode link.
• Your hosting control panel, which may log automatic updates or backups.

Step 2: If the site shows “Briefly unavailable for scheduled maintenance”

WordPress puts the site into maintenance mode during an update and creates a file called .maintenance in the root folder. If the update stops halfway, the file stays behind and the site stays locked. Delete .maintenance in File Manager or over SFTP. Our guide to fixing WordPress stuck in maintenance mode covers this in detail, including how to finish the interrupted update.

Step 3: If the update failed to install

Common messages and fixes:

• “Could not create directory” or “Destination folder already exists”: a previous attempt left files behind or WordPress cannot write to the folder. Check wp-content/upgrade and delete any leftover folders inside it. If a plugin folder exists but the plugin is incomplete, delete that folder and install the plugin again. Folders should normally have 755 permissions and files 644.
• “Download failed” or timeouts: the server could not reach WordPress.org or ran out of time. Try again later, or download the plugin’s ZIP file and upload it under Plugins → Add New → Upload Plugin. Recent WordPress versions offer to replace the installed version with the uploaded one.
• “Update package not available”: this is common with premium plugins and themes. Check that your license key is entered and active, or download the latest version from the vendor’s account area.
• Disk space: a full hosting account makes updates fail in odd ways. Check your disk usage in the control panel and remove old backups stored on the server.

Step 4: If the update broke the site

If you see “There has been a critical error on this website”, a white screen, or a 500 error, use the recovery mode link from the WordPress email to log in and deactivate the plugin it names. If you have no link, deactivate the plugin without wp-admin:

1. Open wp-content/plugins in File Manager or over SFTP.
2. Rename the folder of the plugin you just updated, for example plugin-name to plugin-name-off.
3. Reload the site. If it works, you have found the cause.

If you are not sure which update caused it, follow our guide to fixing the WordPress critical error, which shows how to read the debug log and find the exact file.

Step 5: Roll back to the previous version

Once you know which plugin or theme is at fault, go back to the version that worked:

• Plugins from WordPress.org: install the free WP Rollback plugin, which adds a “Rollback” link to each plugin and lets you pick an earlier version. You can also download older versions from the plugin’s page on WordPress.org under Advanced View.
• With WP-CLI: you can install a specific version directly:

wp plugin install plugin-name --version=1.2.3 --force

• Premium plugins and themes: many vendors offer older versions in your account area. Otherwise, ask their support.
• Restoring a backup: if many things broke at once, restoring the files and database from just before the update is often fastest. Be aware that a full restore removes any orders, comments, or form entries received since the backup.

After rolling back, pause automatic updates for that plugin (on the Plugins page, click Disable auto-updates) until a fixed version is out.

Step 6: If the layout or a feature broke

When the site loads but looks wrong or a feature stopped working, the update often changed code that other parts of the site depend on:

• Clear every cache: your caching plugin, server cache, CDN such as Cloudflare, and your browser. Old cached CSS or JavaScript is the most common reason a site looks broken after an update.
• Page builders: regenerate CSS files in the builder’s tools, and update any add-on plugins to versions that support the new builder version.
• Child themes and custom code: if your child theme overrides template files, the parent theme update may have changed them. WooCommerce shows outdated template overrides under WooCommerce → Status.
• Check the browser console (F12, then Console) for JavaScript errors that name the file causing the problem.

Step 7: Update safely next time

• Take a full backup before updating, and keep a copy off the server.
• Update one major plugin at a time, and check the key pages and forms after each.
• Read the changelog for major version jumps, such as 4.x to 5.0.
• Test big updates on a staging copy first. Many hosts offer one-click staging.
• Avoid updating just before a busy period or when you will be away.

When to call an expert

Get help if rolling back does not fix the site, if the database was changed by the update (common with WooCommerce and membership plugins), if you run a store and orders are failing, or if you do not have a backup. A careless rollback can leave data out of step with the code.

Frequently asked questions

Should I turn off automatic updates?

Not completely. Security updates matter, and an out-of-date site is a bigger risk than an occasional broken update. A good middle ground is to keep automatic minor core updates on and update major plugins yourself after a backup.

Is it safe to stay on an older plugin version?

For a short time, yes. Older versions may have known security issues, so update again once the developer releases a fix, and check the changelog for security notes.

Why did a theme update remove my changes?

Updating a theme replaces all its files. Any edits made directly in the theme are lost. Put custom code in a child theme or a code snippets plugin so it survives updates.