Security · Guide
Should You Turn On Plugin Auto-Updates?
Short answer
Turn on plugin auto-updates for low-risk plugins, such as small utilities and security plugins, and leave them off for plugins that run your store, checkout, or custom features until you have tested the update. WordPress lets you enable auto-updates plugin by plugin from the Plugins screen, and you can turn them off again at any time. Always keep a recent backup, so a bad update is a restore, not a rebuild.
Key takeaways
- Plugin and theme auto-updates arrived in WordPress 5.5 and are off by default.
- Minor WordPress core updates have installed themselves since version 3.7.
- Enable auto-updates plugin by plugin, starting with low-risk plugins.
- Auto-updates need WP-Cron to run, so a broken cron job stops them silently.
- A backup before you enable auto-updates turns a bad update into a quick restore.
What are plugin auto-updates in WordPress?
Plugin auto-updates let WordPress install new versions of a plugin by itself, without you clicking Update each time.
Since WordPress 5.5, site administrators can opt in to automatic updates theme by theme and plugin by plugin (Plugin and themes auto-updates). Each plugin gets its own toggle, so you can update some plugins automatically and others by hand.
Auto-updates are off by default. Plugin and theme auto-updates are disabled by default, and administrators need to enable the feature to receive automatic updates (Controlling Plugin and Theme auto-updates UI).
Core updates work differently. Since WordPress 3.7, minor and development versions of core, and translations, have been auto-updated by default (auto_update hook). New installs on WordPress 5.6 or higher also auto-update major versions by default (auto_update hook).
Should you turn on plugin auto-updates?
Turn auto-updates on for low-risk plugins, and leave them off for plugins that run your store, checkout, or custom features.
The case for turning them on is security. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, with 91% in plugins, and 46% of disclosed flaws had no fix at disclosure (Patchstack). A plugin update often closes a known flaw, so waiting weeks to install it leaves the flaw open.
The case against turning them all on is breakage. An update can change how a plugin works, clash with your theme, or break a custom feature. WordPress does not test updates against your site before it installs them.
| Approach | How it works | Best for | Risk |
|---|---|---|---|
| One plugin at a time | Enable auto-updates on the Plugins screen | Low-risk plugins | Low |
| Bulk enable | Select plugins, use bulk actions | Many small utilities | Medium |
| All plugins on | Enable for every plugin | Simple blogs with backups | High |
| Code filter | auto_update_plugin filter | Developers | High if wrong |
| Managed by host | Host updates plugins for you | Managed hosting | Low |
The middle path works best for most sites. Enable auto-updates for small, low-risk plugins, and update the risky ones by hand after a staging test. That way you get security fixes fast without risking your checkout.
How do you enable auto-updates for one plugin?
Open Plugins > Installed Plugins, find the plugin, and click Enable auto-updates in the Automatic Updates column.
- Log in to WordPress and go to “Plugins > Installed Plugins”.
- Find the plugin in the list and look at the “Automatic Updates” column.
- Click “Enable auto-updates” beside the plugin.
- Check that the link changes to “Disable auto-updates”, which confirms it is on.
Each plugin has its own toggle. Navigate to the Plugins screen, and for each plugin there is an “Automatic update” column with a link to enable or disable auto-updates plugin by plugin (Plugin and themes auto-updates).
How do you enable auto-updates for many plugins at once?
Select several plugins with the checkboxes, choose Enable Auto-updates from the bulk actions menu, and click Apply.
- Go to “Plugins > Installed Plugins”.
- Tick the checkbox beside each low-risk plugin you want to update automatically.
- Open the “Bulk actions” menu at the top of the table and choose “Enable Auto-updates”.
- Click “Apply” and check that each plugin now shows auto-updates as enabled.
Bulk actions work the same way for themes. Select the themes, pick the matching bulk action, and apply it. Only enable auto-updates in bulk for plugins you would trust to update without a test.
How do you turn auto-updates off again?
Go back to the Plugins screen and click Disable auto-updates beside the plugin, or use bulk actions to switch several off at once.
Once enabled, auto-updates can be disabled at any time, using the same toggle link (Plugin and themes auto-updates). Themes work the same way: open the theme details and click “Disable auto-updates”.
Developers can switch updates off with code. Returning false to the auto_update_plugin filter stops plugin auto-updates, and the plugins_auto_update_enabled filter hides the toggle in the dashboard (auto_update hook). Use code only if you manage updates another way, such as through your host.
If the auto-update controls are missing from your dashboard, check your WordPress version first. If the controls are not available, check you are running WordPress 5.5 or newer, since plugin and theme auto-updates were introduced in 5.5 (Plugin and themes auto-updates).
What should you check before you enable auto-updates?
Check your backups, your staging site, and which plugins are safe to update without a test.
- A recent backup you have tested, so a bad update is a restore, not a rebuild.
- A staging copy where risky updates get tested first.
- The plugin changelog, to see whether the update changes features or only fixes flaws.
- Whether the plugin is abandoned, since an abandoned plugin gets no updates at all.
- Whether your host already manages updates, since double management can clash.
Check abandoned plugins first. A plugin with no update for over a year may never get a security fix, so auto-updates cannot help it. Read our guide to find abandoned WordPress plugins and replace any you find.
Check whether a plugin is closed on WordPress.org. A closed plugin gets no updates from the directory, so enabling auto-updates for it does nothing. See what happens when a plugin is closed on WordPress.org.
How do auto-updates work behind the scenes?
WordPress checks for updates on a schedule, then downloads and installs new versions for the plugins you enabled.
Auto-updates rely on WP-Cron to run. Depending on your server and plugins, auto-update scheduling may not work correctly, since updates rely on WordPress Cron tasks to actually perform the update (Plugin and themes auto-updates).
Only some users can change the settings. By default, all users with the update_plugins and update_themes capabilities can toggle auto-updates, and on multisite only network administrators can do it (Controlling Plugin and Theme auto-updates UI).
Language packs update on their own. Language packs for plugins and themes have always auto-updated when new versions are available, and the auto-update toggles do not change that (Controlling Plugin and Theme auto-updates UI).
You can also control updates with filters. The auto_update_plugin filter decides whether a plugin updates itself, and the plugins_auto_update_enabled filter controls whether the dashboard toggle appears (auto_update hook).
What if an auto-update breaks your site?
Restore your backup first, then turn off auto-updates for that plugin and report the problem to its author.
- Restore the backup you made before the update, and confirm the site works again.
- Turn off auto-updates for the plugin that broke, so it does not update again.
- Check the plugin changelog and support forum for reports of the same problem.
- Wait for a fixed release, test it on staging, then turn auto-updates back on.
A staging test would have caught most breaks. Test risky updates on staging first, and keep auto-updates for the plugins you trust. See how to set up a staging site for WordPress.
For WooCommerce stores, test every update. A broken checkout costs more than a delayed security fix, so update store plugins by hand. Read how to update WooCommerce safely before you touch a store plugin.
What mistakes should you avoid?
Do not enable auto-updates for every plugin at once, and do not enable them without a tested backup.
- Turning on auto-updates for all plugins on a store or membership site without testing.
- Enabling auto-updates with no backup, so a bad update means rebuilding by hand.
- Assuming auto-updates ran, when a broken WP-Cron job stopped them silently.
- Leaving auto-updates off forever, so known flaws stay open for months.
- Updating a plugin you customized, since the update can overwrite your changes.
Check that updates are actually running. Open Dashboard > Updates once a month, and look for plugins that should have updated but did not. If updates are stuck, check WP-Cron first, since auto-updates depend on it.
Backups are the safety net for every update choice. See how often you should back up WordPress and keep a copy off the server.
Frequently asked questions
Do plugin auto-updates run at a set time?
No. WordPress checks for updates on a schedule driven by WP-Cron, which runs when your site gets visits, so there is no fixed update time. A site with little traffic may check less often. If your cron jobs are broken, auto-updates may not run at all, so check Dashboard > Updates on a regular schedule.
Will auto-updates update my theme too?
Only if you enable them for that theme. Plugin and theme auto-updates are separate toggles, and both are off by default. Open Appearance > Themes, click a theme, and use the Enable auto-updates link in the theme details. Test theme updates on staging first, since themes control what visitors see.
Do auto-updates work on multisite?
Yes, but only network administrators can toggle them, and only from the network dashboard. Regular site administrators cannot change auto-update settings for plugins or themes on a multisite network. Check with your network admin before you change anything.
Can my host turn off auto-updates?
Yes. If the auto-update controls are missing from your dashboard even though you run WordPress 5.5 or newer, your host or a plugin may have disabled the feature. Some managed hosts update plugins themselves and hide the toggles. Ask your host whether it manages updates before you change anything.
Should I enable auto-updates for WooCommerce?
No, not without testing. WooCommerce and payment gateway updates can change checkout behavior, so test them on staging first. Enable auto-updates only for small, low-risk plugins, and update store plugins by hand after a backup and a staging test.
Sources
- Plugin and themes auto-updates WordPress.org
- Controlling Plugin and Theme auto-updates UI in WordPress 5.5 Make WordPress Core
- auto_update_{$type} – Hook WordPress Developer Resources
- State of WordPress Security in 2026 Patchstack
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.
