Backups & maintenance · Guide
How to Update Plugins in WordPress (Step by Step)

Short answer
Take a backup, then go to Dashboard, Updates, tick the plugins listed and click Update Plugins. You can also click update now under a plugin on the Plugins screen, or turn on auto-updates, then check your key pages and clear the cache afterwards.
Key takeaways
- Back up before updating, and test big updates on staging.
- Dashboard Updates handles many plugins at once.
- Auto-updates suit trusted, low-risk plugins.
- Premium plugins need an active licence or a manual ZIP upload.
- Roll back or deactivate a plugin if an update breaks the site.
How do you update plugins in WordPress?
Back up the site, go to Dashboard > Updates or the Plugins screen, select the plugins with updates, click Update, then check the site still works.
WordPress tells you when updates are ready. A red number appears next to Plugins and Updates in the admin menu, showing how many are waiting.
Updating takes seconds per plugin. The real work is doing it safely: a backup before, a quick check after, and a plan if something breaks.
Plugin updates fix bugs, add features and, most importantly, close security holes. Outdated plugins are one of the most common ways WordPress sites get hacked.
| Method | Best for |
|---|---|
| Dashboard > Updates | Updating several plugins at once |
| Plugins screen | Updating one plugin and reading its details |
| Auto-updates | Trusted, low-risk plugins |
| Upload a ZIP file | Premium plugins without automatic updates |
| WP-CLI | Developers and many sites over SSH |
| SFTP | When the dashboard is broken |
What should you do before updating?
Take a full backup, read the changelog for big version jumps, and test major updates on a staging site first.
A backup lets you undo a bad update in minutes. Many hosts take daily backups, but a fresh manual one right before updating is safer. Our guide on how to restore a WordPress site from backup is worth reading now, not during an emergency.
Click View version details on the Plugins screen to read the changelog. Small updates, such as 4.2.1 to 4.2.2, are usually bug fixes. A jump to a new major version may change features or settings.
For shops, membership sites and busy blogs, test big updates on staging first. Our guide to setting up a staging site shows how.
Check that your PHP version is supported. Some plugin updates drop old PHP versions, and the PHP supported versions page shows which ones still get security fixes.
Method 1: Update from Dashboard > Updates
Go to Dashboard, then Updates, scroll to the Plugins section, tick the plugins you want, and click Update Plugins.
This screen lists every pending update for core, plugins, themes and translations in one place. The Dashboard Updates screen documentation explains each section.
You can tick Select All to update everything at once. That is fine for small sites, but on complex sites it is safer to update a few at a time so you know which one caused a problem.
WordPress puts the site into maintenance mode for a few seconds during updates. Visitors see a short notice, then the site comes back.
When the updates finish, WordPress shows a success message for each plugin. Any failures are listed with a reason.
Method 2: Update from the Plugins screen
Go to Plugins, find the plugin with an update notice, and click update now under it; or tick several plugins and choose Update from Bulk actions.
The notice reads something like There is a new version of Plugin Name available. The update now link updates that plugin without leaving the page.
For several plugins, tick their boxes, open the Bulk actions dropdown, choose Update and click Apply.
The official Manage Plugins guide covers this screen and the other plugin actions in more detail.
If no update notices appear even though you know a new version exists, see our guide on why WordPress won't show plugin updates.
Method 3: Turn on automatic updates
Click Enable auto-updates next to a plugin on the Plugins screen, and WordPress will install new versions for it in the background.
Auto-updates have been built into WordPress since version 5.5. The plugin and theme auto-updates documentation explains how they work and how to turn them off.
They suit well-maintained plugins with a good track record, such as security tools and simple utilities. Be more careful with page builders, WooCommerce and anything that changes data structures.
WordPress emails the site admin after auto-updates run. Read those emails, and check the site if one reports a failure.
Our guide on enabling automatic updates for plugins covers bulk settings and host-level options.
Method 4: Update a premium plugin
Enter the licence key in the plugin's settings so updates appear in the dashboard, or download the new ZIP from the vendor and upload it.
Premium plugins are not hosted on WordPress.org, so they need an active licence to receive one-click updates. An expired licence is the most common reason a premium plugin stops updating.
To update by upload, go to Plugins, then Add New Plugin, then Upload Plugin, and choose the new ZIP. WordPress detects the existing plugin and offers to replace the current version with the uploaded one.
Only download premium plugins from the official vendor. Copies from other sites may contain malware, which our look at whether nulled plugins are safe explains.
Method 5: Update plugins with WP-CLI
Run wp plugin update followed by the plugin slug, or add the all flag to update every plugin from the command line.
These commands update one plugin, or all of them:
wp plugin update akismet
wp plugin update --all
The wp plugin update reference lists more options, such as a dry run that shows what would change and an option to only apply minor releases.
WP-CLI is fast and works even when the dashboard is slow. It suits developers and anyone managing many sites over SSH.
Method 6: Update manually through SFTP
Download the new version, upload it over SFTP to wp-content/plugins, and replace the old plugin folder.
Use this only when the dashboard is broken or blocked. Delete or rename the old folder first, then upload the fresh one with the same name.
Your settings live in the database, not the plugin folder, so they normally survive a manual replace. Back up first anyway.
Check file ownership after uploading. If WordPress cannot write to the new files, future dashboard updates may fail.
What should you check after updating?
Visit the home page, a few key pages and any forms, checkout or login flows the plugin touches, and look for errors or layout changes.
Clear your cache before checking. A caching plugin or CDN can hide problems by serving old pages.
Test the features the updated plugin powers. After a form plugin update, send a test entry; after a WooCommerce update, place a test order.
Check the admin too. Some updates add new settings screens or database update notices that need a click to finish.
What if a plugin update breaks the site?
Roll the plugin back to the previous version, or deactivate it, then restore from backup if the site still fails.
Recent WordPress versions try to roll back a plugin automatically if an auto-update causes a fatal error. That helps, but it does not catch every problem.
If you can reach the dashboard, use a rollback tool. Our guide on rolling back a plugin update walks through the options.
If the dashboard will not load, rename the plugin's folder over SFTP to deactivate it. Our guide on deactivating plugins without admin access shows how.
Then report the problem to the plugin developer in its support forum, with your WordPress and PHP versions and any error message.
What are common update errors?
The most common are a stuck maintenance message, an update already in progress, failed downloads and file permission errors.
If the site shows Briefly unavailable for scheduled maintenance long after an update, a leftover .maintenance file is to blame. Our fix for being stuck in maintenance mode explains how to delete it.
If WordPress says Another update is currently in progress, an earlier update left a lock behind. It usually clears within 15 minutes, or you can remove it with our fix for another update in progress.
Download failures often mean a timeout or temporary host issue. Wait a few minutes and try again, or use the upload method.
For a regular routine, the Learn WordPress lesson on managing updates covers core, theme and plugin updates together.
Frequently asked questions
How often should I update WordPress plugins?
Check for updates at least once a week and install security fixes as soon as they appear. Busy or business-critical sites benefit from a set weekly routine with a backup before each round.
Is it safe to update all plugins at once?
It is usually fine on simple sites. On complex sites, update a few at a time so you can tell which plugin caused a problem, and test major version jumps on staging first.
Will updating a plugin delete my settings?
Normally not. Plugin settings are stored in the database, and updates replace only the plugin files. Major versions can change settings, so read the changelog and keep a backup.
Why can't I update a premium plugin?
Premium plugins need an active licence key entered in the plugin settings to get dashboard updates. If the licence expired, renew it, or download the latest ZIP from the vendor and upload it.
Should I turn on automatic plugin updates?
For trusted, well-maintained plugins, yes. They close security holes faster. Keep manual control over complex plugins such as page builders and WooCommerce, and keep regular backups either way.
Sources
- Manage Plugins WordPress.org Documentation
- Dashboard Updates Screen WordPress.org Documentation
- Plugins and themes auto-updates WordPress.org Documentation
- wp plugin update WordPress Developer Resources
- Managing Updates Learn WordPress
- Supported Versions PHP.net
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


