If a WordPress update broke something, you don't need a developer to fix it. For content, use the block editor's built-in revision history. For a plugin or theme, reinstall the previous version directly. If the site is actually broken (white screen, fatal error, database mismatch), restore from a backup instead of trying to undo the update piece by piece.
Which path you take depends on what broke: content, a single plugin or theme, or the whole site.
Rolling back content with the block editor
WordPress keeps a revision history for every post and page, saved automatically as you edit. To get back an earlier version:
- Open the post or page in the block editor.
- Click the
...options menu in the top right, or open the Document panel on the right sidebar. - Click Revisions (shows a count, like "12 Revisions").
- Drag the slider or step through revisions to compare against the current version.
- Click Restore This Revision on the version you want back.
This only covers post and page content. It won't undo a plugin update, a theme change, or a settings change made outside the editor. WordPress prunes old revisions over time on some configurations, so this isn't a permanent safety net. It's a quick undo for recent edits.
Rolling back a plugin
If a plugin update caused the problem, downgrading that one plugin is usually faster and safer than a full site restore.
From wp-admin:
- Deactivate the plugin first:
Plugins → Installed Plugins → Deactivate. This stops the immediate damage while you sort out the fix. - Check if the plugin author publishes older versions. Many do, through the WordPress.org plugin page's Advanced View (look for "Previous Versions" in the sidebar) or the developer's own site for premium plugins.
- Download the last known-good version as a
.zip. - Go to
Plugins → Add New → Upload Plugin, choose the zip, and install. WordPress will prompt to replace the current version, confirm. - Reactivate and test.
Same logic applies to a theme: download the previous version's zip, then Appearance → Themes → Add New → Upload Theme and replace it. If you're on a child theme, this is even lower risk since your customizations live separately from the parent theme files.
Not every plugin publishes old versions publicly, and rolling back a database-touching plugin (WooCommerce, a page builder that stores layout data) can leave stale data behind even after the code reverts. If you're not sure what a plugin changed on update, test on a copy of the site first. See Using WordPress staging for how to clone the site and try the rollback there before touching production.
Full restore from backup
If the site won't load, the admin area is broken, or you can't isolate which plugin caused it, skip the piece-by-piece rollback and restore from a backup instead.
Flashcloud runs full nightly backups of your hosting account, restorable through the Backups tile on your service page. A restore can bring back single files, a whole account, or just a database, so you don't have to overwrite everything to recover one piece.
Restoring rolls back files and database together, so it undoes the plugin update, any content changes, and anything else that happened since that backup was taken. That's the tradeoff: it's reliable, but you lose changes made after the backup point. See Backing up your WordPress site for how the backup layers work and what each one covers.
If you run UpdraftPlus or a similar backup plugin, it has its own restore flow under its settings page, useful for restoring individual tables (like just the posts table) instead of the whole database.
After the rollback: prevent a repeat
Once the site is stable again, two habits catch this before it happens again:
- Take a fresh backup before every update, manual or automatic, so you always have a clean rollback point. See Updating WordPress safely for the full update workflow, including which updates are riskiest.
- Test risky updates (major core versions, page builders, anything touching WooCommerce) on a staging copy first, so a bad update never reaches visitors at all.
If the site was slow rather than broken after an update, that's a different problem. See My WordPress site is slow for what to check.
When to contact support
If a restore doesn't bring the site back, or the backup you need isn't available, open a ticket from the portal.