What a watch face actually does all day

In normal wear, Connect IQ wakes the active face once per minute, the face draws the screen, and everything sleeps again. That is the whole job, and it is deliberately cheap; Garmin designed the platform so a watch face cannot casually ruin the multi-week battery life the watch is sold on. When you raise your wrist, the face gets a short high-power window (this is when live seconds tick), then drops back to the once-a-minute rhythm.

So where do the horror stories come from? From the exceptions: things a face can do, or you can enable, that break out of that cheap rhythm.

The four real battery costs, ranked

CostWho controls itHow much it matters
Always-on displayYou, in watch settingsThe big one on AMOLED watches; applies to built-in faces too
Seconds always visibleYou, in face settings60 redraws per minute instead of 1; noticeable over a day
Careless drawing codeThe face developerLoading images or fonts on every redraw instead of once at start; the classic sin of hastily built faces
Heavy data habitsThe face developerPolling sensors and connections more often than the data changes

Notice that the top two are your settings, not the developer's code. That is the honest core of this topic: the most common "this face drains my watch" cases are really "I turned on always-on display and seconds at the same time I installed the face".

The one-day test

Skip the speculation. Charge the watch, run your Connect IQ face for a normal day, note the drain. Next day, same routine on a built-in Garmin face. If the difference is a few percent, the face is fine and your battery story lives elsewhere (firmware updates, GPS activities, a chatty notification day). If the difference is dramatic, you have your answer, and the developer deserves to hear it; a face that eats battery on your model is usually doing one of the two developer sins above, and both are fixable in an update.

How we build for battery, stated plainly

Our faces load every resource once at startup and never allocate while drawing, seconds default to wrist-raise only, and always-on modes draw a reduced layout within Garmin's low-power rules. We test drain against built-in faces on the same watch before shipping. That is not a promise of magic numbers, battery depends on your settings and your day, but it is why "runs like a built-in face" is the bar we aim at. A proper measured study across display types is on our roadmap, and when we publish it, the numbers will be on this site.

Frequently asked

Will deleting unused watch faces improve battery life?
No. Installed but inactive faces are just files in storage; only the active face runs. Deleting them frees space for new installs, which is useful on older watches, but changes nothing about battery.
Does showing seconds drain the battery?
Always-visible seconds force the face to redraw every second instead of once a minute, which costs real battery over a day. The common middle ground, and the default in our faces, is seconds on wrist raise: live for a few moments when you look, asleep otherwise.
Is always-on display the face’s fault?
No, it is a display-mode cost you chose in watch settings, and it applies to built-in faces too. On AMOLED watches always-on typically shortens battery life noticeably regardless of which face you run. A face can only decide how much it draws in that mode; it cannot make always-on free.
How do I check whether my watch face is the battery problem?
Switch to a built-in Garmin face for a full day and compare the drain. That single test separates "this face is hungry" from "something else changed" (a firmware update, a failing sensor, heavy notifications) better than any guesswork.
Are paid faces more battery-friendly than free ones?
Price says nothing about efficiency. What correlates with battery behavior is developer care: faces that are updated regularly, mention their memory or battery approach, and answer reviews tend to be built by people who also optimize the drawing code. Free or paid, look for signs of maintenance.

Last verified: 2026-07-18 · Connect IQ platform behavior from our own face development; drain comparisons on Fenix 8, built-in vs our faces