Ocean Digest
How iPhone widgets actually refresh, and why one looks frozen
Two questions come up every time someone puts an animated widget on their Home Screen. Will it drain my battery, and why did it stop moving? The usual answer is that battery use varies, which tells you nothing. Apple publishes real numbers for both, in the WidgetKit documentation and the Human Interface Guidelines, and they explain almost every case of a widget that looks stuck.
This page quotes those numbers and says where each one comes from. It also says plainly which of the popular explanations Apple does not publish anywhere, because a lot of what circulates about widget refreshes is guesswork repeated until it sounded official.
A widget is not a live view. It renders a timeline of snapshots, and the system decides when to redraw it. Apple states the ceiling: for a widget you view often, a daily budget typically includes from 40 to 70 refreshes, roughly one every 15 to 60 minutes. A widget that looks frozen has usually run out of refreshes rather than broken.
A widget is a timeline of snapshots, not a live view
The single most useful fact about widgets is that nothing is running behind the one on your Home Screen. Apple states it in one sentence: "WidgetKit renders the views on your behalf in a separate process. As a result, your widget extension is not continually active, even if the widget is onscreen."
What the app hands over instead is a timeline. Apple describes it as an array of entries where "Each entry in the timeline has a date and time, and additional information the widget needs to display its view." Alongside the entries the app sets a refresh policy, which, in Apple's words, "tells WidgetKit when to request a new timeline."
So the app is not pushing updates to your Home Screen. It is filing a schedule in advance, and the system draws whichever snapshot matches the current time. When the schedule runs out, the system asks the app for a new one, on its own terms and at a time of its choosing.
The Human Interface Guidelines put the consequence bluntly: widgets "periodically refresh their information but don't support continuous, real-time updates, and the system may adjust the limits for updates depending on various factors." Elsewhere on the same page, more briefly: "Widgets don't show real-time information."
Apple's refresh budget, quoted exactly
Here is the number everyone half-remembers, in full. Apple's page on keeping a widget up to date says: "For a widget the user frequently views, a daily budget typically includes from 40 to 70 refreshes. This rate roughly translates to widget reloads every 15 to 60 minutes, but it's common for these intervals to vary due to the many factors involved."
Note how heavily that sentence is hedged, because the detail matters more than the figure. Apple is explicit that "The budget allocation is dynamic and takes many factors into account," and names them.
- The factors Apple lists: how often and at what times the widget is visible to you, the widget's last reload time, and whether the widget's app is active.
- Each widget has its own budget. Apple's example is two copies of one sports widget showing different teams, and says each "has its own budget." Two aquarium widgets do not share an allowance.
- The window is not the calendar day. The budget covers a 24-hour period, but Apple "tunes the 24-hour window to the user's daily usage pattern, which means the daily budget doesn't necessarily reset at exactly midnight."
- There is a floor on how close entries can be. Apple: "Your timeline provider should create timeline entries that are at least about 5 minutes apart," and the system "may coalesce reloads across multiple widgets."
- A new widget gets more at first. Apple notes that "The system takes a few days to learn the user's behavior. During this learning period, your widget may receive more reloads than normal." A widget that was livelier in its first week was not imagining it.
The battery question, answered the way Apple answers it
Apple gives a cause rather than a percentage: "Reloading widgets consumes system resources and causes battery drain due to additional networking and processing." The budget exists precisely to cap that, which is why it is the honest answer to the battery question. The system will not let a widget refresh often enough to matter, whatever the app would prefer.
That also reframes which widgets are expensive. The cost Apple names is networking and processing at reload time, so a widget that fetches from a server every reload is doing work that one drawing from data already on the device is not. Neither can exceed the same ceiling.
Pushes are not a way round it either. For widget updates sent from a server, Apple says: "Like timeline updates, the system budgets WidgetKit push notifications and delivers them opportunistically."
The refreshes that are free
Some reloads happen without touching the budget at all, and this is the part that explains why a widget springs to life the moment you open its app. Apple lists the exemptions directly.
- The widget's containing app is in the foreground.
- The app has an active audio or navigation session.
- The app is the current Now Playing app.
- The widget performs an app intent, such as when you tap a button or toggle a switch in it.
- The widget performs an animation.
- The system locale changes.
- Dynamic Type or Accessibility settings change.
- In StandBy, where Apple says the system refreshes the display "at a system-defined rate that doesn't count against its budget."
Where the widget sits changes how often it refreshes
Two of Apple's documented behaviours are about placement rather than code, and both are worth knowing before you blame an app.
The first is the rarely-visited page. Apple: "If a widget is on a Home Screen page that the user rarely visits, WidgetKit may reduce the frequency of reloads for that widget. Later, when the user views the page, WidgetKit may reload the widget when it becomes visible." A widget parked on your fourth page is being deliberately starved, and will often catch up when you swipe to it.
The second is location. For widgets that use Location Services, Apple says WidgetKit "reloads them after a significant location change happens." That is a free extra trigger for weather and transit widgets and irrelevant to everything else.
There is also a first-run condition that catches people installing a new app: "For an app's widget to appear in the widget gallery, a person must launch the app that contains the widget at least once after the app is installed."
What animation in a widget is, and what it is not
This is where expectations and documentation part company. WidgetKit animation is documented as animation of data updates: "Widgets and Live Activities animate data updates with default animations or SwiftUI animations you choose." Text views animate content changes, images and SF Symbols get content transitions, and views added or removed between updates fade in and out.
There is a hard ceiling stated twice. The WidgetKit page: "Animations in widgets and Live Activities have a maximum duration of two seconds." The Human Interface Guidelines, giving the same figure as design guidance, says to "use standard and custom animations with a duration of up to two seconds to let people know when new information is available or when content displays differently."
Read together, what Apple documents is a transition between states, up to two seconds long, triggered when the content changes. Apple's documentation does not describe an arbitrary animation loop that a widget runs by itself for as long as you are looking at it, and the Guidelines' line about no continuous, real-time updates points the same way. Animation is listed among the things that do not count against the budget, so it is not throttled like a reload, but that exemption is not a statement about how long it may run.
One documented exception to animation happening at all: "On devices that include an Always-On display, the system doesn't perform animations to preserve battery life in Always On."
The one thing that genuinely updates without a refresh
Dates and times are special-cased, and this is why a countdown widget seems to defy everything above. Apple: "some SwiftUI views let you display content that continues updating while your widget is visible."
A text view set to the relative, offset or timer style keeps counting on screen. A progress view given a time interval "fills in automatically as time passes from the start of the date range to the end." Apple's example is "a countdown timer that continues to count down even if your widget extension isn't running."
The Guidelines actively recommend leaning on this: "Because widget update frequency is limited, let the system automatically refresh date and time information to preserve update opportunities." If a widget shows you a clock that is correct to the second, that is the system drawing the clock, not evidence that the widget is live.
Why your widget looks frozen
Most frozen-widget reports are one of a handful of documented situations. The table separates what Apple documents from what it does not, because two of the most commonly repeated explanations fall in the second group.
| Symptom | Likely cause | What to do |
|---|---|---|
| Content is stale by half an hour or so | Normal. Apple's own range is a reload every 15 to 60 minutes | Nothing. Open the app if you need it current now |
| Updates were frequent, then slowed after a few days | The learning period ended; Apple says a widget may get more reloads than normal during it | Nothing to fix. This is the documented steady state |
| A widget on a back page never seems current | Apple: WidgetKit may reduce reload frequency for a rarely visited page | Move it to a page you actually look at |
| Two copies of the same widget disagree | Each widget instance has its own budget | Expected. Keep one if you want it fresher |
| It updates instantly whenever you open the app | Foreground reloads are exempt from the budget | This is the reliable way to force a refresh |
| Nothing moves at all until you open the app | Not documented by Apple as a single cause | Check the app's own animation setting, then reboot |
| Frozen in Low Power Mode | Unconfirmed. Apple's Low Power Mode page lists Background App Refresh among what it turns off, and does not mention widgets | Turn Low Power Mode off and see, rather than assuming |
| Frozen with Background App Refresh off | Unconfirmed. Apple documents no link between that setting and widget reloads | Worth trying, but no Apple source promises it helps |
What you can actually do
Short list, and every item on it is either a documented exemption or a plain process restart.
- Open the app. Foreground reloads do not count against the budget, so this is the one method Apple's documentation guarantees.
- Move the widget somewhere you look. Visibility is a named budget factor, and a rarely visited page is documented as getting fewer reloads.
- Keep fewer copies. Separate budgets mean five instances of a widget each get their own smaller share of your attention.
- Launch a newly installed app once. Apple requires it before the widget appears in the gallery at all.
- Expect less on an Always-On display. Apple states the system skips animations there to save battery.
- Give it a day or two after installing. The learning period is documented, and so is the slowdown when it ends.
- Restart the phone before reporting a bug. Not a documented remedy, just the cheapest way to rule out a stuck extension.
What Apple does not publish
Being straight about the gaps is more useful than filling them. Apple does not document that Low Power Mode freezes widgets. The support page for Low Power Mode lists eight things it changes, ending with "Turns off Background App Refresh," and widgets appear nowhere on that list. The same goes for turning Background App Refresh off by hand: no Apple page connects that setting to widget reloads. Both may well have an effect. Neither is something we can show you in writing.
There is no published battery figure for widgets, in milliamp-hours, percentages or anything else. The nearest Apple gets is the cause, networking and processing at reload time. Anyone quoting you a percentage is estimating.
Apple also publishes no memory limit for widget extensions, though developers report one from crash logs. And on the widest question of all, whether a widget may run a continuous animation loop of its own, Apple's documentation is silent rather than permissive: it describes transitions up to two seconds triggered by data updates, and says widgets do not support continuous, real-time updates.
For the related question of why a widget cannot simply embed a live web page, which is the same architecture seen from another angle, our One Big Widget guide walks through Apple's list of views a widget may use and the specific prohibition on wrapping a web view. The link is below.
Questions
How often does an iPhone widget refresh?
Apple's documentation says that for a widget you view frequently, a daily budget typically includes from 40 to 70 refreshes, which it describes as roughly a reload every 15 to 60 minutes. Apple immediately adds that it is common for those intervals to vary, because the budget is dynamic and depends on how often the widget is visible, when it last reloaded and whether its app is active.
Do animated widgets drain the battery?
Apple does not publish a battery figure, but it does name the cause: reloading widgets consumes system resources and causes battery drain through additional networking and processing. The refresh budget exists to cap that, and no widget can exceed it. Animation itself is on Apple's list of things that do not count against the budget, so it is not the expensive part. Reloads are.
Why did my widget stop moving?
The documented causes are that it is on a Home Screen page you rarely visit, which Apple says can reduce its reload frequency, that its budget for the current 24-hour window is used up, or that the first few days of extra reloads during the system's learning period have ended. Opening the app refreshes it without using budget. Apple does not document Low Power Mode or Background App Refresh as causes, so treat those as worth testing rather than established.
Does Low Power Mode stop widgets refreshing?
We cannot confirm it from Apple. Apple's Low Power Mode support page lists what the mode changes, including turning off Background App Refresh, and does not mention widgets or widget refreshes at all. It would not be surprising if widgets refreshed less, but no Apple page says so, so we are not going to claim it.
How do I force a widget to update right now?
Open the app it belongs to. Apple lists reloads that happen while the widget's containing app is in the foreground as exempt from the budget, which makes it the only method the documentation actually guarantees. Tapping a button or toggle inside a widget is also exempt, if the widget has one.
Why does a countdown widget update every second when others cannot?
Because the system draws it. Apple provides date and time views that keep updating while the widget is visible, including relative, offset and timer text styles and a progress view driven by a time interval. Apple's own example is a countdown that keeps counting even when the widget extension is not running. It is not a sign that the widget is live.
Can a widget run a continuous animation loop?
Apple's documentation does not describe one. What it documents is animation of data updates, with a stated maximum duration of two seconds, and the Human Interface Guidelines say widgets do not support continuous, real-time updates. Animation is listed among the things that do not count against the refresh budget, but that exemption says nothing about how long an animation may run. We are reporting the absence of a statement, not a prohibition.
Sources, and which claim came from where. Apple, Keeping a widget up to date (https://developer.apple.com/documentation/widgetkit/keeping-a-widget-up-to-date) for the separate-process rendering sentence, the timeline and refresh-policy description, the 40 to 70 refreshes quote and the 15 to 60 minute range, the dynamic budget and its three named factors, the per-widget-instance budget, the 24-hour window not resetting at midnight, the learning-period note, the full list of reloads exempt from the budget including app intents and animation, the StandBy system-defined rate, the rarely-visited-page reduction, the significant-location-change reload, the roughly 5 minutes apart floor and reload coalescing, and the statement that reloading widgets causes battery drain through networking and processing. Apple, Animating data updates in widgets and Live Activities (https://developer.apple.com/documentation/widgetkit/animating-data-updates-in-widgets-and-live-activities) for animation being animation of data updates, the two-second maximum duration, the default text, image and SF Symbol transitions, and the Always-On display exception. Apple, Human Interface Guidelines: Widgets (https://developer.apple.com/design/human-interface-guidelines/widgets) for widgets periodically refreshing but not supporting continuous real-time updates, for "Widgets don't show real-time information", for animations of up to two seconds, and for the advice to let the system refresh dates and times to preserve update opportunities. Apple, Displaying dynamic dates (https://developer.apple.com/documentation/widgetkit/displaying-dynamic-dates) for the relative, offset and timer text styles, the time-interval progress view, and the countdown that continues while the extension is not running. Apple, Creating a widget extension (https://developer.apple.com/documentation/widgetkit/creating-a-widget-extension) for the requirement that the app be launched once after installation before its widget appears in the widget gallery. Apple, Updating widgets with WidgetKit push notifications (https://developer.apple.com/documentation/widgetkit/updating-widgets-with-widgetkit-push-notifications) for push updates also being budgeted and delivered opportunistically. Apple, SwiftUI views (https://developer.apple.com/documentation/widgetkit/swiftui-views) for widgets being able to use many but not all SwiftUI views. Apple Support, Use Low Power Mode to save battery life on your iPhone (https://support.apple.com/en-us/101604) for the list of what Low Power Mode changes, which ends with turning off Background App Refresh and does not mention widgets. Not confirmed, and labelled as such on the page: that Low Power Mode freezes or slows widget refreshes; that turning Background App Refresh off stops widget reloads; any battery cost figure for widgets, since Apple publishes a cause and no number; any memory limit for widget extensions; and whether a widget may run a continuous animation loop, where Apple describes only transitions of up to two seconds tied to data updates and publishes no statement either way about a self-driven loop. Restarting the phone is offered as a cheap thing to try, not as an Apple-documented remedy. The WWDC 2021 figure of one update every 15 to 30 minutes was left out in favour of the 15 to 60 minute range the current documentation gives.
Read next: why a widget cannot show a live web page