Black FridayCyber Monday 2026
14Days
15Hrs
22Mins
44Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Auto Updates: Turn Them On, Off, or Half On? A Safe Way to Decide

WordPress auto updates can save you from old, vulnerable plugins or surprise you with a broken site. Learn what is automatic by default and a risk-based way to choose.

wpallsolution 8 min read

WordPress auto updates sit between two kinds of pain. Leave them off, and an old plugin with a known security hole sits on your site for months. Switch everything on, and one bad update can break your checkout while you sleep. The right answer is rarely “all” or “nothing”. This guide shows what WordPress updates by itself, what you can switch on, and a simple risk-based way to decide plugin by plugin.

Quick answer

According to the WordPress documentation, WordPress core applies minor and security updates automatically on most sites, while plugin and theme auto updates, available since WordPress 5.5, are off until an administrator switches them on, one plugin or theme at a time. Our recommendation: make sure you have a restore point, turn on auto updates for simple low-risk plugins, and keep anything that touches payments, checkout, memberships or forms on a manual, tested update routine. Then check that scheduled updates actually run.

How this guide was prepared: the facts follow the WordPress documentation and core announcement listed under Sources, read on October 21, 2026. The risk grouping in this guide is our own recommendation, not a WordPress rule. Hosts and plugins can change how updates behave, and we did not test this on your site.

Before you change anything

  • Have a backup you can restore. The WordPress documentation says to make sure you can roll back before enabling auto updates. See Is your WordPress backup really safe?
  • List your plugins and mark which ones affect money or data (shop, forms, memberships, page builder).
  • Know who gets the emails. WordPress sends notices after update attempts, so use an inbox that someone reads.
  • Do not switch everything on at once. Start small and watch the results.

WordPress auto updates: the decision tree

WordPress auto updates flowchart: five questions covering backups, low-risk plugins, checkout and payment plugins, missing controls and cron
Five questions split your plugins into automatic and manual.
  1. Do you have a backup you can restore quickly? If not, fix that before anything else (Step 2).
  2. Is the plugin simple and low-risk? Then it is a good candidate for auto updates (Step 4).
  3. Does it touch checkout, payments, memberships or forms? Update it manually, on staging first (Step 5).
  4. Are the auto update controls missing? Look at your WordPress version, host and plugins (Step 1).
  5. Do scheduled updates seem not to run? Check WordPress cron (Step 6).

Symptoms and likely causes

What you seeLikely causeStart with
No “Automatic updates” column on the Plugins screenWordPress older than 5.5, or disabled by host or pluginStep 1
Plugins stay outdated for weeksAuto updates are off and nobody updates manuallySteps 3 and 4
Site broke after an update you did not runA plugin auto-updated with no restore planSteps 2 and 5
“Next update” never changesWordPress cron is not running correctlyStep 6
You get emails about failed updatesA plugin or theme could not be updatedStep 7
Site Health says background updates are not workingPermissions, blocked connection or host restrictionSteps 1 and 6

7 steps to decide your WordPress auto updates

Step 1: See what is already on

The documentation says plugin and theme auto updates were introduced in WordPress 5.5, and that core minor and security updates have long been automatic by default. Open Dashboard → Updates and the Plugins screen. If you see an “Automatic updates” column, each plugin shows its state and a link to enable or disable it. For themes, open Appearance, select a theme and look for “Enable auto-updates” in the theme details. If these controls are missing, the documentation says it probably means your host or a plugin has partly or completely turned the feature off. Site Health (Tools → Site Health) also reports problems with background updates, as explained in our WordPress Site Health guide.

Step 2: Get a restore point first

This is the step people skip. Before you enable auto updates, you need a recent backup of files and database and a way to restore it. A backup you have never tried to restore is a hope, not a plan. Know where the backup is, how long a restore takes, and who does it. If your host offers one-click restore or staging, learn how it works now, not during an outage.

Step 3: Sort your plugins by risk

This grouping is our own suggestion. Low risk: simple plugins whose failure would be annoying but not costly, such as a security scanner or a small utility. Medium risk: SEO, caching and performance plugins, which can change how pages look or load. High risk: anything involved in checkout, payments, memberships, bookings, forms that collect leads, and page builders that control your layout. Core WordPress security updates stay automatic. Write the list down; you will use it every month.

Step 4: Switch on auto updates for the low-risk group

On the Plugins screen, use the enable link for each plugin, or select several and use the bulk action. The documentation says you can turn auto updates off again with the same link, and that by default WordPress runs auto updates twice per day, with the time until the next run displayed under the link. Start with a few plugins, watch for a few weeks, then decide about the medium-risk group.

Step 5: Keep high-risk plugins on a tested manual routine

For plugins that touch money or leads, read the changelog, update on a staging copy, test the real flows (checkout, login, forms), and only then update the live site. Our guide how to update WordPress plugins safely gives a routine. If an update ever breaks the site, see WordPress 500 internal server error after a plugin update for the way back. Do not leave important plugins months behind, because that is its own security risk. The point of manual is control, not neglect.

Step 6: Make sure scheduled updates actually run

The documentation warns that auto update scheduling relies on WordPress cron tasks, and that depending on your server, installation or plugins it may not work correctly. If the “next update” time never changes, or Site Health reports failing background updates or loopback requests, check with your host whether WordPress cron runs, and whether a security rule blocks it. A host can sometimes run cron from a server scheduler instead of on page loads.

Step 7: Read the emails and review monthly

The documentation says WordPress sends email notifications about plugin and theme auto update results, including when some succeeded and some failed. Make sure those go to an inbox someone actually checks. Once a month, spend ten minutes: look at what updated, test the key pages, and move plugins between groups. This review is part of regular WordPress maintenance.

Version and hosting differences

  • Plugin and theme auto updates need WordPress 5.5 or later.
  • Some managed hosts run their own update system and may override these settings.
  • Staging and development sites often have auto updates turned off on purpose.
  • Premium plugins may update through their own license system, which can behave differently.

How to verify the fix

  • The Plugins screen shows the setting you chose for each plugin, and the next scheduled update time changes.
  • You received an email after the first automatic update and the site still works.
  • You tested login, forms and checkout after an update cycle.
  • You know where the backup is and how to restore it.

How to prevent it from happening again

  • Keep the risk list up to date as you add or remove plugins.
  • Test updates on staging for high-risk plugins, and remove plugins you do not use.
  • Check Site Health monthly. If you would rather hand this over, our WordPress maintenance plans cover updates, backups and monitoring.

Frequently asked questions

Does WordPress update itself?

Core minor and security updates are automatic on most sites, per the documentation. Plugin and theme auto updates must be switched on by an administrator.

Are auto updates safe?

They are safer than ignoring updates, and riskier than tested updates for important plugins. That is why we suggest deciding per plugin.

Can I turn auto updates off later?

Yes, with the same link you used to enable them, or the bulk action.

What if an update breaks my site?

Deactivate the plugin, restore the backup if needed and read the log. See our guides on the critical error screen and finding the plugin that broke your site.

What to do next

Take ten minutes: list your plugins, mark the high-risk ones and turn on auto updates for the safe few. If your WordPress auto updates behave strangely, send your host the Site Health message and the update emails. If you would like a person to look, wpallsolution offers independent plugin support. We cannot promise results without seeing your setup.

Sources and official documentation

Last reviewed: October 21, 2026. WordPress is a trademark of the WordPress Foundation. wpallsolution is not affiliated with or endorsed by the WordPress Foundation or Automattic.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us